Configuring a QSIG Centralized Messaging Solution using Avaya Modular Messaging between Avaya Communication Manager and Cisco CallManager - Issue 1.

Transcription

1 Avaya Solution & Interoperability Test Lab Configuring a QSIG Centralized Messaging Solution using Avaya Modular Messaging between Avaya Communication Manager and Cisco CallManager - Issue 1.0 Abstract These Application Notes describe how to configure QSIG centralized messaging using an Avaya Modular Messaging System to provide voic service for two sites. One site has Avaya Communication Manager running on an Avaya S8700 Media Server with G650 Media Gateway and the other site has a Cisco CallManager with 3660 MGCP Gateway. These two sites are connected via a QSIG T1 trunk. The Avaya Modular Messaging System is connected to Avaya Communication Manager via QSIG IP Trunk integration. 1 of 42

2 1. Introduction The Avaya Modular Messaging platform provides messaging services via a standard QSIG interface to support centralized messaging in a multi-vendor voice network. Centralized messaging provides voic service to remote switch users, where the voic server resides in the central location. This solution eases the administration and management of voic servers. These Application Notes provide a centralized messaging configuration consisting of Avaya Modular Messaging, Avaya Communication Manager and Cisco CallManager with Cisco 3660 MGCP Gateway using the QSIG protocol. Features such as call coverage with Ring no answer, Find-Me, Call-Me, and Message Waiting Indicator (MWI) were verified. Figure 1 illustrates the verified centralized messaging configuration. Avaya Communication Manager and Cisco CallManager are connected via a T1/PRI QSIG trunk. The Avaya Modular Messaging is connected to Avaya Communication Manager via an H.323 IP trunk with the QSIG protocol enabled. Avaya Communication Manager is at the central site and the Cisco CallManager is at the remote site. Local extensions for Avaya Communication Manager are of the form 24XXX. Local extensions for the Cisco site are of the form 27XXX. These two switches have dialing plans that allow subscribers on each side to call each other using five-digit dialing. Other dialing plans are acceptable. Figure 1: Centralized Messaging Configuration 2 of 42

3 2. Equipment and Software Validated The following equipment and software were used for the configuration provided: Equipment Software Avaya Messaging Application Server Version 2 Avaya Messaging Storage Server Release 2.0 Avaya Communication Manager running on an Avaya S8700 Media Server with G650 Media Gateway Release 2.1 (R012x ) Cisco CallManager Version 4.1 Cisco 3660 MGCP Gateway Version 12.3 Avaya 4624 IP Phone Release Avaya 4620 IP Phone Release Cisco 7940 IP Phone Ver 7.0 (2.0) Cisco 7960 IP Phone Ver 7.0 (2.0) 3. Configure Customer Options on Avaya Communication Manager QSIG centralized messaging requires several customer options to be activated in Avaya Communication Manager. The following steps validate the appropriate licensing on Avaya Communication Manager. Step 1. Log into Avaya Communication Manager and at the prompt type display systemparameters customer-options. Verify that the number of IP trunks is sufficient to add IP trunk between Avaya Modular Messaging and Avaya Communication Manager. display system-parameters customer-options Page 2 of 10 OPTIONAL FEATURES IP PORT CAPACITIES USED Maximum Administered H.323 Trunks: Maximum Concurrently Registered IP Stations: Maximum Administered Remote Office Trunks: Maximum Concurrently Registered Remote Office Stations: 0 0 Maximum Concurrently Registered IP econs: 0 0 Maximum Administered SIP Trunks: 0 0 Maximum Number of DS1 Boards with Echo Cancellation: 0 0 Maximum TN2501 VAL Boards: 0 0 Maximum G700/G350 VAL Sources: 1 0 (NOTE: You must logoff & login to effect the permission changes.) 3 of 42

