Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Configuring Dynamic Call Admission Control (D-CAC) with Inter-Gateway Alternate Routing (IGAR) between an Avaya G450 Media Gateway and Avaya Communication Manager Over a Primary Cisco MPLS and a Secondary ISDN PRI Network. - Issue 1.0 Abstract These Application Notes present configuring Dynamic Call Admission Control (D-CAC) with Inter-Gateway Alternate Routing (IGAR) between an Avaya G450 Media Gateway and Avaya Communication Manager, over a primary Cisco MPLS and a secondary ISDN PRI network. A Main Office and Branch Office utilize the Cisco MPLS network as their primary connection path for VoIP. Should network congestion trigger the D-CAC and IGAR functions, calls between the sites will be accomplished via an ISDN PRI trunk. 1 of 33

2 1. INTRODUCTION EQUIPMENT AND SOFTWARE VALIDATED CONFIGURE THE AVAYA G450 MEDIA GATEWAY CONFIGURE AVAYA COMMUNICATION MANAGER Enable IGAR IP Network Regions IP Codec Automatic Route Selection (ARS) Route Patterns PRI Trunk DS1 Interfaces Signaling Groups Trunk Groups Incoming Call Handling Treatment Save Translations CISCO ROUTER CONFIGURATIONS Configure Cisco 3825 Router Cisco One Router Configuration Cisco 2811-Two Router Configuration VERIFICATION CONCLUSIONS of 33

3 8. REFERENCES Avaya Product Documentation Avaya Application Notes Cisco Documentation of 33

4 1. Introduction Figure 1 shows the reference network used for the verification of these Application Notes. The reference network is comprised of a Main Office and a Branch Office connected via a Multi- Protocol Label Switching (MPLS) core network. The Main Office contains an Avaya S8500 Server, an Avaya G650 Media Gateway (containing IPSI, CLAN, and MedPro cards) and Avaya 4621SW IP Telephones. The Branch Office contains an Avaya G450 Media Gateway and Avaya 4621SW IP Telephones. The Main Office uses extensions 5xxxx and the Branch Office uses extensions 6xxxx. In the reference configuration, the Avaya equipment in the Main Office is provisioned on Avaya Communication Manager in Network Region one. The Avaya equipment in the Branch Office is provisioned in Network Region 2. The MPLS core is comprised of one Cisco 3825 router and two Cisco 2811 routers (designated 2811-One and 2811-Two ). These routers function as MPLS Provider Edges (PEs) and share network routing information between each other via Border Gateway Protocol (BGP). In addition, Cisco s Enhanced Interior Gateway Routing Protocol (EIGRP) is used between the core routers to determine adjacency states. Each core router has a loopback IP address defined. These loopback addresses are used by EIGRP (see Section 5). Under normal conditions, calls between the Main and Branch locations take place over the Cisco MPLS core. If the core network traffic congestion reaches a pre-defined level, Avaya Dynamic Call Admission Control (D-CAC) and Inter Gateway Alternate Routing (IGAR) functions can be used to re-route any new calls via the PRI trunk connecting the two offices. D-CAC and IGAR are provisioned in Avaya Communication Manager via the ip-network-region form. The actual D-CAC threshold value is defined on the Avaya G450 Media Gateway. This value can be defined based on the total bandwidth used by the active calls. The number of VoIP calls supported is based on the Codec being used between Network Regions. Avaya Communication Manager will count 27 kbps for each G.729 call and 85 kbps for each G.711 call. If this D-CAC value is exceeded, then IGAR is triggered and the call is routed via the PRI trunk. 4 of 33

5 Figure 1 Reference Configuration 2. Equipment and Software Validated The following equipment and software were used to test the sample configuration. Network Component Hardware/Firmware Version Avaya S8500c Server - Avaya G650 Media Gateway IPSI TN2312BP CLAN TN799DP MedPro TN2302AP DS1 TN464HP Avaya G450 Media Gateway DS1 MM710 Avaya 4621 SW IP - HW15 FW040 HW01 FW024 HW20 FW117 HW02 FW HW05 FW019 Software Version Avaya Communication Manager 5.0 R015x a20d01b3_8.bin - Telephones (H.323) Cisco 3825 Router - c3825-spservicesk9-mz 12.3(11)T Cisco 2811 Routers - c2800nm-adventerprisek9-mz 12.4(10a) Table 1: Test Equipment List of 33

6 3. Configure the Avaya G450 Media Gateway The D-CAC value is statically configured on an interface with a priority. The number of VoIP calls supported is based on the reported D-CAC value and the Codec being used between Network Regions. Avaya Communication Manager will count 27 kbps for each G.729 call and 85 kbps for each G.711 call. In the reference configuration, the Avaya G450 Media Gateway is assigned to Network Region 2 in Avaya Communication Manager (see Section 4.2). The following commands configure an IP interface for the Avaya G450 Media Gateway and a Loopback interface that will define the D-CAC bandwidth. In the sample configuration, the D- CAC value of 100 (kbps) is configured on interface Loopback 1 with priority 255, the highest priority. This value is used by Avaya Communication Manager when determining bandwidth availability for calls between IP Network Regions (see Section 4.2). The 100 kbps bandwidth limit will only allow one G.711 call to be placed before triggering IGAR. The following commands were entered from the Avaya G450 Media Gateway Command Line Interface (CLI). Parameter values shown are specific to the reference configuration. For information on other values see [1]. 1. Configure an IP interface for the Avaya G450 Media Gateway. a. interface vlan 2 Creates the interface Vlan2. b. ip address Sets the network IP address and mask for the Avaya G450 Media Gateway. c. pmi Sets the Primary Management Interface. d. exit 2. Configure a loopback interface to define the dynamic-cac value. a. interface loopback 1 Creates the interface loopback 1. b. dynamic-cac Sets the D-CAC bandwidth to 100 kbps and the priority to 255. c. exit 3. Configure the default gateway for the Avaya G450 Media Gateway. a. ip default-gateway is the IP address of the Cisco 2811-One router. 4. After the provisioning is completed, enter the command copy run start to save the configuration on the Avaya G450 Media Gateway. Figure 2 shows the Avaya G450 Media Gateway console output from the provisioning for Steps of 33

