Configuring Avaya Communication Manager H.323/LRQ Trunks in a Cisco Multi-Gatekeeper Environment - Issue 1.0

Transcription

1 Avaya Solution & Interoperability Test Lab Configuring Avaya Communication Manager H.323/LRQ Trunks in a Cisco Multi-Gatekeeper Environment - Issue 1.0 Abstract These Application Notes describe the configuration of Avaya Communication Manager H.323/LRQ trunking in a Cisco multi-gatekeeper Environment. Avaya Communication Manager provides Gatekeeper and Gateway functionality for one location via H.323/LRQ trunks. A Cisco Gatekeeper and a Cisco Gateway are located in a second location. In the second site, the Cisco Gateway provides access via E1/PRI to a second Avaya Communication Manager. A Cisco Directory Gatekeeper is located in the common IP network providing call directory service for both locations. These Application Notes are the result of a customer Proof of Concept, 1 of 37

2 1. Introduction Location Request (LRQ) processing between Gatekeepers (GK) is a method for providing IP call trunking. IP Gateways (GW) register to GK. The GW will then forward their call requests to that GK via Remote Access Services (RAS) protocol. Based on call route provisioning the GK will send LRQs to a destination GK. If the destination GK is authoritive for a GW that can deliver the call, the destination GK will respond to the originating GK with a Location Confirm (LCF) message. The LCF contains the IP address of the terminating GW. The origination GK forwards this information to the originating GW. The originating GW then establishes a Q.931 call setup sequence with the destination GW to complete the call. This method may require all local GKs to contain call routing information for all possible destinations. To minimize provisioning of local GKs, an alternate configuration may be used. This method utilizes a centralized Directory Gatekeeper (DGK). The DKG is provisioned with call routing information for all the GKs for which it is authoritive. When a local GK generates an LRQ request, that GK will send the LRQ to the DKG. The DKG will then forward the LRQ to the appropriate destination GK. The DGK is only involved in the delivery of the LRQ. LCF responses still go GK to GK, bypassing the DKG. Due to the different LRQ/LCF processing when a DGK is involved, additional H.323 trunk provisioning is required in Avaya Communication Manager. These Application Notes describe the Avaya Communication Manager provisioning as well as the provisioning of the Cisco DGK, GK, and GW as implemented in the reference configuration. 2 of 37

3 2. Reference Configuration These Application Notes use the reference configuration shown in Figure 1. Figure 1 Reference Configuration In Company A, Avaya Communication Manager is running on an Avaya S8300C Server which resides in an Avaya G350 Media Gateway. Avaya Communication Manager provides both H.323 Gateway (GW) and Gatekeeper (GK) functionality. The Company A Avaya Communication Manager utilizes H.323/LRQ trunks. Company A uses the 5 digits dial plan, 5xxxx. An H.323 station is defined on Customer A (x50001). In Company B, an Avaya S8300B Server is running Avaya Communication Manager and resides in an Avaya G700 Media Gateway. A Cisco 3845 access router is configured to be both an H.323 Gatekeeper and a Gateway. The Cisco 3845 router is connected to Avaya Communication Manager via E1/PRI. Company B uses the 5 digits dial plan, 4xxxx. An H.323 station is defined on Customer B (x40001). The Cisco 3825 router is configured as a Directory Gatekeeper (DGK). The DGK forwards LRQ requests from the Avaya Communication Manager GK to Company B, and forwards LRQ requests from the Cisco 3845 Gatekeeper to Company A. Note: The H.323 and E1/PRI trunks were configured as QSIG in the reference configuration. However, this is not required. 3 of 37

4 2.1. Call Flows A ten digit dial plan is used to place calls between Company A and Company B. Auto Route Selection (ARS) is used in both Avaya Communication Manager instances to access outbound trunk dialing Company A Calls Company B A company A user will dial 9 (to access ARS) plus , where is the number of the Company B phone. Avaya Communication Manager A will send a LRQ message with the called number to the Cisco 3825 DGK. The Cisco 3825 DGK will forward the LRQ message to the Cisco 3845 GK. The Cisco 3845 GK will respond with a Location Confirm (LCF) message to Avaya Communication Manager A. The LCF message includes the Cisco 3845 GW IP address for call setup. Avaya Communication Manager A will initiate a Q.931 call setup sequence to the Cisco 3845 GW via H.323. This will initiate an additional Q.931 call setup sequence between the Cisco 3845 GW and the Company B Avaya Communication manager, via the ISDN PRI trunk. Once these call setup sequences are complete, a talk path will exist between Company A and Company B Company B Calls Company A A company B user will dial 9 (to access ARS) plus , where is the number of the Company A phone. Avaya Communication Manager B will send an ISDN Q.931 call setup message with the called number to the Cisco 3845 GW. The Cisco 3845 GW will send a RAS message to the Cisco 3845 GK. The Cisco 3845 GK will send an LRQ request to the Cisco 3825 DKG. The Cisco 3825 DGK will forward the LRQ request to Avaya Communication Manager A. Avaya Communication Manager will send an LCF back to the Cisco 3845 GK. The LCF message includes the Avaya Communication Manager IP address for call setup. The Cisco 3845 GK forwards the address of Avaya Communication Manager A to the Cisco 3845 GW. The Cisco 3845 GW then initiates a Q.931 call setup sequence to Avaya Communication Manager A. Once these call setup sequences are complete, a talk path will exist between Company B and Company A. 4 of 37

