Documente Academic
Documente Profesional
Documente Cultură
Configuring Avaya IP Office and Avaya Communication Manager to Utilize Avaya Modular Messaging for Centralized Voicemail - Issue 1.0
Abstract
These Application Notes describe the steps necessary to configure Avaya IP Office, Avaya Communication Manager and Avaya Modular Messaging to provide a centralized voice messaging solution for users at remote locations. In the sample configuration, one remote site uses an Avaya IP Office, and another remote site uses an Avaya IP Office - Small Office Edition. Each remote site has an IP Trunk to Avaya Communication Manager at a central site. The Avaya Modular Messaging at the central site communicates with Avaya Communication Manager via an IP QSIG trunk to provide voicemail coverage for all sites. A Microsoft Exchange Server is integrated as a storage server with the Avaya Modular Messaging Application Server.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
1 of 41 MM-IPO.doc
1. Introduction
Avaya Modular Messaging can provide a centralized messaging solution for the enterprise customer. Figure 1 illustrates a configuration with smaller customer sites networked to a central site by an IP MPLS Wide Area Network (WAN). Each remote site has a T1 facility using framerelay protocol connected to the WAN. The Avaya IP Office IP 406 and Avaya IP Office - Small Office Edition handle calls at the remote sites, and a pair of Avaya S8710 Media Servers with a G650 Media Gateway handles calls at the central site. The Avaya Modular Messaging system is integrated with a Microsoft Exchange Server as its storage server. An IP QSIG trunk is established between the Avaya Modular Messaging Application Server and the C-LAN in the Avaya G650 Media Gateway, which is controlled by Avaya Communication Manager. Voice calls and messages are routed among these three sites via QSIG based IP trunks. These Application Notes provide detailed configurations for IP Office, Avaya Communication Manager, Avaya Modular Messaging as well as some required configurations for Microsoft Exchange Server to function as a storage server for the Avaya Modular Messaging Application Server. The network diagram shown below was used for these Application Notes.
Central Site
Avaya Modular Messaging ( MAS) Avaya 6211 Analog Telephone x222-0100 Avaya Phone Manager x222-0102 x222-0101 Avaya c360 Switch DNS Active Directory Server Avaya S8710 Media Servers Avaya G650 Media Gateway Microsoft Exchange Server 2003 Cisco 3825 IPO 406V2 Enterprise Edition Avaya 4621 IP Telephone
Ext: 22x-xxxx
IP Addresses: S8710-1: 30.1.1.1, S8710-2: 30.1.1.2 CLAN: 30.1.1.4, MedPro: 30.1.1.5 MAS: 30.1.1.19, MS Exchange: 30.1.1.10
Remote Site 1
Avaya 5410 Digital Avaya 6211 Telephone Analog Telephone Avaya Phone Manager x50001 x50002 x51001 Avaya C360 Switch Avaya 5610 IP Telephone x50004 Router
TM -A T3
MPLS WAN T1- FR
Cisco 2811
T1- FR
Ext: 5xxxx
Remote Site 1 IP Addresses: IP Office: LAN 1: 11.1.1.1 Gateway: 11.1.1.254 Cisco 2811: Fast Ethernet 1: 11.1.1.254 Serial 0: 1.1.1.1
Remote Site 2
Avaya 6211 Analog Telephone x4003 Avaya C360 Switch Avaya 5410 Digital Telephone x4002
Ext: 4xxx
Remote Site 2 IP Addresses: IP Small Office: LAN 1: 44.1.1.1 Gateway: 44.1.1.254 Cisco 2811: Fast Ethernet 1: 44.1.1.254 Serial 0: 4.1.1.1
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
2 of 41 MM-IPO.doc
3. IP Office Configuration
This section describes the required configuration for IP Office to utilize Avaya Modular Messaging for centralized voicemail services. Both IP Office (remote site 1) and IP Office-Small Office Edition (remote site 2) have an IP connection to Avaya Communication Manager (central site) via an MPLS-enabled IP network. Both remote sites use a T1 frame relay circuit to connect to an MPLS WAN edge router. Calls within each location use the G.711 codec and calls between locations use the G.729 codec to conserve bandwidth on the WAN links. Messaging features, including voice coverage, call me, and find me, will be configured for IP Office users. Since the configuration for the IP Office - Small Office Edition is similar to the IP Office, only the IP Office configuration is included in these Application Notes. Note: Both the IP Office 406 and the IP Office - Small Office Servers are configured with a serial port license key.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
3 of 41 MM-IPO.doc
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
4 of 41 MM-IPO.doc
Click the System tab and ensure that the Licence Server IP Address field is set to the IP Office IP Address of LAN1, since the needed license key is attached directly to the IP Office serial port. Alternatively, if the configuration uses a separate License Server PC, then enter that PCs IP address in this field. Both configurations are supported. Enter a TFTP Server IP Address, which is 11.1.1.120 in the sample configuration. Default values may be retained for other fields. Click OK.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
5 of 41 MM-IPO.doc
Configure a default IP route to forward IP traffic to the next routers IP address over LAN1. From the IP Office configuration tree, Click on IP Route and right click to select new. Leave IP Address and IP Mask fields blank, which means for any network, use the default gateway defined below. Enter 11.1.1.254 as Gateway IP Address. Selection LAN1 from the Destination drop-down. Click OK.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
6 of 41 MM-IPO.doc
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
7 of 41 MM-IPO.doc
Click on the ShortCodes tab Right click to select Add for creating a ShortCode as shown below. Enter 22xxxxx as Short Code. Retain default values for other fields as shown below. Click OK.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
8 of 41 MM-IPO.doc
Click on the VoIP tab and enter the Avaya Communication Manager C-LAN IP address as the Gateway IP Address. Select QSig as the signaling protocol from the H450 Support drop-down (Note: QSIG protocol is required to work with Avaya Modular Messaging system). Set the check boxes as shown. Ensure that the Enable Faststart, Out of Band DTMF and Allow Direct Media Path options are checked. The Compression Mode can be left at Automatic Selection or set to the first choice of the corresponding Avaya Communication Manager ip-codec-set form entry. Click OK.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
9 of 41 MM-IPO.doc
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
10 of 41 MM-IPO.doc
Click on the ShortCodes tab Right click to select Add. Enter 4xxx as Short Code. Retain default values for other fields as shown below and Click OK.
Click on the VoIP tab and enter the Small Offices IP address 44.1.1.1 as the Gateway IP Address. Select H450 as the signaling protocol from the H450 Support drop-down. Ensure that the Enable Faststart, Out of Band DTMF and Allow Direct Media Path options are checked, and click OK.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
11 of 41 MM-IPO.doc
To use voicemail service, each user must have Voicemail On checked on the users form. For steps to add a user and extension on IP Office, refer to the references listed in Section 8. The following example shows how to configure voicemail for user Extn50004. Click Users and double click user Extn50004. Check the box Voicemail On. Other entries do not apply to this configuration. Click OK.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
12 of 41 MM-IPO.doc
Save any changes made to the IP Office by choosing Save from the File Menu and following the presented screens.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
13 of 41 MM-IPO.doc
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
14 of 41 MM-IPO.doc
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
15 of 41 MM-IPO.doc
display system-parameters customer-options OPTIONAL FEATURES IP PORT CAPACITIES Maximum Administered H.323 Trunks: Maximum Concurrently Registered IP Stations: Maximum Administered Remote Office Trunks: Maximum Concurrently Registered Remote Office Stations: Maximum Concurrently Registered IP eCons: Max Concur Registered Unauthenticated H.323 Stations: Maximum Video Capable H.323 Stations: Maximum Video Capable IP Softphones: Maximum Administered SIP Trunks: Maximum Number of DS1 Boards with Echo Cancellation: Maximum TN2501 VAL Boards: Maximum G250/G350/G700 VAL Sources: Maximum TN2602 Boards with 80 VoIP Channels: Maximum TN2602 Boards with 320 VoIP Channels: Maximum Number of Expanded Meet-me Conference Ports: Maximum G700/G350 VAL Sources: 200 50 0 0 0 0 0 0 10 0 1 10 5 5 50 0
Page
2 of
10
USED 42 27 0 0 0 0 0 0 0 0 1 0 1 0 0 0
y IP Stations? y Internet Protocol (IP) PNC? y ISDN Feature Plus? y ISDN Network Call Redirection? n ISDN-BRI Trunks? n ISDN-PRI? y Local Survivable Processor? n Malicious Call Trace? n Media Encryption Over IP? n Mode Code for Centralized Voice Mail? n n Multifrequency Signaling? n Multimedia Appl. Server Interface (MASI)? y Multimedia Call Handling (Basic)? y Multimedia Call Handling (Enhanced)? y
y n y y y y n n y n y n n n
IP Attendant Consoles? y
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
16 of 41 MM-IPO.doc
On page 5, ensure that Private Networking and Uniform Dialing Plan are enabled.
display system-parameters customer-options OPTIONAL FEATURES Multinational Locations? n Multiple Level Precedence & Preemption? n Multiple Locations? n Personal Station Access (PSA)? Posted Messages? PNC Duplication? Port Network Support? y n n y Page 5 of 10
Station and Trunk MSP? y Station as Virtual Extension? n System Management Data Transfer? Tenant Partitioning? Terminal Trans. Init. (TTI)? Time of Day Routing? Uniform Dialing Plan? Usage Allocation Enhancements? TN2501 VAL Maximum Capacity? n n n n y y y
Processor and System MSP? n Private Networking? y Processor Ethernet? n Remote Office? n Restrict Call Forward Off Net? y Secondary Data Module? y
On page 8, ensure that the QSIG Basic Call Setup and Basic Supplementary Services are enabled.
display system-parameters customer-options QSIG OPTIONAL FEATURES Basic Call Setup? Basic Supplementary Services? Centralized Attendant? Interworking with DCS? Supplementary Services with Rerouting? Transfer into QSIG Voice Mail? Value-Added (VALU)? y y n n y n y Page 8 of 10
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
17 of 41 MM-IPO.doc
On page 16, ensure that Direct IP-IP Audio Connections is set to y to allow configuration of this item on the signaling group to IP Office.
display system-parameters features FEATURE-RELATED SYSTEM PARAMETERS AUTOMATIC EXCLUSION PARAMETERS Automatic Exclusion by COS? n Recall Rotary Digit: 2 Duration of Call Timer Display (seconds): 3 WIRELESS PARAMETERS Radio Controllers with Download Server Permission (enter board location) 1: 2: 3: 4: 5: IP PARAMETERS Direct IP-IP Audio Connections? IP Audio Hairpinning? RUSSIAN MULTI-FREQUENCY PACKET SIGNALING Re-try? T2 (Backward Signal) Activation Timer (secs): y n n 20 Page 16 of 17
Use the command change public-unknown-numbering to configure calling line identification as shown below.
SZ; Reviewed: SPOC 8/21/2006 Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved. 18 of 41 MM-IPO.doc
change public-unknown-numbering NUMBERING - PUBLIC/UNKNOWN FORMAT Total Ext Ext Trk CPN CPN Ext Ext Trk Len Code Grp(s) Prefix Len Len Code Grp(s) 4 4 5 5 7 222 4 5 7
Page
1 of
CPN Prefix
Use the command change feature-access-codes to enter the AAR access code 8.
change feature-access-codes Page 1 of FEATURE ACCESS CODE (FAC) Abbreviated Dialing List1 Access Code: Abbreviated Dialing List2 Access Code: Abbreviated Dialing List3 Access Code: Abbreviated Dial - Prgm Group List Access Code: Announcement Access Code: Answer Back Access Code: Attendant Access Code: Auto Alternate Routing (AAR) Access Code: 8 Auto Route Selection (ARS) - Access Code 1: 9 Access Code 2: 5
Use the command change uniform-dialplan 2 to configure the matching pattern. The first entry shown below is used for routing calls to Modular Messaging (5-digit numbers beginning with 2000) and the other two entries are used for routing calls to remote sites 1 and 2. Submit the form.
change uniform-dialplan 2 UNIFORM DIAL PLAN TABLE Page 1 of 2
Percent Full: 0 Matching Insert Node Pattern Len Del Digits Net Conv Num 2000 5 0 aar n 4 4 0 aar n 5 5 0 aar n Matching Insert Node Pattern Len Del Digits Net Conv Num n n n
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
19 of 41 MM-IPO.doc
n n
Enter qsig-mwi for Message Center Enter 20001 as Voice Mail Number. This is the number that Modular Messaging will receive when users dial the hunt group extension 20000. Enter 8 (the AAR Access Code) for Routing Digits.
Page HUNT GROUP LWC Reception: spe AUDIX Name: 2 of 60
add hunt-group 10
Message Center: Send Reroute Request: Voice Mail Number: Routing Digits (e.g. AAR/ARS Access Code):
qsig-mwi y 20001 8
Provide Ringback? Y
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
20 of 41 MM-IPO.doc
DIFFSERV/TOS PARAMETERS Call Control PHB Value: 34 Audio PHB Value: 46 802.1P/Q PARAMETERS Call Control 802.1p Priority: 7 Audio 802.1p Priority: 6 H.323 IP ENDPOINTS H.323 Link Bounce Recovery? n Idle Traffic Interval (sec): 20 Keep-Alive Interval (sec): 5 Keep-Alive Count: 5
On page 3, ensure that codec set 2 is the appropriate codec set for all calls between region 1 and 2. In this configuration, the C-LAN is in region 1. WAN-BW limits can be set here if required.
change ip-network-region 2 Inter Network Region Connection Management src rgn 2 2 2 2 dst rgn 1 2 3 4 codec set 2 2 direct WAN y Dynamic CAC Gateway Page 3 of 19
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
21 of 41 MM-IPO.doc
Type change ip-codec-set 2 to configure the IP Codec Set for the IP Office ip-network-region. G.729A was used in this example to conserve bandwidth (compared with G.711mu). Make sure that Media Encryption is set to none.
change ip-codec-set 2 IP Codec Set Codec Set: 2 Audio Codec 1: G.729A 2: 3: 4: 5: 6: 7: Silence Suppression n Frames Per Pkt 2 Packet Size(ms) 20 Page 1 of 2
IP Address . . . . . . . . . . . . . . . . . .
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
22 of 41 MM-IPO.doc
add trunk-group 11 Group Type: isdn TRUNK PARAMETERS Codeset to Send Display: 6 Supplementary Service Protocol: b
Page
2 of
21
Codeset to Send National IEs: 6 Charge Advice: none Digit Handling (in/out): enbloc/overlap QSIG Value-Added? y Digital Loss Group: 18 Format: unk-unk
Incoming Calling Number - Delete: Disconnect Supervision - In? y Answer Supervision Timeout: 0
Insert:
Out? n
Page Measured: Internal Alert? Data Restriction? Send Name: Hop Dgt? Format: unknown UUI none n n y n
3 of
21
Maintenance Tests? NCA-TSC Trunk Member: Send Calling Number: Send EMU Visitor CPN?
y 1 y y
IE Treatment: service-provider n n n y n
Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y
Replace Restricted Numbers? Replace Unavailable Numbers? Send Called/Busy/Connected Number: Hold/Unhold Notifications? Modify Tandem Calling Number?
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
23 of 41 MM-IPO.doc
Type add signaling-group 11 to create an H323 signaling group to the IP Office. Ensure that the items in bold are set as shown.
add signaling-group 11 SIGNALING Group Number: 11 Group Type: Remote Office? SBS? IP Video? Trunk Group for Channel Selection: Supplementary Service Protocol: T303 Timer(sec): Near-end Node Name: C-LAN Near-end Listen Port: 1720 LRQ Required? n RRQ Required? n Media Encryption? n DTMF over IP: out-of-band GROUP h.323 n n n 11 b 10 Page 1 of 1
Max number of NCA TSC: 20 Max number of CA TSC: 20 Trunk Group for NCA TSC: 11 Network Call Transfer? n
Far-end Node Name: IPO-406 Far-end Listen Port: 1720 Far-end Network Region: 2 Calls Share IP Signaling Connection? n Bypass If IP Threshold Exceeded? n H.235 Annex H Required? n Direct IP-IP Audio Connections? y IP Audio Hairpinning? n Interworking Message: PROGress DCP/Analog Bearer Capability: 3.1kHzchange
Type change trunk-group 11 again. On page 5, configure the number of channels desired for the trunk group by typing IP in the Port field, and the signaling group number, 11, in the Sig Grp field for each channel. Submit the form. When viewed via a change command, page 5 should appear similar to the screen below.
change trunk-group 11 Page TRUNK GROUP Administered Members (min/max): Total Administered Members: 5 of 1/20 20 21
Port Name Night Sig Grp 1: T00032 11 2: T00033 11 3: T00034 11 4: T00035 11 5: T00036 11 6: T00037 11 7: T00062 11 8: T00063 11 9: T00064 11 10: T00065 11
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
24 of 41 MM-IPO.doc
add trunk-group 10 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Service Type:
Page
1 of
21
10 Group Type: isdn CDR Reports: y To-Modular Messaging COR: 1 TN: 1 TAC: 110 two-way Outgoing Display? n Carrier Medium: H.323 y Busy Threshold: 255 Night Service: 0 tie Auth Code? n Member Assignment Method: manual Page 2 of 21
add trunk-group 10 Group Type: isdn TRUNK PARAMETERS Codeset to Send Display: 6 Supplementary Service Protocol: b
Codeset to Send National IEs: 6 Charge Advice: none Digit Handling (in/out): enbloc/overlap QSIG Value-Added? y Digital Loss Group: 18 Format: unk-unk
Incoming Calling Number - Delete: Disconnect Supervision - In? y Answer Supervision Timeout: 0
Insert:
Out? n
Page Measured: Internal Alert? Data Restriction? Send Name: Hop Dgt? Format: unknown UUI none n n y n
3 of
21
Maintenance Tests? NCA-TSC Trunk Member: Send Calling Number: Send EMU Visitor CPN?
y 10 y y
IE Treatment: service-provider n n n y n
Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y
Replace Restricted Numbers? Replace Unavailable Numbers? Send Called/Busy/Connected Number: Hold/Unhold Notifications? Modify Tandem Calling Number?
Incoming Calling Number - Delete: Insert: Bit Rate: 1200 Synchronization: async Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0
Type add signaling-group 10. Ensure that the items in bold are set as shown. Note that the Supplementary Service Protocol b is used for QSIG and the Far-end Node Name exchange-mas is the name of the Modular Messaging Application Server (MAS).
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
25 of 41 MM-IPO.doc
add signaling-group 10 SIGNALING GROUP Group Number: 10 Group Type: Remote Office? SBS? IP Video? Trunk Group for Channel Selection: Supplementary Service Protocol: T303 Timer(sec): h.323 n n n 10 b 10
Page
1 of
Max number of NCA TSC: 20 Max number of CA TSC: 20 Trunk Group for NCA TSC: 10 Network Call Transfer? n
Near-end Node Name: C-LAN Near-end Listen Port: 1720 LRQ Required? n RRQ Required? n Media Encryption? n DTMF over IP: out-of-band
Far-end Node Name: exchange-mas Far-end Listen Port: 1720 Far-end Network Region: 1 Calls Share IP Signaling Connection? n Bypass If IP Threshold Exceeded? n H.235 Annex H Required? n Direct IP-IP Audio Connections? n IP Audio Hairpinning? n Interworking Message: PROGress DCP/Analog Bearer Capability: 3.1kHz
Type change trunk-group 10 again to add members to the group. On page 5, enter IP in the Port field, and the signaling group number, 10, in the Sig Grp field for each channel to be used for transport and message waiting updates. Submit the form. When viewed via a change command, page 5 should appear similar to the screen below.
change trunk-group 10 Page TRUNK GROUP Administered Members (min/max): Total Administered Members: 5 of 1/23 23 21
Port Name Night Sig Grp 1: T00038 10 2: T00039 10 3: T00040 10 4: T00041 10 5: T00042 10 6: T00043 10 7: T00044 10 8: T00045 10 9: T00046 10 10: T00047 10
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
26 of 41 MM-IPO.doc
Page
1 of
2 1
Percent Full: Dialed String 2000 4 5 Total Min Max 5 5 4 4 5 5 Route Pattern 10 2 11 Call Type aar aar aar Node Num ANI Reqd n n n
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
27 of 41 MM-IPO.doc
IXC
No. Numbering LAR Dgts Format Subaddress unk-unk none none none
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
28 of 41 MM-IPO.doc
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
29 of 41 MM-IPO.doc
5.2. PBXs
Select the Voice Mail Domain and expand PBXs (under retail-vdm). Select Avaya MV (IP H323). Select the Outgoing Call tab and set the Origin Number to match the pilot number sent toward the Modular Messaging system for coverage and direct calls. Select Local for Number Type. Select Private for Number Plan. Select the Layer1 Protocol to match the Avaya Communication Manager codec set configuration. In the sample network, G.711 u-law was used. Click OK. MAS will prompt to restart the services. Do not restart the server until all configuration is completed.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
30 of 41 MM-IPO.doc
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
31 of 41 MM-IPO.doc
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
32 of 41 MM-IPO.doc
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
33 of 41 MM-IPO.doc
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
34 of 41 MM-IPO.doc
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
35 of 41 MM-IPO.doc
Double click on the user test. Click the Modular Messaging tab as shown below. Check the box Enable Modular Messaging. Select retail-vdm for Voice mail domain. Enter the extension 51001 for extension number (Note this is the 5 digit extension from IP Office). Enter the mail box number 2251001 (Note this is the 7 digit mailbox number in Modular Messaging). Enter 2251001 as Numeric address. Enter password for mailbox access (TUI password).
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
36 of 41 MM-IPO.doc
To configure users other properties, Click the Advanced button. Select an appropriate Class of service. Class of service 1 was used in this example. Check the appropriate boxes to enable these capabilities for this user. Note that the Allow intercom paging is grayed out because it is not enabled on MAS yet.
To access other available capabilities, scroll down. Check the other boxes desired. Click OK
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
37 of 41 MM-IPO.doc
To configure subscriber options, Click the button User options. Click the Assistant tab. Check appropriate boxes for options. In this example, all options are selected. Note the Messaging Waiting Indicator must be checked in order for the phone to light its lamp. The Rule description box displays the default rules for MWI. The default rule was retained in this example. If needed, click the links shown in blue to modify the rules. If needed, click the Help tab at the bottom right of the form to get online configuration assistance. Click OK when done.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
38 of 41 MM-IPO.doc
6. Verification Steps
The following steps are used to verify the configuration. 1. From an IP Office extension 51001, dial *17 and verify Modular Messaging prompts for the password of user test. 2. Make a call from IP Office extension 51001 to another IP Office extension 50003. Do not answer the call. Verify the call goes to coverage and that Modular Messaging plays the proper mailbox greeting. 3. Leave a message in the users mailbox and verify that the appropriate message-waiting indicator is lit. 4. From the extension 2220102, dial Modular Messaging pilot # 20000 and verify that Modular Messaging prompts for the password to user 2220102. 5. Make a call from Avaya Communication Manager extension 2220100 to the IP Office Small Office extension 4001. Leave the message for extension 4001 and verify that the message-waiting indicator is turned on. 6. From the extension 4001, Dial *17 to log into mailbox and verify that a new message is in mailbox. Play the message and verify that message is from station 2220100. Verify that the MWI is turned off after deleting all new messages. 7. From the extension 4003, Make a call to the Phone Manager extension 50001 and leave a message. Verify that a new voicemail icon is shown in the Phone Managers desktop. Double click the voicemail icon to play the message and verify that the message is from station 4003. Delete the message and verify that the voicemail icon disappears from the desktop.
7. Conclusion
These Application Notes illustrate how Avaya Modular Messaging can provide a centralized voice messaging solution to IP Office users located at multiple locations.
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
39 of 41 MM-IPO.doc
8. Additional References
The following documents can be found at http://support.avaya.com/. [1] Modular Messaging for Microsoft Exchange Release 3 Installation and Upgrades, Issue: January 2006 [2] Modular Messaging Release 3 Subscriber Options User Guide, Issue: January 2006 The following Application Notes can be found at http://www.avaya.com/. [3] Configuring a QSIG Centralized Messaging Solution using Avaya Modular Messaging and Avaya Communication Manager Issue 1.0 [4] Configuring Avaya Communication Manager and Avaya Modular Messaging for Voice Mail service to Sites Using Avaya Media gateways with Local Survivable Processors Issue 1.0 [5] Configuring a QSIG Centralized Messaging Solution using Avaya Modular Messaging and Avaya Communication Manager Issue 1.0
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
40 of 41 MM-IPO.doc
Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please e-mail any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at interoplabnotes@list.avaya.com
Solution & Interoperability Test Lab Application Notes 2006 Avaya Inc. All Rights Reserved.
41 of 41 MM-IPO.doc