Abstract. Testing was conducted via the Internal Interoperability Program at the Avaya Solution and Interoperability Test Lab.

Transcription

1 Avaya Solution & Interoperability Test Lab Configuring the Avaya G860 Media Gateway to provide Connectivity between the Public Switched Telephone Network (PSTN) and the Avaya Meeting Exchange Enterprise S6800 Conferencing Server directly and via Avaya SIP Enablement Services Issue 1.0 Abstract These Application Notes describe a compliance tested solution comprised of the Avaya Meeting Exchange Enterprise S6800 Conferencing Server communicating directly with the Avaya G860 Media Gateway and via Avaya SIP Enablement Services (SES). The Avaya G860 Media Gateway is utilized to enable connectivity between the Avaya Meeting Exchange Enterprise S6800 Conferencing Server (MX) and the PSTN. This configuration provides a rich set of conferencing options available on the Avaya Meeting Exchange Enterprise S6800 Conferencing Server to participants associated with the PSTN. Testing was conducted via the Internal Interoperability Program at the Avaya Solution and Interoperability Test Lab. 1 of 71

2 TABLE OF CONTENTS 1. Introduction Avaya Meeting Exchange Enterprise S6800 Conferencing Server Avaya G860 Media Gateway Equipment and Software Validated Configure the Avaya Meeting Exchange Enterprise S6800 Conferencing Server Configure the Avaya Meeting Exchange Enterprise S6800 Application Server Configure the RadiSys CMS-9000 Media Server Network File System Configure NFS on the Avaya Meeting Exchange Enterprise S6800 Application Server Configure NFS on the RadiSys CMS-9000 Media Server CBUTIL Utility Bridge Talk Configure the Avaya SIP Enablement Services (SES) Configure the Avaya G860 Media Gateway Configure the Avaya G860 Media Gateway Properties Configure the TP6310 Board Configure DS3/DS1 Trunking Configure SIP and T1 Trunking Configure B-channels Administer Call Routing Rules Configuring In-band DTMF and RFC2833 (Out-Of-band) in the Avaya G860 Media Gateway Installing and Configuring Avaya Signed TLS Certificates on the Avaya G860 Media Gateway Interoperability Compliance Testing General Test Approach Verification Steps Verify Call Routing Conclusion Additional References of 71

3 Scroll * SPEAKER HEAD SET AB C D EF GHI JLK MNO PQRS TUV WXYZ # CONFERENC E Scroll * SPEAKER HEAD SET AB C D EF GHI JLK MNO PQRS TUV WXYZ # CONFERENC E 1. Introduction These Application Notes describe a compliance tested solution comprised of the Avaya Meeting Exchange Enterprise S6800 Conferencing Server (MX), Avaya SIP Enablement Services (SES) and the Avaya G860 Media Gateway. The Avaya G860 Media Gateway is utilized to enable connectivity between the Avaya Meeting Exchange Enterprise S6800 Conferencing Server and the PSTN. The end to end signalling connectivity between Avaya Meeting Exchange Enterprise S6800 conferencing server and the PSTN, either via the Avaya G860 Media Gateway directly or via Avaya SIP Enablement Services is shown in Figure 1. BLUE DDI/DNIS DevConnect Network RED DDI/DNIS SIL (Dublin) Avaya SIP Enablement Services Host Mapping IP Network /24 DS3 AVAYA G860 MEDIA GATEWAY GREEN DDI/DNIS Simulated PSTN RadiSys CMS Avaya Meeting Exchange Enterprise S6800 Application Server One-X Desktop Figure 1: Network Configuration Note: Figure 1 has two call flows configured (G860-MXS6800) and (G860-SES- MXS6800).These can be individual configured or both together depending on the requirement. Extra steps required to configure G860-SES-MXS6800 are described in Step 3.1.3b, Step 3.6 and Step Signalling and media connectivity between the PSTN and the Avaya Meeting Exchange Enterprise S6800 Conferencing Server traversed the following paths. T1 ISDN-PRI (D-channel on channel 24) multiplexed over a DS3 from the PSTN to the Avaya G860 Media Gateway (Black Dotted Line) SIP/(UDP,TLS and TCP) between the Avaya G860 Media Gateway and the Avaya Meeting Exchange Enterprise S6800 Application Server (Blue Line) SIP/(UDP,TLS and TCP) between the Avaya G860 Media Gateway and the Avaya Meeting Exchange Enterprise S6800 Application Server via Avaya SIP Enablement Services host mapping (Red Line) SIP/(UDP,TLS and TCP) between Avaya One-X Desktop to Avaya Meeting Exchange Enterprise Application Server S6800 via Avaya SIP Enablement 3 of 71

4 Services host mapping (Green Line) RTP/UDP between the Avaya G860 Media Gateway and the RadiSys CMS-9000 Media Server (Blue line) 1.1. Avaya Meeting Exchange Enterprise S6800 Conferencing Server The Avaya Meeting Exchange Enterprise S6800 Conferencing Server comprises Avaya Meeting Exchange Enterprise S6800 Application Server for signalling and the RadiSys CMS 9000 Media Gateway for media processing. Avaya Meeting Exchange Enterprise S6800 Conferencing Server is a SIP-based voice conferencing solution that extends Avaya's conferencing applications, including reservation-less, attended, event, and mobile to support various IP network implementations. The following capabilities are supported by the Avaya Meeting Exchange Enterprise S6800 Conferencing Server: RFC 2833 DTMF support. In-band DTMF support. Up to 1400-user using 1 RadiSys MPC and 140-operator conferences. Support for up to four digitally recorded music sources. Support for one recorded music channel and up to four connection based (FDAPI) music channels. Any combination of G.711 a-law or u-law, G.729, G723, G.722, G726-16, G726-24, G726-32, or G codecs. Up to four Avaya Meeting Exchange S6800 Conferencing Server(s) configured as Application Server(s), e.g., call signalling processes are managed by the S6800(s). For these Application Notes, one Avaya Meeting Exchange Enterprise S6800 Conferencing Server is utilized as an Application Server. A RadiSys CMS-9000 Media Server, containing the following cards: o One Media Processor Card (MPC). o One Shelf Control Card (SCC). Signalling between the Avaya Meeting Exchange Enterprise S6800 Application Server(s) and the RadiSys CMS-9000 Media Server is SIP. 4 of 71