5 3. Equipment and Software Validated The following equipment and software were used to test the sample configuration. Equipment Software Avaya S8300C Media Server Avaya Communication Manager 4.1 (R014x.731.2) Avaya G350 Gateway Avaya G700 Media Gateway P333 MGP MM710 T1/E HW5 FW18 Avaya 4621 H.323 telephone 2.8 Cisco Directory Gatekeeper (Cisco 3825 Router) c3825-ipvoice_ivs-mz t5.bin Cisco Gatekeeper and Gateway (Cisco 3845 Router) c3845-ipvoice_ivs-mz t5.bin Table 1: Test Equipment List 5 of 37

6 4. Configuring Avaya Communication Manager Customers A and B As described in Section 1, there are two instances of Avaya Communication Manager in the reference configuration. Company A contains Avaya Communication Manager (running on an S8300/G350 platform) provisioned with H.323/LRQ trunks to the IP network. Company B contains Avaya Communication Manager (running on an S8300/G700 platform) provisioned with an E1/PRI trunk to the Cisco 3845 GW. The screens in this section are accessed using Avaya Communication Manager System Access Terminal (SAT). Log in with the appropriate credentials. The license file installed on the system controls the maximum permitted. If a required feature is not enabled or there is insufficient capacity, contact an authorized Avaya sales representative to make the appropriate changes. Note: Only the Avaya Communication provisioning pertinent to H.323 trunking to the Cisco Gatekeepers and Gateways is discussed. All other Avaya Communication Manager provisioning is beyond the scope of this document. See [1] for information regarding Avaya Communication Manager provisioning Company A - H.323/LRQ Trunk Access In a typical Avaya Communication Manager to Cisco GK/GW configuration, two Signaling Group/Trunk Group pairs are provisioned. One Signaling Group has its far-end node name defined as the Cisco GK. This Signaling/Trunk Group is used by Avaya Communication Manager for LRQ exchanges with the Cisco GK. In this case Avaya Communication Manager operates as a GK. The second Signaling Group is provisioned with the far-end node field left blank. This is to allow Avaya Communications Manager to accept inbound calls from unknown locations (e.g. the Cisco GW). In this case Avaya Communication Manager operates as a GW. In the reference configuration (see Figure 1) there are two Cisco Gatekeepers, the 3825 DGK and the 3845 GK in Company B. Just as in a typical configuration described above, Signaling Group 1 is defined (and associated Trunk Group) with the far-end node of the 3825 DGK for LRQ sequences. An inbound blank Signaling Group 2 (with its associated Trunk Group) is also defined for calls to Company A from the Company B GW. However a third Signaling Group must also be defined with the far-end node of the 3845 GK. This Signaling Group is for sending LCF responses directly to the Company B GK. This Signaling Group will share Trunk Group 2 with Signaling Group 2. In this case Avaya Communication Manager operates as a GK. The reason for the third Signaling Group is as follows. When Company B calls Company A, the Company B GK will send an LRQ to the DGK. The DGK will forward the LRQ to Avaya Communication Manager in Company A, but the Company A Avaya Communication Manager must send its LCF response directly to the Company B GK, not the DGK. In order for the Company 6 of 37

7 A Avaya Communication Manager to do this, the IP address of the Company B GK must be defined in Avaya Communication Manager A. This function is performed by defining the third Signaling Group with the far-end node of the 3845 GK. Since inbound call processing is already handled by Signaling/Trunk Group 2, Signaling Group 3 can use Trunk 2 as well. Note: In the reference configuration Customer A has an H.323 telephone provisioned (x50001). The provisioning of this telephone is not included in this document System Parameters Customer Options In the OPTIONAL FEATURES form, verify the following values are set by using the display system-parameters customer-options command : Form page 2 - Maximum Administered H.323 Trunks: This field must be set to a nonzero value greater than the total number of trunk members the system requires. 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: 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: Maximum Number of DS1 Boards with Echo Cancellation: 0 0 Maximum TN2501 VAL Boards: 0 0 Maximum Media Gateway VAL Sources: 0 0 Maximum TN2602 Boards with 80 VoIP Channels: 0 0 Maximum TN2602 Boards with 320 VoIP Channels: 0 0 Maximum Number of Expanded Meet-me Conference Ports: 0 0 (NOTE: You must logoff & login to effect the permission changes.) 7 of 37

8 Form Page 3 - ARS? This value must be set to y to enable Auto Route Selection. 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 CAS Branch? n A/D Grp/Sys List Dialing Start at 01? n CAS Main? n Answer Supervision by Call Classifier? n Change COR by FAC? n ARS? y Computer Telephony Adjunct Links? n ARS/AAR Partitioning? y Cvg Of Calls Redirected Off-net? y ARS/AAR Dialing without FAC? n DCS (Basic)? y ASAI Link Core Capabilities? n DCS Call Coverage? y ASAI Link Plus Capabilities? n DCS with Rerouting? y Async. Transfer Mode (ATM) PNC? n Async. Transfer Mode (ATM) Trunking? n Digital Loss Plan Modification? n ATM WAN Spare Processor? n DS1 MSP? n ATMS? n DS1 Echo Cancellation? y Attendant Vectoring? n (NOTE: You must logoff & login to effect the permission changes.) Form page 4 - IP Trunks? This value must be set to y to enable IP trunks. display system-parameters customer-options Page 4 of 10 OPTIONAL FEATURES Emergency Access to Attendant? y Enable 'dadmin' Login? y Enhanced Conferencing? n Enhanced EC500? y Enterprise Survivable Server? n Enterprise Wide Licensing? n ESS Administration? n Extended Cvg/Fwd Admin? n External Device Alarm Admin? n Five Port Networks Max Per MCC? n Flexible Billing? n Forced Entry of Account Codes? n Global Call Classification? n Hospitality (Basic)? y Hospitality (G3V3 Enhancements)? n IP Trunks? y IP Stations? y ISDN Feature Plus? n ISDN Network Call Redirection? n ISDN-BRI Trunks? y ISDN-PRI? y Local Survivable Processor? n Malicious Call Trace? n Media Encryption Over IP? n Mode Code for Centralized Voice Mail? n Multifrequency Signaling? 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.) 8 of 37

