Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for NexTone Multiprotocol Session Controller with Avaya Communication Manager, Avaya Converged Communications Server, and Avaya H.323 and SIP Telephones - Issue 1.0 Abstract These Application Notes describe how to configure NexTone Multiprotocol Session Controller to work with Avaya Communication Manager, Avaya Converged Communications Server, and Avaya H.323 and SIP telephones. All test cases completed successfully. Information in these Application Notes has been obtained through compliance testing and additional technical discussions. Testing was conducted via the DeveloperConnection Program at the Avaya Solution and Interoperability Test Lab. 1 of 52

2 1. Introduction NexTone Multiprotocol Session Controller (MSC) is a high performance, high capacity border controller that integrates signaling and media control for SIP and H.323 protocols. The MSC FlexPeer capabilities, consisting of dynamic call admission control, SIP/H.323 interworking function, network address translation (NAT) and VoIP firewall functionality, enable carriers to flexibly and securely interconnect with other IP based carriers. The NexTone iview Management System (ivms) combines core intelligence with edge management, simplifying the provisioning and management of large-scale voice over IP (VoIP) and other of real-time IP service deployments. The network diagram in Figure 1 shows two offices. The Main Office contains an Avaya S8500 Media Server controlling a local Avaya G650 Media Gateway, and an Avaya Converged Communications Server. SIP trunks are configured between the Avaya S8500 Media Server and the Avaya Converged Communications Server. The Branch Office contains an Avaya S8300 Media Server controlling an Avaya G700 Media Gateway. In order for Avaya SIP telephones to support Avaya Communication Manager features, each SIP telephone must be administered on the Avaya S8500 Media Server as an Off-PBX-Station (OPS). The NexTone MSC is deployed at the network edge in the Main Office. One H.323 signaling group is configured between the NexTone MSC and the Avaya S8500 Media Server. Another H.323 signaling group is configured between the NexTone MSC and the Avaya S8300 Media Server. The SIP telephones in the Branch Office are registered with the Avaya Converged Communications Server via the NexTone MSC using the NexTone mirror proxy feature. The NexTone VoIP Firewall functionality will secure VoIP communication between the Main Office and the Branch Office. The NexTone iview Management System is used to configure the NexTone MSC. The NexTone iview software can be installed on a PC. 2 of 52

3 Main Office Cisco Catalyst 6509 NexTone iview Management System Branch Office Cisco 3725 Access Router Digital Phone Digital Phone H A H B SIP OPS A Avaya Communication Manager S8500 G650 Media Gateway C-LAN: SIP Trunk H.323 Trunk Eth2 NexTone MSC H.323 Trunk Eth0 Avaya Communication Manager S8300/G SIP (OPS) C H C H D SIP OPS B Ava ya Converged Communications Server SIP (OPS) D H.323 Signaling: Media Pool: Mirror Proxy: none SIP signaling : H.323 Signaling: Media Pool: SIP Proxy Server: Mirror Proxy: Figure 1: Network Configuration 3 of 52

4 2. Equipment and Software Validated Table 1 below shows the versions verified in these Application Notes. Hardware Component Avaya Converged Communications Server 2.1 (load 38) Avaya 8500 Media Server 2.2 (load 118.1) Avaya S8300 Media Server 2.2 (load 118.1) Avaya G650 Media Gateway IPSI (TN2312BP HW03) C-LAN (TN799DP HW01) MEDPRO (TN2302AP HW15) Avaya G700 Media Gateway P330 L2 Stack MGP VoIP-V0 FW021 FW015 FW Avaya 4602SW SIP Telephones 1.1 Avaya 4620SW IP Telephone Avaya 4610SW IP Telephone Avaya 4622SW IP Telephone Cisco Catalyst 6509 Layer 2 8.3(4) Cisco 3725 Access Router NexTone MSC NexTone iview Software Version (T) 4.0.1T c2 4 of 52

5 3. Configurations 3.1. Configure Avaya Communication Manager in the Main Office Configure Avaya Communication Manager to Control Avaya G650 Media Gateway This section presents configuration for the Avaya S8500 Media Server and the Avaya G650 Media Gateway. It is assumed that appropriate license and authentication files have been installed on the Avaya S8500 Media Server. It is also assumed that the control network on the Avaya S8500 Media Server has been configured to and the IPSI in the Avaya G650 Media Gateway has been configured to /24 by following standard procedures. The Avaya Communication Manager SAT screens can be accessed using telnet from a computer connected to the services port, or telnet through the control network. Use the command change system-parameters ipserver-interface to globally enable IPSI control. Set the Field IPSI Control of Port Networks to enabled. change system-parameters ipserver-interface Page 1 of 1 IP SERVER INTERFACE (IPSI) SYSTEM PARAMETERS SERVER INFORMATION IPSI Host Name Prefix: Primary Control Subnet Address: Secondary Control Subnet Address: * OPTIONS Switch Identifier: A IPSI Control of Port Networks: enabled Use the command display system-parameter features to verify that Trunk-to-Trunk Transfer is configured to all to support call transfer feature over trunks. display system-parameters features Page 1 of 15 FEATURE-RELATED SYSTEM PARAMETERS Self Station Display Enabled? n Trunk-to-Trunk Transfer: all Automatic Callback - No Answer Timeout Interval (rings): 3 The following illustrates the mapping of node names to IP addresses. CLAN and MEDPRO refer to the names of C-LAN and MEDPRO circuit packs in the Avaya G650 Media Gateway. The node name Avaya-CCS refers to the name of the Avaya Converged Communications Server and the node name msc refers to the name of the NexTone MSC (Figure 1). 5 of 52