7 interface Vlan 2 ip address pmi exit interface Loopback 1 dynamic-cac exit ip default-gateway Figure 2 Avaya G450 Media Gateway Provisioning 4. Configure Avaya Communication Manager When the IP network between two different Network Regions is not capable of delivering additional voice bearer traffic because of insufficient bandwidth, an alternate route for voice bearer may be established via IGAR, typically via a TDM trunk. IGAR activation relies on Call Admission Control to check for available bandwidth for voice bearer. One unique DID number (known as a Listed Directory Number or LDN) per Network Region is used to define the IGAR extension for that particular Network Region. In the sample configuration LDN was used for Network Region one and LDN was used for Network Region two. When triggered, IGAR will convert the LDN to a specified public number to be routed over a public network trunk (see Section 4.2). In the reference configuration a PRI trunk is used to connect the Main and Branch Offices for IGAR calls. In the reference configuration, there are two Network Regions. The Avaya equipment in the Main Office is defined in Network Region 1 and the Avaya equipment in the Branch Office is defined in Network Region 2. Since the call bandwidth is related to the codec being used, the codec form must be defined as well. The following commands were entered during an Avaya Communication Manager SAT session. Parameter values shown are specific to the reference configuration. For information on other values see [2]. 4.1 Enable IGAR 1. Enable IGAR on Avaya Communication manager a. change system-parameters features Go to page 5 of the form. b. Enable Inter-Gateway Alternate Routing? y Setting this value to y enables the IGAR feature. Figure 3 shows the Avaya Communication Manager SAT output from enabling IGAR. 7 of 33

8 change system-parameters features Page 5 of 17 FEATURE-RELATED SYSTEM PARAMETERS SYSTEM PRINTER PARAMETERS Endpoint: Lines Per Page: 60 SYSTEM-WIDE PARAMETERS Switch Name: Emergency Extension Forwarding (min): 10 Enable Inter-Gateway Alternate Routing? y Enable Dial Plan Transparency in Survivable Mode? n COR to Use for DPT: station MALICIOUS CALL TRACE PARAMETERS Apply MCT Warning Tone? n MCT Voice Recorder Trunk Group: SEND ALL CALLS OPTIONS Send All Calls Applies to: station Auto Inspect on Send All Calls? n UNIVERSAL CALL ID Create Universal Call ID (UCID)? n UCID Network Node ID: Figure 3 Avaya Communication Manager Provisioning Enable IGAR 4.2 IP Network Regions Network Regions one (Main Office) and two (Branch Office) are configured. 1. Configure Network Region 1. a. change ip-network-region 1 This opens the Network Region form. b. On page one of the form provision the field: i. Codec Set: 1 change ip-network-region 1 Page 1 of 19 IP NETWORK REGION Region: 1 Location: 1 Authoritative Domain: do.com Name: MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes Codec Set: 1 Inter-region IP-IP Direct Audio: yes UDP Port Min: 2048 IP Audio Hairpinning? n UDP Port Max: 3329 DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value: 46 Use Default Server Parameters? y Video PHB Value: P/Q PARAMETERS Call Control 802.1p Priority: 5 Audio 802.1p Priority: 5 Video 802.1p Priority: 5 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 Figure 4 Avaya Communication Manager Provisioning IP Network Region 1 Page 1 8 of 33

9 c. On page two of the form provision the following fields: i. Incoming LDN Extension: was used as the Main Office LDN (the Main Office uses 5xxxx extensions). ii. Conversion To Full Public Number Delete: 1 Insert: digit was deleted and the digits were inserted. This modifies the LDN to for trunk calls. iii. Maximum Number of Trunks To Use for IGAR: 5 The trunks created for the IGAR calls were defined with 5 channels (see Section 4.1). change ip-network-region 1 Page 2 of 19 IP NETWORK REGION INTER-GATEWAY ALTERNATE ROUTING / DIAL PLAN TRANSPARENCY Incoming LDN Extension: Conversion To Full Public Number - Delete: 1 Insert: Maximum Number of Trunks to Use for IGAR: 5 Dial Plan Transparency in Survivable Mode? n BACKUP SERVERS(IN PRIORITY ORDER) H.323 SECURITY PROFILES 1 1 challenge Allow SIP URI Conversion? y TCP SIGNALING LINK ESTABLISHMENT FOR AVAYA H.323 ENDPOINTS Near End Establishes TCP Signaling Socket? y Near End TCP Port Min: Near End TCP Port Max: Figure 5 Avaya Communication Manager Provisioning IP Network Region 1 Page 2 d. On page three of the form the first line is pre-defined (Network Region 1 can communicate with Network Region 1). On the second line define the communication between Network Regions 1 and 2 by provisioning the following fields: i. src rgn = 1 In the Network Region 1 form, Network Region 1 is always the source. ii. dst rgn = 2 Region 2 was the destination Network Region used in the reference configuration. iii. codec set = 1 iv. direct WAN = y This permits direct access between the Network Regions. v. WAN-BW-Limits Units = Dynamic This sets D-CAC to determine the bandwidth available. vi. Dyn CAC = 1 In the reference configuration the Avaya G450 Media Gateway was 9 of 33