9 System Parameters Special Applications In the SPECIAL APPLICATIONS form, verify the following values are set using the display system-parameters special-applications command: Form page 4 - (SA8507) - H245 Support With Other Vendors? This must be set to y to enable out-of-band DTMF to work correctly with Cisco. display system-parameters special-applications Page 4 of 7 SPECIAL APPLICATIONS (SA8481) - Replace Calling Party Number with ASAI ANI? n (SA8500) - Expanded UUI Display Information? n (SA8506) - Altura Interoperability (FIPN)? n (SA8507) - H245 Support With Other Vendors? y (SA8508) - Multiple Emergency Access Codes? n (SA8510) - NTT Mapping of ISDN Called-Party Subaddress IE? n (SA8517) - Authorization Code By COR? n (SA8518) - Automatic Callback with Called Party Queuing? n (SA8520) - Hoteling Application for IP Terminals? n (SA8558) - Increase Automatic MWI & VuStats (S8700 only)? n (SA8567) - PHS X-Station Mobility over IP? n (SA8569) - No Service Observing Tone Heard by Agent? n (SA8573) - Call xfer via ASAI on CAS Main? n (SA8582) - PSA Location and Display Enhancements? n (SA8587) - Networked PSA via QSIG Diversion? n (SA8589) - Background BSR Polling? n 9 of 37

10 Dial Plan In the DIAL PLAN ANALYSIS TABLE form, set the numbers to be used for local extensions, ARS trunk access, and Trunk Access Codes (TAC) using the change dialplan analysis command. In the reference configuration the following values are used. Local phone extensions In the reference configuration, five digit extensions beginning with 5 (5xxxx) is used. o Dial String 5 (first digit) o Total Length 5 (number of digits) o Call Type ext (extension) ARS access code In the reference configuration, the number 9 is used. This value is used in the feature-access-code form o Dial String 9 o Total Length 1 o Call Type dac (dial access code) Trunk Access Code In the reference configuration, a four digit number beginning with * is used. This value is used in the trunk group form. o Dial String * o Total Length 4 o Call Type dac (dial access code) change dialplan analysis Page 1 of 12 DIAL PLAN ANALYSIS TABLE Percent Full: 3 Dialed Total Call Dialed Total Call Dialed Total Call String Length Type String Length Type String Length Type 5 5 ext 9 1 dac * 4 dac Public Unknown Numbering In the NUMBERING PUBLIC/UNKNOWN FORMAT form, enter the extension information that was specified in the dial plan (Section 4.1.3) using the change public-unknown-numbering command. This permits the local extension to be used as the calling number. Ext Len Enter the number of digits used for extensions in the system dial plan (e.g. 5). Ext Code Enter the first digit of the extensions used in the system dial plan (e.g. 5). Total CPN Len Enter the same value used for Ext Len above. change public-unknown-numbering 5 Page 1 of 2 NUMBERING - PUBLIC/UNKNOWN FORMAT Total Ext Ext Trk CPN CPN Len Code Grp(s) Prefix Len Total Administered: Maximum Entries: of 37

11 Feature Access Codes In the FEATURE ACCESS CODE (FAC) form, enter access code for ARS using the change feature-access-code command. Auto Route Selection (ARS) - Access Code 1: Based on the dial plan entry (Section 4.1.3), enter an ARS access code (e.g. 9). 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: Auto Route Selection (ARS) - Access Code 1: 9 Access Code 2: Automatic Callback Activation: Deactivation: Call Forwarding Activation Busy/DA: All: Deactivation: Call Forwarding Enhanced Status: Act: Deactivation: ARS Analysis In the ARS DIGIT ANALYSIS TABLE form, set the matching dialed string that ARS will use to route the outbound call using the change ars analysis command. Dialed String Enter a matching dial pattern for the outbound call (e.g ). Total Min Enter the minimum number of digits in the matching string (e.g. 10). Total Max Enter the maximum number of digits in the matching string (e.g. 10). Route Pattern Enter the route pattern to be used (e.g. 1). Call Type Enter hnpa (home number plan area). change ars analysis Page 1 of 2 ARS DIGIT ANALYSIS TABLE Location: all Percent Full: 3 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd hnpa n 11 of 37

12 Route Pattern In the PATTERN form (e.g. route-pattern 1), specify a trunk group where the matching dialed digit string (specified in Section 4.1.6) will be sent using the change route-pattern command. Grp No Enter the trunk group number (e.g. 1). FRL Enter an appropriate Facility Restriction Level in the range 0 (lowest) to 7 (highest). change route-pattern 1 Page 1 of 3 Pattern Number: 1 Pattern Name: To_Cisco_DGK 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: 1 0 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 PARM No. Numbering LAR M 4 W Request Dgts Format Subaddress 1: y y y y y n n rest 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 12 of 37

13 Node Names In the IP NODE NAMES form, specify a node name and IP address for the Cisco 3825 Directory Gatekeeper and the Cisco 3845 Gatekeeper using the change node-names ip command. Cisco 3825 o Name Enter a name for this node (e.g. 3825_DGK). o IP Address Enter an IP address for this node (e.g ). Cisco 3845 o Name Enter a name for this node (e.g. 3845_GK). o IP Address Enter an IP address for this node (e.g ). Note: procr is a node automatically defined by Avaya Communication Manager for the S8300. The IP address of the procr is defined during Avaya Communication Manager installation (beyond the scope of this document). change node-names ip Name IP Address 3825_DGK _GK default procr IP NODE NAMES 13 of 37