6 change node-names ip Page 1 of 1 IP NODE NAMES Name IP Address Name IP Address Avaya-CCS CLAN MEDPRO default msc procr Use the command add cabinet < cabinet number> to add a cabinet. Cabinet Layout must be configured to G650-rack-mount-stack for the Avaya G650 Media Gateway. Use the command display cabinet to verify the configuration. display cabinet 1 CABINET CABINET DESCRIPTION Cabinet: 1 Cabinet Layout: G650-rack-mount-stack Cabinet Type: expansion-portnetwork Location: 1 Rack: Room: Floor: Building: CARRIER DESCRIPTION Carrier Carrier Type Number E not-used PN 01 D not-used PN 01 C not-used PN 01 B not-used PN 01 A G650-port PN 01 Use the command add ipserver-interface <#> to add an IPSI. Type the IPSI IP address ( in the example) in the Host field. Use the command display ipserver-interface to verify the configuration. display ipserver-interface 1 IP SERVER INTERFACE (IPSI) ADMINISTRATION - PORT NETWORK 1 IP Control? y Ignore Connectivity in Server Arbitration? n Socket Encryption? y Enable QoS? n Primary IPSI Location: 1A01 Host: DHCP ID: ipsi-a01a 6 of 52

7 Use the command list ipserver-interface to get the IPSI status information. The following screen shows that the IPSI in the Avaya G650 Media Gateway is in the active state. If any IPSI is out of service, troubleshoot the issue based on the State of Health flags. list ipserver-interface IP SERVER INTERFACE INFORMATION Port Pri/ Primary/ Primary/ Primary/ State Of Ntwk Sec Secondary Secondary Secondary Serv Control Health Num Bd Loc IP Address Host Name DHCP ID State State C P E G A ipsi-a01a IN actv-aa Use the command list configuration all to verify that the Avaya S8500 Media Server recognizes all the circuit packs in the Avaya G650 Media Gateway. 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 HW03 FW A02 CONTROL-LAN TN799DP HW01 FW015 u u u u u u u u u u u u u u u u 17 01A03 IP MEDIA PROCESSOR TN2302AP HW15 FW A04 DIGITAL LINE TN2224B u u u u u u u u u u u u u u u Use the command add data-module <ext.> for the C-LAN configuration. Set the Type field to Ethernet and the Port field to the C-LAN circuit pack (from list configuration all) with port 17. The following screen displays the C-LAN data-module configuration. display data-module 3000 DATA MODULE Data Extension: 3000 Name: G650-CLAN Type: ethernet Port: 01A0217 Link: 1 Network uses 1's for Broadcast Addresses? y 7 of 52

8 Use the command add ip-interface <board location> to add and configure the C-LAN and the MEDPRO of the Avaya G650 Media Gateway. Use the command list ip-interface or display ipinterface to verify the configuration. The C-LAN and MEDPRO are assigned to network region 1 in the sample configuration. list ip-interface IP INTERFACES Net ON Type Slot Code Sfx Node Name Subnet Mask Gateway Address Rgn VLAN y C-LAN 01A02 TN799 D CLAN n y MEDPRO 01A03 TN2302 MEDPRO n Configure H.323 Trunks on Avaya Communication Manager with NexTone MSC In order for Avaya Communication Manager to send out-of-band DTMF via H.245 messages, H245 Support With Other Vendors must be set to y in the Special Applications form. Use the command display system-parameters special-applications to verify that this is set to y. display system-parameters special-applications Page 4 of 4 SPECIAL APPLICATIONS (SA8481) - Replace Calling Party Number with ASAI ANI? n (SA8500) - Expanded UUI Display Information? n (SA8506) - Altura Interoperability (FIPN)? n (SA8507) - H245 Support With Other Vendors? y (SA8508) - Multiple Emergency Access Codes? n (SA8510) - NTT Mapping of ISDN Called-Party Subaddress IE? n Use the command add signaling-group <signaling #> to add a signaling group for the NexTone MSC. The Near-End Node Name and Far-end Node Name are configured to the C-LAN and the NexTone MSC, respectively. The Near-end Listen Port and Far-end Listen Port must be configured to 1720 for H.323 IP trunks. Direct IP-IP Audio Connections and IP Audio Hairpinning must be set to y for direct IP media paths. The DTMF over IP must be configured to out-of-band for supporting out-of-band DTMF. In order to control which codec set is used, the Far-end Network Region must be configured to a different network region from the Main Office in order to support a different codec between the Avaya S8500 Media Server and the NexTone MSC. Leave the Trunk Group for Channel Selection field to blank since a trunk group has not been configured. 8 of 52