10 defined as Media Gateway 1. Note As described previously, the Avaya G450 Media Gateway is part of Network Region 2. Therefore this field cannot be completed manually for Network Region 1. It will be populated automatically when the Network Region 2 form is completed. vii. IGAR = y This enables IGAR to this Network Region. change ip-network-region 1 Page 3 of 19 Inter Network Region Connection Management src dst codec direct WAN-BW-limits Video Dyn rgn rgn set WAN Units Total Norm Prio Shr Intervening-regions CAC IGAR y Dynamic 0 0 y 1 y Figure 6 Avaya Communication Manager Provisioning IP Network Region 1 Page 3 2. Configure Network Region 2. a. change ip-network-region 2 This opens the Network Region form. b. On page one of the form provision the field: i. Codec Set: 1 change ip-network-region 2 Page 1 of 19 IP NETWORK REGION Region: 2 Location: 1 Authoritative Domain: do.com Name: MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes Codec Set: 1 Inter-region IP-IP Direct Audio: yes UDP Port Min: 2048 IP Audio Hairpinning? n UDP Port Max: 3329 DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value: 46 Use Default Server Parameters? y Video PHB Value: P/Q PARAMETERS Call Control 802.1p Priority: 5 Audio 802.1p Priority: 5 Video 802.1p Priority: 5 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 Figure 7 Avaya Communication Manager Provisioning IP Network Region 2 Page 1 c. On page two of the form provision the following fields: i. Incoming LDN Extension: was used for the Branch Office LDN (the Branch Office uses 6xxxx extensions). 10 of 33

11 Figure 9 Avaya Communication Manager Provisioning IP Network Region 2 Page 3 11 of 33 ii. Conversion To Full Public Number Delete: 1 Insert: digit was deleted and the digits were inserted. This modifies the LDN to for trunk calls. iii. Maximum Number of Trunks To Use for IGAR: 5 The trunks created for the IGAR calls were defined with 5 channels (see Section 4.6). change ip-network-region 2 Page 2 of 19 IP NETWORK REGION INTER-GATEWAY ALTERNATE ROUTING / DIAL PLAN TRANSPARENCY Incoming LDN Extension: Conversion To Full Public Number - Delete: 1 Insert: Maximum Number of Trunks to Use for IGAR: 5 Dial Plan Transparency in Survivable Mode? n BACKUP SERVERS(IN PRIORITY ORDER) H.323 SECURITY PROFILES Allow SIP URI Conversion? y TCP SIGNALING LINK ESTABLISHMENT FOR AVAYA H.323 ENDPOINTS Near End Establishes TCP Signaling Socket? y Near End TCP Port Min: Near End TCP Port Max: Figure 8 Avaya Communication Manager Provisioning IP Network Region 2 Page 2 d. On page three of the form the first line is pre-defined (Network Region 2 can always communicate with Network Region 2). On the second line define the communication between Network Regions 2 and 1 by provisioning the fields: i. src rgn = 2 In the Network Region 2 form, Network Region 2 is always the source. ii. dst rgn = 1 The destination Network Region used in the reference configuration. iii. codec set = 1 iv. direct WAN = y This permits direct access between the Network Regions. v. WAN-BW-Limits Units = Dynamic This sets D-CAC to determine the bandwidth available. vi. Dyn CAC = 1 In the reference configuration the value 1 was specified as the Avaya G450 Media Gateway was defined as Media Gateway 1. vii. IGAR = y This enables IGAR to this Network Region. change ip-network-region 2 Page 3 of 19 Inter Network Region Connection Management src dst codec direct WAN-BW-limits Video Dyn rgn rgn set WAN Units Total Norm Prio Shr Intervening-regions CAC IGAR y Dynamic 0 0 y 1 y 2 2 1

12 4.3 IP Codec As described in Section 4.2, Network Regions 1 and 2 will use IP Codec Set change ip-codec 1 a. Audio Codec 1: G.711MU In the reference configuration the G.711MU codec was used. As described in Section 4.2, the D-CAC value defined in the Avaya G450 Media Gateway was 100 kbps. Avaya Communication Manager allocates 85 kbps for a G.711 call. Therefore by specifying a G.711 codec, D-CAC will trigger IGAR after one active call. b. Once the codec type is specified, the other fields will automatically populate. These default values were used in the reference configuration. change ip-codec-set 1 Page 1 of 2 IP Codec Set Codec Set: 1 Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n 2 20 Figure 10 Avaya Communication Manager Provisioning IP Codec Set Automatic Route Selection (ARS) IGAR uses ARS for call routing. The following screens show the ARS configuration for the Main and Branch Offices. A PRI trunk connects the Avaya G650 Media Gateway in the Main Office to the Avaya G450 Media Gateway in the Branch Office. As described in Section 4.2 LDN for Network Region 1 (Main Office) is converted to and LDN for Network Region 2 is converted to (Branch Office). Two PRI trunks are defined in Avaya Communication Manager (see Section 4.6). One trunk is used for IGAR calls from Network Region 1 to Network Region 2 ( is dialed by IGAR). The other is used for IGAR calls from Network Region 2 to Network Region 1 ( is dialed by IGAR). It is the function of ARS to take the dialed digits and direct them to the appropriate route pattern and its defined trunk. 1. Provisioning ARS for Network Region 1 to Network Region 2 IGAR calls a. change ars analysis In the reference configuration was entered because Network Region 1 will dial to access Network Region 2. i. Dialed String = is a unique string of digits that ARS will use to define a match. ii. Total Min = 10 In the reference configuration a 10 was the minimum number of digits in the dialed string. iii. Total Max = 10 In the reference configuration a 10 was the maximum number of digits in the dialed string. iv. Route Pattern = 5 v. Call Type = hnpa 12 of 33

