Abstract. AM; Reviewed: WCH/JK 2/28/2003. Solution & Interoperability Test Lab Application Notes 2003 Avaya Inc. All Rights Reserved.

Transcription

1 H.323 IP Trunk Configuration Differences Between an Avaya IP600 Internet Protocol Communication Server and Avaya G700 Media Gateway Equipped With an Avaya S8300 Media Server - Issue 1.0 Abstract These Application Notes highlight the basic H.323 IP Trunk configuration differences between DEFINITY (pre R10 releases) and the Avaya MultiVantage software platforms (release R11 and beyond). As an example, a description of the system configuration parameters required to configure an H.323 IP trunk between an Avaya G700 Media Gateway with an Avaya S8300 Media Server and an Avaya IP600 Internet Protocol Communications Server is included. 1 of 23

2 1. Introduction These Application Notes highlight the basic H.323 IP Trunk configuration differences between DEFINITY (pre R10 releases) and the Avaya MultiVantage software platforms (release R11 and beyond). Basic administration steps necessary to interconnect an Avaya G700 Media Gateway with an Avaya S8300 Media Server and an Avaya IP600 Internet Protocol Communication Server together via a H.323 IP trunk are also included. PBX switches use trunks to communicate with each other. Among the many types of trunks, the most commonly 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. 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 trunks to interconnect 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 an Avaya IP600 Server and Avaya G700 Media Gateway equipped with an Avaya S8300 Media server operating in different subnets. The two server platforms are connected together via an H.323 IP trunk through the two Avaya P580 MultiService Switches. Both Avaya gatekeepers/gateways were configured in the same network region. Extension is registered with the IP600 server in Office A, while extension is registered to the S8300 Media Server located in the G700 Media Gateway in Office B. 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 IP600 and the S8300/G700 is established on basic network fundamentals, and more advanced topics such as VLAN, IP Routing, QoS, etc, are out of the scope of this document. As a result, the Avaya P580 Switch and DHCP/TFTP Server configuration is not part of this document. These Application Notes point out what parameters, other than the default parameters, need to be set to obtain a functioning network. 2 of 23

3 S Y S M O N S Y S M O N DHCP/TFTP Servers x IP Telephone (registered to IP600) Office A IP600 Server.2.3 C-LAN MedPro.4 P5 P2.1 P3.1 P4 P580-1 Switch Office A Subnet /24 VLAN ID 32.1 P1.2 Link Subnet /24 VLAN ID 10 Office B P1 P580-2 Switch P3 S8300/G700 IP Addresses: Cajun Stack: MGP: S8300 Media Server: VoIP "v0" Resources: P2 P1/1 Office B Subnet /24 VLAN ID 16 S8300 Media Server/ G700 Media Gateway.2 x IP Telephone (registered to S8300) Figure 1: Sample IP600 and S8300 IP Trunk Configuration 2. Equipment and Software Validated The following hardware and software versions were used for this configuration: Avaya IP600 Internet Protocol Communication Server release R009c Avaya P580 MultiService Switches version Avaya S8300 Media Server version R011rl Avaya G700 Media Gateway version 1 Avaya P330 Stack Processor version Avaya IP Telephone firmware version 1.6 (registered with the S8300 Media Server) Avaya IP Telephone firmware version 1.6 (registered with the IP600 Server) DHCP/TFTP Server - 750MHz, 20GB HD, 512MB RAM, Microsoft NT 4.0 Server 3. IP600 Server Configuration via a Terminal Emulator These notes assume the C-LAN and IP Media Processor circuit packs have been previously administered. Furthermore, it is assumed that all customer and feature options have been previously administered to support IP trunks, shuffling, and hairpinning on the Avaya IP600 Server. Please refer to the appropriate Administration for Network Connectivity Guide for additional details Basic H.323 Trunk Administration Tasks 1. Define IP Network Region for optimal audio packet performance. At the terminal command prompt, enter change ip-network-region 1 and match the parameters in Figure 2. Then apply the changes. 3 of 23