14 Signaling Group for Outbound Calls to the DGK Add a signaling group specifying an identification number (e.g. 1 ). In the SIGNALING GROUP form, define a signaling group for outbound calls to the DKG (see Section 4.1) using the add signaling-group command. This signaling group is used in conjunction with the trunk group defined in Section Group Type: Enter h.323 Trunk Group For Channel Selection: Enter the trunk group associated with this signaling group. This entry can only be made after the trunk group in Section is defined. TSC Supplementary Service Protocol: Enter b. This specifies QSIG. Note: The H.323 trunks were configured as QSIG in the reference configuration, however this is not required. Near-end Node Name: Enter procr (S8300 processor). Near-end Listen Port: Enter 1719 (port used for LRQ). Far-end Node Name: Enter the node name defined for the Cisco 3825 in Section (e.g. 3825_DGK). Far-end Listen Port: Enter 1719 (port used for LRQ). LRQ Required: Enter Y. add signaling-group 1 SIGNALING GROUP Group Number: 1 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 SBS? n Max number of CA TSC: 0 IP Video? n Trunk Group for NCA TSC: Trunk Group for Channel Selection: 1 TSC Supplementary Service Protocol: b T303 Timer(sec): 10 Near-end Node Name: procr Far-end Node Name: 3825_DGK Near-end Listen Port: 1719 Far-end Listen Port: 1719 Far-end Network Region: 1 LRQ Required? y Calls Share IP Signaling Connection? n RRQ Required? n H245 Control Addr On FACility? 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 Link Loss Delay Timer(sec): 90 IP Audio Hairpinning? n Enable Layer 3 Test? n Interworking Message: PROGress DCP/Analog Bearer Capability: 3.1kHz 14 of 37

15 Trunk Group Configuration for Outbound Calls to the DKG Add a trunk group specifying an identification number (e.g. 1 ). In the TRUNK GROUP form enter the following parameters using the add trunk-group command. Note: Once the trunk group is submitted go back to the Signaling Group defined in Section and enter the Trunk Group For Channel Selection: parameter. Trunk Group Form Page 1 o Group Type: Enter isdn. o Group Name: Enter a name for the trunk (e.g. To_Cisco_DGK). o TAC: Enter a fac code based on the dial plan defined in Section (e.g. *101). o Carrier Medium: Enter H.323. o Service Type: Enter tie. add trunk-group 1 Page 1 of 21 TRUNK GROUP Group Number: 1 Group Type: isdn CDR Reports: y Group Name: To_Cisco_DGK COR: 1 TN: 1 TAC: *101 Direction: two-way Outgoing Display? n Carrier Medium: H.323 Dial Access? n Queue Length: 0 Service Type: tie Busy Threshold: 255 Night Service: Auth Code? n Member Assignment Method: manual Trunk Group Form Page 2 o Codeset to Send Display: Enter 0 (zero). Cisco is not compatible with the default value of 6. o Supplementary Service Protocol: Enter b. This specifies QSIG. Note: The H.323 trunks were configured as QSIG in the reference configuration, however this is not required. add trunk-group 1 Page 2 of 21 Group Type: isdn TRUNK PARAMETERS Codeset to Send Display: 0 Codeset to Send National IEs: 6 Charge Advice: none Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc Digital Loss Group: 18 Incoming Calling Number - Delete: Insert: Format: Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 15 of 37

16 Trunk Group Form Page 3 o Send Name: Enter y. o Send Calling Number: Enter y. add trunk-group 1 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: y Send Calling Number: y Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? n Suppress # Outpulsing? n Format: public UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send 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 Trunk Group Form Page 5 o Port Enter IP. Once the form is submitted the word IP will be replaced with Txxxxx where xxxxx is the number of the next available H.323 trunk member. o Sig Grp Enter the associated signaling group number defined in Section (e.g. 1 ). add trunk-group 1 Page 5 of 21 TRUNK GROUP Administered Members (min/max): 1/5 GROUP MEMBER ASSIGNMENTS Total Administered Members: 5 Port Name Night Sig Grp 1: IP 1 2: IP 1 3: IP 1 4: IP 1 5: IP 1 16 of 37

17 Signaling Group for Inbound Calls (Blank) Add a signaling group specifying an identification number (e.g. 2 ). In the SIGNALING GROUP form, define a signaling group for inbound calls with a blank far-end node field (see Section 4.1) using the add signaling-group command. This signaling group is used in conjunction with the trunk group defined in Section Group Type: Enter h.323 Trunk Group For Channel Selection: Enter the trunk group associated with this signaling group. This entry can only be made after the trunk group in Section is defined. TSC Supplementary Service Protocol: Enter b. This specifies QSIG. Near-end Node Name: Enter procr (S8300 processor). Near-end Listen Port: Enter 1720 Far-end Node Name: Leave this field blank. Far-end Listen Port: Leave this field blank. LRQ Required: Enter N. add signaling-group 2 SIGNALING GROUP Group Number: 2 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 SBS? n Max number of CA TSC: 0 IP Video? n Trunk Group for NCA TSC: Trunk Group for Channel Selection: 2 TSC Supplementary Service Protocol: b T303 Timer(sec): 10 Near-end Node Name: procr Far-end Node Name: Near-end Listen Port: 1720 Far-end Listen Port: Far-end Network Region: 1 LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n H245 Control Addr On FACility? 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 Link Loss Delay Timer(sec): 90 IP Audio Hairpinning? n Interworking Message: PROGress DCP/Analog Bearer Capability: 3.1kHz 17 of 37

