• The $MPSHOME/mpsN/ directory contains files specific to a single MPS 500
component where N is the node number.
SIP/RTP
This section details the hardware needed to implement SIP/RTP on the MPS system.
The MPS architecture can include the implementation of voice or vocabulary transmission over a
private or public IP network. The system is RFC3261 SIPcompliant and systems running SIP
compliant client software can initiate or receive calls. Calls can be made from client to phone, phone
to client, or client to client. MPS SIP can interface with both E1 and T1 standards as a gateway.
Clients can also interact with the vocabulary driven IVR menus.
The following diagram shows a typical SIP/RTP implementation.
SIP/RTP Hardware
Add one of the following hardware packages to the TMS for your required number of SIP/RTP
channels:
Channels
Supported
60
240
DCC
3000 (P/N 5036437-01 or 5036474-01)
3000 (P/N 5036437-01 or 5036474-01)
CTPM
TPM 200 TPM 800 TPM 1100-72
TPM 800 TPM 1100-240 TPM 1100-240
AMR
SIP/RTP
October 2014
Avaya Media Processing Server 500 Hardware Installation and Maintenance
69