4 Note 1: Administrators may need to use a different network region number depending on the configuration used. Be sure the parameters for both servers are configured as follows to allow Avaya IP Telephones registered on each system the ability to establish media paths directly. Please be aware shuffling is known as Direct IP-IP Audio Connections by the IP600 Server. IP600 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 2 Region: 1 Name: Audio Parameters Codec Set: 1 UDP Port Range Min: 2048 Max: IP Network Region DiffServ PHB Value: p/Q Enabled? n Direct IP-IP Audio Connections? y IP Audio Hairpinning? y 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 it introduces delay and lowers voice quality. 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 match the codec-set value at both ends of an H.323 IP Trunk connection. The supported codecs are: G.711MU (mu-law), G.711A (a-law), G.729, G.729A, G.729B, G.729AB, G K, G K. The ordering and availability of these codecs can be customized to fit a particular application. 4 of 23

5 Change ip-codec-set 1 IP Codec Set Codec Set: 1 Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n : G.729 n : 4: Figure 3: Configuring the IP Codec Set 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. 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 Net Eth Pt Type Slot Code Sfx Node Name Subnet Mask Gateway Address Rgn y C-LAN 01A04 TN799 C clan y MEDPRO 01A05 TN2302 medpro n N Figure 4: Configuring IP Interfaces 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 for the Avaya S8300 Media server along with a unique name so that it can be provisioned in the signaling-group between the systems in section 4.2. Remember to use the specified names consistently throughout the remaining tasks. 5 of 23

6 change node-names ip Page 1 of 1 IP NODE NAMES Name IP Address Name IP Address clan medpro procr default Figure 5: Configuring IP Node Names 5. Administer Ethernet Data Module link between the C-LAN board and the LAN. The data module associates a link number and an extension number with the C-LAN Ethernet port location. At the terminal command prompt, enter add data-module next and match the parameters in Figure 6. Then apply the changes. Note: Administrators may need to use a different data-module and C-LAN slot, depending on the particular configuration. If multiple C-LAN circuit packs are in use, the administrator may be required to change the link number. However, port 17 must be used on the C-LAN circuit pack regardless. change data-module Page 1 of 1 DATA MODULE Data Extension: Type: ethernet Port: 01A0417 Link: 1 Name: clan ip 1a04 Figure 6: Configuring the Data Module 3.2. Detailed H.323 Trunk Administration Tasks on the IP Create a signaling group for the H.323 IP trunk connecting to the Avaya S8300 Media Server. At the terminal command prompt, enter add signaling-group 1 and match the parameters in Figure 7. Then apply the changes. Note: One or more signaling groups must be established for the remote Avaya S8300 Media Server. A different signaling-group may be needed depending on the specific setup. Since a trunk group has not been created, the Trunk Group for the 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 4.1, step 3). 6 of 23

7 The Near-end Listen Port and the Far End Listen Port must be the same. The default port number 1720 was used for both the Near-end and Far-end Listen ports. The fields Calls Share IP Signaling Connection, Direct IP-IP Audio Connections and IP Audio Hairpinning fields should be enabled. add signaling-group 1 Page 1 of 5 SIGNALING GROUP Group Number: 1 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: _ Supplementary Service Protocol: a Near-end Node Name: clan Far-end Node Name: procr Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 1 LRQ Required? n Calls Share IP Signaling Connection? y RRQ Required? n Bypass If IP Threshold Exceeded? n Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress Figure 7: Configuring the Signaling Group 2. Create a new trunk group for the H.323 IP trunk. Each H.323 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 8 through 10. Then apply the changes. Note: One may need to use a different trunk-group number depending on the specific setup. The parameters on page 1 of 10 (see Figure 8) that need to be changed are: Group Type TAC Carrier Medium Service Type 7 of 23