13 change ars analysis Page 1 of 2 ARS DIGIT ANALYSIS TABLE Location: all Percent Full: 1 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd hnpa n Figure 11 Avaya Communication Manager Provisioning ARS Analysis Network Region 1 to Network-Region 2 2. Provisioning ARS for Network Region 2 to Network Region 1 IGAR calls a. change ars analysis In the reference configuration was entered because Network Region 1 will dial to access Network Region 1. i. Dialed String = is a unique string of digits that ARS will use to define a match. ii. Total Min = 10 In the reference configuration a 10 was the minimum number of digits in the dialed string. iii. Total Max = 10 In the reference configuration a 10 was the maximum number of digits in the dialed string. iv. Route Pattern = 6 v. Call Type = hnpa change ars analysis Page 1 of 2 ARS DIGIT ANALYSIS TABLE Location: all Percent Full: 1 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd hnpa n Figure 12 Avaya Communication Manager Provisioning ARS Analysis Network Region 2 to Network-Region Route Patterns Route patterns direct the dialed digits provided by ARS (see Section 4.4) to the appropriate trunk group. Route patterns 5 and 6 are defined to match trunk groups 5 and 6 (see Section 4.6). 1. Provisioning Route Pattern 5 IGAR calls from the Main Office to the Branch Office a. Change route-pattern 5 In the reference configuration route pattern 5 was used to direct the dialed string to trunk 5 for delivery to the Branch Office. i. Grp No = 5 ii. FRL = 0 iii. All other values are default. 13 of 33

14 change route-pattern 5 Page 1 of 3 Pattern Number: 5 Pattern Name: To_G450 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: 5 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 Figure 13 Avaya Communication Manager Provisioning Route Pattern 5 2. Provisioning Route Pattern 6 IGAR calls from the Branch Office to the Main Office a. Change route-pattern 6 In the reference configuration, route pattern 6 was used to direct the dialed string to trunk 6 for delivery to the Main Office. i. Grp No = 6 ii. FRL = 0 iii. All other values are default. change route-pattern 6 Page 1 of 3 Pattern Number: 6 Pattern Name: PRI_To_HDQ 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: 6 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 Figure 14 Avaya Communication Manager Provisioning Route Pattern 6 14 of 33

15 4.6 PRI Trunk As described previously, a PRI trunk connects the Main Office and the Branch Office. This trunk is used by IGAR when triggered by D-CAC due to network congestion. Even though there is a single physical PRI trunk, two trunk groups are defined in Avaya Communication Manager. One trunk group (trunk 5) is defined for when the Branch Office LDN is dialed ( ). The second trunk group (trunk 6) is defined for when the Main Office LDN is dialed ( ). Before the trunk groups can be defined, DS1 Interfaces and Signaling Groups must be provisioned on Avaya Communication Manager DS1 Interfaces DS1 interfaces define the line level attributes of the trunks. In the Main Office an Avaya TN464HP DS1 board is used in the Avaya G560 Media Gateway. In the Branch Office an Avaya MM710 DS1 board is used in the Avaya G450 Media Gateway. The Avaya Communication Manager command, list configuration all, will display these boards and their locations. The locations are used to define the DS1 interfaces. Below is the output from Avaya Communication Manager command list configuration all in the reference configuration. The location of the Main Office DS1 board is 01A05. The location of the Branch Office DS1 board is 001v2. list configuration all Page 1 SYSTEM CONFIGURATION Board Assigned Ports Number Board Type Code Vintage u=unassigned t=tti p=psa 01A00 POWER SUPPLY 655A 01A01 IP SERVER INTFC TN2312BP HW15 FW A02 CONTROL-LAN TN799DP HW01 FW024 u u u u u u u u u u u u u u u u 17 01A03 IP MEDIA PROCESSOR TN2302AP HW20 FW A05 DS1 INTERFACE TN464HP HW02 FW u u u u u u u u u u u u u u u u u u 24 u u u u u u u u 001V2 DS1 MM MM710AP HW05 FW u u u u u u u u u u u u u u u u u u 24 u u u u u u u u 01A IP SERVER INTFC TN2312BP HW15 FW Figure 15 Avaya Communication Manager Provisioning Hardware Configuration 1. Main Office DS1 a. add ds1 01a05 In the reference configuration the Main Office DS1 board is in location 01A05. i. Name: <enter a descriptive name> ii. Bit Rate: iii. Line Coding: b8zs iv. Signaling Mode = isdn-pri v. Framing Mode: esf 15 of 33

16 vi. Connect: pbx vii. Interface: network Note that since the network value is used here, the DS1 defined for the Avaya G450 Media Gateway must use an interface: user value. viii. All other values are default. add ds1 01a05 Page 1 of 2 DS1 CIRCUIT PACK Location: 01A05 Name: To_Branch Bit Rate: Line Coding: b8zs Line Compensation: 1 Framing Mode: esf Signaling Mode: isdn-pri Connect: pbx Interface: network TN-C7 Long Timers? n Country Protocol: 1 Interworking Message: PROGress Protocol Version: 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 Figure 16 Avaya Communication Manager Provisioning Main Office DS1 Interface 2. Branch Office DS1 a. add ds1 01v2 In the reference configuration the Branch Office DS1 board is in location 01v2. i. Name: <enter a descriptive name> ii. Bit Rate: iii. Line Coding: b8zs iv. Signaling Mode = isdn-pri v. Framing Mode: esf vi. Connect: pbx vii. Interface: user Note that the value user must be used here since the DS1 defined for the Avaya G650 Media Gateway used the interface: network value. viii. All other values are default add ds1 01v2 Page 1 of 2 DS1 CIRCUIT PACK Location: 001V2 Name: To_HDQ Bit Rate: Line Coding: b8zs Line Compensation: 1 Framing Mode: esf Signaling Mode: isdn-pri Connect: pbx Interface: user TN-C7 Long Timers? n Country Protocol: 1 Interworking Message: PROGress Protocol Version: 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 Figure 17 Avaya Communication Manager Provisioning Branch Office DS1 Interface 16 of 33