4 Step 2. Go to Page 3. Verify that ARS? is set to y. display system-parameters customer-options Page 3 of 10 OPTIONAL FEATURES Abbreviated Dialing Enhanced List? n Audible Message Waiting? n Access Security Gateway (ASG)? n Authorization Codes? n Analog Trunk Incoming Call ID? n Backup Cluster Automatic Takeover? n A/D Grp/Sys List Dialing Start at 01? n CAS Branch? n Answer Supervision by Call Classifier? n CAS Main? n ARS? y Change COR by FAC? n ARS/AAR Partitioning? y Computer Telephony Adjunct Links? n ARS/AAR Dialing without FAC? n Co-Res DEFINITY LAN Gateway? n ASAI Link Core Capabilities? n Cvg Of Calls Redirected Off-net? n ASAI Link Plus Capabilities? n DCS (Basic)? n Async. Transfer Mode (ATM) PNC? n DCS Call Coverage? n Async. Transfer Mode (ATM) Trunking? n DCS with Rerouting? n ATM WAN Spare Processor? n ATMS? n Digital Loss Plan Modification? n Attendant Vectoring? n DS1 MSP? n DS1 Echo Cancellation? y (NOTE: You must logoff & login to effect the permission changes.) 3. Go to Page 4 and verify that IP Trunks? and ISDN-PRI? are set to y. display system-parameters customer-options Page 4 of 11 OPTIONAL FEATURES Emergency Access to Attendant? y IP Stations? y Enable 'dadmin' Login? n Internet Protocol (IP) PNC? y Enhanced Conferencing? y ISDN Feature Plus? n Enhanced EC500? n ISDN Network Call Redirection? n Enterprise Wide Licensing? n ISDN-BRI Trunks? n Extended Cvg/Fwd Admin? n ISDN-PRI? y External Device Alarm Admin? n Local Spare Processor? n Five Port Networks Max Per MCC? n Malicious Call Trace? y Flexible Billing? n Media Encryption Over IP? n Forced Entry of Account Codes? n Mode Code for Centralized Voice Mail? n Global Call Classification? n Hospitality (Basic)? y Multifrequency Signaling? y Hospitality (G3V3 Enhancements)? n Multimedia Appl. Server Interface (MASI)? n IP Trunks? y Multimedia Call Handling (Basic)? n Multimedia Call Handling (Enhanced)? n IP Attendant Consoles? n (NOTE: You must logoff & login to effect the permission changes.) 4 of 42

5 Step 4. Go to Page 5 and verify that Uniform Dialing Plan? and Private Networking? are set to y. display system-parameters customer-options Page 5 of 10 OPTIONAL FEATURES Multinational Locations? n Multiple Level Precedence & Preemption? n Multiple Locations? n Personal Station Access (PSA)? n Posted Messages? n PNC Duplication? n Port Network Support? n Processor and System MSP? n Private Networking? y Processor Ethernet? y Remote Office? y Restrict Call Forward Off Net? y Secondary Data Module? y Station and Trunk MSP? n Station as Virtual Extension? n System Management Data Transfer? n Tenant Partitioning? n Terminal Trans. Init. (TTI)? n Time of Day Routing? n Uniform Dialing Plan? y Usage Allocation Enhancements? y TN2501 VAL Maximum Capacity? y Wideband Switching? n Wireless? n (NOTE: You must logoff & login to effect the permission changes.) 5. Go to Page 8 and verify that Basic Call Setup?, Basic Supplementary Services?, and Transfer into QSIG Voice Mail? are set to y as shown below. display system-parameters customer-options Page 8 of 11 QSIG OPTIONAL FEATURES Basic Call Setup? y Basic Supplementary Services? y Centralized Attendant? n Interworking with DCS? n Supplementary Services with Rerouting? n Transfer into QSIG Voice Mail? y Value-Added (VALU)? n (NOTE: You must logoff & login to effect the permission changes.) 5 of 42

6 4. Configure System Features on Avaya Communication Manager The following steps set the necessary system features on Avaya Communication Manager to support QSIG voic integration. Step 1. Log into Avaya Communication Manager and at the prompt type change systemparameters features. Assign a dial plan extension for QSIG TSC Extension, and enter 5 for MWI Number of Digits Per Voice Mail Subscriber. This configuration used a 5-digit dialing plan, however other dialing plans are acceptable. change system-parameters features Page 8 of 14 FEATURE-RELATED SYSTEM PARAMETERS ISDN PARAMETERS Send Non-ISDN Trunk Group Name as Connected Name? n Display Connected Name/Number for ISDN DCS Calls? n Send ISDN Trunk Group Name on Tandem Calls? n QSIG TSC Extension: MWI - Number of Digits Per Voice Mail Subscriber: 5 National CPN Prefix: International CPN Prefix: Pass Prefixed CPN to ASAI? n Unknown Numbers Considered Internal for AUDIX? n USNI Calling Name for Outgoing Calls? n Path Replacement with Measurements? n QSIG Path Replacement Extension: Path Replace While in Queue/Vectoring? n 5. Configure Avaya Communication Manager This section provides configuration steps for Avaya Communication Manager according to the configuration illustrated in Figure 1. Step 1. From the SAT, type display dialplan analysis. Verify dialed strings are configured for a 5-digit dial plan, including extensions beginning with 4 and 2. 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 5 ext 3 5 ext 4 5 ext 7 5 ext 8 1 fac 9 1 fac * 3 fac # 3 fac 6 of 42