8 add trunk-group 1 Page 1 of 10 TRUNK GROUP Group Number: 1 Group Type: isdn CDR Reports: y Group Name: IP Trunk to S8300 COR: 1 TN: 1 TAC: 101 Direction: two-way Outgoing Display? n Carrier Medium: IP Dial Access? n Busy Threshold: 99 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: unre Far End Test Line No: TestCall BCC: 0 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: a Digit Handling (in/out): enbloc/enbloc Trunk Hunt: cyclical QSIG Value-Added? n Digital Loss Group: 13 Calling Number - Delete: Insert: Numbering Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? y Answer Supervision Timeout: 0 Figure 8: Configuring Trunk-Group Page 1 of 10 Note: The parameters on page 2 of 10 (see Figure 9) that need be changed are: Send Name Send Calling Number Send Connected Number add trunk-group 1 Page 2 of 10 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? n Maintenance Tests? n Data Restriction? n NCA-TSC Trunk Member: Used for DCS? n Suppress # Outpulsing? n Outgoing Channel ID Encoding: preferred Send Name: y Send Calling Number: y UUI IE Treatment: service-provider Send UCID? n Send Codeset 6/7 LAI IE? y Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: y Network (Japan) Needs Connect Before Disconnect? n Figure 9: Configuring Trunk-Group Page 2 or 10 8 of 23

9 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 and trunk group. The parameters on page 4 of 10 (see Figure 10) which needs to be set are: Port Sig Grp. add trunk-group 1 Page 4 of 10 TRUNK GROUP Administered Members (min/max): 1/5 GROUP MEMBER ASSIGNMENTS Total Administered Members: 5 Port Code Sfx Name Night Sig Grp 1: ip p1 1 2: ip p2 1 3: ip p3 1 4: ip p4 1 5: ip p5 1 Figure 10: Configuring Trunk-Group Page 4 of Add a trunk group to the signaling group. At the terminal command prompt, enter busy signaling-group 1 to busy out the signaling group. 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 your trunk group you chose in section 4.2, step 2 then apply the changes. Note: A different trunk-group value may need to be used depending on the specific setup. Only basic trunk connectivity has been provisioned at this point. Call routing will need to be administered in order to be able to place calls between the systems using the H.323 IP trunk. 9 of 23

10 change signaling-group 1 Page 1 of 5 SIGNALING GROUP Group Number: 1 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 1 Supplementary Service Protocol: a Near-end Node Name: clan Far-end Node Name: procr Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 1 LRQ Required? n Calls Share IP Signaling Connection? y RRQ Required? n Bypass If IP Threshold Exceeded? n Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress Figure 11: Linking the Signaling Group with a Trunk Group Finally, enter release signaling-group 1 to release the signaling group Administering Basic Uniform Dial Plan (UDP) Call Routing Tasks This section represents one way in which 5-digit UDP dialing can be administered for interoperability with the Avaya S8300 Media Server. Some applications may require a different routing method. Please refer to the appropriate Administration for Network Connectivity Guide for additional details. 1. Change UDP to route 20xxx numbers to the Avaya S8300 Media Server. At the terminal command prompt, enter change udp 2 and match the parameters shown in Figure 12. Then apply the changes. Note: The UDP entry created in Figure 12 tells ACP to use UDPCode 200 when it receives a 5-digit dial string beginning with 20xxx. After ACP processes this step, the 5- digit number will become a 7-digit number. For example, if the user dialed 20010, the digit 2 is removed leaving The prefix 200 is then inserted, resulting in a 7-digit number In addition the UDPCode 200 entry instructs the ACP 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 AARCode 200, the ACP would check the AAR Digit Conversion table first for further conversion before going to the AAR Analysis table. 10 of 23