9 add signaling-group 11 Page 1 of 5 SIGNALING GROUP Group Number: 11 Group Type: h.323 Remote Office? c Max number of NCA TSC: 0 SBS? n Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: Supplementary Service Protocol: a T303 Timer(sec): 10 Near-end Node Name: CLAN Far-end Node Name: msc Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 2 LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n H245 Control Addr On FACility? n Media Encryption? n Bypass If IP Threshold Exceeded? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress Use the command add trunk group <group #> to add an IP trunk group. Use the command display trunk-group to verify the configuration. The following screen shows the IP trunk group 11 configuration. As a standard IP trunk configuration, Group Type is configured to isdn, Carrier Medium to IP and Service Type to tie. display trunk-group 11 Page 1 of 23 TRUNK GROUP Group Number: 11 Group Type: isdn CDR Reports: y Group Name: To-S8300 COR: 1 TN: 1 TAC: 111 Direction: two-way Outgoing Display? n Carrier Medium: IP 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 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc Trunk Hunt: ascend Digital Loss Group: 18 Incoming Calling Number - Delete: Insert: Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? y Answer Supervision Timeout: 0 9 of 52

10 In order to support caller ID on H.323 IP trunks, set the Send Name and Send Calling Number to y. In the sample configuration, the Format is configured to unk-pvt. display trunk-group 11 Page 2 of 23 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: y Send Calling Number: y Used for DCS? n Suppress # Outpulsing? n Format: unk-pvt 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 Hold/Unhold Notifications? y Modify Tandem Calling Number? n Network (Japan) Needs Connect Before Disconnect? N IP trunk member port values are initially configured to ip in the Port field. The system will then assign a Txxxxx value to the port as shown below. IP trunk members are virtual ports. In the following screen, four members associated with signaling group 11 are configured. These trunk members are used for both incoming and outgoing calls. change trunk-group 11 Page 7 of 23 TRUNK GROUP Administered Members (min/max): 1/4 GROUP MEMBER ASSIGNMENTS Total Administered Members: 4 Port Code Sfx Name Night Sig Grp 1: T : T : T : T Use the command change signaling-group 11 to configure the Trunk Group for Channel Selection to of 52

11 change signaling-group 11 Page 1 of 5 SIGNALING GROUP Group Number: 11 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 SBS? n Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 11 Supplementary Service Protocol: a T303 Timer(sec): 10 Near-end Node Name: CLAN Far-end Node Name: msc Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 2 LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n H245 Control Addr On FACility? n Media Encryption? n Bypass If IP Threshold Exceeded? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress Configure SIP Trunks and OPS Stations on Avaya Communication Manager and Avaya Converged Communications Server Use the command add signaling-group <signaling #> to add SIP signaling group for the Avaya Converged Communications Server. The Near-End Node Name and Far-end Node Name are configured to the CLAN and the Avaya-CCS, respectively. As a standard configuration, the Transport Method is configured to tls, the Near-end Listen and Far-end Listen Port are set to The Far-end Domain must be configured to match the domain configuration on the Avaya Converged Communications Server. In the sample configuration, the domain is configured to avaya.com. The DTMF over IP must be configured to rtp-payload to work with the H.323 out-of-band DTMF. The Direct IP-IP Audio Connections and IP Audio Hairpinning must be set to y for direct IP media paths between SIP endpoints. add signaling-group 3 Page 1 of 1 SIGNALING GROUP Group Number: 3 Group Type: sip Transport Method: tls Near-end Node Name: CLAN Far-end Node Name: Avaya-CCS Near-end Listen Port: 5061 Far-end Listen Port: 5061 Far-end Network Region: 1 Far-end Domain: avaya.com Bypass If IP Threshold Exceeded? n DTMF over IP: rtp-payload Session Establishment Timer(min): 120 Direct IP-IP Audio Connections? y IP Audio Hairpinning? y 11 of 52

12 Use the command add trunk group <group number> to add a SIP trunk group. Use the command display trunk-group <group number> to verify the configuration. The following screen shows SIP trunk group 3 configuration. As a standard SIP trunk configuration, the Group Type is set to sip, and the Service Type is set to tie. In the sample configuration, The Signaling Group is set to 3 and the Number of Members is set to 18. display trunk-group 3 Page 1 of 22 TRUNK GROUP Group Number: 3 Group Type: sip CDR Reports: y Group Name: To-Avaya-CCS COR: 1 TN: 1 TAC: 103 Direction: two-way Outgoing Display? y Dial Access? n Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n Signaling Group: 3 Number of Members: 18 TRUNK PARAMETERS SCCAN?n Digital Loss Group: 18 Use the command add off-pbx-telephone station-mapping to add all the SIP extensions (66001, 66002, and in Figure 1) as OPS stations on Avaya Communication Manager. These SIP extensions are associated with SIP trunk group 3. When a called number matches an OPS extension, Avaya Communication Manager will place the call on the associated SIP trunk. Use the command display off-pbx-telephone station-mapping to verify the configuration. display off-pbx-telephone station-mapping Page 1 of 2 STATIONS WITH OFF-PBX TELEPHONE INTEGRATION Station Application Dial Phone Number Trunk Configuration Extension Prefix Selection Set OPS OPS OPS OPS Use the command change off-pbx-telephone feature-name-extensions to configure standard voice features. The SIP telephones can use these features by dialing the associated feature extensions. Refer to [1] for detailed information. 12 of 52

