10.8.0.2 Enet_B_Gateway
10.7.1.8 nic2-a
The MPS 500 clients and AP server networking are now configured. Reboot the system and verify
that all MPS 500 clients load properly through bootp.
Repeat the procedure for each Application Processor in an MPS 500 cluster.
Configuration Files
Configuration files for the MPS 500 are invoked as part of the system Startup and Recovery Process
(SRP). During the SRP, configuration files are read to inform the system software of hardware
configurations, resources, and protocols. Resources typically available to the MPS 500 are DTMF
detectors and generators, call progress detectors (CPD), telephone lines, and tone generators
(TGEN). Typical line protocols are ISDN and SS7 for digital spans, and loop start for analog.
Exercise caution when editing configuration files as there are two types of remark characters used in
the configuration files for the MPS 500 product. The remark characters used are the octothorpe (#)
and semicolon (;).
For detailed information about the following configuration files, refer to the MPS System Reference
Manual.
MPSHOME
During installation, a base directory is created to install the files. By default, this directory is:
/opt/vps
For Windows 2003:
C:\Program Files\Avaya\SelfService
For Windows 2008 R2:
C:\Program Files (x86)\Avaya\SelfService
The installation also defines the environment variable MPSHOME to refer to this home
directory. In most cases:
$MPSHOME = /opt/vps
Configuration Files
October 2014
Avaya Media Processing Server 500 Hardware Installation and Maintenance
63