17 4.6.2 Signaling Groups Signaling Groups define the signaling channel used for the trunk. ISDN-PRI uses the 24 th channel for signaling. As described in Section 4.6, two trunks groups (5 and 6) must be created for the IGAR calls. Therefore a signaling group must be defined for each one. The signaling groups use the DS1 location reference. 1. Signaling Group 5 Signaling group 5 ( and trunk group 5) will be used for IGAR calls from the Main Office to the Branch Office. a. add signaling group 5 Note - In the reference configuration the Main Office DS1 board is in location 01A05. i. Group Type: isdn-pri ii. Primary D-Channel: 01a0524 iii. Trunk Group for Channel Selection: 5 Note This value can only be entered after trunk group 5 is provisioned. iv. All other values are default. add signaling-group 5 Page 1 of 5 SIGNALING GROUP Group Number: 5 Group Type: isdn-pri Associated Signaling? y Max number of NCA TSC: 0 Primary D-Channel: 01A0524 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 5 TSC Supplementary Service Protocol: a Figure 18 Avaya Communication Manager Provisioning Signaling Group 5 2. Signaling Group 6 Signaling group 6 ( and trunk group 6) will be used for IGAR calls from the Branch Office to the Main Office. a. add signaling group 6 Note - In the reference configuration the Branch Office DS1 board is in location 01v2. i. Group Type: isdn-pri ii. Primary D-Channel: 01v224 iii. Trunk Group for Channel Selection: 6 Note This value can only be entered after trunk group 6 is provisioned. iv. All other values are default. 17 of 33

18 display signaling-group 6 Page 1 of 5 SIGNALING GROUP Group Number: 6 Group Type: isdn-pri Associated Signaling? y Max number of NCA TSC: 0 Primary D-Channel: 001V224 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 6 TSC Supplementary Service Protocol: a Figure 19 Avaya Communication Manager Provisioning Signaling Group Trunk Groups As described in Section 4.6, two trunks groups (5 and 6) must be created for the IGAR calls. The signaling groups use the DS1 location reference. 1. Trunk Group 5 Trunk group 5 will be used for IGAR calls from the Main Office to the Branch Office. a. add trunk group 5 i. Page 1 of the form. 1. Group Type: isdn 2. Group Name: <enter a descriptive name> 3. TAC: Carrier Medium: PRI/BRI 5. Service Type: tie 6. All other values are default. add trunk-group 5 Page 1 of 21 TRUNK GROUP Group Number: 5 Group Type: isdn CDR Reports: y Group Name: PRI_To_Branch COR: 1 TN: 1 TAC: 105 Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI Dial Access? n 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 Figure 20 Avaya Communication Manager Provisioning Trunk Group 5- Page 1 ii. Page 5 of the form. 1. Port: 01a Sig Grp: 5 3. All other values are default. 4. Repeat steps 1 and 2, incrementing the port numbers, until five ports are defined (e.g., 01a0502, 01a0503, etc). 5. Go back to the signaling group forms and populate the Trunk Group for Channel Selection: field (see Section 4.6). 18 of 33

19 add trunk-group 5 Page 5 of 21 TRUNK GROUP Administered Members (min/max): 1/5 GROUP MEMBER ASSIGNMENTS Total Administered Members: 5 Port Code Sfx Name Night Sig Grp 1: 01A0501 TN464 H 5 2: 01A0502 TN464 H 5 3: 01A0503 TN464 H 5 4: 01A0504 TN464 H 5 5: 01A0505 TN464 H 5 Figure 21 Avaya Communication Manager Provisioning Trunk Group 5 Page 5 2. Trunk Group 6 Trunk group 6 will be used for IGAR calls from the Branch Office to the Main Office. a. add trunk group 6 i. Page 1 of the form. 1. Group Type: isdn 2. Group Name: <enter a descriptive name> 3. TAC: Carrier Medium: PRI/BRI 5. Service Type: tie 6. All other values are default. add trunk-group 6 Page 1 of 21 TRUNK GROUP Group Number: 6 Group Type: isdn CDR Reports: y Group Name: PRI_To_HDQ COR: 1 TN: 1 TAC: 106 Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI Dial Access? n 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 Figure 22 Avaya Communication Manager Provisioning Trunk Group 6 Page 1 ii. Page 5 of the form. 1. Port: 01v Sig Grp: 6 3. All other values are default. 4. Repeat steps 1 and 2, incrementing the port numbers, until five ports are defined (e.g., 01v202, 01v203, etc). 5. Go back to the signaling group forms and populate the Trunk Group for Channel Selection: field (see Section 4.6). 19 of 33