11 Change udp 2 Page 1 of 2 UNIFORM DIALING PLAN Ext Codes: 2ddxx Ext Code: 2xxxx Type: dd Type dd Type dd Type dd Type dd Type 0x: UDPCode 200 1x: 2x: 3x: 4x: 00: 10: 20: 30: 40: 01: 11: 21: 31: 41: 02: 12: 22: 32: 42: 03: 13: 23: 33: 43: 04: 14: 24: 34: 44: 05: 15: 25: 35: 45: 06: 16: 26: 36: 46: Figure 12: Configuring the Uniform Dialing Plan 2. Change AAR Analysis to route 7-digit calls starting with 200 to the Avaya S8300 Media Server. At the terminal command prompt, enter change aar analysis 200 and match the parameters shown in Figure 13. Apply the changes. Note: This AAR entry created in Figure 13 tells ACP to use route-pattern 1 when it receives a 7-digit dial string beginning with 200xxxx. change aar analysis 200 AAR DIGIT ANALYSIS REPORT Dialed Total Route Call Node String Min Max Pattern Type Number aar 3. Configure a route pattern. Figure 13: Configure AAR Analysis At the terminal command prompt, enter change route-pattern 1 and match the parameters in Figure 14. Then apply the changes. Note: A different route pattern may be needed depending on availability. In this step ACP removes the leading three digits (200) and re-inserts the digit 2. For example, if the 5-digit number was dialed it would be processed as according to UDPcode 200 in Figure 12. The route pattern specified forces ACP to strip the leading three digits (200) from the 7-digit dial-string then re-insert the digit 2. The result will be the original 5-digit extension 20010, which is then routed over trunk-group of 23

12 change route-pattern 1 Page 1 of 1 Grp. FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No. Mrk Lmt List Del Digits QSIG Dgts Intw 1: n user 2: n user 3: n user 4: n user 5: n user 6: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR W Request Dgts Format Figure 14: Configure a Route Pattern 4. S8300 Media Server Configuration These notes assume the Avaya G700 Media Gateway and Avaya S8300 Media Server have been previously administered. Furthermore, it is assumed that all customer and feature options have been previously provisioned to support IP trunks, shuffling and hairpinning on the Avaya S8300 Media Server. Please refer to the appropriate Administration for Network Connectivity Guide for additional details. Note: The steps below assume that physical connectivity, call routing and IP trunk provisioning have been completed on the IP600 Server and P580 switches Basic H.323 Trunk Administration Tasks 1. Define IP Network Region for optimal audio packet performance. At the terminal command prompt, enter change ip-network-region 1 and match the parameters in Figure 15. Then apply the changes. Note: Administrators may need to use a different network region number depending on the configuration used. Be sure the parameters for both servers are configured as follows to allow Avaya IP Telephones registered on each system the ability to establish media paths directly. Please note that shuffling is known as Direct IP-IP Audio Connections by the S8300 Media Server. S8300 Media Server ip-network-region: Codec Set = 1 Direct IP-IP Audio Connections = y IP Audio Hairpinning = y 12 of 23

13 change ip-network-region 1 Page 1 of 2 IP Network Region Region: 1 Name: Domain 1 Audio Parameters Codec Set: 1 Location: UDP Port Range Min: 2048 Max: DiffServ/TOS Parameters Call Control PHB Value: 34 VoIP Media PHB Value: 46 BBE PHB Value: p/Q Enabled? n Direct IP-IP Audio Connections? y IP Audio Hairpinning? y RTCP Enabled? y RTCP Monitor Server Parameters Use Default Server Parameters? y Resource Reservation Parameters RSVP Enabled? n Figure 15: Configuring the IP Network Region 2. Specify the type of codec used for voice encoding and compression/decompression. The main difference between codecs is in the compression algorithm used. Compression results in lower bandwidth requirements but also introduces delay and lowers voice quality. At the terminal command prompt, enter change ip-codec-set 1 and match the parameters in Figure 16. 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 match the codec-set value at both ends of an H.323 IP Trunk connection. The supported codecs are: G.711MU (mu-law), G.711A (a-law), G.729, G.729A, G.729B, G.729AB, G K, G K. The ordering and availability of these codecs can be customized to fit a particular application. change ip-codec-set 1 Page 1 of 1 Codec Set: 1 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n : G.729 n : 4: 13 of 23