5 1.2. Avaya G860 Media Gateway The Avaya G860 Media Gateway provides a means for customers to consolidate facilities and reduce communications costs by concentrating PSTN traffic over a DS3 interface. For high call traffic applications such as conferencing servers, using DS3 facilities can provide a higher density, lower cost solution compared with DS1 facilities. The Avaya G860 Media Gateway is a carrier class product that supports up to 8000 channels of SIP VoIP telephony. It uses N+1 redundancy of media gateway, Ethernet switch, shelf controller, and power supply modules to achieve high availability in mission critical applications. The Avaya G860 Media Gateway is shipped with an Element Management System (EMS) that is used for operations, administration, management, and provisioning functions. A Solaris based EMS server communicates with the Avaya G860 Media Gateway using SNMP. An EMS client communicates with the EMS server from a Microsoft Windows based PC, and provides the graphical user interface 2. Equipment and Software Validated The following equipment and software versions were used for the sample configuration provided in these Application Notes. Equipment Software Avaya Bridge Talk (BT) Avaya G860 Media Gateway Chassis Type M5k10 Software Version Board Type Tp6310Ds3 EMS Server EMS Client Avaya SIP Enablement Services (SES) build Avaya Meeting Exchange Enterprise S6800 Application 5.1 build.161 Server (MX) RadiSys CMS Table 1: Hardware and Software Versions 5 of 71

6 3. Configure the Avaya Meeting Exchange Enterprise S6800 Conferencing Server This section describes the steps for configuring the Avaya Meeting Exchange Enterprise S6800 Conferencing Server to interoperate with the PSTN via the Avaya G860 Media Gateway. (see Figure 1) Configure the Avaya Meeting Exchange Enterprise S6800 Application Server The following steps describe the administrative procedures for configuring the Avaya Meeting Exchange Enterprise S6800 Application Server signalling to originate/terminate calls utilizing the RadiSys CMS-9000 Media Server for media processing. System.cfg telnumtouri.tab Step Description Log in to the Avaya Meeting Exchange Enterprise S6800 Application Server console (PuTTY) using ssh to access the Command Line Interface (CLI) with the appropriate credentials. 6 of 71

7 3.1.2 Configure settings that enable SIP connectivity between the Avaya Meeting Exchange Enterprise S6800 Application Server and other Devices by editing the system.cfg file as follows: Edit /usr/ipcb/config/system.cfg Add S6800 IP address o IPAddress= Add a line to populate the From Header Field in SIP INVITE messages o MyListener=sip:6000@ Note: The user field 6000, defined for this SIP URI must conform to RFC For consistency, it is selected to match the user field provisioned for the respcontact entry (see below). Add a line to provide SIP Device Contact address to use for acknowledging SIP messages from the Avaya Meeting Exchange S6800 Application Server: o respcontact=<sip:6000@ :5061;transport=tls> Note: Configure the following if your using TCP and UDP o respcontact=<sip:6000@ :5060;transport=tcp> o respcontact=<sip:6000@ :12;transport=udp> Add the following lines to set the Min-SE timer to 900 seconds in SIP INVITE messages from the Avaya Meeting Exchange S6800 Application Server: o sessionrefreshtimervalue= 900 o minsetimervalue= 900 Note: The values for the sessionrefreshtimervalue and the minsetimervalue are defined in seconds and should be provisioned to be greater than or equal to the value used by SIP User Agent(s) connecting to the Avaya Meeting Exchange S6800 Application Server, e.g., the Avaya G860 Media Gateway. This setting is necessary to enable Dial-Out from the Avaya Meeting Exchange Enterprise S6800 Application Server to the PSTN via the Avaya G860 Media Gateway. 7 of 71

8 3.1.3 a) To enable Dial-Out from the Avaya Meeting Exchange Enterprise S6800 Application Server to the PSTN via the Avaya G860 Media Gateway, edit the telnumtouri.tab file as follows: o Edit /usr/ipcb/config/telnumtouri.tab file with a text editor, o Add a line to the file to route outbound calls from the Avaya Meeting Exchange S6200 Server to the Avaya G860 Media Gateway: b) * sip:$1@ :5061;transport=tls G860 To enable Dial-Out from the Avaya Meeting Exchange Enterprise S6800 Application Server to the PSTN via the Avaya SES to the Avaya G860 Media Gateway, edit the telnumtouri.tab file as follows: o Edit /usr/ipcb/config/telnumtouri.tab file with a text editor. o Add a line to the file to route outbound calls from the Avaya Meeting Exchange Enterprise S6800 Application Server to the Avaya SES to the G860 Media Gateway: * sip:$1@ :5061;transport=tls SES 8 of 71

9 3.1.4 To configure the Avaya Meeting Exchange Enterprise S6800 Application Server to utilize MPC resources on the RadiSys CMS-9000 Media Server, edit the processtable.cfg file as follows: o Edit the /usr/ipcb/config/processtable.cfg file with a text editor o Add an ipaddress for each corresponding procces name in this file. Note: The processtable.cfg for these Application Notes contains IP Addresses of , where is defined as a global IP address on the Avaya Meeting Exchange Enterprise S6800 Application Server. Alternatively, the IP address of the Avaya Meeting Exchange Enterprise S6800 Application Server (as defined in the /etc/hosts file) could have been entered in the ipaddress for each processname. # processes file, enumerates the number of processes in the network. # will have the name of the process Key ID and the IP address # # The default configuration is a single MPC board system. There are # two commented out entries for a second and third MPC board. If more # than 1 board is needed for the system then uncomment out the appropriate # line(s). The last thing on the line correlates to the _* entry in the # mediaserverinterface.cfg. For example, for the 1st mediaserver line that # ends with a 1. The _1 entries in the mediaserverinterface.cfg are used. # processes file, enumerates the number of processes in the network. # will have the name of the process Key ID and the IP address proccessname ipckeynumber autostart ProcessExe ipaddress route ProcessArgs initipcb noexecute bridget noexecute dspevents/msdispatcher,netevents/sipagent commsprocess /usr/dcb/bin/servercomms sipagent /usr/dcb/bin/sipagent dspevents/msdispatcher,appevents/bridget700 msdispatcher /usr/dcb/bin/msdispatcher netevents/sipagent,appevents/bridget700,dspevents/mediaserver mediaserver /usr/dcb/bin/convms appevents/msdispatcher,netevents/msdispatcher 1 notifyservice noexecute :10235 snmpagent noexecute #mxmonitor noexecute <aps1-ip> appevents/msdispatcher,netevents/msdispatcher aps1 "processtable.cfg" 16L, 1826C 9 of 71

10 3.2. Configure the RadiSys CMS-9000 Media Server The following steps describe the administrative procedures for configuring the RadiSys CMS-9000 Media Server to enable collaboration with the Avaya Meeting Exchange Enterprise S6800 Application Server. See Section 8 for additional information regarding configuring the RadiSys CMS-9000 Media Server. Configuring SCC and MPC IP Address Configuring Codecs Step Description Provision the SCC on the RadiSys CMS-9000 Media Server as follows: Establish an RS-232 connection from a services PC to the RadiSys CMS-9000 Media Server by connecting a serial cable to the front of the SCC card (slot 1). Start a terminal server application, e.g., HyperTerminal on the services PC with the following settings: o Speed: 9600 bps. o Data bits: 8 bits. o Parity: No parity. o Stop bit: 1 bit. o Flow control: none. wait for the system to establish the connection, or press <Enter>. 10 of 71