20 add trunk-group 6 Page 5 of 21 TRUNK GROUP Administered Members (min/max): 1/5 GROUP MEMBER ASSIGNMENTS Total Administered Members: 5 Port Code Sfx Name Night Sig Grp 1: 001V201 MM : 001V202 MM : 001V203 MM : 001V204 MM : 001V205 MM710 6 Figure 22 Avaya Communication Manager Provisioning Trunk Group 6 Page Incoming Call Handling Treatment When IGAR generates a call from the Main Office to the Branch Office, the destination Branch LDN is first converted to public number before being routed over the PRI trunk. Similarly when IGAR generates a call from Branch Office to the Main Office, the destination Main LDN is first converted to public number before being routed over the PRI trunk. Therefore when each destination receives the call, the digits must be converted back to the appropriate LDN so the call will be accepted. This function is performed by the receiving trunk group via the Incoming Call Handling Treatment form. 1. change inc-call-handling-trmt trunk-group 5 Define incoming call handling treatment on trunk 5 for IGAR calls coming from the Branch Office to the Main Office. a. Service/Feature: tie b. Called Length: 10 The incoming digit string is 10 digits long ( ) c. Called Number: Enter enough of the incoming digit string to make a unique match. d. Del: all Deletes all incoming digits. e. Insert: Replaces the deleted digits with the Main Office LDN. change inc-call-handling-trmt trunk-group 5 Page 1 of 30 INCOMING CALL HANDLING TREATMENT Service/ Called Called Del Insert Per Call Night Feature Len Number CPN/BN Serv tie all Figure 23 Avaya Communication Manager Provisioning Incoming Call Handling Treatment Trunk 5 20 of 33

21 2. change inc-call-handling-trmt trunk-group 6 Define incoming call handling treatment on trunk 6 for IGAR calls coming from the Main Office to the Branch Office. a. Service/Feature: tie b. Called Length: 10 The incoming digit string is 10 digits long ( ) c. Called Number: Enter enough of the incoming digit string to make a unique match. d. Del: all Deletes all incoming digits. e. Insert: Replaces the deleted digits with the Branch Office LDN. change inc-call-handling-trmt trunk-group 6 Page 1 of 30 INCOMING CALL HANDLING TREATMENT Service/ Called Called Del Insert Per Call Night Feature Len Number CPN/BN Serv tie all Figure 24 Avaya Communication Manager Provisioning Incoming Call Handling Treatment Trunk Save Translations After the provisioning is completed, enter the command save trans to save the configuration on Avaya Communication Manager. 21 of 33

22 5. Cisco Router Configurations An MPLS core comprised of one Cisco 3825 router and two Cisco 2811 routers (designated 2811-One and 2811-Two ) connect the Main Office and the Branch Office. These routers function as MPLS Provider Edges (PEs) and share network routing information between each other via Border Gateway Protocol (BGP). In addition, Cisco s Enhanced Interior Gateway Routing Protocol (EIGRP) is used between the core routers to determine adjacency states. Each core router has a loopback IP address defined. These loopback addresses are used by EIGRP. Virtual Routing and Forwarding (VRF) is defined on the core routers. VRF routing tables are generated that contain routing information specific to (and only available to) members of a particular VRF. In the reference configuration, the defined VRF is called VRFMPLS. Routing Information Protocol (RIP) is used by the Cisco 3825 router to advertise the Main Office IP addressing to VRFMPLS. The Cisco router 2811-One uses RIP to advertise the IP addressing of the Branch to VRFMPLS. The default routing tables in the core routers will contain the loopback IP addresses of the adjacent routers but not the addresses of the Main or Branch Offices. However, the VRF routing tables of the core routers will contain the IP addressing of the Main and Branch Offices. In this manner, unless a network device is part of VRFMPLS, routing to the Main and Branch Offices is not possible. 5.1 Configure Cisco 3825 Router The 3825 router connects the Main Office to the MPLS core. It provides RIP routing information to the core regarding the Main Office IP addressing ( x). This routing information is only available to members of VRFMPLS. The following commands were entered via Cisco CLI from the enable/config t access prompt. See [4] and [5] for more information. 1. Enter ip cef to enable Cisco Express Forwarding (CEF). ip cef Figure 25 Cisco 3825 Enable CEF 2. Create the VRF VRFMPLS a. Enter ip vrf VRFMPLS i. Enter rd 1:10 Create a route distinguisher ID ii. Enter route-target export 1:10 This defines the export routing to BGP. iii. Enter route-target import 1:10 This defines the import routing from BGP. iv. Enter ip vrf forwarding Enables vrf forwarding. 22 of 33

23 ip vrf VRFMPLS rd 1:10 route-target export 1:10 route-target import 1:10 ip vrf forwarding Figure 26 Cisco 3825 Create VRFMPLS 3. Configuring the IP interface to the Main Office. a. Enter interface fastethernet 1/1 i. Enter description To_Main ii. Enter ip vrf forwarding VRFMPLS This defines the interface to VRFMPLS. iii. Enter ip address This defines the IP address of the interface iv. Enter duplex full This command sets the interface to full duplex. v. Enter speed 100 This command sets the interface to 100mbps. FastEthernet1/1 description To_Main ip vrf forwarding VRFMPLS ip address duplex full speed 100 Figure 27 Cisco 3825 Configure the IP interface to the Main Office 4. Configuring the MPLS interface to core router 2811-One a. Enter interface gigabitethernet 0/0 i. Enter description To_2811_One ii. Enter ip address This defines the IP address of the interface iii. Enter media-type rj45 This command defines the interface as type rj45. iv. Enter mpls label switching ldp This command sets enables Label Distribution Protocol (LDP). v. Enter tag-switching ip This command sets enables tag-switching on the interface. interface GigabitEthernet0/0 description To_2811_One ip address media-type rj45 mpls label protocol ldp tag-switching ip Figure 28 Cisco 3825 Configure the IP interface to MPLS core router 2811-One 23 of 33