14 Figure 16: Configuring the IP Codec Set 3. Verify the IP interface for the Avaya S8300 Media Server processor being used for the H.323 IP trunk is enabled. The IP identity of the S8300 Media Server is configured using a Web interface through the services port of the S8300 Media Server, located in slot 1 on the left side of the G700 Media Gateway. The details of the web interface are beyond the scope of this document. Please refer to the appropriate Administration Guide for details on configuring the S8300 Media Server IP address. The S8300 Media Server processor s Ethernet interface must be enabled. Use the change ip-interfaces command to ensure that the processor Ethernet port is enabled and contains the IP information previously configured through the web interface. The IP address and Gateway address are stored in a configuration file, and are displayed, but not entered, using the command in Figure 17. change ip-interfaces Page 1 of 6 IP INTERFACES Enable Net Eth Pt Type Slot Code Sfx Node Name Subnet Mask Gateway Address Rgn y PROCR n n N Figure 17: Configuring IP Interfaces 4. Assign node names and IP addresses to the remote node in the network. At the terminal command prompt, enter change node-names ip and match the parameters in Figure 18. Then apply the changes. Note: Be sure to add the IP address of the IP600 Server C-LAN circuit pack along with its unique name so that it can be provisioned in the signaling-group in section 5.2. The naming conventions used are open, but remember to carry the names throughout the remaining tasks. change node-names ip Page 1 of 1 IP NODE NAMES Name IP Address Name IP Address default procr clan Figure 18: Configuring IP Node Names 14 of 23

15 4.2. Detailed H.323 Trunk Administration Tasks 1. Create a signaling group for the H.323 IP trunk connecting to the Avaya IP600 Server. At the terminal command prompt, enter add signaling-group 1 and match the parameters in Figure 19. Then apply the changes. Note: One or more signaling groups must be established for the remote Avaya IP600 Server. A different signaling-group may be needed depending on the specific setup. Since a trunk group has not been created, the Trunk Group for the 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 5.1, step 4). The Near-end Listen Port on the S8300 Media Server must match the Far End Listen Port on the IP600 Server. The default port number 1720 was used for both the Near-end and Far-end Listen ports. The fields Calls Share IP Signaling Connection, Direct IP-IP Audio Connections and IP Audio Hairpinning fields should be enabled. add signaling-group 1 Page 1 of 5 SIGNALING GROUP Group Number: 1 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: Supplementary Service Protocol: a Network Call Transfer? n Near-end Node Name: procr Far-end Node Name: clan Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 1 LRQ Required? n Calls Share IP Signaling Connection? y RRQ Required? n Bypass If IP Threshold Exceeded? n Figure 19: Configuring the Signaling Group 2. Create a new trunk group for the H.323 IP trunk. Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress Each H.323 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 20 through 22. Apply the changes. 15 of 23

16 Note: A different trunk-group number may need to use depending on the specific setup. The parameters on page 1 of 22 (see Figure 20) that need to be changed are: Group Type TAC Carrier Medium Service Type add trunk-group 1 Page 1 of 22 TRUNK GROUP Group Number: 1 Group Type: isdn CDR Reports: y Group Name: IP Trunk to IP600 COR: 1 TN: 1 TAC: 101 Direction: two-way Outgoing Display? n Carrier Medium: IP Dial Access? n Busy Threshold: 99 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: unre Far End Test Line No: TestCall BCC: 0 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: a Digit Handling (in/out): enbloc/enbloc Trunk Hunt: cyclical QSIG Value-Added? n Digital Loss Group: 13 Calling Number - Delete: Insert: Numbering Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? y Answer Supervision Timeout: 0 Figure 20: Configuring Trunk-Group Page 1 of 22 Note: The parameters on page 2 of 22 (see Figure 21) that need be changed are: Send Name Send Calling Number Send Connected Number 16 of 23

