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.
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 frame-relay 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.
2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided:
Equipment Software Avaya IP Office IP406 R3.1 (65) Avaya IP Office - Small Office Edition R3.1 (65) Avaya S8710 Media Server with G650 Media Gateway
Avaya Communication Manager R3.1.1 (R013x.01.1.628.7)
Avaya Modular Messaging Application Server R3.0 Avaya 4621SW IP Telephone R2.3 Avaya 5610SW IP Telephone R2.2 Avaya 5410 Digital Telephone 4.3.10 Avaya Phone Manager V3.1.12 Microsoft Exchange Server Version 2003 Microsoft 2003 Advanced Server with Active Directory and DNS
Server 2003 Enterprise Edition with Service Pack 1
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.
3.1. Configure IP Address and Default Gateway to Interface LAN 1 From a PC with the IP Office Manager installed, open the IP Office for configuration. Double-click the System configuration tree item and select the LAN1 tab as shown below.
• Enter IP address 11.1.1.1 in IP Address field. • Enter 255.255.255.0 in IP Mask field. • Click Server to enable the IP Office as a DHCP Server. In the sample configuration, the
value 200 was entered in the field Number Of DHCP IP Addresses. • Click OK.
• 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 PC’s 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.
Configure a default IP route to forward IP traffic to the next router’s 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.
3.2. Verify Audix Voicemail License Click the IP Office License configuration tree item and ensure that the AUDIX Voicemail license has been entered. If not, right click to new, enter the license key and click OK. The license Status will not show Valid until the configuration has been updated. To update the configuration, click File Save to save the configuration and reboot the IP Office. The screen below shows that the AUDIX Voicemail license status is valid.
3.3. Configure Line (IP Trunk) IP Office uses the line form to configure IP trunks. Two lines are needed in this configuration, one for the IP trunk to Avaya Communication Manager at the central site, and one for the IP Trunk to the IP Office - Small Office site. The line to the central site also serves as the path for Avaya Modular Messaging access.
3.3.1. Line to Avaya Communication Manager Use the following steps to configure a line to Avaya Communication Manager.
• Click the Line item from the IP Office configuration tree. • Right click to select new. • From the Line tab, enter the desired number of channels and unique Incoming and
Outgoing Group IDs. Line 20 is used in this example. • Click OK.
• 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.
• 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.
3.3.2. Line to Remote Site 2 Follow the steps in section 3.3.1 to configure a line to remote site 2 (IP Office - Small Office site).
• Click the Line item from the IP Office configuration tree. • Right click to select new. • From the Line tab, enter the desired number of channels and unique Incoming and
Outgoing Group IDs. Line 40 is used in this example. • Click OK.
• 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 Office’s 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
3.4. Configure Voicemail for Avaya Modular Messaging Use the following steps to configure Avaya IP Office voicemail for Avaya Modular Messaging.
• From the System Configuration screen, click on the Voicemail tab and set the Voicemail Type to Audix.
• Enter 20 in the Voicemail Destination to use this line for voicemail (Note: the Line group 20 is created in Section 3.3).
• Enter 20000 as Audix UDP Number. This is the Hunt Group number created in the Avaya Communication Manager for the Modular Messaging System.
• Click OK.
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.
Save any changes made to the IP Office by choosing Save from the File Menu and following the presented screens.
3.5. Configure Short Code IP Office uses “short codes” to route calls to different destinations. Three short code are used in this configuration.
3.5.1. Short Code for Voice Mail IP Office has a default short code *17 for voice mail. These Application Notes will use this short code for Modular Messaging access. Use the following steps to verify the short code settings.
• Double click short code *17 from the IP Office configuration tree. • Ensure that the ?U is used for telephone number. • Ensure that the VoicemailCollect is in the Feature field. • Leave the default Line Group ID 0 as shown. The VoicemailCollect feature will use line
20 configured in the Voicemail Destination field as shown in Section 3.4. • Click OK.
3.5.2. Short Code for Central Site Right click in the short code screen and select new to add a new short code.
• Enter 22N to match the called number starting with 22 and 7 digits in length. • Enter 20 for Line Group ID (as defined in Section 3.3.1). • Select Dial for Feature. • Click OK.
3.5.3. Short Code for Remote Site 2 Right click in the short code screen and select new to add a new short code for remote site 2.
• Enter 4N to match the called number starting with 4 and 4 digits in length. • Enter 40 for Line Group ID (as defined in Section 3.3.2). • Select Dial for Feature. • Click OK.
4. Configure Avaya Communication Manager This section describes the configuration of the Avaya S8710 Media Server with G650 Media Gateway, focusing on those aspects that are required to support centralized messaging for the IP Office. Native Avaya Communication Manager interfaces have been used to describe the configuration. These administration screens may be referred to as the SAT (System Access Terminal). It is assumed that the appropriate license files have been installed on all products, and that login and password credentials for all products are available to the reader.
4.1. Verify System Wide Parameters
4.1.1. Customer-options Use the command display system-parameters customer-options to verify that the customer options are set correctly. On page 2, ensure that the Maximum Administered H.323 trunks capacity is sufficient for the channels to the IP Office that will be configured.
display system-parameters customer-options Page 2 of 10 OPTIONAL FEATURES IP PORT CAPACITIES USED Maximum Administered H.323 Trunks: 200 42 Maximum Concurrently Registered IP Stations: 50 27 Maximum Administered Remote Office Trunks: 0 0 Maximum Concurrently Registered Remote Office Stations: 0 0 Maximum Concurrently Registered IP eCons: 0 0 Max Concur Registered Unauthenticated H.323 Stations: 0 0 Maximum Video Capable H.323 Stations: 0 0 Maximum Video Capable IP Softphones: 0 0 Maximum Administered SIP Trunks: 10 0 Maximum Number of DS1 Boards with Echo Cancellation: 0 0 Maximum TN2501 VAL Boards: 1 1 Maximum G250/G350/G700 VAL Sources: 10 0 Maximum TN2602 Boards with 80 VoIP Channels: 5 1 Maximum TN2602 Boards with 320 VoIP Channels: 5 0 Maximum Number of Expanded Meet-me Conference Ports: 50 0 Maximum G700/G350 VAL Sources: 0 0
On page 4, ensure that ISDN-PRI and IP Trunks are enabled. display system-parameters customer-options Page 4 of 10 OPTIONAL FEATURES Emergency Access to Attendant? y IP Stations? y Enable ‘dadmin’ Login? y Internet Protocol (IP) PNC? n Enhanced Conferencing? y ISDN Feature Plus? y Enhanced EC500? y ISDN Network Call Redirection? y Enterprise Survivable Server? n ISDN-BRI Trunks? y Enterprise Wide Licensing? n ISDN-PRI? y ESS Administration? y Local Survivable Processor? n Extended Cvg/Fwd Admin? n Malicious Call Trace? n External Device Alarm Admin? n Media Encryption Over IP? y Five Port Networks Max Per MCC? n Mode Code for Centralized Voice Mail? n Flexible Billing? n Forced Entry of Account Codes? n Multifrequency Signaling? y Global Call Classification? n Multimedia Appl. Server Interface (MASI)? n Hospitality (Basic)? y Multimedia Call Handling (Basic)? n Hospitality (G3V3 Enhancements)? y Multimedia Call Handling (Enhanced)? n IP Trunks? y IP Attendant Consoles? y
On page 5, ensure that Private Networking and Uniform Dialing Plan are enabled. display system-parameters customer-options Page 5 of 10 OPTIONAL FEATURES Multinational Locations? n Station and Trunk MSP? y Multiple Level Precedence & Preemption? n Station as Virtual Extension? n Multiple Locations? n System Management Data Transfer? n Personal Station Access (PSA)? y Tenant Partitioning? n Posted Messages? n Terminal Trans. Init. (TTI)? n PNC Duplication? n Time of Day Routing? n Port Network Support? y Uniform Dialing Plan? y Usage Allocation Enhancements? y Processor and System MSP? n TN2501 VAL Maximum Capacity? y Private Networking? y Processor Ethernet? n Wideband Switching? n Wireless? 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 Page 8 of 10 QSIG OPTIONAL FEATURES Basic Call Setup? y Basic Supplementary Services? y Centralized Attendant? n Interworking with DCS? n Supplementary Services with Rerouting? y Transfer into QSIG Voice Mail? n Value-Added (VALU)? y
4.1.2. System-parameters Features Use the command display system-parameters features to verify that QSIG features are configured. On page 8, ensure that there is a valid dial plan extension entered in the QSIG TSC Extension field, and the number of digits for MWI is set to 7. display system-parameters features Page 8 of 17 FEATURE-RELATED SYSTEM PARAMETERS ISDN PARAMETERS Send Non-ISDN Trunk Group Name as Connected Name? n Display Connected Name/Number for ISDN DCS Calls? y Send ISDN Trunk Group Name on Tandem Calls? n QSIG TSC Extension: 2223333 MWI - Number of Digits Per Voice Mail Subscriber: 7
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 Page 16 of 17 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? y IP Audio Hairpinning? n RUSSIAN MULTI-FREQUENCY PACKET SIGNALING Re-try? n T2 (Backward Signal) Activation Timer (secs): 20
4.1.3. Dialplan and Feature Access Code Use command display dialplan analysis to observe the extensions used for the configuration. These include the IP Office extension range and the extension used to access Modular Messaging. display dialplan analysis Page 1 of 12 DIAL PLAN ANALYSIS TABLE Percent Full: 1 Dialed Total Call Dialed Total Call Dialed Total Call String Length Type String Length Type String Length Type 1 3 dac 2 7 ext 2000 5 ext 4 4 ext 5 5 ext 8 1 fac 9 1 fac * 3 fac
Use the command change public-unknown-numbering to configure calling line identification as shown below.
change public-unknown-numbering Page 1 of 2 NUMBERING - PUBLIC/UNKNOWN FORMAT Total Total Ext Ext Trk CPN CPN Ext Ext Trk CPN CPN Len Code Grp(s) Prefix Len Len Code Grp(s) Prefix Len 4 4 4 5 5 5 7 222 7
Use the command change feature-access-codes to enter the AAR access code 8. change feature-access-codes Page 1 of 5 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:
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 Page 1 of 2 UNIFORM DIAL PLAN TABLE Percent Full: 0 Matching Insert Node Matching Insert Node Pattern Len Del Digits Net Conv Num Pattern Len Del Digits Net Conv Num 2000 5 0 aar n n 4 4 0 aar n n 5 5 0 aar n n
4.2. Configure Hunt Group Use the following steps to configure a Hunt Group to route calls to Modular Messaging.
• Type add hunt-group 10 to create a voicemail hunt group. • Enter extension 20000 as the hunt group extension. This extension is a voicemail pilot
number that a user can dial to access voicemail. • Enter ucd-mia as Group Type. Go to page 2.
add hunt-group 10 Page 1 of 60 HUNT GROUP Group Number: 10 ACD? n Group Name: Modular Messaging Queue? n Group Extension: 20000 Vector? n Group Type: ucd-mia Coverage Path: TN: 1 Night Service Destination: COR: 1 MM Early Answer? n Security Code: Local Agent Preference? n ISDN/SIP Caller Display:
• 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.
add hunt-group 10 Page 2 of 60 HUNT GROUP LWC Reception: spe AUDIX Name: Message Center: qsig-mwi Send Reroute Request: y Voice Mail Number: 20001 Routing Digits (e.g. AAR/ARS Access Code): 8 Provide Ringback? Y
4.3. Configure IP-Network-Region and IP Codec IP network region 2 will be created for IP Office. Type change ip-network-region 2 to configure the network region to be associated with IP Office. The UDP Port parameters must be set consistently with any networking requirements. For example, some routers will require RTP traffic to be within a range to be recognized for header compression. Set the QOS parameters consistently with the overall Quality Of Service plan. change ip-network-region 2 Page 1 of 19 IP NETWORK REGION Region: 2 Location: Home Domain: Name: ipo Intra-region IP-IP Direct Audio: yes AUDIO PARAMETERS Inter-region IP-IP Direct Audio: yes Codec Set: 2 IP Audio Hairpinning? n UDP Port Min: 26000 UDP Port Max: 65535 RTCP Reporting Enabled? y RTCP MONITOR SERVER PARAMETERS DIFFSERV/TOS PARAMETERS Use Default Server Parameters? y Call Control PHB Value: 34 Audio PHB Value: 46 802.1P/Q PARAMETERS Call Control 802.1p Priority: 7 Audio 802.1p Priority: 6 AUDIO RESOURCE RESERVATION PARAMETERS H.323 IP ENDPOINTS RSVP Enabled? n 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 Page 3 of 19 Inter Network Region Connection Management src dst codec direct Dynamic CAC rgn rgn set WAN WAN-BW-limits Intervening-regions Gateway 2 1 2 y :NoLimit 2 2 2 2 3 2 4
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 Page 1 of 2 IP Codec Set Codec Set: 2 Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.729A n 2 20 2: 3: 4: 5: 6: 7: Media Encryption 1: none 2: 3:
4.4. Configure Node-names, Signaling Group, and IP Trunk Group Before configuring the signaling group, node-names and IP addresses for the C-LAN, MedPro, far end switches (IP Office and IP Office - Small Office) and Modular Messaging Application Server (MAS) must be configured. Type change node-names ip and enter the appropriate information, as shown below. change node-names ip Page 1 IP NODE NAMES Name IP Address Name IP Address C-LAN 30 .1 .1 .4 . . . Medpro 30 .1 .1 .5 . . . IPO-406 11 .1 .1 .1 . . . Small-office 44 .1 .1 .1 . . . default 0 .0 .0 .0 . . . exchange-mas 30 .1 .1 .19 . . .
4.4.1. H.323 Signaling Group and IP Trunk to Remote Site 1 Type add trunk-group 11 to administer a trunk group to the IP Office. Ensure that the items in bold are set as shown. Set the Supplementary Service Protocol to b for QSIG and Incoming calling number to unk-unk (unknown-unknown). Multiple pages of the trunk group screen are included in the same figure below for brevity in illustration. add trunk-group 11 Page 1 of 21 TRUNK GROUP Group Number: 11 Group Type: isdn CDR Reports: y Group Name: To Retail-S1 COR: 1 TN: 1 TAC: 101 Direction: two-way Outgoing Display? n Carrier Medium: H.323 Dial Access? y Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n Member Assignment Method: manual add trunk-group 11 Page 2 of 21 Group Type: isdn TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Charge Advice: none Supplementary Service Protocol: b Digit Handling (in/out): enbloc/overlap QSIG Value-Added? y Digital Loss Group: 18 Incoming Calling Number - Delete: Insert: Format: unk-unk Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 add trunk-group 11 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: 1 Send Name: y Send Calling Number: y Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? y Suppress # Outpulsing? n Format: unknown UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Called/Busy/Connected Number: n Hold/Unhold Notifications? y Send UUI IE? y Modify Tandem Calling Number? n Send UCID? n Send Codeset 6/7 LAI IE? y
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 Page 1 of 1 SIGNALING GROUP Group Number: 11 Group Type: h.323 Remote Office? n Max number of NCA TSC: 20 SBS? n Max number of CA TSC: 20 IP Video? n Trunk Group for NCA TSC: 11 Trunk Group for Channel Selection: 11 Supplementary Service Protocol: b Network Call Transfer? n T303 Timer(sec): 10 Near-end Node Name: C-LAN Far-end Node Name: IPO-406 Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 2 LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n Media Encryption? n Bypass If IP Threshold Exceeded? n H.235 Annex H Required? n DTMF over IP: out-of-band 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 5 of 21 TRUNK GROUP Administered Members (min/max): 1/20 GROUP MEMBER ASSIGNMENTS Total Administered Members: 20 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 ……………………………………………………………………………………………………………………………………………………………………………
4.4.2. Signaling and Trunk Group to the Modular Messaging Use the following steps to administer a trunk group and a signaling group to Modular Messaging. Type add trunk-group 10 to administer a trunk group. Ensure that the items in bold are set as shown. Multiple pages of the trunk group screen are included in the same figure below for brevity in illustration.
add trunk-group 10 Page 1 of 21 TRUNK GROUP Group Number: 10 Group Type: isdn CDR Reports: y Group Name: To-Modular Messaging COR: 1 TN: 1 TAC: 110 Direction: two-way Outgoing Display? n Carrier Medium: H.323 Dial Access? y Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n Member Assignment Method: manual add trunk-group 10 Page 2 of 21 Group Type: isdn TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Charge Advice: none Supplementary Service Protocol: b Digit Handling (in/out): enbloc/overlap QSIG Value-Added? y Digital Loss Group: 18 Incoming Calling Number - Delete: Insert: Format: unk-unk Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 add trunk-group 10 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: 10 Send Name: y Send Calling Number: y Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? y Suppress # Outpulsing? n Format: unknown UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Called/Busy/Connected Number: n Hold/Unhold Notifications? y Send UUI IE? y Modify Tandem Calling Number? n Send UCID? n Send Codeset 6/7 LAI IE? y Incoming Calling Number - Delete: Insert: Format: unk-unk Bit Rate: 1200 Synchronization: async Duplex: full 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).
add signaling-group 10 Page 1 of 1 SIGNALING GROUP Group Number: 10 Group Type: h.323 Remote Office? n Max number of NCA TSC: 20 SBS? n Max number of CA TSC: 20 IP Video? n Trunk Group for NCA TSC: 10 Trunk Group for Channel Selection: 10 Supplementary Service Protocol: b Network Call Transfer? n T303 Timer(sec): 10 Near-end Node Name: C-LAN Far-end Node Name: exchange-mas Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 1 LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n Media Encryption? n Bypass If IP Threshold Exceeded? n H.235 Annex H Required? n DTMF over IP: out-of-band 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 5 of 21 TRUNK GROUP Administered Members (min/max): 1/23 GROUP MEMBER ASSIGNMENTS Total Administered Members: 23 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 ………………………………………………………………………………………………………………………………………………………………………………………………………………………
4.5. Configure Call Routing Type change aar analysis to verify that the aar table has been set correctly. As shown, calls to the IP Office extension range 5xxxx and IP Office - Small Office extension range 4xxx will be directed to route pattern 11 and 2 respectively. Calls to Modular Messaging extension range 2000x will be directed to route pattern 10.
change aar analysis 2 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Percent Full: 1 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd 2000 5 5 10 aar n 4 4 4 2 aar n 5 5 5 11 aar n
4.5.1. Route-pattern to Remote Site 1 (IP Office Site) Type change route-pattern 11 to configure the route pattern for calls and message waiting updates to IP Office. Key items include the routed to trunk group number, the Facility Restriction Level, Number of Deleted Digits and the digits to insert to create the called number to be sent. In this configuration, the called number sent to Remote Site 1 (IP Office) will be a 5-digit number beginning with 5. Also, on the line corresponding with the trunk group at the bottom half of the form, ensure that the TSC column value is set to y and the Temporary Signaling Connection Request is set as-needed in order to support message-waiting updates. Set the Numbering Format field to unk-unk. change route-pattern 11 Page 1 of 3 Pattern Number: 11 Pattern Name: To Remote Site 1 SCCAN? n Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: 11 0 n user 2: n user 3: n user 4: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR 0 1 2 3 4 W Request Dgts Format Subaddress 1: y y y y y n y as-needed rest unk-unk none 2: y y y y y n n rest none 3: y y y y y n n rest none
4.5.2. Route-pattern to Modular Messaging Type change route-pattern 10 to configure the route pattern for calls to Modular Messaging. Enter 10 as the Grp No to Modular Messaging and a 0 for FRL to allow the appropriate calls. No. Del Dgts and Inserted Digits should be configured to send the proper 5-digit called party number to the Modular Messaging. In the corresponding line on the lower half of the form, set TSC to y to enable Temporary Signaling Connections and the Numbering Format to unk-unk. change route-pattern 10 Page 1 of 3 Pattern Number: 10 Pattern Name: To MM SCCAN? n Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: 10 0 n user 2: n user 3: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR 0 1 2 3 4 W Request Dgts Format Subaddress 1: y y y y y n y as-needed rest unk-unk none 2: y y y y y n n rest none 3: y y y y y n n rest none
5. Modular Messaging Configuration This section describes the steps for configuring the Modular Messaging Application Server (MAS). For storage server configuration, refer to reference [1] in Section 8. The voice domain retail-vdm has been created during the MAS installation. To access the Voice Mail System Configuration application, click Start Programs Avaya Modular Messaging Voice Mail System Configuration.
5.1. Telephone User Interface • Expand folder voice domain retail-vdm • Select Telephone User Interface under retail-vdm. • Click tab General and enter 7 for Number of Digits in a Mailbox. Since the central site
(Avaya Communication Manager) uses 7-digit extension, the 7-digit mailbox number is needed for this voice domain.
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
• Select Telephony Interface (under Message Application Servers) • Set the Playback Volume. The value 2 was used in this example. • Set the Maximum Concurrent Calls. The value 23 was used in this example. • Click OK to save changes.
5.5. Port Groups • Double click Port Groups to add an mwi group with a single port member. • Click Add Group and assign mwi for group name. • Check 1 from Port Group Members for MWI and uncheck all other ports as shown • Check the box Outgoing. • Click OK to save changes.
5.6. PBX Integration • Select PBX Integration and select the General tab to ensure the integration type is IP
H323 (not shown). • Select the IP H323 tab. • Enter the following information as shown in the form.
30.1.1.19 for MAS Corporate IP address 30.1.1.4 for C-LAN IP address 1720 for TCP port and 5000 –5999 for UDP Port Range 1 for Max MWI Sessions and mwi for Port Group Name
5.7. Modular Messaging User Configuration The section describes the steps of configuring Modular Messaging users on Microsoft Exchange Server. It is assumed that the Modular Messaging extension has been installed on the Microsoft Exchange server and the Exchange Server has been properly configured as a storage server for Avaya MAS. All users have been added on Exchange server with email address ending with @retail.com. For detailed configuration of integrating a Microsoft Exchange Server as a Modular Messaging storage server, refer to the references listed in Section 8. In this example, a user named test is used for configuration. The user named test has an email address [email protected] and mailbox 2251001 with extension 51001 on IP Office. Log into the Microsoft Exchange server with a user that has permissions to manage a Modular Messaging account. This account has been defined in DCT file used to build the MAS.
• Click Start Programs Microsoft Exchange Active Directory Users and Computers.
• Expand the folder Users (under retail.com in this example).
• 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).
• 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
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.
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 user’s 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 Manager’s 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.
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”