11 3.2.2 From the RS-232 Interface login screen that is displayed, log in to the RadiSys CMS-9000 Media Server craft interface with the appropriate credentials. 11 of 71

12 3.2.3 From the RS-232 Interface Main Menu screen that is displayed, select Network Settings and press <Enter>. 12 of 71

13 3.2.4 From the RS-232 Interface Network Menu that is displayed, configure network settings for the sample configuration as follows. Administer network parameters used for control and management traffic on the RadiSys CMS-9000 Media Server by specifying: A Hostname for the RadiSys CMS-9000 Media Server. An IP Address and Netmask for Port 1. Administer routing parameters used for remote control or management networks on the RadiSys CMS-9000 Media Server by specifying: A Network IP address, Netmask and Gateway for Rte 1. Note: To indicate the default gateway, leave the Network IP address and Netmask blank ( ). The Gateway must be on a directly connected network. Save the settings by using <Tab> to navigate down to Save and Quit and press <Enter>. 13 of 71

14 3.2.5 From the RS-232 Interface Main Menu screen that is displayed, preserve the configuration administered in the previous steps by rebooting the RadiSys CMS-9000 Media Server. Select Reboot and press <Enter>. o [Not Shown] A confirmation message displays to confirm the reboot. o [Not Shown] Use the <Tab> key to toggle to the YES option and press <Enter>. o [Not Shown] Use the spacebar to toggle to the Choose the Restart with Current Configuration option. o [Not Shown] A confirmation message displays to confirm the reboot. o [Not Shown] Use the <Tab> key to toggle to the YES option and press <Enter>. The media server restarts and the network settings are enabled. 14 of 71

15 3.2.6 Administer settings for RadiSys CMS-9000 Media Server via the web GUI as follows: Open a web browser and enter the following URL: o address of RadiSys CMS-9000 Media Server > Log in to the RadiSys CMS-9000 Media Server with the appropriate credentials. 15 of 71

16 3.2.7 Administer settings for Audio Codec(s) on the RadiSys CMS-9000 Media Server sample configuration as follows: Click Configuration Slot Configuration Configure Audio Codec List. Select either the Slot Number for the MPC card or all (MPC cards) to which this Audio Codec List will be applied. Click Execute. Note: Audio Codecs in the Audio Codec List are prioritized from First codec to Eleventh codec. 16 of 71

17 3.2.8 Administer settings for MPC(s) on the RadiSys CMS-9000 Media Server sample configuration as follows: Click Configuration Slot Configuration Configure MPC. Select the Slot Number for the MPC. For these Application Notes, the MPC was placed in Slot number of 71

18 3.2.9 Configure the MPC in slot 2 on the RadiSys CMS-9000 Media Server as shown for the sample configuration: Enter a Hostname and IP Address for the Control Interface. Enter IP Address, Subnet Mask, Connection Mode and Default Gateway information for Media Ports 1 and 2. Click on the Save Settings button when finished. Note: Configure each MPC on the RadiSys CMS-9000 Media Server. For these Application Notes, there is only one MPC. 18 of 71

19 3.3. Network File System The following steps describe the administrative procedures to enable Network File System (NFS) sharing between the Avaya Meeting Exchange Enterprise S6800 Application Server and the RadiSys CMS-9000 Media Server. In this configuration, the Avaya Meeting Exchange Enterprise S6800 Application Server will function as the NFS server. This will allow playback of audio conference(s) recorded on the RadiSys CMS Media Server from the Avaya Meeting Exchange Enterprise S6800 Application Server. Configure NFS on the Avaya Meeting Exchange Enterprise S6800 Application Server The following steps describe the administrative procedures to provision NFS on the Avaya Meeting Exchange Enterprise S6800 Application Server. Configuring NFS server Step Description Log in to the Avaya Meeting Exchange Enterprise S6800 Application Server console to access the CLI with the appropriate credentials The NFS server communicates with the control interface on the RadiSys CMS Media Server MPC. To resolve the IP address for the control interface on the RadiSys CMS-9000 Media Server MPC, edit the hosts file sample configuration as follows: cd to /etc Edit the hosts file with a text editor, e.g., vi. Add a line to the file to resolve the IP address of the control interface to the RadiSys CMS-9000 Media Server MPC in slot 2: o mpc2 Where and mpc2 are the IP address and hostname of the control interface assigned to the RadiSys CMS-9000 Media Server MPC 19 of 71

20 3.3.3 To configure the Avaya Meeting Exchange Enterprise S6800 Application Server as an NFS server, edit the mediaserverinterface.cfg file as follows: cd to /usr/ipcb/config Edit the mediaserverinterface.cfg file with a text editor, e.g., vi. Add a line to the file to assign the Avaya Meeting Exchange Enterprise S6800 Application Server as the NFS server: o NFSServerIPAddress= Where is the IP address assigned to the Avaya Meeting Exchange Enterprise S6800 Application Server. Add a line to the file to assign the RadiSys CMS-9000 Media Server as a media server: o MediaServerIP_1= Where is the IP address of the control interface assigned to the RadiSys CMS-9000 Media Server MPC. Note: Multiple MPC cards on the RadiSys CMS-9000 Media Server would each require an entry in the mediaserverinterface.cfg file. The requirement for successive entries is to increment the MediaServerIP_X variable by 1, e.g., MediaServerIP_2 would correspond to a second MPC, MediaServerIP_3 to a third, etc. Add a line to the file to assign a port to the RadiSys CMS-9000 Media Server: o MediaServerInterfaceSipListenPort_1=5050 Note: Multiple MPC cards on the RadiSys CMS-9000 Media Server would each require an entry for a unique port in the mediaserverinterface.cfg file. The requirement for the successive port entries are to decrease the port number by ten for each MPC card, e.g., the port number for a second MPC would be 5040, a third MPC would have a port entry of 5030, etc. # This file contains the configuration information for the # Media Server Interface. This information includes the # IP Address for the NFS Server (where recordings are stored), # the IP address of the Media Server(may be more than 1), and # the udp port that the Media Server Interface code should # listen for SIP responses. # # NFS Server NFSServerIPAddress= # # MPC 1 on RadiSys CMS-9000 Media Server (Control Port) MediaServerIP_1= MediaServerInterfaceSipListenPort_1= of 71

21 3.3.4 The NFS server communicates with the control interface on the RadiSys CMS Media Server MPC. To resolve the recording location for the control interface on the RadiSys CMS-9000 Media Server MPC, edit the export file as follows: vi to /etc/exports Add a line to the file to resolve the recording location of the control interface to the RadiSys CMS-9000 Media Server MPC in slot 2: /var/ duqampc102(rw,async,no_root_squash) Reboot the Avaya Meeting Exchange Enterprise S6800 Application Server for changes to take effect. Note: Rebooting the Avaya Meeting Exchange Enterprise S6800 Application Server is service impacting. [S6800]> init 6 21 of 71