24 5. Configuring the MPLS interface to core router 2811-Two The commands are similar to Step 4. interface GigabitEthernet0/1 description To_2811_Two ip address duplex auto speed auto media-type rj45 mpls label protocol ldp tag-switching ip Figure 29 Cisco 3825 Configure the IP interface to MPLS core router 2811-Two 6. Configuring the loopback interface. a. Enter interface loopback 0 i. Enter ip address This defines the IP address of the interface. interface Loopback0 ip address Figure 30 Cisco 3825 Configure the Loopback interface. 7. Enable EIGRP routing for the core router loopback addresses. a. Enter router eigrp 10 This command enables EIGRP with a network ID of 10. i. Enter network This command defines the IP domain. ii. Enter no auto-summary This command allows disconnected subnets to be advertised in RIP. router eigrp 10 network no auto-summary Figure 31 Cisco 3825 Configure the EIGRP. 8. Enable BGP routing for the core routers including RIP and VRFMPLS. a. Enter router bgp This command enables BGPP with an autonomous system ID of i. Enter no synchronization This command allows GP to update network routes without waiting for IGP updates. ii. Enter bgp log-neighbor changes This command enables logging of Border Gateway Protocol (BGP) neighbor resets. iii. Enter neighbor remote-as Adds an entry to the BGP neighbor table for network (loopback address of core router 2811-Two). iv. Enter neighbor update-source Loopback0 Allows BGP sessions to use interface Loopback 0 for TCP connections to core router 2811-Two. v. Enter neighbor remote-as of 33

25 Adds an entry to the BGP neighbor table for network (loopback address of core router 2811-One). vi. Enter neighbor update-source Loopback0 Allows BGP sessions to use interface Loopback 0 for TCP connections to core router 2811-Two. b. Enter address-family vpnv4 Enter address family configuration mode for configuring routing sessions. i. Enter neighbor activate Enable the exchange of information with BGP neighbor router 2811-Two. ii. Enter neighbor next-hop-self Configure the router as the next hop for a BGP neighbor router 2811-Two. iii. Enter neighbor send-community both Specify that this communities attributes should be sent to BGP neighbor router 2811-Two. iv. Enter neighbor activate Enable the exchange of information with BGP neighbor router 2811-One. v. Enter neighbor next-hop-self Configure the router as the next hop for a BGP neighbor router 2811-TOne. vi. Enter neighbor send-community both Specify that this communities attributes should be sent to BGP neighbor router 2811-One. vii. Enter exit-address-family c. Enter address-family ipv4 vrf VRFMPLS Configure an BGP family for VRFMPLS. i. Enter redistribute rip Specify the BGP will redistribute RIP routing updates. ii. Enter no auto-summary To advertise and carry subnet routes in BGP. iii. Enter no synchronization Allows the Cisco IOS software to advertise a network route without waiting for the IGP. iv. Enter exit-address-family 25 of 33

26 router bgp no synchronization bgp log-neighbor-changes neighbor remote-as neighbor update-source Loopback0 neighbor remote-as neighbor update-source Loopback0 address-family vpnv4 neighbor activate neighbor next-hop-self neighbor send-community both neighbor activate neighbor next-hop-self neighbor send-community both exit-address-family address-family ipv4 vrf VRFMPLS redistribute rip no auto-summary no synchronization exit-address-family Figure 32 Cisco 3825 Configure BGP. 9. Enable the RIP advertisement of the Main Office IP network to VRFMPLS and BGP. a. Enter router rip Enables RIP protocol. b. Enter version 2 Specifies RIP version 2 to be used. c. Enter address-family ipv4 vrf VRFMPLS Enter address family configuration mode for configuring routing sessions for VRFMPLS. d. Enter redistribute bgp metric transparent Redistributes routes with BGP autonomous system ID e. Enter network Specifies the network that RIP will advertise to BGP. f. Enter no auto-summary Disable automatic summarization to perform routing between disconnected subnets. g. Enter exit-address-family router rip version 2 address-family ipv4 vrf VRFMPLS redistribute bgp metric transparent network no auto-summary exit-address-family Figure 32 Cisco 3825 Configure RIP. 26 of 33

27 5.2 Cisco One Router Configuration Cisco 2811 router 2811-One connects the Branch Office to the MPLS core. It provides RIP routing information to the core regarding the Branch Office IP addressing ( x). This routing information is only available to members of VRFMPLS. It is configured in a similar fashion as the 3825 router (Section 5.1). 2811_One# ip cef ip vrf VRFMPLS rd 1:10 route-target export 1:10 route-target import 1:10 ip vrf forwarding interface Loopback0 ip address interface FastEthernet0/0 description To_2811_Two ip address duplex full speed 100 mpls label protocol ldp mpls ip interface FastEthernet0/1 description To_G450_Media_gateway ip vrf forwarding VRFMPLS ip address duplex auto speed auto interface GigabitEthernet1/0 description MPLS_To_3825 ip address mpls label protocol ldp mpls ip router eigrp 10 network no auto-summary router rip version 2 address-family ipv4 vrf VRFMPLS redistribute bgp metric transparent network no auto-summary 27 of 33