7 Step 2. Type display circuit-packs to verify that the Control-LAN circuit pack and IP Media Processor circuit pack are installed. display circuit-packs Page 1 of 3 CIRCUIT PACKS Cabinet: 1 Cabinet Layout: rack-mount-stack Carrier: A Carrier Type: rmc-port Slot Code Sf Mode Name 01: TN464 F DS1 INTERFACE 02: TN2312 IP SERVER INTFC 03: TN799 D CONTROL-LAN 04: TN2302 IP MEDIA PROCESSOR 05: TN793 B ANALOG LINE 06: ASAIM1 RESERVED-LANGATE 07: ASAIM1 RESERVED-LANGATE 08: TN801 B MAPD BOARD 09: TN464 F DS1 INTERFACE 10: TN2501 VAL-ANNOUNCEMENT '#' indicates circuit pack conflict. 3. Type display data-module 24980, where is an assigned extension, to verify that the data module is assigned to the Control-LAN circuit pack. display data-module Data Extension: Type: ethernet Port: 01A0317 Link: 1 DATA MODULE Name: CLAN Network uses 1's for Broadcast Addresses? y 4. Assign node names and IP addresses to the Control-LAN, IP Media Processor, and the Avaya Modular Messaging (MAS server) using the change node-names ip command. Type display node-names ip to verify the node names and IP addresses. display node-names ip IP NODE NAMES Name IP Address clan cms default dev ir lzmas medpro pbx procr... ( 9 of 9 administered node-names were displayed ) Use 'list node-names' command to see all the administered node-names Use 'change node-names ip xxx' to change a node-name 'xxx' or add a node-name 7 of 42

8 Step 5. Type list configuration all to display the port addresses of Control-LAN and IP Media Processor. list configuration all Page 1 SYSTEM CONFIGURATION Board Assigned Ports Number Board Type Code Vintage u=unassigned t=tti p=psa 01A01 DS1 INTERFACE TN464F u u u u u u u u 01A02 IP SERVER INTFC TN2312AP HW32 FW A03 CONTROL-LAN TN799DP HW00 FW010 u u u u u u u u u u u u u u u u 17 01A04 IP MEDIA PROCESSOR TN2302AP HW03 FW A05 ANALOG LINE TN793B A06 RESERVED-LANGATE TN801 mapd u u u u u u u u Type change ip-interface 1a03. Enter clan for Node Name, for Subnet Mask, for Gateway Address and y for Enable Ethernet Port. change ip-interface 1a03 Page 1 of 1 IP INTERFACES Type: C-LAN Slot: 01A03 Code/Suffix: TN799 D Node Name: clan IP Address: Subnet Mask: Gateway Address: Enable Ethernet Port? y Network Region: 1 VLAN: n ETHERNET OPTIONS Auto? y Number of CLAN Sockets Before Warning: 400 Type change ip-interface 1a04 and enter the corresponding information for the MEDPRO card. change ip-interface 1a04 Page 1 of 1 IP INTERFACES Type: MEDPRO Slot: 01A04 Code/Suffix: TN2302 Node Name: medpro IP Address: Subnet Mask: Gateway Address: Enable Ethernet Port? y Network Region: 1 VLAN: n ETHERNET OPTIONS Auto? y 8 of 42

9 Step 6. Define the IP Network Region. This configuration uses one network region. Alternatively, multiple network regions can be configured for each voic node. Type change ip-network-region 1. The UDP ports used in this network region must be the same range as the UDP port range configured in the Avaya Modular Messaging. Enter name centralized MM for Name, 1 for Codec Set, 5000 for UDP port Min, 5999 for UDP port Max. change ip-network-region 1 Page 1 of 19 IP NETWORK REGION Region: 1 Location: 1 Home Domain: Name: centralized MM Intra-region IP-IP Direct Audio: yes AUDIO PARAMETERS Inter-region IP-IP Direct Audio: yes Codec Set: 1 IP Audio Hairpinning? y UDP Port Min: 5000 UDP Port Max: 5999 RTCP Reporting Enabled? y RTCP MONITOR SERVER PARAMETERS DIFFSERV/TOS PARAMETERS Use Default Server Parameters? y Call Control PHB Value: 34 Audio PHB Value: P/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? y Idle Traffic Interval (sec): 20 Keep-Alive Interval (sec): 5 Keep-Alive Count: 5 Type change ip-codec-set 1. Verify that codec G.711MU is set. change ip-codec-set 1 Page 1 of 2 Codec Set: 1 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n of 42