22 Configure NFS on the RadiSys CMS-9000 Media Server The following steps describe the administrative procedures to provision NFS on the RadiSys CMS-9000 Media Server. Step Description Administer settings for NFS on the RadiSys CMS-9000 Media Server MPC(s) via the web GUI as follows: Click Configuration Slot Configuration Configure NFS. Select the Slot Number for the MPC to administer settings for NFS. For these Application Notes, the MPC was placed in Slot number of 71

23 3.3.7 Configure NFS parameters for the MPC in slot 2 on the RadiSys CMS-9000 Media Server as shown for the sample configuration: Select Enabled for the NFS Operational Mode to enable NFS on this MPC. Enter the IP address for the NFS server in the NFS Server IP Address or Hostname field. Enter /var/ in the NFS Server Exported Directory field. Remaining fields are default settings. Click on the Save Settings button when finished.(not shown on this page) Note: Configure NFS for each MPC on the RadiSys CMS-9000 Media Server. For these Application Notes, there is only one MPC. 23 of 71

24 3.3.8 Reset the RadiSys CMS-9000 Media Server MPC in slot 2 for changes to take effect as follows: Click Configuration Reset Card. Select the slot number for the MPC to reset. For these Application Notes, the MPC was placed in slot number 2. Select Forced for the Type of reset operation. Click Execute. Note: If there is only one MPC in the RadiSys CMS-9000 Media Server chassis, resetting the MPC is service impacting. If more than one MPC is present, resetting a single MPC would not be service impacting, as all traffic on the MPC being reset would fail over to an active MPC. 24 of 71

25 3.4. CBUTIL Utility The following steps provide examples of how to provision Scan Flow(Scheduled and Demand) conference call functions by utilizing the cbutil utility on the Avaya Meeting Exchange Enterprise S6800 Application Server.. Step Description To map DNIS entries, run the cbutil utility on MX as follows: If not already logged on, log in to the Avaya Meeting Exchange Enterprise S6800 Application Server with an ssh connection using PuTTY with the appropriate credentials. Enable Dial-In access (via passcode) to conferences provisioned on the Avaya Meeting Exchange Enterprise S6800 Application Server as follows: Add a DNIS entry for a scan call function corresponding to DID by entering the following command at the command prompt: cbutil add <dnis> <rg> <msg> <ps> <ucps> <func> [-l <ln> -c <cn>], where the variables for add command is defined as follows: o <dnis> DNIS o <rg> Reservation Group o <msg> Annunciator message number o <ps> Prompt Set number (0-20) o <ucps> Use Conference Prompt Set (y/n) o <func> One of: DIRECT/SCAN/ENTER/HANGUP/AUTOVL/FLEX o -l <"ln"> Optional line name to associate with caller o -c <"cn"> Optional company name to associate with caller In this sample configuration: [sroot@mx-g860]# cbutil add n scan cbutil Copyright 2004 Avaya, Inc. All rights reserved At the command prompt, enter cbutil list to verify the DNIS entries provisioned [sroot@mx-g860 config]# cbutil list cbutil Copyright 2004 Avaya, Inc. All rights reserved. DNIS Grp Msg PS CP Function On Failure Line Name Company Name Room Start Room End N SCAN ENTER LocalMX- OneX N SCAN ENTER MX-G N SCAN ENTER MX-SES- G of 71

26 3.5. Bridge Talk The following steps utilize the Avaya Bridge Talk application to provision a sample conference on the Avaya Meeting Exchange Enterprise S6800 Application Server. This sample conference enables both Dial-In and Dial-Out access to audio conferencing for endpoints on the PSTN. Note: If any of the features displayed in the Avaya Bridge Talk screen captures are not present, contact an authorized Avaya sales representative to make the appropriate changes. Login Bridge Talk Creating Dial List (Manual/Blast dial) Scheduling Conference Step Description Invoke the Avaya Bridge Talk application as follows: [Not Shown] Double-click on the desktop icon from a PC loaded with the Avaya Bridge Talk application and with network connectivity to the Avaya Meeting Exchange Enterprise S6800 Application Server. Enter the IP address of the Avaya Meeting Exchange Enterprise S6800 Application Server ( ) in the Bridge field. Enter the appropriate credentials in the Sign-In and Password fields. 26 of 71

27 3.5.2 Provision a dial list that is utilized for Dial-Out (e.g., Blast dial and Fast Dial) from the Avaya Meeting Exchange Enterprise S6800 Application Server. From the Avaya Bridge Talk Menu Bar, click Fast Dial New. 27 of 71

28 3.5.3 From the New Dial List Dial List Editor window that is displayed: Enter a descriptive label in the Name field. Enable conference participants on the dial list to enter the conference without a passcode by checking the Directly to Conf box as displayed. Add entries to the dial list by clicking on the Add button and enter Name, Company and Telephone number for dial out for each participant. [Optional] Moderator privileges may be granted to a conference participant by checking the Moderator box. When finished, click on the Save button on the bottom of the screen. 28 of 71

29 3.5.4 Provision a conference with Auto Blast enabled. From the Avaya Bridge Talk Menu Bar, click View Conference Scheduler From the Conference Scheduler window that is displayed, click File Schedule Conference. 29 of 71

30 3.5.6 From the Schedule Conference window that is displayed, provision a conference as follows: Enter a unique Conferee Code to allow participants access to this conference. Enter a unique Moderator Code to allow participants access to this conference with moderator privileges. Enable moderator access with a passcode for this conference call by configuring the following: Note: This conference remains open for participants to enter as either moderator or participant by entering the appropriate code when prompted. Enter a descriptive label in the Conference Name field. Administer settings to enable an Auto Blast dial by setting Auto Blast/Manual depending on the test. o [Not Shown] Select a dial list by clicking on the Dial List button select a dial list from the Create, Select or Edit Dial List window that is displayed click on the Select button. When finished, click on the Save button on the bottom of the screen. 30 of 71

31 3.6. Configure the Avaya SIP Enablement Services (SES) The following steps describe the administrative procedures for configuring the Avaya SIP Enablement Services to enable collaboration with the Avaya Meeting Exchange Enterprise S6800 Conferencing Server and Avaya G860 Media Gateway using host mapping. SES-MX6800 for dial in calls to MX SES-G860 for dial out calls from MX Adding Trusted Hosts Step Description Configure host mapping in SES for the following: SES-S6800 for dial in calls from MX SES-G860 for dial outs from MX Open the SES web page the appropriate credentials, Click on Launch SES Administration Interface. Click on Hosts Tab->List Hosts tab and Click on Map. Add the host map from Avaya SIP Enablement Services to the Avaya G860 Media Gateway by clicking Add Map in New Group and Add another Contact. Repeat the same for mapping from Avaya SIP Enablement Services to Avaya Meeting Exchange Enterprise S6800 Conferencing Server as shown below. The Screen shot show ports configured as 5060/UDP it should be 5061 if it is TLS as per Figure1. 31 of 71

32 Step Description Add the Avaya Meeting Exchange Enterprise S6800 Application Server and Avaya G860 Media Gateway as Trusted Hosts. 32 of 71