18 Trunk Group for Inbound Calls Add a trunk group specifying an identification number (e.g. 2 ). In the TRUNK GROUP form enter the following parameters using the add trunk-group command. Note: Once the trunk group is submitted go back to the Signaling Group defined in Section and enter the Trunk Group For Channel Selection: parameter. Trunk Group Form Page 1 o Group Type: Enter isdn. o Group Name: Enter a name for the trunk (e.g. From_Company_B). o TAC: Enter a fac code based on the dial plan defined in Section (e.g. *102). o Carrier Medium: Enter H.323. o Service Type: Enter tie. add trunk-group 2 Page 1 of 21 TRUNK GROUP Group Number: 2 Group Type: isdn CDR Reports: y Group Name: From_Company_B COR: 1 TN: 1 TAC: *102 Direction: two-way Outgoing Display? n Carrier Medium: H.323 Dial Access? n Queue Length: 0 Service Type: tie Busy Threshold: 255 Night Service: Auth Code? n Member Assignment Method: manual Trunk Group Form Page 2 Enter the same values as page 2 in Section Trunk Group Form Page 3 Enter the same values as page 3 in Section Trunk Group Form Page 5 o Port Enter IP. Once the form is submitted the word IP will be replaced with Txxxxx where xxxxx is the number of the next available H.323 trunk member. o Sig Grp Enter the associated signaling group number defined in Section (e.g. 2 ). add trunk-group 2 Page 5 of 21 TRUNK GROUP Administered Members (min/max): 1/10 GROUP MEMBER ASSIGNMENTS Total Administered Members: 10 Port Name Night Sig Grp 1: IP 2 2: IP 2 3: IP 2 4: IP 2 5: IP 2 18 of 37

19 Signaling Group for Outbound LCF to Cisco Company B GK Add a signaling group specifying an identification number (e.g. 3 ). In the SIGNALING GROUP form, define a signaling group for outbound LCF messages to the Company B GK (see Section 4.1) using the add signaling-group command. This signaling group is used in conjunction with the trunk group defined in Section Group Type: Enter h.323 Trunk Group For Channel Selection: Enter the trunk group associated with this signaling group. This entry can only be made after the trunk group in Section is defined. TSC Supplementary Service Protocol: Enter b. This specifies QSIG. Near-end Node Name: Enter procr (S8300 processor). Near-end Listen Port: Enter 1719 (port used for LRQ). Far-end Node Name: Enter the node name defined for the Cisco 3845 in Section (e.g. 3845_GK). Far-end Listen Port: Enter 1719 (port used for LRQ). LRQ Required: Enter y. add signaling-group 3 SIGNALING GROUP Group Number: 3 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 SBS? n Max number of CA TSC: 0 IP Video? n Trunk Group for NCA TSC: Trunk Group for Channel Selection: 2 TSC Supplementary Service Protocol: b T303 Timer(sec): 10 Near-end Node Name: procr Far-end Node Name: 3845_GK Near-end Listen Port: 1719 Far-end Listen Port: 1719 Far-end Network Region: LRQ Required? y Calls Share IP Signaling Connection? n RRQ Required? n H245 Control Addr On FACility? 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 Link Loss Delay Timer(sec): 90 IP Audio Hairpinning? n Enable Layer 3 Test? n Interworking Message: PROGress DCP/Analog Bearer Capability: 3.1kHz 19 of 37