13 display off-pbx-telephone feature-name-extensions EXTENSIONS TO CALL WHICH ACTIVATE FEATURES BY NAME Active Appearance Select: Automatic Call-Back Cancel: Call Forward All: Call Forward Busy/No Answer: Call Forward Cancel: Call Park: Call Park Answer Back: Call Pick-Up: Conference on Answer: Calling Number Block: Calling Number Unblock: Directed Call Pick-Up: Drop Last Added Party: Exclusion (Toggle On/Off): Held Appearance Select: Idle Appearance Select: Last Number Dialed: Malicious Call Trace: Malicious Call Trace Cancel: Off-Pbx Call Enable: Off-Pbx Call Disable: Priority Call: Send All Calls: Send All Calls Cancel: Transfer On Hang-Up: Transfer to Voice Mail: 3.2. Configure the Avaya G700 Media Gateway in the Branch Office This section illustrates the configurations for the following components within the Avaya G700 Media Gateway. Refer to the configuration guide for details. Avaya P330 stack processor (resident on the Avaya G700 Media Gateway Layer 2 switch) G700 Media Gateway Processor (MGP) VoIP v0 Module resident on the Avaya G700 Media Gateway motherboard Avaya G700 Media Gateway Control List Use the command set interface inband on the P330 stack to configure the inband interface and use the command show interface to verify the configuration. P330-1(super)# show interface Interface Name VLAN IP address Netmask inband ppp disabled Use the command set ip route to configure a static router. Use the command show IP route to verify the routing table. The following screen shows that the default route is configured to the Cisco access router in Branch Office. P330-1(super)# show ip route Destination Gateway of 52

14 The MGP Command Line Interface (CLI) can be accessed via the session mgp command from the Avaya P330 stack. The MGP can also be accessed directly once IP settings have been assigned to the Avaya MGP. Use the command show interface on the Avaya MGP to show the mgp and the voip-v0 configuration. MG-???-1(super)# show interface INTERFACE SRC VLAN IP ADDRESS NETMASK MAC ADDRESS mgp S D-02-0D-5C voip-v0 S D C Use the command set ip route map to configure a static route for the mgp. Use the command show ip route mgp to verify the configuration. The following screen shows that the default route is configured to the Cisco router in Branch Office. MG-???-1(super)# show ip route mgp DESTINATION MASK GATEWAY INTERFACE (F/C/U) motfec0 (3/0/1710) motfec0 (101/0/0) In order to add the Avaya G700 Media Gateway to the Avaya S8300 Media Server, the serial number is required. Use the show system command to obtain its serial number. MG-???-1(super)# show system MAC Address : D-02-0D-5C Serial No : 03DR Model No : G700 HW Vintage : 00 HW Suffix : A FW Vintage : The Avaya G700 Media Gateway will be configured to register with the Avaya S8300 Media Server. The Avaya G700 Media Gateway maintains a list of controller IP addresses. In this sample configuration, the Avaya S8300 Media Server IP address is added to this list. Use the command set mgc list to configure the mgc list and the command show mgc list to show the configuration: MG-???-1(super)# show mgc list CONFIGURED MGC HOST of 52

15 Once the Avaya G700 Media Gateway has registered with its controller, the prompt will show the media gateway number assigned by the active controller. The command show mgc displays the status of the H.248 link to the controller, as well as the contents of the controller list. The following screen shows that the Avaya MGP has registered with the Avaya S8300 Media Server ( ). MG-001-1(super)# show mgc CALL CONTROLLER STATUS Registered : YES Active Controller : H248 Link Status : UP H248 Link Error Code: 0x0 CONFIGURED MGC HOST Configure Avaya Communication Manager in the Branch Office Configure Avaya Communication Manager to Control the Avaya G700 Media Gateway Use the command add media-gateway on the Avaya S8300 Media Server to add the Avaya G700 Media Gateway with the following parameters (the Serial No is obtained from the show system command on the Avaya G700 MGP CLI in Section 3.2): Type: G700 Serial No: 03DR Network Region: 1 Use the command display media-gateway to verify the registration status. The following screen shows that the Avaya G700 Media Gateway has registered with the Avaya S8300 Media Server. display media-gateway 1 MEDIA GATEWAY Number: 1 IP Address: Type: g700 FW Version/HW Vintage: /0 Name: G700GW MAC Address: 00:04:0d:02:0d:5c Serial No: 03DR Encrypt Link? y Network Region: 1 Location: 1 Registered? y Controller IP Address: Site Data: Slot Module Type Name V1: S8300 ICC MM V2: V3: MM712 DCP MM V4: MM711 ANA MM 15 of 52