33 4. Configure the Avaya G860 Media Gateway The following sections describe the steps for configuring the SIP and PSTN trunks and call routing for the Avaya G860 Media Gateway. This configuration will enable the Avaya G860 Media Gateway to interoperate with the Avaya Meeting Exchange Enterprise S6800 Conferencing Server both directly and via Avaya SIP Enablement Services (see Figure 1). Configuration is performed using the EMS client GUI-based provisioning system, which is supported by the Microsoft Operating System. It is assumed that the Avaya G860 Media Gateway, EMS server, and EMS client have already been installed. Logging into Gateway using EMS Client Step Description 4.1 Invoke the GUI provisioning system from a PC running the EMS client by double-clicking on the desktop icon as shown below. From the login screen that is displayed, enter the login, password and the IP address of the EMS server. 33 of 71

34 4.2 From the main GUI provisioning screen that is displayed, locate the Regions List pane where logical/geographical regions are presented. Double-click on the appropriate row entry. Note: Media gateways, including Avaya G860 Media Gateway reside in logical/geographical regions. The icon shown on the right side of the screen can be clicked recursively to navigate from this screen or any successive screen back to a previous screen. 34 of 71

35 4.1. Configure the Avaya G860 Media Gateway Properties The following steps describe the administrative procedures for configuring system-wide parameters on the Avaya G860 Media Gateway Step Description From the media gateway list in the MGs List pane that is displayed: Select the entry corresponding to the Avaya G860 Media Gateway to be configured. Click on Properties. 35 of 71

36 4.2. Configure the TP6310 Board The following steps describe the administrative procedures for configuring the active TP6310 board in the Avaya G860 Media Gateway chassis. These procedures will administer settings for SIP and DS3 trunking, as well as the call routing rules associated with this TP6310 board to enable signalling/media connectivity between the Avaya Meeting Exchange Enterprise S6800 Conferencing Server and the PSTN. Board IP Address and Board Voice configuration Step Description Prior to making any change to the configuration of the TP6310 board, the board must be locked. On the MGs List pane, double-click on the row corresponding to the Avaya G860 Media Gateway. Note: The MG Status tab will be highlighted and the Status pane will open, depicting a replica of the front panel of the Avaya G860 Media Gateway chassis. Board slots are numbered from 1 to 10 from bottom to top on the left side. For these Application Notes, installed gateway boards include the TP6310 DS3 boards in slots 8, 9 and 10. Click on the active TP6310 board shown in black, and use mouse button to select Maintenance Lock. [Not Shown] To confirm Lock, click Yes in the confirmation window that is displayed. Note: If there is a single TP6310 board in the Avaya G860 Media Gateway, locking this board removes it from service and is service impacting. 36 of 71

37 4.2.2 Administer settings on the locked TP6310 board as follows: Select the locked TP6310 board in the Status pane. Note: A locked board is indicated by a blue locking pin on its right hand side (see slot 9). Select the Properties link. 37 of 71

38 4.2.3 From the Board6310 Parameters Provisioning window that is displayed: Click on General Settings under Parameters List. Set IP Address 1 to the IP address for this board Select pstn for the None Mode Clk Source. Remaining fields are default settings. Click on Apply and then Close. 38 of 71

39 4.2.4 From the Board6310 Parameters Provisioning window that is displayed: Click on Voice under Parameters List. Set DSP Load File Version to 0. Set the Jitter Buffer Min Delay to 10 milliseconds. Note: The jitter buffer is administered to align with the network configuration utilized for these Application Notes, e.g., VoIP traffic will be on an internal enterprise network with low delay characteristics. Remaining fields are default settings. Click on Apply and then Close. 39 of 71

40 4.3. Configure DS3/DS1 Trunking The following steps describe the administrative procedures for configuring the DS3 and constituent DS1 trunking between the Avaya G860 Media Gateway and the PSTN. Configuring DS3 and DS1 Step Description Administer settings for a DS3 trunk to enable connectivity to the PSTN as follows: [Not Shown] Double-click on the locked TP6310 board in the Status pane Click on the DS3 tab. From the DS3 Status pane that is displayed, double-click on the DS3 for which the DS1 channel interface parameters are to be defined. Note: The DS3 Status pane displays the status of each of the 3 DS3 interfaces on this board. 40 of 71

41 4.3.2 From the DS1 Carriers List pane that is displayed, provision a DS1 on this DS3 interface by double-clicking on its entry in the list. 41 of 71

42 4.3.3 From the General Info pane, in the Trunk Parameters Provisioning window that is displayed: Administer settings to enable connectivity with the PSTN. Note: Obtain configuration details regarding the setting required for this connection to the PSTN from the service provider. The entries for this trunk correspond to a T1 PRI connection between the Avaya G860 Media Gateway and the PSTN. 42 of 71

43 4.3.4 From the DS1 Carriers List pane that is displayed, provision the third DS1 on this DS3 interface by double-clicking on its entry in the list. 43 of 71

44 4.3.5 From the General Info pane, in the Trunk Parameters Provisioning window that is displayed: Administer settings to enable connectivity with the PSTN. Note: Obtain configuration details regarding the setting required for this connection to the PSTN from the service provider. The entries for this trunk correspond to a T1 ISDN-PRI connection between the Avaya G860 Media Gateway and the PSTN. Click on Apply. Click on ISDN/DPNSS under Parameters List. 44 of 71

45 4.3.6 From the ISDN/DPNSS pane that is displayed:. Select the appropriate value for the Termination Side, usually userterminationside if the PSTN connection is to a service provider. Click on Apply. From the Profile Management pane, select Save to save the DS1, and assign a name to the profile. Note: The Profile Management pane can be used to define a configuration profile that can be applied to many DS1 interfaces, saving configuration steps. 45 of 71

46 4.3.7 Apply the DS1 configuration to the fourth DS1 on this DS3. The resultant DS1 Carriers List is shown below. 46 of 71

47 4.4. Configure SIP and T1 Trunking The following steps describe the administrative procedures for configuring SIP and T1 trunking between the Avaya G860 Media Gateway and the Avaya Meeting Exchange S6800 Application Server. Configuring Transport Protocol/Codecs between Avaya G860 Media Gateway and Meeting Exchange Enterprise S6800 Conferencing Server Step Description Double Click on Board 9, and administer settings for SIP trunking to enable connectivity with the Avaya Meeting Exchange Enterprise S6800 Application Server as follows: [Not Shown] Click on the icon to navigate back to the screen displayed below. Click on the SIP tab Click on the SIP Protocol tab; then click on the Protocol Settings tab. 47 of 71

48 4.4.3 From the General Settings pane, in the SIP Protocol Definitions window that is displayed, administer settings to enable SIP connectivity with the Avaya Meeting Exchange Enterprise S6800 Application Server as follows: Set the SIP Destination Port and Transport Type to enable SIP- TLS/UDP/TCP connectivity with the Avaya Meeting Exchange Enterprise S6800 Application Server: Remaining fields are default settings. Click on Apply and then Close. 48 of 71