17 add trunk-group 1 Page 2 of 22 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? n Maintenance Tests? n Data Restriction? n NCA-TSC Trunk Member: Send Name: y Send Calling Number: y Used for DCS? n Suppress # Outpulsing? n Numbering Format: public Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: y Network (Japan) Needs Connect Before Disconnect? Figure 21: Configuring Trunk-Group Page 2 or 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 and trunk group. The parameters on page 6 of 22 (see Figure 22) which needs to be set are: Port Sig Grp. add trunk-group 1 Page 6 of 22 TRUNK GROUP Administered Members (min/max): 1/5 GROUP MEMBER ASSIGNMENTS Total Administered Members: 5 Port Code Sfx Name Night Sig Grp 1: ip p1 1 2: ip p2 1 3: ip p3 1 4: ip p4 1 5: ip p5 1 Figure 22: Configuring Trunk-Group Page 6 of Add a trunk group to the signaling group. At the terminal command prompt, enter busy signaling-group 1 to busy out the signaling group. 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 specific trunk group chosen in section 5.2, step 2. Apply the changes. 17 of 23

18 Note: A different trunk-group value may need to be used depending on the specific setup. Only basic trunk connectivity has been provisioned at this point. Call routing will need to be administered in order to be able to place calls between the systems using the H.323 trunk. change signaling-group 1 Page 1 of 5 SIGNALING GROUP Group Number: 1 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 1 Supplementary Service Protocol: a Near-end Node Name: procr Far-end Node Name: clan Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 1 LRQ Required? n Calls Share IP Signaling Connection? y RRQ Required? n Bypass If IP Threshold Exceeded? n Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress Figure 23: Linking the Signaling Group with a Trunk Group Finally, enter release signaling-group 1 to release the signaling group 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 IP600 Server. 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 400xx numbers to the Avaya IP600 Server. At the terminal command prompt, enter change uniform-dialplan 400 and match the parameters shown in Figure 24. Then apply the changes. Note: The AAR entry created in Figure 24 tells the MultiVantage software to use pattern 400 when it receives a 5-digit dial string beginning with 400xx. After MultiVantage processes this step, the 5-digit number will become a 7-digit number. For example, if the user dialed 40010, the digit 4 is removed leaving The prefix 400 is then inserted, resulting in a 7-digit number Setting the Conv field to n instructs the MultiVantage 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 18 of 23

19 field, MultiVantage would check the AAR Digit Conversion table first for further conversion before going to the AAR Analysis table. change uniform-dialplan 400 UNIFORM DIAL PLAN TABLEB Percent Full: 0 Matching Insert Node Matching Insert Node Pattern Len Del Digits Net Conv Num Pattern Len Del Digits Net Conv Num aar n Figure 24: Configuring the Uniform Dialing Plan 2. Change AAR Analysis to route 7-digit calls starting with 400 to the Avaya IP600 Server. At the terminal command prompt, enter change aar analysis 400 and match the parameters shown in Figure 25. Then apply the changes. Note: This AAR entry created in Figure 25 tells the MultiVantage software to use routepattern 1 when it receives a 7-digit dial string beginning with 400xxxx. change aar analysis 400 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Percent Full: 5 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd aar n 3. Configure a route pattern. Figure 25: Configure AAR Analysis At the terminal command prompt, enter change route-pattern 1 and match the parameters in Figure 26. Then apply the changes. Note: A different route pattern may need to be used depending on availability. In this step, the MultiVantage software removes the leading three digits (400) and re-inserts the digit 4. For example, if the 5-digit number was dialed it would be processed as according to entry 400 in Figure 24. The route pattern specified forces MultiVantage to strip the leading three digits (400) from the 7-digit dial-string then reinsert the digit 4. The result will be the original 5-digit extension 40010, which is then routed over trunk-group of 23