10 Step 7. Add the DS1 circuit pack. Type add ds1 2a08 where 2a08 is the slot of the DS1 circuit pack. For this sample configuration, Avaya Communication Manager was configured as peer-master and Cisco CallManager was configured as peer-slave. add ds1 2a08 Page 1 of 2 DS1 CIRCUIT PACK Location: 02A08 Name: Cisco3660 Bit Rate: Line Coding: b8zs Line Compensation: 1 Framing Mode: esf Signaling Mode: isdn-pri Connect: pbx Interface: peer-master TN-C7 Long Timers? n Peer Protocol: Q-SIG Interworking Message: PROGress Side: a Interface Companding: mulaw CRC? n Idle Code: DCP/Analog Bearer Capability: 3.1kHz T303 Timer(sec): 4 Slip Detection? n Near-end CSU Type: other 8. Add a signaling group. Type add signaling-group 60. Assign the bolded values to the corresponding fields. add signaling-group 60 Page 1 of 1 SIGNALING GROUP Group Number: 60 Group Type: isdn-pri Associated Signaling? y Max number of NCA TSC: 10 Primary D-Channel: 02A0824 Max number of CA TSC: 0 Trunk Group for NCA TSC: Tru nk Group for Channel Selection : Supplementary Service Protocol: b Network Call Transfer? n 10 of 42

11 9. Create a trunk to the Cisco switch. Use the add trunk command and associate this trunk to the above DS1. Enter the values in bold in their corresponding fields. add trunk-group 23 Page 1 of 22 TRUNK GROUP Group Number: 60 Group Type: isdn CDR Reports: y Group Name: cisco3660 COR: 1 TN: 1 TAC: 116 Direction: two-way Outgoing Display? y Carrier Medium: PRI/BRI Dial Access? y Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: rest Far End Test Line No: TestCall BCC: 4 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc Trunk Hunt: cyclical QSIG Value-Added? n Digital Loss Group: 13 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 add trunk-group 23 Page 2 of 22 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n 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 Suppress # Outpulsing? n Format: unknown Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: y Modify Tandem Calling Number? n Ds1 Echo Cancellation? n Path Replacement with Retention? n Path Replacement Method: better-route SBS? n Network (Japan) Needs Connect Before Disconnect? n When a call to the Cisco station covers to Avaya Modular Messaging, Avaya Communication Manager will send a reroute request back to Cisco to route the call with a new Setup message. Cisco reroutes the call with a new Setup message with incompatible divert information. An acceptable solution is to use Avaya Communication Manager to manipulate the incoming digits for the voic hunt group and reroute the call directly to the voic number to bypass the service reroute request. As shown in the table below, Avaya Communication Manager will delete the called number (voic pilot number 25100) received from Cisco CallManager and insert This number is the voic number not the voic hunt group number specified in the Avaya Communication Manager coverage path. 11 of 42

12 Step add trunk-group 60 Page 3 of 22 INCOMING CALL HANDLING TREATMENT Service/ Called Called Del Insert Per Call Night Feature Len Number CPN/BN Serv tie all Assign 23 members to this trunk group. Only 3 members are shown below. add trunk-group 60 Page 6 of 22 TRUNK GROUP Administered Members (min/max): 1/3 GROUP MEMBER ASSIGNMENTS Total Administered Members: 3 Port Code Sfx Name Night Sig Grp 1: 02A0801 TN464 F 60 2: 02A0802 TN464 F 60 3: 02A0803 TN464 F Assign the above trunk to the signaling group. Type change signaling-group 60. Enter the trunk group number to the Trunk Group for Channel Selection and Trunk Group for NCA TSC. change signaling-group 60 Page 1 of 1 SIGNALING GROUP Group Number: 60 Group Type: isdn-pri Associated Signaling? y Max number of NCA TSC: 10 Primary D-Channel: 02A0824 Max number of CA TSC: 0 Trunk Group for NCA TSC: 60 Trunk Group for Channel Selection: 60 Supplementary Service Protocol: b Network Call Transfer? n 11. Change the uniform-dialplan table to route calls from the Avaya S8700 to the Cisco CallManager. Type change uniform-dialplan 2. Enter 27 for Matching Pattern, 5 for Len, 0 for Del, 27 for Insert Digits and aar for Net. When a user at the central site dials 27xxx, Avaya Communication Manager will use the aar table to route the call. 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 aar n n 12 of 42

13 Step 12. Type change aar analysis 27. Enter 27 for Dialed String, 7 for Min and Max, 80 for Route Pattern, and aar for Call Type. change aar analysis 27 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Percent Full: 1 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd aar n 13. Type change route-pattern 80. Enter a name for Pattern name, 60 for Grp No, 0 for FRL, 2 No. Del Dgts, y for TSC, as-needed for CA-TSC Request, and unk-unk for Numbering Format. Trunk 60 is the T1/PRI QSIG trunk to Cisco CallManager. change route-pattern 80 Page 1 of 3 Pattern Number: 80 Pattern Name: ciscocm4.1 Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: n user 2: n user 3: n user 4: n user 5: n user 6: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR 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 14. Type change public-unknown-numbering. This allows the Avaya Communication Manger to send calling party number along with the call information. change public-unknown-numbering Page 1 of 8 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 Enter 5 for Ext Len, 2 for Ext Code and 5 for CPN Len. 13 of 42