49 4.4.4 Click on the Coders tab, under SIP Protocol to administer the codec preferences for this SIP trunk between the Avaya G860 Media Gateway and the Avaya Meeting Exchange S6800 Application Server. From the Sip Coder List pane that is displayed, click on the icon to add codec(s), ordered sequentially from most to least preferred From the Coders General Settings pane, in the SIP Coders window that is displayed: Add a codec that is supported on the Convedia CMS-6000 Media Server. In this case, administer settings for G.711 U-law 64k. Remaining fields are default settings. Click on Apply and then Close. 49 of 71

50 4.5. Configure B-channels The following steps describe the administrative procedures for assigning profiles to B- channels. These profiles are logical entities referred to as trunk group(s) that are used for routing IP to telephone calls with common rules, e.g., methods in which new calls are assigned to B-channels within each trunk group. Configuring Trunk Groups Adding PRI trunk Group Step Description Administer settings to assign profiles to the Avaya G860 Media Gateway s T1 B- channels as follows: Click on the Trunk Groups tab. Click on the Trunk Group tab. From the Sip Trunk Group List pane that is displayed, click on the icon to add trunk group(s). 50 of 71

51 4.5.2 Administer settings for ISDN-PRI trunking between the Avaya G860 Media Gateway and the PSTN with the following parameters: Enter All Trunks in the Name field. Set the Trunk Group ID to 2. Set the First Trunk ID to 1 (first T1 in the first T3) and the Last Trunk ID to 28; thus, logically provisioning this trunk with 46 B-channels. Set the Starting Channel to 1 (first B-channel in each T1) and Ending Channel to 24 (last B-channel in each T1). Set Starting Phone Number field to The resultant Sip Trunk Group List is shown below. 51 of 71

52 4.5.3 Administer settings that are used to determine the method in which new calls are assigned to B-channels within each trunk group as follows: Click on the Trunk Groups tab. Click on the Trunk Group Settings tab. From the Sip Trunk Group Settings List pane that is displayed, click on the icon to add trunk group setting(s) Administer settings to determine the method in which new calls are assigned to B-channels within the ISDN-PRI trunk group provisioned with the following parameters: Enter PRI in the Name field. Set the Trunk Group ID to correspond to the Trunk Group ID assigned to the trunk provisioned Set the Channel Select Mode to Ascending. Note: This channel selection pattern, in combination with the logical trunk provisioning enable ascending channel selection over 46 B-channels spread over two physical DS1 connections between the Avaya G860 Media Gateway and the PSTN. Thus, if one DS1 goes out of service, service will not be impacted for call origination from the Avaya G860 Media Gateway. The resultant Sip Trunk Group Settings List is shown below. 52 of 71

53 4.6. Administer Call Routing Rules The following steps describe the administrative procedures for administering call routing rules on the Avaya G860 Media Gateway to enable call origination/termination between the Avaya Meeting Exchange Enterprise S6800 Conferencing Server and the PSTN. Configuring Tel To IP Routing (Avaya G860 Media Gateway to Avaya SIP Enablement Services and Avaya Meeting Exchange Enterprise S6800 Conferencing Server) Step Description Administer call routing rule(s) that are applied to calls originating from the PSTN to the Avaya Meeting Exchange Enterprise S6800 Conferencing Server by adding Tel To IP routing rule(s) as follows: Click on the SIP tab Routing tab. Click on the Tel To IP tab. From the Sip Tel To IP Routing List pane that is displayed, click on the icon to add routing rule(s). Note: The Tel To IP routing table is used to route incoming Tel calls from the PSTN to IP addresses. This routing table associates a called/calling telephone number s prefix with a destination IP address or with an FQDN (Fully Qualified Domain Name). When a call is routed through the Avaya G860 Media Gateway, the called and calling numbers are compared to the list of prefixes on the IP Routing Table (up to 50 prefixes can be configured). Calls that match these prefixes are sent to the corresponding IP address or FQDN. If the number dialed does not match these prefixes, the call is not made. 53 of 71

54 4.6.2 From the SIP Routing Tel to IP window that is displayed, administer settings to enable Dial-In to the Avaya Meeting Exchange Enterprise S6800 Conferencing Server from the PSTN as follows: Enter a descriptive label in the Name field. Enter a rule in the Dest Phone Prefix field that matches the pattern of incoming calls to the Avaya Meeting Exchange Enterprise S6800 Conferencing Server from the PSTN. For these Application Notes, all calls to the Avaya Meeting Exchange Enterprise S6800 Conferencing Server from the PSTN are five digits in length with a leading digit of 7. The rule 7xxxx is utilized, where x is a wildcard and will match any single digit. Enter an * in the Source Phone Prefix field to allow routing for any source telephone number dialing in to the Avaya Meeting Exchange Enterprise S6800 Conferencing Server from the PSTN. Enter the IP address of the Avaya Meeting Exchange Enterprise S6800 Conferencing Server in the Dest Address field. Click on Apply and then Close. 54 of 71

55 4.6.3 From the SIP Routing Tel to IP window that is displayed, administer settings to enable dial-in to the Avaya Meeting Exchange Enterprise S6800 Conferencing Server from the PSTN via Avaya SES as follows: Enter a descriptive label in the Name field. Enter a rule in the Dest Phone Prefix field that matches the pattern of incoming calls to the Avaya Meeting Exchange Enterprise S6800 Conferencing Server from the PSTN. For these Application Notes, all calls to the Avaya Meeting Exchange Enterprise S6800 Conferencing Server from the PSTN are five digits in length with a leading digit of 8. The rule 8xxxx is utilized, where x is a wildcard and will match any single digit. Enter an * in the Source Phone Prefix field to allow routing for any source telephone number dialing in to the Avaya Meeting Exchange Enterprise S6800 Conferencing Server from the PSTN. Enter the IP address of the Avaya SES Server in the Dest Address field. Click on Apply and then Close. 55 of 71

56 4.6.4 Administer call routing rule(s) that are applied to calls originating from the Avaya Meeting Exchange Enterprise S6800 Conferencing Server to the PSTN by adding IP To Tel routing rule(s) to as follows: Click on the Routing tab. Click on the IP To Tel tab. From the Sip IP To Tel Routing List pane that is displayed, click on the icon to add routing rule(s). Note: The IP to Tel routing table is used to route incoming IP calls to provisioned groups of B-channels referred to as trunk group(s). Calls are assigned to trunk groups according to any combination of the following three options (or using each independently): Destination phone prefix. Source phone prefix. Source IP address. The call is then sent to the Avaya G860 Media Gateway channels assigned to that trunk group. The specific channel, within a trunk group, that is assigned to accept the call is determined according to the trunk group s channel selection mode which is defined in the provisioned Trunk Group Settings Table. 56 of 71