20 change route-pattern 1 Page 1 of 3 Pattern Number: 1 Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: n user 2: n user 3: n user 4: n user 5: n user 6: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR W Request Dgts Format Figure 26: Configure a Route Pattern 5. Basic IP Trunk Configuration Differences Between the MultiVantage and DEFINITY Software Platforms This section highlights the basic H.323 IP Trunk configuration differences between DEFINITY (pre R10 releases) and the Avaya MultiVantage software platforms (release R11 and beyond). The major difference between the two platforms is associated with the Dial Plan configuration. The table below describes the basic differences in the Dial Plan configuration: Dial Plan Configuration DEFINITY Software Command: change udp <pattern> UDP automatically deletes the first digit from the 5-digit extension dialed by design. In the UDP form, the Ext Codes field display a string of digits, x and dd. The Type field allows us to configure the switch network used to analyze the converted number. The options are: AARCode, ENPNode, Local, TempOOS, UDPCode. Calls area routed either as an extension number (local) or via its converted AARCode address, EPN number, or TempOOS (calls receive reorder). When an extension is assigned an AARCode, the call is directed to the AAR Digit Conversion Table for further conversion. If the extension is MultiVantage Software Command: change uniform-dialpan <pattern> The form has changed. Please look at Figure 24 for the new form format. UDP provides a common 3 to 7 digit dial plan length. The Del field allows us to configure the number of digits to delete before routing the call. The Insert Digits field enters the digits that replace the deleted portion of the dialed number. The Net field allows us to configure the switch network used to analyze the converted number. The options are: aar, ars, enp, ext. Calls area routed either as an extension number (ext) or via its converted AAR/ARS address, or EPN number. The Conv field allows additional digit conversion by entering y. Entering n directs the call to the 20 of 23

21 DEFINITY Software assigned an UDPCode the call is directed to the AAR Analysis Table skipping the AAR Digit Conversion Table. Figure 12 shows the UDP form format. Please consult the appropriate administration guide for more information on the Dial Plan Configuration. MultiVantage Software AAR Analysis Table, skipping the AAR Digit Conversion Table. Please consult the Administrator s Guide for Avaya MultiVantage Software for more information on the Dial Plan configuration. Table 1: Dial Plan Configuration There are two additional differences between S8300 Media Servers and IP600 Servers. IP600 Servers use MedPro circuit packs for IP media processing while the G700 Media Gateway has IP media processing integrated on the motherboard (with the option to expand capacity via MM760 media modules). Secondly, whereas the IP600 Server contains C-LAN circuit packs for terminating H.323 signaling connections, H.323 signaling connections are terminated directly on the processor Ethernet interface of the S8300 Media Server. 6. IP Telephone configuration The Avaya IP Telephones get their IP address and corresponding system initialization values from the DHCP Server. When the IP Telephones start for the first time, the following prompt appears: Ext.= #=OK New= 1. Enter the IP Telephone extension, then press # for OK, get prompt Password= #=OK 2. Enter Password (The password should match the security code entered when the station was added), then press # for OK. Note: This configuration applies to all IP Telephones. 7. Verify Connectivity Configure IP telephone to register with the C-LAN circuit pack in the Avaya IP600 Server and IP Telephone to register with the Avaya S8300 Media Server. Make sure that calls can be made between the two IP Telephones. The command status trunk <trunk #> can be used to check the trunk status. In addition, the list trace station <station #> command can be used to verify the call is routed over the right trunk. 21 of 23

22 8. Conclusion These Application Notes highlight the basic H.323 IP Trunk configuration differences between DEFINITY (pre R10 releases) and the Avaya MultiVantage software platforms (release R11 and beyond). The Application Notes also provide administrators with the basic steps necessary to provision an H.323 IP trunk between an Avaya IP600 Server and an Avaya S8300 Media Server. The steps provided should be helpful for implementing most deployments, but they do not address all possible configuration scenarios. 9. Product Documentation References! Administration for Network Connectivity, Issue 2.0, November 2000! Administrator s Guide for Avaya MultiVantage Software, Issue 4.0, May 2002! 4600 Series IP Telephone Installation Guide, Issue 1.5, Comcode , June 2001! Application Notes: Sample Stacking Configuration between the Avaya P333T-PWR Switch and the Avaya G700 Media Gateway equipped with an Avaya S8300 Media Server, Issue 1.0, April 2002! Application Notes: How to configure an H.323 IP Trunk between an Avaya IP600 IP Communications Server and an Avaya IP Office Server, Issue 1.0, May of 23

23 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 and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 23 of 23