14 Step 15. Create a voic hunt group. Type add hunt 250. Enter a group name, group extension and group type. Group extension is a voic pilot number that the user can dial to access voic . Go to Page 2. add hunt-group 250 Page 1 of 60 HUNT GROUP Group Number: 250 Group Name: MSGserver Group Extension: Group Type: ucd-mia TN: 1 COR: 1 Security Code: ISDN Caller Display: mbr-name ACD? n Queue? n Vector? n Coverage Path: Night Service Destination: MM Early Answer? n Enter qsig-mwi for Message Center, for Voice Mail Number, 8 for Routing Digits and n for Send Reroute Request. add hunt-group 250 Page 2 of 60 HUNT GROUP Message Center: qsig-mwi Voice Mail Number: Routing Digits (e.g. AAR/ARS Access Code): 8 Send Reroute Request: n LWC Reception: none AUDIX Name: 16. Modify the AAR table to route calls to voic . Type change aar analysis 852. Enter for Dialed String, 7 for Total Min and Max, 299 for Route Pattern and aar for Call Type. change aar analysis 852 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Percent Full: 1 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd aar n aar n n n 14 of 42

15 Step 17. Create a coverage path. Type add coverage path 1. Enter the voic hunt group created in Step 14, h250 for Point1. This applies for Avaya Communication Manager coverage calls only. add coverage path 1 Page 1 of 1 COVERAGE PATH Coverage Path Number: 1 Next Path Number: Hunt after Coverage? n Linkage COVERAGE CRITERIA Station/Group Status Inside Call Outside Call Active? n n Busy? y y Don't Answer? y y Number of Rings: 2 All? n n DND/SAC/Goto Cover? y y COVERAGE POINTS Terminate to Coverage Pts. with Bridged Appearances? n Point1: h250 Rng: Point2: Point3: Point4: Point5: Point6: 6. Assign a Coverage Path to a Station The following step illustrates how to configure an Avaya Communication Manager station for coverage by Avaya Modular Messaging. Step 1. Type add station Enter necessary values for the station, enter 1 for coverage path 1 and enter qsig-mwi for MWI Served User Type. change station Page 1 of 4 STATION Extension: Lock Messages? n BCC: 0 Type: 4612 Security Code: 1234 TN: 1 Port: IP Coverage Path 1: 1 COR: 1 Name: U1 Coverage Path 2: COS: 1 Hunt-to Station: STATION OPTIONS Loss Group: 19 Personalized Ringing Pattern: 1 Message Lamp Ext: Speakerphone: 2-way Mute Button Enabled? y Display Language: english Survivable GK Node Name: Media Complex Ext: IP SoftPhone? n 15 of 42

16 Step change station Page 2 of 4 STATION FEATURE OPTIONS LWC Reception: spe Auto Select Any Idle Appearance? n LWC Activation? y Coverage Msg Retrieval? y LWC Log External Calls? n Auto Answer: none CDR Privacy? n Data Restriction? n Redirect Notification? y Idle Appearance Preference? n Per Button Ring Control? n Bridged Call Alerting? n Restrict Last Appearance? y Active Station Ringing: single H.320 Conversion? n Per Station CPN - Send Calling Number? Service Link Mode: as-needed Multimedia Mode: enhanced MWI Served User Type: qsig-mwi Display Client Redirection? n Select Last Used Appearance? n Coverage After Forwarding? s Emergency Location Ext: Direct IP-IP Audio Connections? y IP Audio Hairpinning? y 7. Configure IP Trunk for Avaya Modular Messaging The following configuration steps explain how to create an IP trunk between the Avaya Modular Messaging and Avaya Communication Manager. The Avaya Communication Manager configuration is shown below. The Avaya Modular Messaging configuration is shown in Section 10. Step 1. From the SAT, type add signaling-group # where # is an arbitrary number assigns to the trunk. Set the following fields to the values shown below: Group Type h.323 Max number of NCA TSC 10 Max number of CA TSC 10 Trunk Group for NCA TSC 18 Supplementary Service protocol b Near-end Node Name clan Near-end Listen Port 1720 Far-end Node Name lzmas1 Far-end Listen Port 1720 Far-end Network Region 1 16 of 42

17 Step add signaling-group 18 Page 1 of 1 SIGNALING GROUP Group Number: 18 Group Type: h.323 Remote Office? n Max number of NCA TSC: 10 SBS? n Max number of CA TSC: 0 Trunk Group for NCA TSC: 18 Trunk Group for Channel Selection: Supplementary Service Protocol: b Near-end Node Name: clan Far-end Node Name: lzmas1 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 Bypass If IP Threshold Exceeded? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? n IP Audio Hairpinning? n Interworking Message: PROGress 2. From the SAT, type add trunk-group # where # is an arbitrary number. Enter the values in bold in the trunk form. add trunk-group 18 Page 1 of 22 TRUNK GROUP Group Number: 18 Group Type: isdn CDR Reports: y Group Name: LZMAS1 COR: 1 TN: 1 TAC: 118 Direction: two-way Outgoing Display? y Carrier Medium: IP Dial Access? y Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: rest Far End Test Line No: TestCall BCC: 4 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc Trunk Hunt: cyclical QSIG Value-Added? n Digital Loss Group: 18 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 17 of 42