57 4.6.5 From the SIP Routing IP to Tel window that is displayed, administer settings to enable dial-out from the Avaya Meeting Exchange Enterprise S6800 Conferencing Server to the PSTN over a PRI trunk as follows: Enter a descriptive label in the Name field. Enter a rule in the Dest Phone Prefix field that matches the pattern of outgoing calls from the Avaya Meeting Exchange Enterprise S6800 Conferencing Server to the PSTN. For these Application Notes, all calls from the Avaya Meeting Exchange Enterprise S6800 Conferencing Server to the PSTN via PRI trunking are placed, where * is a wildcard and will match any digit(s). Enter an * in the Source Phone Prefix and Source Address fields to allow routing for any party dialling-out from the Avaya Meeting Exchange Enterprise S6800 Conferencing Server to the PSTN. Enter the Trunk Group ID for the PRI trunk group provisioned in the Trunk Group ID field. Click on Apply and then Close. 57 of 71

58 4.6.6 The board must be unlocked for the configuration to be applied to the TP6310 board, after which it is reset and enabled for service. [Not Shown] Click on the icon to navigate back to the screen displaying the locked TP6310 board). Click on the locked TP6310 board and use mouse button to select Maintenance Unlock. [Not Shown] To confirm Unlock, click Yes in the confirmation window that is displayed. Note: The TP6310 board will reset and return to service after several minutes. The Alarm Browser pane at the bottom of the window will indicate the status of the board. 58 of 71

59 4.7 Configuring In-band DTMF and RFC2833 (Out-Of-band) in the Avaya G860 Media Gateway The following steps describe the configuration of In-Band DTMF and RFC2833 (Out-Of- Band) in the Avaya G860 Media gateway. Board 9 DTMF settings Step Description Board9->Protocol Settings->DTMF Settings Configuring In Band DTMF Declare RFC2833 in SDP= DontDeclareRFC2833inSDP DTMF RFC2833 Negotiation=NoNegotiation as show below Configuring RFC 2833 Out Of DTMF Declare RFC2833 in SDP= DeclareRFC2833InSDP DTMF RFC2833 Negotiation= EnableRfc2833PTNegotiation as show below 59 of 71

60 4.8 Installing and Configuring Avaya Signed TLS Certificates on the Avaya G860 Media Gateway Installing and Configuring TLS certificates on the Avaya G860 Media gateway enables it to communicate with Avaya SIP Enablement Services and Avaya Meeting Exchange Enterprise S6800 Application Server using TLS Uploading files Configuring the certs Step Description The following certificates are required: private.key, server.cert and root.cert. They can be obtained from an Avaya sales representative. Using the EMS client, on the Menu bar go to Tools Software Manager. Click on the + sign to add a file and click on the Auxiliary Files Tab. Under the Security section, browse and load the files by clicking on Apply as shown below As shown below, the files are loaded on the Server. 60 of 71

61 Step Description To Configure the files on Avaya G860 Media Gateway Click on the MG Status->Properties button and select MG Security Settings as displayed. Configure the certificates as show below. Press Apply. Connect to the Active SC board via telnet, SSH or RS-232 console. Use Global IP address when connecting via telnet or SSH. Login as the CLI user with administrative privileges At the prompt type x509 and press Enter. Wait until expiration date for all configured certificates is calculated and updated. Now configure Certification Expiration Date Reminder Days and Trusted Root Certificate Expiration Date Reminder Days. Click Apply. Go Back and click on the MG Status button in the EMS navigation bar Right click on the desired Media Gateway board and from the popup menu select Maintenance ->Lock and again unlock the board.(this restarts the board and certificates are applied ) Now go back to the MG Security Settings make sure certificates are applied. Note: In this case certificates have been loaded and configured on all available boards 61 of 71

62 5. Interoperability Compliance Testing 5.1. General Test Approach The general test approach was to place calls between the Avaya Meeting Exchange Enterprise S6200 Application Server and the PSTN directly via the Avaya G860 Media Gateway and via Avaya SES utilizing the network configuration displayed in Figure 1. The main objectives were to verify the following: Dial-In Conferencing: o DNIS Scan call function, where conference participants enter a conference as moderator, without entering a participant-access-code (passcode). o Scan call function, where conference participants enter a conference with a valid passcode. Dial-Out Conferencing: o Blast dial o DNIS Scan call function and enter Moderator Code and autonomously invokes a Blast dial to a pre-provisioned dial list of one or more participants. o Manual, where a conference participant is already in a conference as moderator and invokes a Blast dial (by entering *92) to a preprovisioned dial list of one or more participants. o Originator Dial-Out, where a conference participant is already in a conference as moderator and invokes a Dial-Out (by entering *1) to a single participant o Operator Fast Dial, where an operator can Dial-Out to a preprovisioned dial list of one or more participants. Operator Dial-Out to establish an Audio Path. Operator Dial-In to establish an Audio Path. All the conference features using DTMF/Touchtone commands All the conference features using DTMF/Touchtone commands o *0 Request Help o *2 (as moderator) to start/stop conference recording o *3 to start/stop playback of conference recording o *5 (as moderator) toggle lecture on/off o *6 toggle mute on/off o *7 (as moderator) toggle conference security on/off o *8 play the roster of participant name during conference o *93X (where X is defined from 1 to 9) to invoke a subconference o *930 entered from a subconference to go back to the main conference o *93# entered from a subconference (as moderator) to bring all conference participants back to the main conference o ## (as moderator) to end the conference Codecs verified: G711MU, G.711ALaw, G.723,G.729 and G TLS, UDP and TCP connectivity between Avaya Meeting Exchange Enterprise S6200 Application Server and Avaya G860 Media Gateway directly and via Avaya SES In-Band DTMF and RFC of 71

63 6. Verification Steps The following steps were used to verify the administrative steps presented in these Application Notes and are applicable for similar configurations in the field. The verification steps in this section validated the following: The Avaya Meeting Exchange Enterprise S6800 Application Server configuration as displayed in Figure 1 NFS between the Avaya Meeting Exchange Enterprise S6800 Application Server and the RadiSys CMS-9000 Media Server MPC Bi-directional end to end layer-3 connectivity between the MPC in slot 2 on the RadiSys CMS-9000 Media Server and the TP6310 board on the Avaya G860 Media Gateway Verify that the DS3 and DS1 trunks are up on the Avaya G860 Media Gateway by verifying the icons for those entries on the Trunk & Channel Status screen are green Verify successful inbound and outbound calls between the Avaya Meeting Exchange Enterprise S6800 Conferencing Server and the PSTN via Avaya SES Step Description 6.1 Verify all conferencing related processes are running on the Avaya Meeting Exchange Enterprise S6800 Application Server as follows: Log in to the Avaya Meeting Exchange Enterprise S6800 Application Server console to access the CLI with the appropriate credentials. cd to /usr/dcb/bin At the command prompt, run the script dcbps and confirm all processes are running by verifying an associated Process ID (PID) for each process. Note: The process convms is running, verifying the RadiSys CMS-9000 is functioning as a media server in the Avaya S6800 Conferencing Server architecture. [sroot@mxs6800-g860 config]# dcbps 8802? 00:00:01 initdcb 8916? 00:00:00 log 8919? 00:00:00 bridgetranslato 8920? 00:00:00 netservices 8967? 00:00:00 timer 8968? 00:00:00 traffic 8969? 00:00:00 chdbased 8970? 00:00:23 startd 8971? 00:00:00 cdr 8972? 00:00:00 modapid 8973? 00:00:00 schapid 8974? 00:00:01 callhand 8975? 00:00:00 initipcb 8979? 00:00:00 sipagent 8983? 00:00:00 msdispatcher 8985? 00:00:00 servercomms 8987? 00:00:00 convms 9013? 00:00:00 cdrland 3083? 00:00:00 postmaster with 23 children 63 of 71