16 3.3.2 Configure H.323 Trunks on Avaya Communication Manager with the NexTone MSC In Section 3.1.2, an H.323 signaling group and trunk group were configured between the Avaya S8500 Media Server and the NexTone MSC. Similar configuration should be done on the Avaya S8300 Media Server. The following shows this configuration. Use the command display system-parameters special-applications to verify that the H245 Support With Other Vendors is set to y in the Special Application form. change system-parameters special-applications Page 4 of 5 SPECIAL APPLICATIONS (SA8481) - Replace Calling Party Number with ASAI ANI? n (SA8500) - Expanded UUI Display Information? n (SA8506) - Altura Interoperability (FIPN)? n (SA8507) - H245 Support With Other Vendors? y Use the command display system-parameter features to verify that the Trunk-to-Trunk Transfer is set to all to support the call transfer feature over trunks. display system-parameters features Page 1 of 15 FEATURE-RELATED SYSTEM PARAMETERS Self Station Display Enabled? n Trunk-to-Trunk Transfer: all Automatic Callback - No Answer Timeout Interval (rings): 3 The following illustrates the mapping of node names to IP addresses. The node name msc refers to the NexTone MSC (Figure 1). change node-names ip Page 1 of 1 IP NODE NAMES Name IP Address Name IP Address MSC default procr of 52

17 Use the command display signaling-group 1 to verify the signaling group configuration with the NexTone MSC. display 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 SBS? n Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 1 Supplementary Service Protocol: a T303 Timer(sec): 10 Near-end Node Name: procr Far-end Node Name: MSC Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 2 LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n H245 Control Addr On FACility? n Media Encryption? n Bypass If IP Threshold Exceeded? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress Use the command display-trunk group 1 to verify the trunk group configuration with the NexTone MSC. display trunk-group 1 Page 1 of 23 TRUNK GROUP Group Number: 1 Group Type: isdn CDR Reports: y Group Name: To_MSC COR: 1 TN: 1 TAC: 101 Direction: two-way Outgoing Display? n Carrier Medium: IP 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 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc Trunk Hunt: ascend Digital Loss Group: 18 Incoming Calling Number - Delete: Insert: Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? y Answer Supervision Timeout: 0 17 of 52

18 display trunk-group 1 Page 2 of 23 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: y Send Calling Number: y Used for DCS? n Suppress # Outpulsing? n Format: unk-pvt 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 Hold/Unhold Notifications? y Modify Tandem Calling Number? n 3.4. Configure Avaya Converged Communications Server Refer to [2] for details for Avaya Converged Communications Server installation and administration. This section presents the related configuration for the Avaya converged Communications Server. It is assumed that The initial setup has been done by the command ccsinstaller via the Linux shell on the Avaya Converged Communications Server. In the sample configuration, the Avaya Converged Communications Server is configured with the domain name of avaya.com. Appropriate license has also been installed via the Maintenance Web interface. The IP address on the Avaya Converged Communications Server has been configured to The Avaya Converged Communications Server is configured to accept SIP endpoint registration using both the domain name (avaya.com) and IP address ( ). The Avaya Converged Communications Server can be administered via the Web interface using URL Provide appropriate user name and password to log into the Web interface. 18 of 52

19 Double click Launch Administration Web Interface for SIP Server Management. Click Media Servers Add to add the Avaya S8500 Media Server. The following screen shows the configuration. For the sample configuration, enter the IP address of the C-LAN ( ) in the Name or IP address field since DNS servers are not used in the sample configuration. 19 of 52

20 After the Avaya S8500 Media Server is added, click Media Servers List Media Server. Click Map from the List Media Servers screen, the List Media Server Address Map screen shows up: 20 of 52

21 Click Add Map In New Group, and configure a dial plan to use the SIP trunks with the Avaya S8500 Media Server. Click Add to add a map in new group. The following screen shows that the called number with prefixes 2 to 7 will be put on this SIP trunk. Click Users Add to add a user. Enter the Handle, Password, Confirm Password, First Name and Last Name. Check the Add Media Server Extension to add the user as an OPS extension. 21 of 52

22 Click Add to add the user and then the Add Media Server Extension screen will show up. Enter an OPS Extension and associate this extension with the Avaya S8500 Media Server. Click the Add to add the extension. The OPS extensions have been configured in Section on the Avaya S8500 Media Server. 22 of 52

23 3.5. Configure NexTone MSC This section provides the related MSC configuration using the NexTone iview Management System. It assumes that the appropriate user names and passwords have been provided for the NexTone iview and the NexTone MSC access. The following screen shows a default screen for the NexTone iview application. IP address is the management IP address configured on the NexTone MSC. 23 of 52

24 Double click the NexTone MSC icon, and the following screen should be displayed. Click on Load from iserver to load the configuration. The following screen shows the Database screen. Click Utilities Calling Plan to configure the Calling Plan. The following screen displays the Calling Plan configuration for the sample configuration. The Plan Name G650 is associated with the called party number 5* and 6*, and the Plan Name ACM-S8300 is associated with the called port number 2* ( * is used to match any digits). 24 of 52