18 Step add trunk-group 18 Page 2 of 22 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n 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? y Suppress # Outpulsing? n Format: unknown Outgoing Channel ID Encoding: exclusive UUI IE Treatment: service-provider Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Called/Busy/Connected Number: n Modify Tandem Calling Number? n Path Replacement with Retention? y Path Replacement Method: always SBS? n Network (Japan) Needs Connect Before Disconnect? n add trunk-group 18 Page 6 of 22 TRUNK GROUP Administered Members (min/max): 1/24 GROUP MEMBER ASSIGNMENTS Total Administered Members: 24 Port Code Sfx Name Night Sig Grp 1: ip 18 2: ip 18 3: ip : ip 18 15: ip of 42

19 Step Set the following fields to the values shown below: Group Type: isdn Group Name: LZMAS1 Arbitrary name assigns to far end switch. TAC: 118 Trunk Access Code number according to the dial plan. Direction two-way Outgoing Display y Carier Medium IP Service Type tie Supplementary Service b Protocol Digit Handling enbloc/ enbloc QSIG Value-Added y Format unk-unk NCA-TSC Trunk Member 1 Send Name y Send Calling Number y Format unknown Port (1-24) IP For each active channel. Sig Group (1-24) 18 Assigned in Step of 42

20 Step 3. From the SAT, type change signaling-group 18. Set Trunk Group for Channel Selection and Trunk Group for NCA TSC to 18. change signaling-group 18 Page 1 of 1 SIGNALING GROUP Group Number: 18 Group Type: h.323 Remote Office? n Max number of NCA TSC: 10 SBS? n Max number of CA TSC: 0 Trunk Group for NCA TSC: 18 Trunk Group for Channel Selection: 18 Supplementary Service Protocol: b Near-end Node Name: clan Far-end Node Name: lzmas1 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 Bypass If IP Threshold Exceeded? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? n IP Audio Hairpinning? n Interworking Message: PROGress 4. Type change route-pattern 299. Enter a name for Pattern name, 18 for Grp No, 0 for FRL, 3 No. Del Dgts, y for TSC, as-needed for CA-TSC Request, and unk-unk for Numbering Format. Group Number 18 is an IP trunk to the Avaya Modular Messaging. change route-pattern 299 Page 1 of 3 Pattern Number: 299 Pattern Name: message Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: n user 2: n user 3: n user 4: n user 5: n user 6: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR 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: y y y y y n n rest none 5: y y y y y n n rest none 6: y y y y y n n rest none 20 of 42

21 8. Configure Cisco 3660 MGCP Gateway The following step shows the Cisco configuration file that was configured on the Cisco 3660 MGCP Gateway. This configuration assigns an IP address of to the Cisco CallManager and IP Address of to the Cisco 3660 MGCP Gateway. The T1 interface is installed in the slot number 4 of the Cisco 3660 MGCP Gateway. Ethernet 0 of the Cisco 3660 GMCP Gateway was used to communicate with the Cisco CallManager. The Cisco 3660 MGCP Gateway was assigned a hostname cisco3660 in the mm.com domain. The text in bold was explicitly entered on the Cisco 3660 MGCP Gateway. Step 1. cisco3660# show run Building configuration... Current configuration : 1943 bytes version 12.3 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption hostname cisco3660 boot-start-marker boot-end-marker no aaa new-model ip subnet-zero ip cef ip domain name mm.com ip name-server isdn switch-type primary-qsig voice-card 4 ccm-manager mgcp ccm-manager config server ccm-manager config controller T1 4/0 framing esf linecode b8zs 21 of 42

22 Step pri-group timeslots 1-24 service mgcp controller T1 4/1 framing sf linecode ami interface FastEthernet0/0 ip address duplex auto speed auto interface FastEthernet0/1 no ip address shutdown duplex auto speed auto interface FastEthernet3/0 no ip address shutdown duplex auto speed auto interface Serial3/0 no ip address shutdown interface FastEthernet3/1 no ip address shutdown duplex auto speed auto interface Serial4/0:23 no ip address isdn switch-type primary-qsig isdn incoming-voice voice isdn bind-l3 ccm-manager no cdp enable ip default-gateway ip http server ip classless 22 of 42