20 Trunk Group Configuration for Outbound Calls to the DKG This is in continuation of the trunk created in Section Signaling groups 1 and 3 share this trunk group (see Section 4.1. Once the trunk group is submitted go back to the Signaling Group defined in Section and enter this trunk in the Trunk Group For Channel Selection: parameter. Change the trunk-group of the trunk defined in Section and enter the following parameters. Trunk Group Form Page 5 o Port Enter IP. Once the form is submitted the word IP will be replaced with Txxxxx where xxxxx is the number of the next available H.323 trunk member. o Sig Grp Enter the associated signaling group number defined in Section (e.g. 3 ). change trunk-group 2 Page 5 of 21 TRUNK GROUP Administered Members (min/max): 1/10 GROUP MEMBER ASSIGNMENTS Total Administered Members: 10 Port Name Night Sig Grp 1: T : T : T : T : T : IP 3 7: IP 3 8: IP 3 9: IP 3 10: IP 3 20 of 37

21 4.2. Company B - E1/PRI Trunk Access As described in Section 4.1, the Customer B location also contains Avaya Communication Manager running on an S8300 server located in an Avaya G700 Media Gateway. The S8300/G700 platform is connected to the Cisco 3845 GK/GW via an E1/PRI circuit. Note: In the reference configuration Customer B has an H.323 telephone provisioned (x40001). The provisioning of this telephone is not included in this document. See [1] for information on station provisioning System Parameters Customer Options Provision the OPTIONAL FEATURES form with the same values as used for Customer A in Section System Parameters Special Applications Provision the SPECIAL APPLICATIONS form with the same values as used for Customer A in Section of 37

22 Dial Plan In the DIAL PLAN ANALYSIS TABLE form, set the numbers to be used for local extensions, ARS trunk access, and Trunk Access Codes (TAC) using the change dialplan analysis command. In the reference configuration the following values are used. Local phone extensions In the reference configuration, five digit extensions beginning with 4 (4xxxx) is used. o Dial String 4 (first digit) o Total Length 5 (number of digits) o Call Type ext (extension) ARS access code In the reference configuration, the number 9 is used. This value is used in the feature-access-code form o Dial String 9 o Total Length 1 o Call Type dac (dial access code) Trunk Access Code In the reference configuration, a four digit number beginning with * is used. This value is used in the trunk group form. o Dial String * o Total Length 4 o Call Type dac (dial access code) change dialplan analysis Page 1 of 12 DIAL PLAN ANALYSIS TABLE Percent Full: 3 Dialed Total Call Dialed Total Call Dialed Total Call String Length Type String Length Type String Length Type 4 5 ext 9 1 dac * 4 dac 22 of 37

23 Public Unknown Numbering In the NUMBERING PUBLIC/UNKNOWN FORMAT form, enter the extension information that was specified in the dial plan (Section 4.2.3) using the change public-unknown-numbering command. Ext Len Enter the number of digits used for extensions in the system dial plan (e.g. 5). Ext Code Enter the first digit of the extensions used in the system dial plan (e.g. 4). Total CPN Len Enter the same value used for Ext Len above. change public-unknown-numbering 4 Page 1 of 2 NUMBERING - PUBLIC/UNKNOWN FORMAT Total Ext Ext Trk CPN CPN Len Code Grp(s) Prefix Len Total Administered: Maximum Entries: Feature Access Codes In the FEATURE ACCESS CODE (FAC) form, enter access code for ARS using the change feature-access-code command. Auto Route Selection (ARS) - Access Code 1: Based on the dial plan entry (Section 4.2.3), enter an ARS access code (e.g. 9). 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: Auto Route Selection (ARS) - Access Code 1: 9 Access Code 2: Automatic Callback Activation: Deactivation: Call Forwarding Activation Busy/DA: All: Deactivation: Call Forwarding Enhanced Status: Act: Deactivation: ARS Analysis In the ARS DIGIT ANALYSIS TABLE form, set the matching dialed string that ARS will use to route the outbound call using the change ars analysis command. Dialed String Enter a matching dial pattern for the outbound call (e.g ). Total Min Enter the minimum number of digits in the matching string (e.g. 10). Total Max Enter the maximum number of digits in the matching string (e.g. 10). Route Pattern Enter the route pattern to be used (e.g. 1). Call Type Enter hnpa (home number plan area). change ars analysis Page 1 of 2 23 of 37

24 ARS DIGIT ANALYSIS TABLE Location: all Percent Full: 3 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd hnpa n Route Pattern In the PATTERN form (e.g. route-pattern 1), specify a trunk group where the matching dialed digit string (specified in Section 4.2.6) will be sent using the change route-pattern command. Grp No Enter the trunk group number (e.g. 1). FRL Enter an appropriate Facility Restriction Level in the range 0 (lowest) to 7 (highest). change route-pattern 1 Page 1 of 3 Pattern Number: 1 Pattern Name: To_Cisco_DGK 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: 1 0 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 PARM No. Numbering LAR M 4 W Request Dgts Format Subaddress 1: y y y y y n n rest 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 Node Names Since there is no IP trunk defined in the system, no node-names need to be defined. 24 of 37

25 DS1 for E1 In the DS1 CIRCUIT PACK form, define the E1 facility connected to the Cisco 3845 Gateway, using the add ds1 command. The format of the command is add ds1 xxxxx, where xxxxx is the physical location of the DS1 circuit pack. In the reference configuration the DS1 circuit pack is located in the Avaya G700 Media Gateway (001) in slot V4. Location: Enter 001v4 Bit Rate: Enter Line Coding: Enter hdb3 Signaling Mode: Enter isdn-pri Connect: Enter pbx Interface: Enter peer-master Peer Protocol.: Enter Q-SIG CRC: Enter y add ds1 001v4 DS1 CIRCUIT PACK Location: 001V4 Name: E1_PRI_to_Cisco_GW Bit Rate: Line Coding: hdb3 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: alaw CRC? y Idle Code: Channel Numbering: timeslot DCP/Analog Bearer Capability: 3.1kHz T303 Timer(sec): 4 Slip Detection? n Near-end CSU Type: other Echo Cancellation? n 25 of 37

26 Signaling Group E1 PRI Add a signaling group specifying an identification number (e.g. 1 ). In the SIGNALING GROUP form, define a signaling group for the E1 circuit using the add signaling-group command. Group Type: Enter isdn-pri. Primary D-Channel: Enter xxxxx16, where xxxxx is the DS1 circuit pack location specified in Section 4.2.9, and 16 is the E1 signaling channel (e.g. 001v416). Trunk Group For Channel Selection: Enter the trunk group associated with this signaling group. This entry can only be made after the trunk group in Section is defined. TSC Supplementary Service Protocol: Enter b. This specifies QSIG. add signaling-group 1 SIGNALING GROUP Group Number: 1 Group Type: isdn-pri Associated Signaling? y Max number of NCA TSC: 0 Primary D-Channel: 001V416 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 1 TSC Supplementary Service Protocol: b Trunk Group for E1 PRI Add a trunk group specifying an identification number (e.g. 1 ) using the add trunk-group command. Note: Once the trunk group is submitted go back to the Signaling Group defined in Section and enter this trunk in the Trunk Group For Channel Selection: parameter. Trunk Group Form Page 1 o Group Type: Enter isdn. o Group Name: Enter a name for the trunk (e.g. E1_To_Cisco). o TAC: Enter a fac code based on the dial plan defined in Section (e.g. *101). o Carrier Medium: Enter PRI/BRI. o Service Type: Enter tie. add trunk-group 1 Page 1 of 21 TRUNK GROUP Group Number: 1 Group Type: isdn CDR Reports: y Group Name: E1_To_Cisco COR: 1 TN: 1 TAC: *101 Direction: two-way Outgoing Display? n 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 26 of 37

27 Trunk Group Form Page 2 o Codeset to Send Display: Enter 0 (zero). Cisco is not compatible with the default value of 6. o Supplementary Service Protocol: Enter b. This specifies QSIG. o Format: Enter pub-unk. add trunk-group 1 Page 2 of 21 Group Type: isdn TRUNK PARAMETERS Codeset to Send Display: 0 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: ascend Digital Loss Group: 13 Incoming Calling Number - Delete: Insert: Format: pub-unk Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 Administer Timers? n Trunk Group Form Page 3 o Send Name: Enter Y. o Send Calling Number: Enter Y. add trunk-group 1 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? y 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 Send EMU Visitor CPN? n Suppress # Outpulsing? n Format: unknown Outgoing Channel ID Encoding: preferred Send UUI IE? y Send UCID? y Send Codeset 6/7 LAI IE? y Apply Local Ringback? n Show ANSWERED BY on Display? y UUI IE Treatment: service-provider Replace Restricted Numbers? y Replace Unavailable Numbers? y Send Called/Busy/Connected Number: y Hold/Unhold Notifications? y Modify Tandem Calling Number? n Ds1 Echo Cancellation? n 27 of 37

28 Trunk Group Form Page 5 o Port For the first port enter xxxxx01, where xxxxx is the DS1 circuit pack location specified in Section 4.2.9, and 01 is the first available port (e.g. 001v401). o The Code field is automatically populated by the system. o Sig Grp Enter the associated signaling group number defined in Section (e.g. 1 ). Note: The number of trunk members defined must match the number of voice channels defined in the Cisco 3845 Gateway E1 controller (see Section 6). add trunk-group 1 Page 5 of 21 TRUNK GROUP Administered Members (min/max): 1/10 GROUP MEMBER ASSIGNMENTS Total Administered Members: 10 Port Code Sfx Name Night Sig Grp 1: 001V401 MM : 001V402 MM : 001V403 MM : 001V404 MM : 001V405 MM : 001V406 MM : 001V407 MM : 001V408 MM : 001V409 MM : 001V410 MM of 37

29 5. Configure Cisco 3825 Directory Gatekeeper The Cisco 3825 router is configured to be the Directory Gatekeeper (DGK) for both the Company A Avaya Communication Manager (operating as a Gatekeeper) and the Company B Cisco 3845 Gatekeeper. 3825#show run interface FastEthernet1/0 Interface to common IP network. ip address duplex auto speed auto Gatekeeper Enter Gatekeeper mode. zone local DGK-3825 directory.com Define a local domain for the Directory Gatekeeper. DGK-3825 = Zone name directory.com = Zone domain = Zone IP address (FastEthernet1/0 on 3825) zone remote GK-3845 custb.com Define a remote domain for the Customer B Gatekeeper. GK-3845 = Zone name custb.com = Zone domain = Zone IP address (FastEthernet port of Cisco 3845) 1719 = Port for LRQ zone remote CustA-CM custa.com Define a remote domain for the Company A Avaya Communication Manager (Gatekeeper). CustA-CM = Zone name custa.com = Zone domain = Zone IP address (Avaya G350 Media Gateway Ethernet interface) 1719 = Port for LRQ zone prefix GK * Define the LRQ destination dial string to map to zone GK-3845 (any LRQ containing goes to Customer B). zone prefix CustA-CM * Define the LRQ destination dial string to map to zone CustA-CM (any LRQ containing goes to Customer A). lrq forward-queries add-ttl Enable LRQ forwarding. Note: After this command is entered, it will display in the configuration as lrq forward-queries add-hop-count. This should not be confused with the Cisco gatekeeper lrq hop-count command. no shutdown Enables the gatekeeper function. end 29 of 37

30 6. Configure Cisco 3845 Gatekeeper and Gateway The Cisco 3845 is configured as both a Gatekeeper and as a Gateway. The same FastEthernet interface (3/0) and IP address ( ) is used for both processes. 3845#show run isdn switch-type primary-qsig Sets the switch emulation protocol to QSIG Note: QSIG is used in this reference configuration but is not required. voice service voip Define voice over IP as the service type. h323 Define H.323 as the VoIP protocol. voice class codec 1 Define the supported voice codecs. codec preference 1 g729r8 codec preference 2 g729br8 codec preference 3 g711ulaw controller E1 4/0/0 Configure the E1 controller. pri-group timeslots 1-10,16 pri-group = Circuit type is ISDN PRI timeslots 1-10,16 = Ten voice channels are defined on the E1 circuit. Channel 16 is for signaling. Note: The number of defined voice channels must match the number of trunk members defined in the E1 Trunk Group for Customer B Avaya Communication Manager (see Section ). interface FastEthernet3/0 Interface to common IP network. ip address duplex full speed auto h323-gateway voip interface Define this interface as the Gateway interface. The router will use this IP address to register to the 3845 Gatekeeper. This IP address must match the Gatekeeper gw-type-prefix entry below. h323-gateway voip id GK-3845 ipaddr Define the IP address of the 3845 Gatekeeper process. The 3845 Gateway process will register to this address. voice-port 4/0/0:15 This E1 logical voice interface is automatically generated by the router. dial-peer voice pots This pots dial-peer defines call routing over the E1 PRI circuit to the Customer B Avaya Communication Manager. destination-pattern A called dial string matching any 10 digit 30 of 37

31 number starting with will be sent over the E1 circuit. direct-inward-dial Enables DID. port 4/0/0:15 Selects the E1 logical voice port (voice-port 4/0/0:15 listed above). forward-digits 5 Only the last five digits will be sent over the E1 as the called number. For example if the digit string is received, only digits will be forwarded over the E1 to Customer B. dial-peer voice voip This voip dial-peer defines call routing over the IP network. destination-pattern A called dial string matching any 10 digit number starting with will be sent via a RAS message to the 3845 GK. voice-class codec 1 This defines the codecs this dial-peer will use (based on voice-class codec 1 defined above). session target ras This defines the use of the RAS protocol for communicating with the 3845 GK. incoming called-number In order for the Gateway process of the Cisco router to generate out-of-band DTMF tones, a voip dial-peer must be selected via this command (any voip dial-peer can be used). The command identifies an incoming call string, in this case any 10 digit number beginning with If any calls matching that string attempt to use out-of-band DTMF, the Gateway will respond with out-of band DTMF as required. dtmf-relay h245-alphanumeric This command specifies that H.245 protocol will be used for out-of band DTMF. gateway This command activates the gateway process on the router. Gatekeeper Enter Gatekeeper mode. zone local DGK-3845 custb.com Define a local domain for the Directory Gatekeeper. DGK-3845 = Zone name custb.com = Zone domain = Zone IP address (FastEthernet3/0 on 3845) zone remote CustA-CM custa.com Define a remote domain to reach Company A. 31 of 37

32 CustA-CM = Zone name custa.com = Zone domain = Zone IP address (IP address of the Directory Gatekeeper) 1719 = Port for LRQ zone prefix CustA-CM * Defines the LRQ destination dial string to map to zone CustA-CM (any LRQ containing for Customer A, goes to the DGK). gw-type-prefix 7324* gw ipaddr Defines the LRQ destination dial string to map to the 3845 Gateway process (any LRQ containing 7324 goes to the GW for delivery to Customer B via the E1/PRI). 7324* = Matching dial string of 7324 followed by any additional digits = IP address of the 3845 Gateway process = RAS port lrq forward-queries add-ttl Enable LRQ forwarding. Note After this command is entered, it will display in the configuration as lrq forward-queries add-hop-count. This should not be confused with the Cisco gatekeeper lrq hop-count command. no shutdown Enables the gatekeeper function. end 32 of 37

33 7. Verification Steps 7.1. Customer A calls Customer B Step 1 Step 2 Step 3 Step 4 Step 5 Action Using an IP protocol analyzer, monitor the traffic from/to Avaya Communication Manager. Customer A phone x dials Observe the traffic on the IP protocol analyzer. Observe display on Customer B x40001 phone. Answer the call on Customer B Result N/A Extension on Customer B rings. Verify the following: Avaya Communication Manager sends an LRQ to the Cisco 3825 DGK. The Cisco 3845 GK responds with an LCF Avaya Communication Manager sends a Q.931 SETUP message to the Cisco 3845 GW and call setup sequence is initiated between them. Verify Customer B x40001 phone displays calling number of x (Note calling name will not be displayed). Verify 2-way talk path. 33 of 37

34 7.2. Customer B calls Customer A Step 1 Step 2 Step 3 Step 4 Step 5 Action Using an IP protocol analyzer, monitor the traffic from/to Avaya Communication Manager. Customer B phone x dials Observe the traffic on the IP protocol analyzer. Observe display on Customer A x50001 phone. Answer the call on Customer A Result N/A Extension on Customer A rings. Verify the following: Avaya Communication Manager receives an LRQ from the Cisco 3825 DGK. Avaya Communication Manager responds with an LCF to the Cisco 3845 GK. Avaya Communication Manager receives a Q.931 SETUP message from the Cisco 3845 GW and call setup sequence is initiated between them. Verify Customer A x50001 phone displays calling number of x (Note calling name will not be displayed). Verify 2-way talk path. 34 of 37

35 8. Troubleshooting The following procedures may be used to troubleshoot issues Avaya Communication Manager Commands The following commands may be issued from the SAT console. For more information see [1]. list trace tac (tac #) o This command will trace activity on a trunk corresponding with the specified tac number. Use the list trunk command to display all the trunks and their tac codes. o e.g. list trace tac *101 list trace station (station extension) o This command will trace activity on a station corresponding with the specified extension. Use the list station command to display all the stations and their extensions. o e.g. list trace station list ars route-chosen (dial string) o This command will list the ARS routing for a specified dial string. Enter the same dial string used when dialing the phone, excluding the ARS access code. o e.g. list ars route-chosen Cisco The following commands may be issued from the Cisco router console port for either the Cisco 3825 or 3845 routers. For more information see [2]. debug voip ccapi inout o This command shows how a call flows through the router. Using this debug level, you can see the call setup and teardown operations performed on both the telephony and network call legs. debug h225 q931 o This command list H.225/Q.931 activity through the router. Using this debug level, you can see the Q.931 call setup and teardown operations. debug h225 events o Key Q.931 events that occur when placing a H.323 call from one gateway to another will be displayed. debug isdn q931 o Display information about call setup and teardown of ISDN network connections (Layer 3) between the local router (user side) and the network. debug isdn event o Display ISDN events (call setup and teardown of ISDN network connections) occurring on the router. 35 of 37

36 9. Conclusion These Application Notes describe the configuration of Avaya Communication Manager H.323/LRQ trunking in a Cisco multi-gatekeeper Environment. Avaya Communication Manager provides Gatekeeper and Gateway functionality for one location via H.323/LRQ trunks. A Cisco Gatekeeper and a Cisco Gateway are located in a second location. In the second site, the Cisco Gateway provides access via E1/PRI to a second Avaya Communication Manager. A Cisco Directory Gatekeeper is located in the common IP network providing call directory service for both locations. Interoperability testing included verification of successful bi-directional calls. 10. References The following references can be found at [1] Administrator Guide for Avaya Communication Manager, , Issue 3.1, February The following references can be found at [2] Cisco IOS Debug Command Reference, Release 12.4T. [3] Cisco Unified CallManager Release 5.0-PBX Interoperability: Avaya Definity G3 MV1.3 to a Cisco Catalyst 6000 using CMME1 QSIG, August 23, [4] Configuring Basic Gatekeeper Call Admission Control, Document ID: 21030, 24/09/ of 37