25 The following screen shows a Calling Plan Route configuration. In the sample configuration, all of the call routes are set to the DNIS type and are applied to the Egress, and No Digit Strip checkbox was checked. Prefix 6 refers to the SIP phones in Main Office. Click Utilities Vnet to configure virtual networks. Double click a vnet to show the configuration. The following screen shows the vnet1 configuration. This vnet is associated with a physical interface eth2 and the default gateway is configured to the access router in the Main Office. 25 of 52

26 The following screen shows the vnet2 configuration. This vnet is associated with a physical interface eth0 and the default gateway is configured to the access router in the Branch Office. 26 of 52

27 Click Iserver Configure from the Database screen, the following screen should be displayed. Click the SIP tab to show the SIP configuration. In order for the SIP telephone C and D in the Branch Office to register with the Avaya Converged Communications Server, configure the Server Type to Stateful Proxy with the OBP, Dynamic Endpoint and NAT traversal boxes checked. Leave other settings as default. 27 of 52

28 Click the H.323 tab for the H.323 configuration. In order to work with the Avaya Communication Manager, configure the Info Trans Cap to Pass with the Route H.245, Call Routing and H.245 Tunnel boxes checked. Leave other settings as default. 28 of 52

29 Click the FCE tab for the Firewall Control Entity (FCE) configuration. The following screen shows Pool 1 and Pool 2 configuration. Pool 1 is configured with the Realm Media Address (RMA) and is associated with the media-vnet1. Pool 2 is configured with the RMA and is associated with the media-vnet2. Pools 1 and Pool 2 are configured with the port ranges , which are used for RTP and RTCP packets. 29 of 52

30 From the FCE tab, click media-vnet1 and media-vnet2 to get media-vnet1 and media-vnet2 configuration. The media-vnet1 is configured with the default gateway to the access router in the Main Office and media-vnet2 is configured with the default gateway to the access router in the Branch Office. Media-vnet1 is a virtual interface associated with interface Eth0 and mediavnet2 is a virtual interface associated with interface Eth2. For the sample configuration, VLAN ID is not set for these virtual interfaces. 30 of 52

31 The following screen shows IP/Ports configuration for Pools 1 and 2. Pool 1 is configured with IP address with a port range to Pool 2 is configured with IP address with a port range to These IP addresses and port ranges will be used as a media IP address and UDP port range for a VoIP call. Pool 1 is associated with interface media-vnet1 and Pool 2 is associated with interface media-vnet2. 31 of 52

32 Click Utilities Realm from the Database screen for the Realms configuration. The following screen shows the Realm configuration for the sample configuration. 32 of 52

33 Double click a realm name to display the configuration for that realm. The following screen shows the configuration for the realm subneta. The realm SubnetA is configured with the Realm Signaling Address , which is associated with the Vnet Name vnet1. The realm SubnetA is configured to be associated with the Media Pool ID 1 (Pool 1) for the Media. The Enable Signaling checkbox must be checked since Realm subneta is used with the Avaya S8500 Media Server for H.323 signaling. Do not configure the SIP Authentication and Mirror Proxy sections since these are related to SIP. 33 of 52

34 The following screen shows the configuration for the realm subnetb. The realm SubnetB is configured with the Realm Signaling Address , which is associated with the Vnet Name vnet2. The realm SubnetB is configured to be associated with the Media Pool ID 2 (Pool 2) for the Media. The Enable Signaling checkbox must be checked since Realm subnetb is used with the Avaya S8300 Media Server for H.323 signaling. Do not configure the SIP Authentication and Mirror Proxy sections since these are related to SIP. 34 of 52

35 The following screen shows realm subnetb-ops configuration. The Realm Signaling Address is configured to , which is associated with the Vnet Name vnet2. The realm subnetb-ops is configured to be associated with the Media Pool ID 2 (Pool 2) for the Media. The Registration ID for the Mirror Proxy will be added later on after endpoints are configured. The NexTone MSC is configured as a mirror proxy for SIP endpoints and the SIP authentication must not be configured for the realm subnetb-ops. 35 of 52

36 The following screen shows realm Mirror-realm configuration. The Realm Signaling Address is configured to , which is associated with the Vnet Name vnet1. The Media Pool ID 1 is configured for the media. Note that SIP authentication must be configured to all since the Avaya Converged Communications Server will authenticate every SIP message with The NexTone MSC (address ). The Registration ID must be configured to none for the Mirror Proxy. 36 of 52

37 The following shows the Database configuration used in the sample configuration. Note that SIP telephone C (ext ) and D (ext ) are dynamically registered with the NexTone MSC. There is no specific configuration for a dynamic endpoint. 37 of 52

38 Double click a dynamic endpoint to get the detailed registration information for that endpoint. Double click Port 1 under the Avaya_CCS from the Database screen, and then click the Phone tab. The following parameters are configured for the Avaya Converged Communications Server: Device Type: IP Proxy IP Address: Calling Plan: none Realm: Mirror-realm The NexTone MSC only passes the information between the Avaya SIP telephones and the Avaya Converged Communications Server. The Calling Plan is not required. 38 of 52