64 6.2 Verify SIP connectivity between the Avaya Meeting Exchange Enterprise S6800 Application Server and the RadiSys CMS-9000 Media Server. 6.3 Verify that the NFS server is mounted on the RadiSys CMS-9000 Media Server MPC sample configuration as follows: Telnet to the RadiSys SCC console ( ) and log in to access the SCC CLI with the appropriate credentials. From the RadiSys SCC CLI command prompt: o [Not Shown] Enter the command, telnet mpc2 (the hostname provisioned for control interface on the MPC card in slot 2) and log in to the console to access the MPC CLI with the appropriate credentials. From the RadiSys MPC CLI command prompt, change directory to /mnt and list files to verify the NFS server is mounted on this RadiSys CMS-9000 Media Server MPC. [[admin@duqampc3615 ~]$ cd /mnt [admin@duqampc3615 mnt]$ ls nvramdisk ramdisk flashdisk pfa_ [admin@duqampc3615 mnt]$ 6.4 Verify write privileges to the NFS server from the mount point on the RadiSys CMS-9000 Media Server MPC sample configuration as follows: [Not Shown] From /mnt, change directory to pfa_ /usr3/confrp and list files to verify the directory is empty. Create a file that does not already exist on the on the NFS server. List the files in pfa_ /usr3/confrp and verify newly created file is present. [admin@duqampc3615 mnt]$ touch test.nfs [admin@duqampc3615 mnt]$ ls -l -rw-r--r-- 1 admin 0 Feb 10 15:11 test.nfs 6.5 From the NFS server, verify the file created from the mount point on the RadiSys CMS-9000 Media Server MPC is present in /usr3/ipcb/usr3/confrp. [sroot@mxs6800-g860]pwd /usr3/ipcb/usr3/confrp [sroot@mxs6800-g860]ls -l total 0 -rw-r--r Feb 10 15:11 test.nfs 64 of 71

65 6.6 Verify bi-directional end to end layer-3 connectivity between the MPC in slot 2 on the RadiSys CMS-9000 Media Server and the TP6310 board on the Avaya G860 Media Gateway using ping or another network diagnostic tool. Bi-directional end to end layer-3 connectivity between the MPC in slot 2 on the RadiSys CMS-9000 Media Server and the TP6310 board on the Avaya G860 Media Gateway implies a bi-directional audio path, e.g., layer-3 connectivity in one direction may imply one-way audio. Verify bi-directional layer-3 connectivity between the MPC in slot 2 on the RadiSys CMS-9000 Media Server and the TP6310 board on the Avaya G860 Media Gateway as follows: From the MPC in slot 2 on the RadiSys CMS-9000 Media Server, verify layer-3 connectivity to the TP6310 board on the Avaya G860 Media Gateway. From the TP6310 board on the Avaya G860 Media Gateway verify layer-3 connectivity to the MPC in slot 2 on the RadiSys CMS-9000 Media Server. 65 of 71

66 6.1. Verify Call Routing The following steps utilize the network configuration displayed in Figure 1. Step Description The purpose of this step is to obtain a baseline for the number of ports created on the MPC in slot 2 on the RadiSys CMS-9000 Media Server prior to the scenario invoked.verify port utilization on the RadiSys CMS-9000 Media Server MPC in slot 2 via the web GUI as follows: [Optional, Not Shown] Reset statistics for the MPC card in slot 2 as follows: o Click Performance Mgt->Reset Statistics. o Select the Slot Number for the MPC. For these Application Notes, the MPC was placed in Slot number 2. o Click Execute and wait for the message Statistics for card in slot 2 have been reset to display in the Output Messages window. Click Performance Mgt->Show Real-Time Statistics. Select the Slot Number for the MPC. For these Application Notes, the MPC was placed in Slot number 2. Click Execute. 66 of 71

67 6.1.2 From the Show Real-Time Statistics screen that is displayed, note that the number of Ports Created for the MPC in slot 2 is of 71

68 6.1.3 Verify end to end signalling/media connectivity between the Avaya Meeting Exchange Enterprise S6800 Conferencing Server and the PSTN via the Avaya G860 Media Gateway. This is accomplished by placing calls to and from the Avaya Meeting Exchange Enterprise S6800 Conferencing Server. This step utilizes the Avaya Bridge Talk application to verify calls to and from the Avaya Meeting Exchange Enterprise S6800 Conferencing Server are managed correctly, e.g., callers are added/removed from conferences.. From an endpoint on the PSTN, Dial 70001/80001 to enter a conference as Moderator while simultaneously invoking the associated Auto Blast dial feature for this conference. If not already logged on, log in to the Avaya Bridge Talk application with the appropriate credentials. Double-Click on the highlighted Conf # to open a Conference Room window. Verify conference participants are added/removed from conferences by observing the Conference Navigator and/or Conference Room windows. Note: The ANI extracted via this procedure is displayed in the Caller ID field for the participant dialing-in to this conference. 68 of 71

69 6.1.4 Verify ISDN Trunk & Channel Status on the Avaya G860 Media Gateway as follows: Open a web browser and enter the following URL: address of the Active TP6310 board on the Avaya G860 Media Gateway > Log in to the TP6310 board on the Avaya G860 Media Gateway with the appropriate credentials. Click on Status & Diagnostics. Click on Channel Status. Note: The Trunk & Channel Status displays No Alarms for the DS3 and Active OK for the constituent DS1s This screen capture also depicts the channel selection pattern for the three Active channels on this trunk that are associated with the scenario invoked. Note: The PSTN is administered to select channels in a descending pattern over the ISDN-PRI trunk between the PSTN and the Avaya G860 Media Gateway. This display shows Channel 23 on Trunk 4 is selected by the PSTN for Dial-In to the Avaya Meeting Exchange Enterprise S6800 Conferencing Server. Channel 1 on Trunk 1 is selected by the Avaya G860 Media Gateway to Dial-Out to the PSTN over the CAS trunk Channel 1 on Trunk 3 is selected by the Avaya G860 Media Gateway to Dial-Out to the PSTN over the ISDN-PRI trunk. 69 of 71