Avaya G860 User manual

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 1 of 71 MXS6800SES-G860
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.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 2 of 71 MXS6800SES-G860
TABLE OF CONTENTS
1. Introduction................................................................................................................. 3
1.1. Avaya Meeting Exchange Enterprise S6800 Conferencing Server....... 4
1.2. Avaya G860 Media Gateway............................................................................ 5
2. Equipment and Software Validated...................................................................... 5
3. Configure the Avaya Meeting Exchange Enterprise S6800 Conferencing
Server................................................................................................................................6
3.1. Configure the Avaya Meeting Exchange Enterprise S6800 Application
Server............................................................................................................................ 6
3.2. Configure the RadiSys CMS-9000 Media Server...................................... 10
3.3. Network File System........................................................................................ 19
Configure NFS on the Avaya Meeting Exchange Enterprise S6800
Application Server............................................................................................... 19
Configure NFS on the RadiSys CMS-9000 Media Server.......................... 22
3.4. CBUTIL Utility.................................................................................................... 25
3.5. Bridge Talk......................................................................................................... 26
3.6. Configure the Avaya SIP Enablement Services (SES)........................... 31
4. Configure the Avaya G860 Media Gateway...................................................... 33
4.1. Configure the Avaya G860 Media Gateway Properties.......................... 35
4.2. Configure the TP6310 Board......................................................................... 36
4.3. Configure DS3/DS1 Trunking........................................................................ 40
4.4. Configure SIP and T1 Trunking.................................................................... 47
4.5. Configure B-channels..................................................................................... 50
4.6. Administer Call Routing Rules..................................................................... 53
4.7 Configuring In-band DTMF and RFC2833 (Out-Of-band) in the Avaya
G860 Media Gateway............................................................................................... 59
4.8 Installing and Configuring Avaya Signed TLS Certificates on the
Avaya G860 Media Gateway.................................................................................. 60
5. Interoperability Compliance Testing.................................................................. 62
5.1. General Test Approach................................................................................... 62
6. Verification Steps.................................................................................................... 63
6.1. Verify Call Routing........................................................................................... 66
7. Conclusion................................................................................................................ 70
8. Additional References............................................................................................ 70

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 3 of 71 MXS6800SES-G860
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.
IP Network
DevConnect
Network
SIL (Dublin) AVAYA G860
MEDIA
GATEWAY
Simulated
PSTN
DS3
Avaya SIP
Enablement
Services
Host Mapping
One-X
Desktop
BLUE
DDI/DNIS 70001
RED
DDI/DNIS 80001
GREEN
DDI/DNIS 10001
10.1.2.0/24192.168.36.1
10.1.2.63
192.168.36.11
Avaya Meeting
Exchange Enterprise
S6800 Application
Server
192.168.36.12
RadiSys CMS 9000
192.168.36.14-17
123
456
789
0
ABC DEF
GHI JLK MNO
PQRS TUV WXYZ
CONFERENCE
HEADSET
SPEAKER
Scroll
#
*
123
456
789
0
ABC DEF
GHI JLK MNO
PQRS TUV WXYZ
CONFERENCE
HEADSET
SPEAKER
Scroll
#
*
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 4.6.3.
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

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 4 of 71 MXS6800SES-G860
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 G726-40 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:
oOne Media Processor Card (MPC).
oOne Shelf Control Card (SCC).
•Signalling between the Avaya Meeting Exchange Enterprise S6800 Application
Server(s) and the RadiSys CMS-9000 Media Server is SIP.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 5 of 71 MXS6800SES-G860
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) 5.1.0.0.12
Avaya G860 Media Gateway
•Chassis Type
•Software Version
•Board Type
•EMS Server
•EMS Client
5.2.73
M5k10
5.2.49
Tp6310Ds3
5.2.60
5.2.60
Avaya SIP Enablement Services (SES) 5.1.1 build 415.1
Avaya Meeting Exchange Enterprise S6800 Application
Server (MX) 5.1 build .161
RadiSys CMS 9000 4.13.0.4
Table 1: Hardware and Software Versions

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 6 of 71 MXS6800SES-G860
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).
3.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
3.1.1 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.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 7 of 71 MXS6800SES-G860
Step Description
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
oIPAddress=192.168.36.12
•Add a line to populate the From Header Field in SIP INVITE messages
oMyListener=sip:[email protected]
Note: The user field 6000, defined for this SIP URI must conform
to RFC 3261. 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:
orespContact=<sip:[email protected]:5061;transport=tls>
Note: Configure the following if your using TCP and UDP
orespContact=<sip:[email protected]:5060;transport=tcp>
orespContact=<sip:[email protected]: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.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 8 of 71 MXS6800SES-G860
Step Description
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:
oEdit /usr/ipcb/config/telnumToUri.tab file with a text editor,
oAdd a line to the file to route outbound calls from the Avaya
Meeting Exchange S6200 Server to the Avaya G860 Media
Gateway:
* sip:[email protected]:5061;transport=tls G860
b)
•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:
oEdit /usr/ipcb/config/telnumToUri.tab file with a text editor.
oAdd 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:[email protected]:5061;transport=tls SES

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 9 of 71 MXS6800SES-G860
Step Description
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:
oEdit the /usr/ipcb/config/processTable.cfg file with a text editor
oAdd an ipAddress for each corresponding procces name in this file.
Note: The processTable.cfg for these Application Notes contains
IP Addresses of 0.0.0.0, where 0.0.0.0 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 110 0 noexecute
192.168.36.12
bridget700 100 0 noexecute
192.168.36.12 dspEvents/msDispatcher,netEvents/sipAgent
commsProcess 111 1 /usr/dcb/bin/serverComms
192.168.36.12
sipAgent 101 1 /usr/dcb/bin/sipagent
192.168.36.12 dspEvents/msDispatcher,appEvents/bridget700
msDispatcher 102 1 /usr/dcb/bin/msdispatcher
192.168.36.12
netEvents/sipAgent,appEvents/bridget700,dspEvents/mediaServer
mediaServer 141 1 /usr/dcb/bin/convMS
192.168.36.12 appEvents/msDispatcher,netEvents/msDispatcher 1
notifyService 113 1 noexecute
127.0.0.1:10235
snmpAgent 120 1 noexecute
192.168.36.12
#mxmonitor 200 1 noexecute
<aps1-ip> appEvents/msDispatcher,netEvents/msDispatcher aps1
"processTable.cfg" 16L, 1826C

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 10 of 71 MXS6800SES-G860
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
3.2.1 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>.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 11 of 71 MXS6800SES-G860
Step Description
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.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 12 of 71 MXS6800SES-G860
Step Description
3.2.3 From the RS-232 Interface Main Menu screen that is displayed, select
Network Settings and press <Enter>.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 13 of 71 MXS6800SES-G860
Step Description
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 (0.0.0.0). 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>.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 14 of 71 MXS6800SES-G860
Step Description
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.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 15 of 71 MXS6800SES-G860
Step Description
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:
ohttp://<IP address of RadiSys CMS-9000 Media Server >
•Log in to the RadiSys CMS-9000 Media Server with the appropriate
credentials.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 16 of 71 MXS6800SES-G860
Step Description
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.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 17 of 71 MXS6800SES-G860
Step Description
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 2.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 18 of 71 MXS6800SES-G860
Step Description
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.

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 19 of 71 MXS6800SES-G860
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-
9000 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
3.3.1 Log in to the Avaya Meeting Exchange Enterprise S6800 Application Server
console to access the CLI with the appropriate credentials.
3.3.2 The NFS server communicates with the control interface on the RadiSys CMS-
9000 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:
o192.168.36.14 mpc2
Where 192.168.36.14 and mpc2 are the IP address and hostname
of the control interface assigned to the RadiSys CMS-9000 Media
Server MPC

RJ; Reviewed:
SPOC 3/23/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 20 of 71 MXS6800SES-G860
Step Description
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:
oNFSServerIPAddress=192.168.36.12
Where 192.168.36.12 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:
oMediaServerIP_1=192.168.36.15
Where 192.168.36.15 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:
oMediaServerInterfaceSipListenPort_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=192.168.36.12
#
# MPC 1 on RadiSys CMS-9000 Media Server (Control Port)
MediaServerIP_1=192.168.36.15
MediaServerInterfaceSipListenPort_1=5050