H.323 IP Trunk Configuration Between an Avaya™ S8700 Media Server with an Avaya™ G600 Media Gateway and Avaya™ Interactive Response (IR) - Issue 1.0
Abstract
These Application Notes describe the system configuration parameters required to configure an H.323 IP trunk between an Avaya™ S8700 Media Server with an Avaya™ G600 Media Gateway and an Avaya Interactive Response (IR) system. Avaya IR Release 1.0 supports up to 93 Voice over IP (VoIP) channels completely transparent to Avaya IR applications.
1. Introduction These Application Notes describe the basic administration steps necessary to interconnect an Avaya™ S8700 Media Server with an Avaya™ G600 Media Gateway and an Avaya™ Interactive Response (IR) system via an H.323 IP trunk. Avaya IR is the next generation Avaya™ Interactive Voice Response (IVR) system for developing advanced customer self-service solutions. Trunks are commonly used by PBX switches to communicate with each other. Among the many types of trunks, the most widely used types are Central Office (CO) trunks, which provide connections to the public network through a central office, and tie trunks, which provide connections between switches in a private network. Although the Avaya IR Interactive Voice Response (IVR) system is not a switch, it acts as an adjunct capable of connecting to a PBX via H.323 IP trunks. The Avaya IR VoIP functionality is a new feature introduced in the Avaya IR Release 1.0 platform. H.323 IP trunks allow ISDN-PRI equivalent tie trunks to be defined over IP networks. H.323 IP trunks support ISDN trunk features such as DCS+ and QSIG, or generic tie trunk connections with other vendors’ H.323 switches. Additional signaling options are available. Please refer to the appropriate Administration for Network Connectivity Guide for additional details. The sample configuration, depicted in Figure 1, illustrates Avaya™ Interactive Response (IR) and an Avaya™ S8700 Media Server with an Avaya™ G600 Media Gateway operating in different subnets. The two server platforms are connected together via an H.323 IP trunk through a Cisco 2948 Catalyst Switch, and a Cisco 3660 router. Both the Avaya IR system and the Avaya S8700 Media Server/G600 Media Gateway were configured in the same network region. Extension 39002 is assigned to the Avaya IR, while extension 35041 is registered to the Avaya S8700 Media Server. The DHCP/TFTP server was used for IP telephone DHCP address assignment and firmware upgrade. Note: It is important to mention that interoperability between the Avaya IR and the Avaya S8700/G600 is established on basic network fundamentals, and more advanced topics such as VLAN, IP Routing, QoS, etc, are out of the scope of these Application Notes. As a result, the Cisco 2948 Catalyst switch, the Cisco3660 router, and DHCP/TFTP server configurations are not included. These Application Notes point out what parameters, other than the default parameters, need to be set to obtain a functioning network.
Figure 1: Avaya IR and Avaya S8700 H.323 IP Trunk Configuration
2. Equipment and Software Validated The following hardware and software versions were used for this configuration: Equipment Version Avaya™ Communication Manager 1.2 Avaya™ S8700 Media Server 1.2 Avaya™ G600 Media Gateway 1.2 Avaya™ 4620 IP Telephone 1.73 Avaya™ Interactive Response (IR) R1.0 Cisco 3660 Router 12.2(8)T5 Cisco Catalyst 2948 Switch 4.5(9) DHCP/TFTP Servers: Microsoft Windows 2000 Server 5.00.2195 (SP2)
3. Avaya S8700 Media Server Configuration These Application Notes assume the C-LAN and IP Media Processor (also known as MEDPRO) circuit packs in the Avaya™ G600 Media Gateway and Avaya™ S8700 Media Server have been previously administered. Furthermore, it is assumed that all customer and feature options have been previously provisioned to support IP trunks. Please refer to the appropriate Administration for Network Connectivity Guide for additional details. Note 1: The steps below assume that physical connectivity, call routing and IP trunk provisioning have been completed on the Cisco data equipment. Note 2: The Avaya IR requires that the Avaya™ Communication Manager Platform (R9.5 or higher) be equipped with a TN2302 MEDPRO card or higher. A TN799B C-LAN card or higher is also required.
3.1. Basic H.323 Trunk Administration Tasks
1. Define IP Network Region for optimal audio packet performance.
At the System Access Terminal command prompt, enter “change ip-network-
region 1” and match the parameters in Figure 2. Then apply the changes.
Note: Administrators may need to use a different network region number depending on the configuration used. Be sure the parameters are configured as follows to allow each system the ability to establish media paths. Please note that shuffling is known as “Direct IP-IP Audio Connections” by the S8700 Media Server.
S8700 Media Server ip-network-region: Codec Set = 1 Direct IP-IP Audio Connections = y IP Audio Hairpinning = y
Change ip-network-region 1 Page 1 of 2IP Network Region
Region: 1Name: Domain 1
Audio Parameters Direct IP-IP Audio Connections? yCodec Set: 1 IP Audio Hairpinning? yLocation:
UDP Port Range RTCP Enabled? yMin: 2048 RTCP Monitor Server ParametersMax: 3028 Use Default Server Parameters? y
DiffServ/TOS ParametersCall Control PHB Value: 34
VoIP Media PHB Value: 46BBE PHB Value: 43 Resource Reservation Parameters
RSVP Enabled? n802.1p/Q Enabled? n
Figure 2: Configuring the IP Network Region
2. Specify the type of codec used for voice encoding and compression/decompression.
The main difference between codecs is the compression algorithm used. Compression results in lower bandwidth requirements but also introduces delay and lowers voice quality. The Avaya IR R1.0 does not support codec compression; therefore the G.711MU codec must be used.
At the terminal command prompt, enter “change ip-codec-set 1” and match the parameters in Figure 3. Then apply the changes.
Note: Please make sure to use the same code-set number as the Codec Set configured for the ip-network region in Figure 2. Administrators may need to use a different codec-set number, if codec 1 is already being used. If this is the case, the Administrator must be sure to set the codec-set value to G.711MU (mu-law).
change ip-codec-set 1 Page 1 of 1
IP Codec Set
Codec Set: 1
Audio Silence Frames PacketCodec Suppression Per Pkt Size(ms)
3. Define the IP interface for the C-LAN and MEDPRO circuit packs being used for the H.323 IP trunk.
At the terminal command prompt, enter “change ip-interfaces” and match the parameters in Figure 4. Then apply the changes. Note: A different slot value may be needed depending on the location of the C-LAN and MedPro circuit packs.
change ip-interfaces Page 1 of 6
IP INTERFACES
Enable NetEth Pt Type Slot Code Sfx Node Name Subnet Mask Gateway Address Rgn
4. Assign node names and IP addresses to each node in the network.
At the terminal command prompt, enter “change node-names ip” and match the parameters in Figure 5. Then apply the changes. Note: The C-LAN and MEDPRO circuit packs must have unique names and IP addresses assigned in the node-names list. These values must match the node names used in step 3 for each interface. Be sure to add the IP address of the Avaya IR system VoIP card along with a unique name so that it can be provisioned in the signaling-group between the systems in Section 3.2, Step 1. Remember to use the specified names consistently throughout the remaining tasks.
1. Create a signaling group for the H.323 IP trunk connecting to the Avaya IR system.
At the terminal command prompt, enter “add signaling-group 1” and match the parameters in Figure 6. Then apply the changes.
Note: One or more signaling groups must be established for the remote Avaya IR. A different signaling-group number may be needed depending on availability. Since a trunk group has not been created, the “Trunk Group for Channel Selection” field must be left blank for now. The Near-end Node Name and the Far-end Node Name must match the values from the “Node Names” table (section 3.1, step 4). The Far-End Listen Port on the S8700 Media Server must match the Near-End Listen Port on the IR. The default port number “1720” was used for the Near-end and Far-end Listen ports. Be sure the following parameters are configured as follows:
“Group Type:” = h.323 “Supplementary Service Protocol:” = b // needed for call bridging1 “Calls Share IP Signaling Connection” = y “Direct IP-IP Audio Connections” = y “IP Audio Hairpinning” = y “LRQ Required?” = n “RRQ Required?” = n
add signaling-group 1 Page 1 of 5
SIGNALING GROUP
Group Number: 1 Group Type: h.323Remote Office? n Max number of NCA TSC: 0
Max number of CA TSC: 0Trunk Group for NCA TSC:
Trunk Group for Channel Selection:Supplementary Service Protocol: b Network Call Transfer? n
Far-end Network Region: 1LRQ Required? n Calls Share IP Signaling Connection? yRRQ Required? n
Bypass If IP Threshold Exceeded? n
Direct IP-IP Audio Connections? yIP Audio Hairpinning? y
Interworking Message: PROGress
Figure 6: Configuring the Signaling Group
1 For the Call Bridging feature to work with the Avaya IR, the Avaya PBX switch must have R10 or a later release. The “Supplementary Service with Routing” parameter must be enabled on the “QSIG Optional Feature Page” of the “system-parameters customer-options” form”.
2. Create a new trunk group for the H.323 IP trunk.
Each H.323 IP trunk group must be associated with an H.323 signaling group. At the terminal command prompt, enter “add trunk-group 1” and match the parameters shown in Figures 7 through 9. Then apply the changes.
Note: A different trunk-group number may be needed depending on availability. The parameters on page 1 of 22 (see Figure 7) that need to be changed are:
• Group Type • TAC • Carrier Medium • Service Type • Supplementary Service Protocol
add trunk-group 1 Page 1 of 22
TRUNK GROUP
Group Number: 1 Group Type: isdn CDR Reports: yGroup Name: IP Trunk to IR COR: 1 TN: 1 TAC: 101Direction: two-way Outgoing Display? y Carrier Medium: IP
Dial Access? y Busy Threshold: 99 Night Service:Queue Length: 0Service Type: tie Auth Code? n TestCall ITC: unre
Far End Test Line No:TestCall BCC: 0TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc
Trunk Hunt: cyclical QSIG Value-Added? nDigital Loss Group: 17
Calling Number - Delete: Insert: Numbering Format:Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? nAnswer Supervision Timeout: 0
Figure 7: Configuring Trunk-Group Page 1 of 22
Note: The parameters on page 2 of 22 (see Figure 8) to be changed are:
• Send Name • Send Calling Number • Send Connected Number
ACA Assignment? n Measured: none Wideband Support? nInternal Alert? n Maintenance Tests? n
Data Restriction? n NCA-TSC Trunk Member:Send Name: y Send Calling Number: y
Used for DCS? nSuppress # Outpulsing? n Numbering Format: public
Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider
Replace Restricted Numbers? nReplace Unavailable Numbers? n
Send Connected Number: ySend UUI IE? y
Send UCID? nSend Codeset 6/7 LAI IE? n
Network (Japan) Needs Connect Before Disconnect?
Figure 8: Configuring Trunk-Group Page 2 of 22
Note: Each signaling group can support up to 31 trunks. If more than 31 trunks are needed between the two switches, add a second signaling group. The parameters on page 6 of 22 (see Figure 9) to be set are:
• Port • Sig Grp
add trunk-group 1 Page 6 of 22
TRUNK GROUPAdministered Members (min/max): 1/5
GROUP MEMBER ASSIGNMENTS Total Administered Members: 5
Port Code Sfx Name Night Sig Grp1: ip p1 12: ip p2 13: ip p3 14: ip p4 15: ip p5 1
At the terminal command prompt, enter “change signaling-group 1” and change the “Trunk Group for Channel Selection” field. Be sure to change the “Trunk Group for Channel Selection” to the number of the trunk group chosen in Section 3.2, Step 2. Then apply the changes. Note: A different trunk-group value may need to be used depending on your setup. Only basic trunk connectivity has been provisioned at this point. Call routing must be administered in order to place calls between the systems using the H.323 trunk.
change signaling-group 1 Page 1 of 5SIGNALING GROUP
Group Number: 1 Group Type: h.323Remote Office? n Max number of NCA TSC: 0
Max number of CA TSC: 0Trunk Group for NCA TSC:
Trunk Group for Channel Selection: 1Supplementary Service Protocol: b
Far-end Network Region: 1LRQ Required? n Calls Share IP Signaling Connection? yRRQ Required? n
Bypass If IP Threshold Exceeded? n
Direct IP-IP Audio Connections? yIP Audio Hairpinning? y
Interworking Message: PROGress
Figure 10: Linking the Signaling Group with a Trunk Group
3.3. Administering Basic Uniform Dial Plan Call Routing Tasks This section represents one way in which 5-digit UDP dialing can be administered for interoperability with the Avaya™ IR system. Some applications may require a different routing method. Please refer to the appropriate Administration for Network Connectivity Guide for additional details.
1. Change uniform dial plan to route 39xxx numbers to the Avaya IR system.
At the terminal command prompt, enter “change uniform-dialplan 39” and match the parameters shown in Figure 11. Then apply the changes.
Note: The AAR entry created in Figure 11 tells the Avaya™ Communication Manager software to use pattern “39” when it receives a 5-digit dial string beginning with 39xxx. Setting the “Conv” field to “n” instructs the Communication Manager software to go to the Automatic Alternate Routing (AAR) Analysis table next to find a route pattern to
route the call. If the user had entered “y” in the “Conv” field, Communication Manager would check the AAR Digit Conversion table first for further conversion before going to the AAR Analysis table.
change uniform-dialplan 39UNIFORM DIAL PLAN TABLEB
Percent Full: 0
Matching Insert Node Matching Insert NodePattern Len Del Digits Net Conv Num Pattern Len Del Digits Net Conv Num39 5 0 aar n
Figure 11: Configuring the Uniform Dialing Plan
2. Change AAR Analysis to route 5-digit calls starting with 39 to the Avaya IR.
At the terminal command prompt, enter “change aar analysis 39” and match the parameters shown in Figure 12. Then apply the changes.
Note: This AAR entry created in Figure 12 tells the Communication Manager software to use route-pattern 1 when it receives a 5-digit dial string beginning with 39xxx.
change aar analysis 39 Page 1 of 2
AAR DIGIT ANALYSIS TABLEPercent Full: 3
Dialed Total Route Call Node ANIString Min Max Pattern Type Num Reqd
39 5 5 1 aar n
Figure 12: Configure AAR Analysis
3. Configure a route pattern.
At the terminal command prompt, enter “change route-pattern 1” and match the parameters in Figure 13. Then apply the changes. Note: A different route pattern may be used depending on availability. In this step, the Communication Manager software does not remove or insert any digits. The original 5-digit extension 39001 is routed over trunk-group 1.
4. Avaya IR Configuration The following IR configuration was done through the Avaya IR Web Graphical User Interface (GUI). Note: The Avaya IR should have been previously configured with Voice over IP (VoIP) licenses using the ‘RTUmod” command from the command line interface (CLI). To verify the IR system has previously been licensed to support the VoIP feature, navigate to “Configuration Management” and click on “Feature Licensing”. Step Description 1. Bring up a web browser with the IP address or DNS entry of the Avaya IR system. Click the
Step Description 3. The main management screen appears upon logging in to the Avaya IR system. To start
administering the Avaya IR system, stop the voice system by navigating to “Configuration Management” ! “System Control”. Click on “Stop Voice System” ! “Submit”:
5. Assign the Avaya IR VoIP Card parameters. Click the “Submit” button to continue. Be sure
to remember these parameters as they must match the Avaya S8700 Media Server/G600 Media Gateway IP Trunk configuration:
The following fields are displayed by the browser:
• Card - A number associated with a part of the VoIP subsystem used to group VoIP channels. This number can be from 11 to 16.
• Card IP Address - The local IP address to which to bind. This allows for support of multi-homed machines.
• Gatekeeper IP Address - The IP address of the Gatekeeper (C-LAN card). • Card Name - A unique name for the card. Limited to 9 characters in length. • Card Enabled - Whether or not the card is enabled. • Signaling Port - A local H.225 signaling port used by the X-th signaling group on the
VoIP card. There are three signaling groups, each with a maximum capacity of up to 31 channels (depending on how many have been licensed). This port must match the Far-End Listen port configured on the Avaya™ Communication Manager signaling group form.
• Low RTP Port - The lowest UDP port to be used for RTP communication. This can be a value between 0 and 65535.
• High RTP port - The highest UDP port to be used for RTP communication. This can be a value between 0 and 65535, and must be higher than the Low RTP port value.
• RTCP Monitor IP Address - The IP address of the RTCP monitor server to be sent copies of RTCP packets. If the value is set to blank, copies of the RTCP packets will not be generated by the VoIP card. The RTCP Monitor Server configured above is not part of Figure 1.
• RTCP Monitor Port - The UDP port used by the RTCP monitor to receive copies of the RTCP packets. This is a number between 0 and 65535.
• Packet Size - The RTP packet payload size in milliseconds for outgoing calls. This can be 10, 20, 30, 40, 50, or 60.
6. Start the voice system to activate the changes by navigating to “Configuration Management”
! “System Control”. Click on “Start Voice System” ! “Submit”:
2. From the Avaya S8700 Media Server SAT screen, issue the “status trunk <trunk #>” command to verify the trunk group is in the “in service/idle” state.
3. From the Avaya IR Web Administration, navigate to “Configuration Management” ! “Display Equipment”. Verify all VoIP channels are in the in service “Inserv” state and that all channels have the “*DNIS_SVC” service assigned.
4. From the Avaya IR command line interface (CLI), use the “assign service <service_name> to dnis <phone_list>” command to assign a predefined “Service Name” to DNIS extension 39002: ira(root)# assign service avftst to dnis 39002
5. From the Avaya IR command line interface (CLI), use the “display dnis” command to display
current service to DNIS assignments: ira(root)# display dnis
CALLED NUMBERS CALLING NUMBERSFROM TO FROM TO SERVICE-NAME
39002 39002 any any avftst
6. Place a call to the station assigned to Avaya IR from a telephone registered to the Avaya
S8700 Media Server/G600 Media Gateway. Verify Avaya IR answers the call and plays the predefined “avftst” service script.
6. Conclusion These Application Notes provide administrators with the basic steps necessary to provision an H.323 IP trunk between an Avaya Interactive Response (IR) and an Avaya™ S8700 Media Server. The Avaya IR VoIP feature is an alternative solution to buying T1/E1 cards for the Avaya™ Communication Manager platform and the Avaya IR system. The steps provided should be helpful for implementing most deployments, but they do not address all possible configuration scenarios.