28 exit-address-family router bgp no synchronization bgp log-neighbor-changes neighbor remote-as neighbor update-source Loopback0 neighbor remote-as neighbor update-source Loopback0 no auto-summary address-family vpnv4 neighbor activate neighbor send-community both neighbor next-hop-self neighbor activate neighbor send-community both neighbor next-hop-self exit-address-family address-family ipv4 vrf VRFMPLS redistribute rip no synchronization exit-address-family 2811_One# 2811_One# Figure 33 Cisco router 2811-One configuration. 5.3 Cisco 2811-Two Router Configuration Cisco 2811 router 2811-Two is the third router in the MPLS core. Although it does not directly connect to either the Main or Branch Offices, it does forward routing information for VRFMPLS. If the direct link between the 3825 router and router 2811-One fail, connectivity between the Main and Branch Offices would be maintained via router 2811-Two. It is configured in a similar fashion as the 2811-One router (Section 5.2) Two# ip cef ip vrf VRFMPLS rd 1:10 route-target export 1:10 route-target import 1:10 ip vrf forwarding interface Loopback0 ip address interface FastEthernet0/1 description To_2811_One 28 of 33

29 ip address duplex full speed 100 mpls label protocol ldp mpls ip interface GigabitEthernet1/0 description To_3825 ip address mpls label protocol ldp mpls ip router eigrp 10 network no auto-summary router bgp no synchronization bgp log-neighbor-changes neighbor remote-as neighbor update-source Loopback0 neighbor remote-as neighbor update-source Loopback0 no auto-summary address-family vpnv4 neighbor activate neighbor send-community both neighbor next-hop-self neighbor activate neighbor send-community both neighbor next-hop-self exit-address-family address-family ipv4 vrf VRFMPLS redistribute rip no synchronization exit-address-family 2811-Two# Figure 34 Cisco router 2811-Two configuration. 6. Verification As described in Section 3.1 and Section 3.2, 100 kbps was allocated for calls between Network Region 1 (Main Office) and Network Region 2 (Branch Office). Codec G.711MU was specified for calls between these Network Regions. Since Avaya Communication Manager allocates 85 kbps for each G.711MU call, a second G.711MU will trigger IGAR and the second call will be routed via the PRI trunk. 1. From the Avaya Communication Manager SAT console, enter the list trace tac 105 command, where 105 is the TAC code specified for trunk of 33

30 2. Place a call from the Main Office to the Branch Office. Verify that the call completes and that the PRI trunk was not used (no trace of the call is displayed). 3. With the first call active and the trunk trace still running, place a second call from the Main Office to the Branch Office. Verify that IGAR is used with the following trunk trace display: list trace tac 105 Page 1 LIST TRACE time data 10:46:49 dial route:hnpa ARS 10:46:49 route-pattern 5 preference 1 cid 0x251 10:46:49 seize trunk-group 5 member 4 cid 0x251 10:46:49 Setup digits :46:49 Calling Number & Name EXT :46:49 Proceed trunk-group 5 member 4 cid 0x251 10:46:49 tone-receiver 01AXX01 cid 0x251 10:46:49 Alert trunk-group 5 member 4 cid 0x251 10:46:49 active trunk-group 5 member 4 cid 0x251 10:46:50 IGAR active call app A trunks 5/4 & 6/4 cids 0x251 & 0x252 Figure 35 Avaya Communication Manager List Trace TAC Trunk Stop the trunk trace and from the Avaya Communication Manager SAT console, enter the list trace station x command, where x is the extension of the second Main Office phone. 5. With the first call still active, place a call from the second Main Office phone to the Branch Office. Verify that IGAR is used with the following station trace display: 30 of 33

31 list trace station Page 1 LIST TRACE time data 10:47:48 active station cid 0x253 10:47:48 G711MU ss:off ps:20 rn:1/ : : :47:48 xoip: fax:relay modem:off tty:us :2268 uid:0x2 10:47:52 dial :47:52 ring station cid 0x253 10:47:52 denial event 2332: No BW, prowler <--> MG D1=0x7f D2=0x253 10:47:52 dial route:hnpa ARS 10:47:52 term trunk-group 5 cid 0x254 10:47:52 dial route:hnpa ARS 10:47:52 route-pattern 5 preference 1 cid 0x254 10:47:52 seize trunk-group 5 member 5 cid 0x254 10:47:52 Setup digits :47:52 Calling Number & Name EXT :47:52 Proceed trunk-group 5 member 5 cid 0x254 10:47:52 tone-receiver 01AXX05 cid 0x254 10:47:52 Alert trunk-group 5 member 5 cid 0x254 10:47:52 active trunk-group 5 member 5 cid 0x254 10:47:53 IGAR active call app A trunks 5/5 & 6/5 cids 0x254 & 0x255 Figure 35 Avaya Communication Manager List Trace Station Repeat Steps 1-5 originating the calls in the Branch Office. Use the list trace tac 106 command, where 106 is the TAC code specified for trunk 6, and also trace a Branch Office station. 7. Conclusions As illustrated by these Application Notes, the Avaya G450 Media Gateway supports Dynamic Call Admission Control (D-CAC) with Inter-Gateway Alternate Routing (IGAR) to Avaya Communication Manager, over a primary Cisco MPLS and secondary PRI network. 31 of 33

32 8. References 8.1 Avaya Product Documentation The following documents can be found at [1] Administration for the Avaya G450 Media Gateway, , Issue 1, January [2] Administrator Guide for Avaya Communication Manager, , Issue 4.0, Release 5.0, January Avaya Application Notes The following documents can be found at [3] Configuring Avaya Communication Manager with Avaya Inter-Gateway Alternate Routing (IGAR) Using Avaya Dynamic Call Admission Control (D-CAC) and Respond Time Report (RTR) Features - Issue 1.0. [4] Configuring Avaya Communication Manager with Avaya G350 Media Gateway in a Cisco MPLS Networks - Issue Cisco Documentation The following document can be found at [5] Cisco IOS Multiprotocol Label Switching Configuration Guide, Release of 33

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