23 Step control-plane voice-port 4/0:23 mgcp mgcp call-agent service-type mgcp version 0.1 mgcp dtmf-relay voip codec all mode out-of-band mgcp rtp unreachable timeout 1000 action notify mgcp package-capability rtp-package no mgcp package-capability res-package mgcp package-capability sst-package no mgcp package-capability fxr-package mgcp package-capability pre-package no mgcp timer receive-rtcp mgcp sdp simple mgcp fax t38 inhibit mgcp profile default dial-peer voice 1 pots application mgcpapp application mgcpapp out-bound port 4/0:23 line con 0 transport preferred all transport output all line aux 0 transport preferred all transport output all line vty 0 4 login transport preferred all transport input all transport output all cisco3660# 23 of 42

24 9. Configure Cisco CallManager The following steps show how to configure the Cisco CallManager. The following steps below explain how to add the Cisco 3660 MGCP Gateway, configure the QSIG T1 interface, create Route Group, Route List and Route Pattern, create voic pilot and voic profile, and configure Cisco phone. Step 1. Access the Cisco CallManager Administration website, and click on Device Gateway. 2. Click on Add a New Gateway. 3. Select Cisco 366X for the Cisco Gateway type* and select MGCP for Device Protocol*. Click Next. 4. Enter the Domain Name*,, Cisco CallManager Group*, and select the voice interface for Module in Slot 4. Click Insert. 24 of 42

25 5. A Subunit dialog box will appear under the Module in Slot 4 drop-down box. Select the type of VWIC interface and click Update. 6. Click OK at the reset gateway alert message. 7. A T1 voice interface will appear next to the Subunit box. Click on the first T1 with a yellow question mark. 8. In the Device Protocol* form box, select T1-PRI. 25 of 42

26 9. Under Device Information, select the Device Pool*, Call Classification* and Network Locale. 10. Under Interface Information, select the values as shown in the illustration below. 26 of 42

27 11. In the Call Routing Information, select the call information that is appropriate to the voice network environment or use the values below. 27 of 42

28 12. Under PRI Protocol Type Specific Information, select Allowed for the Connected Line ID Presentation ( QSIG Inbound Call)*. 13. Under Product Specific Configuration, select the values as shown in the illustration below. 14. Click Update. 28 of 42

29 15. Click OK at the Reset gateway alert dialog box. 16. Click Reset Gateway Reset OK. 17. Click on Route Plan Route/Hunt Route Group. 18. Click on Add New Route Group. 19. In the Route Group Configuration, enter the Route Group Name, select the Distribution Algorithm and select the T1 in the Available Devices list and click Add to Route Group. 20. Click Insert. 21. Click on Route Plan Route/Hunt Route List. 29 of 42

30 22. In the Route List Configuration, enter the Route List Name, and select the Cisco CallManager Group. 23. Click Insert. 24. After the route list is created, click on Add Route Group. 30 of 42

31 25. Select the Route Group created in Step 18, select Off for use Calling Party s External Phone Number Mask, North American Numbering Plan for Dial Plan*. 26. Click Insert. 27. Click OK in the Reset route list alert message. 31 of 42

32 28. Click Reset OK. 29. Click on Route Plan Route/Hunt Route Pattern. 30. Click on Add a New Route Pattern. 31. This step will create a route pattern to route calls starting with 24XXX to the Avaya site. Enter 24XXX in the Route Pattern*, enter the description for this route pattern, select North American Numbering Plan for Numbering Plan*, select the Route list created in Step 21, check the Route this pattern, select OffNet for Call Classification*, and uncheck Provide Outside Dial Tone. 32 of 42

33 32. Select the values for Calling Party, Connect Party and Called Party Transformations as shown in the illustration below. 33. Click Insert. 34. The Avaya Modular Messaging Pilot number is This step will create a route pattern to route calls starting with 25XXX to the Avaya site. Enter 25XXX in the Route Pattern*, enter the description for this route pattern, select North American Numbering Plan for Numbering Plan*, select the Route list created in Step 21, check the Route this pattern, select OffNet for Call Classification*, and uncheck Provide Outside Dial Tone. 33 of 42

34 35. Select the values for Calling Party, Connect Party and Called Party Transformations as shown in the illustration below. 36. Click Insert. 37. The following step will create a voic pilot number and voic profile. Click Feature Voice Mail Voice Mail Pilot. 38. Click Add a New Voice Mail Pilot. 39. Enter the Modular Messaging voic Pilot number and description. 40. Click Insert. 41. Click Feature Voice Mail Voice Mail Profile. 34 of 42

35 42. Click Add a New Voice Mail Profile. 43. Enter a name without spaces for the Voice Mail Profile Name*, description, and select the Voice Mail Pilot created in Step Click Insert. 45. The following step will configure voic for a Cisco phone. Click on Device Phone. 46. Click on one of the phones. 35 of 42