39 39 of 52

40 Go back to the realm subnetb-ops configuration screen and set the Registration ID to the Avaya_CCS. When an Avaya SIP telephone in the Branch Office sends REGISTER messages to the Realm Signaling Address (RSA) on the realm subnetb-ops, the NexTone MSC will forward the REGISTER messages with modified header content to the Avaya Converged Communications Server (Avaya_CCS: ). The SIP authentication should not be configured for the realm subnetb-ops. 40 of 52

41 Double click Port 1 under the Avaya_G650 from the Database screen, and then click the Phone tab. The following parameters are configured for the Avaya S8500 Media Server: Device Type: H.323 Gateway IP Address: Calling Plan: G650 Realm: subneta 41 of 52

42 Double click Port 1 under the Avaya_S8300-G700 from the Database screen, and then the click the Phone tab. The following parameters are configured for the Avaya S8300 Media Server: Device Type: H.323 Gateway IP Address: Calling Plan: ACM-S8300 Realm: subnetb 42 of 52

43 4. Interoperability Compliance Testing NexTone MSC was compliance tested with Avaya Communication Manager, Avaya Converged Communications Server, and Avaya H.323 and SIP telephones General Test Approach All the test cases were performed manually. A packet analyzer was used to verify that H.323 and SIP protocols were worked as expected between NexTone MSC and Avaya Communication Manager, Avaya Converged Communications Server, and Avaya H.323 and SIP telephones 4.2. Test Results All the related test cases passed successfully. No errors were detected. All the following features were tested successfully: H.323-to-H.323 trunks between Avaya Communication Manager and NexTone MSC. Mirror proxy for Avaya SIP telephones through the NexTone MSC. IP-Shuffling for Avaya H.323 and SIP telephones through NexTone MSC. G729B and G711 Codecs support for Avaya H.323 and SIP telephones. Call transfer and conference support for Avaya H.323 and SIP telephones through NexTone MSC. 43 of 52

44 5. Verification Steps 5.1 Verify H.323 Calls Between the Main Office and the Branch Office Make a phone call between the Main Office and the Branch Office. Use the command status station <ext.> on the Avaya S8500 Media Server to verify the call status. The following screen shows a call status between Avaya IP telephone A in the Main Office and Avaya IP telephone C in the Branch Office. The Audio Connect Type is ip-direct with the Audio path between IP telephone A ( ) and the NexTone MSC media pool 1 ( ). The G.729 codec is used for the call. status station Page 4 of 6 AUDIO CHANNEL Port: S00000 Switch IP IP Port Other-end IP Addr :Port Set-end IP Addr:Port G.729A Audio: : :32634 Node Name: Network Region: 2 1 Audio Connection Type: ip-direct Port: S00000 Product ID and Release: IP_Phone H.245 Tunneled in Q.931? does not apply Registration Status: registered-authenticated MAC Address: 00:04:0d:29:11:82 Native NAT Address: not applicable Shared Port: The following screen shows the status from the Avaya S8300 Media Server for the same call. The Audio Connect Type is ip-direct with the Audio path between IP telephone C ( ) and the NexTone MSC media pool 2 ( ). The G.729 codec is used for the call. status station Page 4 of 6 AUDIO CHANNEL Port: S00000 Switch IP IP Port Other-end IP Addr :Port Set-end IP Addr:Port G.729A Audio: : :2134 Node Name: Network Region: 2 1 Audio Connection Type: ip-direct Port: S00000 Shared Port: Product ID and Release: IP_Phone H.245 Tunneled in Q.931? does not apply Registration Status: registered-authenticated MAC Address: 00:09:6e:09:07:bd Native NAT Address: not applicable 44 of 52

45 If the call cannot be made successfully, use the command list trace station <ext.> on Avaya Communication Manager to troubleshoot the call. The following shows a correct trace from the Avaya S8500 Media Server for the call made from IP telephone A to telephone C. list trace station Page 1 LIST TRACE time data 13:18:08 active station cid 0x478 13:18:08 G729AB ss:off ps:20 rn:1/ : : :18:08 xoip: fax:relay modem:off tty:us uid:0x1 cid:0x478 13:18:10 dial route:aar 13:18:10 term trunk-group 11 cid 0x478 13:18:10 dial route:aar 13:18:10 route-pattern 1 preference 1 cid 0x478 13:18:10 seize trunk-group 11 member 1 cid 0x478 13:18:10 Calling Number & Name G SW 13:18:10 Proceed trunk-group 11 member 1 cid 0x478 13:18:10 Alert trunk-group 11 member 1 cid 0x478 13:18:10 G729 ss:off ps:20 rn:2/ : : :18:10 xoip: fax:off modem:off tty:us uid:0x5001b cid:0x478 13:18:10 G729A ss:off ps:20 rn:2/ : : :18:10 G729 ss:off ps:20 rn:1/ : : :18:11 active trunk-group 11 member 1 cid 0x478 13:18:11 G729A ss:off ps:20 rn:2/ : : :18:11 G729 ss:off ps:20 rn:1/ : : of 52