36 47. In the Phone Configuration, click on available Line, typically Line 1 of the phone. 48. In the Voice Mail Profile field, select the voice mail profile created in Step 43. Check all the forward boxes under the Voice Mail column as shown, except for Forward All. 49. Click Update. 36 of 42

37 10. Configure Avaya Modular Messaging The following steps show the configuration of the Avaya Modular Messaging. Step 1. Run the Voice Mail System Configuration from the MAS program group. 2. Select the Voice Mail Domain. 3. Expand PBXs. 4. Select (double click) the Avaya MV (IP H323) PBX. 5. Click the Transfer/Outbound tab. 6. Set Transfer Mode to Full. 37 of 42

38 Step 7. Click the Outgoing Call tab. Select Local for Number Type. Select Private for Number Plan. Origin Number is the number entered in the Voice Mail Number field of the Hunt Group minus the number of leading digits administered in the route pattern to delete. In our example, the Voice Mail Number is and the number of digits to delete in the route-pattern is 2; therefore, the number entered here must be Click OK. MAS will prompt to restart the services. Do not restart the server until the instructions below are completed. 9. Expand Messaging Application Servers. 10. Double click on Telephony Interface (IP H323). 11. Set the Playback Volume to Set the maximum concurrent calls ( maximum of 20 per MAS) 38 of 42

39 Step 13. Select OK to save changes. 14. Double click on Port Group. 15. Click Add Group. 16. Enter MWI for Group Name. 17. Uncheck all of the ports, except the ports you will be using for WI. 18. Uncheck Incoming under Port Group Usage. 19. Ensure the Default Group has all the appropriate Incoming/Outgoing ports selected, except for the MWI ports. 20. Select OK to save changes 21. Double-click on the PBX Integration. 22. In the General tab, select IP for Integration Type. 23. Click the IP Configuration tab. Enter the following information: MAS Corporate IP Address = IP address assigned to the MAS CORP IP (corporate network) PBX IP Address = IP address assigned to the PBX C-LAN card Port = 1720 UDP Port Range = Refer to the IP Network Region on the PBX Packet size (bytes) = 30 Enable Tunneling = Check box Enable Fast Start = Check box Silence Suppress = Uncheck box Max MWI Sessions = Number of ports assigned in the MWI Port Group Port Group Name = MWI or name entered in MWI Port Group IP Supported Codec s = Highlight G.711-uLaw-64k and Move Up 39 of 42

40 Step 24. Select OK to save changes. 25. Double click on the PBX Type. 26. In the General tab, verify that IP H323 is selected for Telephony Type, and Avaya MV (IP H323) is selected for PBXs. 27. Click OK to save changes. 28. Restart the MAS server. 11. Verification Steps Verification involves several tests to verify that Avaya Modular Messaging provides voic service to the far-end subscribers. Verify that the Cisco 3660 MGCP Gateway D-Channel is in the active state by running the show isdn status command as shown below: cisco3660#show isdn status Global ISDN Switchtype = primary-qsig %Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 0. Layer 3 output may not apply ISDN Serial4/0:23 interface dsl 0, interface ISDN Switchtype = primary-qsig **** Slave side configuration **** L2 Protocol = Q.921 0x0000 L3 Protocol(s) = CCM MANAGER 0x0003 Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status: 0 Active Layer 3 Call(s) Active dsl 0 CCBs = 0 The Free Channel Mask: 0x807FFFFF Number of L2 Discards = 0, L2 Session ID = 3 Total Allocated ISDN CCBs = 0 Verify that the Avaya T1 trunk-group is in-service by using the status trunk command from the Avaya SAT command line as shown below: status trunk 60 TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy 0060/001 02A0801 in-service/idle no 0060/002 02A0802 in-service/idle no Place a test call from a station on Avaya Communication Manager to a station on the far-end switch (Cisco) and leave a voice message. If the Avaya Modular Messaging plays the 40 of 42

41 standard greeting message instead of the subscriber greeting, check to make sure Step 8 of Section 5 is configured correctly. Verify that the message waiting indicator (MWI) light turns on for the far-end station. Make a test call from a station on the Cisco switch to itself and leave a voice message. Verify that the message waiting indicator light turns on. Dial the voic pilot number from the station on the Cisco switch. Verify that Avaya Modular Messaging prompts for the password only. Review and delete a voice message. Verify that the MWI is turned off. 12. Conclusion These Application Notes described the configuration for centralized messaging using the Avaya Modular Messaging platform and Avaya Communication Manager to support voic for remote Cisco CallManager subscribers. 13. Additional References CN:88014 Avaya DEFINITY G3, IP600 & S8300/S8700 (IP Now), Date: 04/22/04, Rev: E, Intg Type: H.323. Avaya QSIG Advantages, 41 of 42

42 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 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 42 of 42