46 5.2 Verify SIP Telephone Registration and Call Status Across the NexTone MSC The following screen shows the SIP settings on Avaya SIP telephone C in the Branch Office. The Proxy Server Address, Registrar Server Address and Registration Domain are configured to the NexTone MSC RSA address facing Avaya SIP telephones C and D. From the Avaya Converged Communications Server, click the View Registered Users under the Users menu to display registered users. The following screen shows that all four users in Figure 1 have registered successfully. Note that the contact messages for SIP telephones C and D have been modified by The NexTone MSC to 55501@ :5060 and 55502@ : is the NexTone MSC RSA IP address facing the Main Office. 46 of 52

47 The registration status for Avaya SIP telephones C and D can also be verified from The NexTone MSC database. See Section 3.5 for details. If a call cannot be made between two Avaya SIP telephones, use the command list trace tac 103 on the Avaya S8500 Media Server to troubleshoot. The following screen shows a trace between SIP telephone C and D. list trace tac 103 Page time data LIST TRACE 12:58:28 Calling party station cid 0x452 12:58:28 Calling Number & Name EXT :58:28 active station cid 0x452 12:58:28 G729B ss:off ps:20 rn:1/ : : :58:28 xoip: fax:relay modem:off tty:us uid:0x5001f cid:0x452 12:58:28 dial :58:28 ring station cid 0x452 12:58:29 active station cid 0x452 12:58:29 G729B ss:off ps:20 rn:1/ : : :58:29 G729B ss:off ps:20 rn:1/ : : of 52

48 Use the command status trunk 3 on the Avaya S8500 Media Server to find the active SIP trunk members. The following screen shows that trunk members 3/1 and 3/2 are active. status trunk 3 TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy 0003/001 T00031 in-service/active no T /002 T00032 in-service/active no T00031 Use the command status trunk 3/1 or 3/2 to get the call status while the call is active. The following screen shows that the media path is between the NexTone MSC pool 1 ( ) and SIP telephone A ( ). The Audio Connect Type is ip-direct. status trunk 3/1 Page 1 of 2 TRUNK STATUS Trunk Group/Member: 0003/001 Port: T00031 Signaling Group ID: Service State: in-service/active Maintenance Busy? no Connected Ports: T00032 Port Near-end IP Addr : Port Far-end IP Addr : Port Signaling: 01A : : 5061 G.729B Audio: : : Audio Connection Type: ip-direct 48 of 52

49 5.3 Verify H.323 and SIP Telephone Call Across the NexTone MSC Make a call between SIP telephone C and H.323 telephone C. Use the command status station <ext.> to verify call status on either the Avaya S8500 Media Server or the Avaya S8300 Media Server. The following screen shows the output from the Avaya S8300 Media Server. status station Page 4 of 6 AUDIO CHANNEL Port: S00000 Switch IP IP Port Other-end IP Addr :Port Set-end IP Addr:Port G.729A Audio: : :2134 Node Name: Network Region: 2 1 Audio Connection Type: ip-direct Port: S00000 Product ID and Release: IP_Phone H.245 Tunneled in Q.931? does not apply Registration Status: registered-authenticated MAC Address: 00:09:6e:09:07:bd Native NAT Address: not applicable Shared Port: Use the command status trunk 3/x (where x is the active trunk member on the call) on the Avaya S8500 Media Server to get the call status. The following screen shows that the Audio Connect Type is ip-tdm. Note that a direct media path will not be established between an H.323 and SIP endpoint. status trunk 3/1 Page 1 of 3 TRUNK STATUS Trunk Group/Member: 0003/001 Port: T00031 Signaling Group ID: Connected Ports: T00027 Service State: in-service/active Maintenance Busy? no Port Near-end IP Addr : Port Far-end IP Addr : Port Signaling: 01A : : 5061 G.729B Audio: 01A : : Audio Connection Type: ip-tdm 49 of 52

50 6. Support NexTone's Technical Support is offered at various levels including 24/7 coverage, 365 days a year. Check for the support link. 7. Conclusion NexTone MSC was compliance tested with Avaya Communication Manager, Avaya Converged Communications Server, and Avaya H.323 and SIP telephones. 8. Additional References [1] Avaya Extension to Cellular and Off-PBX-Station (OPS) Installation and Administration Guide, Release 5.2, Issue 8, Document ID [2] Converged Communications Server, Installation and Administration, Release 2.1, Document ID [3] NexTone iserver (MSC and MSW) Installation and Operation Guide, Release 3.1.2, Issue of 52

51 9. Glossary Technical Term IPSI C-LAN MEDPRO SAT Codec VoIP OPS DNIS FCE RTP RTCP RMA RSA Definition as it pertains to this document IP Server Interface Control-LAN Media Processor System Access Terminal Coder/Decoder Voice over IP Off-PBX-Station Dialed Number Identification Service Firewall Control Entity Real Time Protocol Real Time Control Protocol Realm Media Address Realm Signaling Address 51 of 52

52 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 DeveloperConnection Program at 52 of 52