Avaya Media Processing Server Series System (Software Release 2.1) Reference guide

  • Hello! I am an AI chatbot trained to assist you with the Avaya Media Processing Server Series System (Software Release 2.1) Reference guide. I’ve already reviewed the document and can help you find the information you need or explain it in simple terms. Just ask your questions, and providing more details will help me assist you more effectively!
Avaya Business Communications Manager
Release 6.0
Document Status: Standard
Document Number: P0602477
Document Version: 3.1.12
Date: June 2010
Avaya Media Processing Server Series System
Reference Manual
(Software Release 2.1)
© 2010 Avaya Inc.
All Rights Reserved.
Notices
While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing,
Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document
without the obligation to notify any person or organization of such changes.
Documentation disclaimer
Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation
unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya,
Avaya’s agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with,
subsequent modifications, additions or deletions to this documentation, to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s) provided by
Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not
necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will
work all the time and has no control over the availability of the linked pages.
Warranty
Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In
addition, Avaya’s standard warranty language, as well as information regarding support for this product, while under warranty, is
available to Avaya customers and other parties through the Avaya Support Web site: http://www.avaya.com/support
Please note that if you acquired the product from an authorized reseller, the warranty is provided to you by said reseller and not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/
ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM
AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A
COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO
BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE
OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE
RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A
LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU,
ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE
SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END USER"), AGREE TO THESE
TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE ("AVAYA").
Copyright
Except where expressly stated otherwise, no use should be made of the Documentation(s) and Product(s) provided by Avaya. All content
in this documentation(s) and the product(s) provided by Avaya including the selection, arrangement and design of the content is owned
either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating
to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any
content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or
use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law.
Third Party Components
Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements
("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party
Terms"). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code),
and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the
Avaya Support Web site: http://support.avaya.com/Copyright.
Trademarks
The trademarks, logos and service marks ("Marks") displayed in this site, the documentation(s) and product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior
written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the documentation(s) and
product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-Avaya
trademarks are the property of their respective owners.
Downloading documents
For the most current versions of documentation, see the Avaya Support. Web site: http://www.avaya.com/support
Contact Avaya Support
Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone
number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://
www.avaya.com/support
Table of Contents
# P0602477 Ver: 3.1.11 Page 3
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
How to Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Organization of This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Conventions Used in This Manual . . . . . . . . . . . . . . . . . . . . . . . . 13
Solaris and Windows 2000 Conventions . . . . . . . . . . . . . . . . . . . 15
Trademark Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Avaya MPS Architectural Overview . . . . . . . . . . . . . . . . . . 17
Overview of the Avaya Media Processing Server (MPS) System 18
System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Front Control Panel (FCP) . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Variable Resource Chassis (VRC) . . . . . . . . . . . . . . . . . . . . 22
Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
VRC Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Drive Bays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Application Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Network Interface Controller (NIC) or Hub-NIC . . . . . . 27
Telephony Media Server (TMS). . . . . . . . . . . . . . . . . . . . . . 28
Phone Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Multiple DSP Module (MDM) . . . . . . . . . . . . . . . . . . . . 31
System LAN Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Field Programmable Gate Arrays (FPGA) and the Boot
ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
TelCo Connector Panel (TCCP) . . . . . . . . . . . . . . . . . . . . . 33
Software Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Software Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 35
ASE Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
ASE/VOS Integration Layer . . . . . . . . . . . . . . . . . . . . . . 39
VOS Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
System Utilities and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
alarm . . . . . . . . . . . . . . . . 51
dlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
dlt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
PeriProducer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
PeriReporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
PeriStudio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
PeriView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
PeriWeb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
vsh . . . . . . . . . . . . . . . . . 60
Avaya Media Processing Server Series System Reference Manual
Page 4 # P0602477 Ver: 3.1.11
Base System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Base System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
System Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Solaris Startup/Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Windows Startup/Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . 69
SRP (Startup and Recovery Process) . . . . . . . . . . . . . . . . . . 70
Manually Starting and Stopping SRP . . . . . . . . . . . . . . . 70
VPS Topology Database Server (VTDB) . . . . . . . . . . . . 71
Restart of Abnormally Terminated Programs . . . . . . . . . 72
Communication with VOS Processes . . . . . . . . . . . . . . . 72
SRP Configuration Command Line Arguments . . . . . . . 74
VSH Shell Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 75
SRP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Call Control Manager (CCM/CCMA) . . . . . . . . . . . . . . . . . 82
Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
The hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
User Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
The .xhtrahostsrc File. . . . . . . . . . . . . . . . . . . . . . . . . 86
The MPSHOME Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
The MPSHOME/common Directory . . . . . . . . . . . . . . . . . . . . . . 88
The MPSHOME/common/etc Directory . . . . . . . . . . . . . . 88
The srp.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
The vpshosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
The compgroups File . . . . . . . . . . . . . . . . . . . . . . . . . 95
The gen.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
The global_users.cfg File . . . . . . . . . . . . . . . . . . 98
The alarmd.cfg and alarmf.cfg Files . . . . . . . . . 99
The pmgr.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
The periview.cfg File . . . . . . . . . . . . . . . . . . . . . . 102
The MPSHOME/common/etc/tms Directory . . . . . . . . 103
The sys.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . 103
The tms.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Protocol Configuration Files . . . . . . . . . . . . . . . . . . . . . . . 123
The $MPSHOME/packages Directory . . . . . . . . . . . . . . 125
%MPSHOME%\PERIase - /opt/vps/PERIase. . 127
The /etc/ase.conf file . . . . . . . . . . . . . . . . . . . . . 127
The /etc/services File . . . . . . . . . . . . . . . . . . . . . 129
%MPSHOME%\PERIbrdge - /opt/vps/PERIbrdge 132
%MPSHOME%\PERIdist - /opt/vps/PERIdist. 133
%MPSHOME%\PERIglobl - /opt/vps/PERIglobl 133
%MPSHOME%\PERIview - /opt/vps/PERIview. 134
%MPSHOME%\PERIplic - /opt/vps/PERIplic. 134
%MPSHOME%\PERItms -
/opt/vps/PERItms. . 134
The /cfg/atm_triplets.cfg File . . . . . . . . . . . 135
The /cfg/ps_triplets.cfg File . . . . . . . . . . . . 136
Table of Contents
# P0602477 Ver: 3.1.11 Page 5
The /cfg/tms_triplets.cfg File . . . . . . . . . . . 136
%MPSHOME%\PERImps - /opt/vps/PERImps . 137
The MPSHOME/tmscommN Directory. . . . . . . . . . . . . . . . 138
MPS 500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
MPS 1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
The MPSHOME/mpsN Directory . . . . . . . . . . . . . . . . . . . . 139
The MPSHOME/mpsN/apps Directory . . . . . . . . . . . 140
The MPSHOME/mpsN/etc Directory . . . . . . . . . . . . . 142
VMM Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . 144
The vmm.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
The vmm-mmf.cfg File . . . . . . . . . . . . . . . . . . . . . . . 146
ASE Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . 148
The ase.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
The aseLines.cfg File . . . . . . . . . . . . . . . . . . . . . . 149
CCM Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . 151
The ccm_phoneline.cfg File . . . . . . . . . . . . . . . . 151
The ccm_admin.cfg File . . . . . . . . . . . . . . . . . . . . . 155
TCAD Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . 157
The tcad-tms.cfg File . . . . . . . . . . . . . . . . . . . . . . 157
The tcad.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
TRIP Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . 159
The trip.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
TMS Watchdog Functions . . . . . . . . . . . . . . . . . . . . . . . . . 160
Common Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Multi-Media Format Files (MMFs) . . . . . . . . . . . . . . . . . . . . . . 164
How to Create an MMF File. . . . . . . . . . . . . . . . . . . . . . . . 164
Vocabulary MMF Files vs. CMR MMF Files . . . . . . . . . . 165
Activating MMF Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Delimited and Partial Loading . . . . . . . . . . . . . . . . . . . 168
Audio Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Custom Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Using Hash Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
System MMF Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Application-Specific MMF Files . . . . . . . . . . . . . . . . . 174
Default Vocabulary and Record MMF Files . . . . . . . . 175
Diagnostics and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Synchronizing MMF Files Across Nodes. . . . . . . . . . . . . . 177
ZAP and MMF files on the MPS . . . . . . . . . . . . . . . . . 177
MMF Abbreviated Content (MAC) File . . . . . . . . . . . . 178
Basic Implementation (Low Volume/Traffic) . . . . . . . 178
Advanced Implementation (High Volume/Traffic) . . . 181
Updating a Specific Element . . . . . . . . . . . . . . . . . . . . 185
Exception Processing . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Avaya Media Processing Server Series System Reference Manual
Page 6 # P0602477 Ver: 3.1.11
Synchronization (ZAP) Command Summary . . . . . . . . 191
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Call Simulator Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
VEMUL Script Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Script Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Script Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Phone Line Behavior During Simulation . . . . . . . . . . . . . . 199
Call Simulator Conditions and Usage. . . . . . . . . . . . . . . . . 199
Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Example Call Simulation Script Files. . . . . . . . . . . . . . . . . 202
Alarm Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Filtering Precepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 205
alarmf Command Line Options . . . . . . . . . . . . . . . . 206
Notation Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Logical Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Action Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Filtering Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Interapplication/Host Service Daemon Data Exchange . . . . . . . 215
VMST (VMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Starting Under SRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
PeriPro Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
VTCPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Single Connection to Host . . . . . . . . . . . . . . . . . . . . . . 221
Multiple Connections to Multiple Hosts . . . . . . . . . . . . 221
One Connection Per Line . . . . . . . . . . . . . . . . . . . . . . . 222
Multiple VTCPD Daemons . . . . . . . . . . . . . . . . . . . . . 222
Host Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Attaching to VMST . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Message Identification (ID) . . . . . . . . . . . . . . . . . . . . . 231
Connection Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Application-Host Interaction Configuration Options . . 234
Queuing Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Monitoring Host Connections . . . . . . . . . . . . . . . . . . . . 238
Backup LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
VFTPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Specifying a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Automatic Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Automatic FTP Logins . . . . . . . . . . . . . . . . . . . . . . . . . 241
Identifying the Configured Host Computers . . . . . . . . 242
Table of Contents
# P0602477 Ver: 3.1.11 Page 7
Configuration Procedures and Considerations . . . . . . . . . 243
Making Changes to an Existing System . . . . . . . . . . . . . . . . . . 244
Adding Spans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Modifying the Span Resource Set . . . . . . . . . . . . . . . . . . . 244
Changing Pool/Class Names . . . . . . . . . . . . . . . . . . . . . . . 245
Renumbering a Component . . . . . . . . . . . . . . . . . . . . . . . . 245
Renaming a Solaris MPS Node . . . . . . . . . . . . . . . . . . . . . 246
Renaming a Windows MPS Node . . . . . . . . . . . . . . . . . . . 247
Introducing a New Node. . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Enabling Statistics Collection. . . . . . . . . . . . . . . . . . . . . . . 249
Debug Terminal Connection . . . . . . . . . . . . . . . . . . . . . . . 250
Connection Using a Dumb Terminal or PC . . . . . . . . . 250
Connection from the System Console . . . . . . . . . . . . . 250
Verifying/Modifying Boot ROM Settings . . . . . . . . . . . . . . . . 252
DCC Boot ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
TMS Boot ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
NIC Boot ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Resetting the NIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
TMS Computer Telephony (CT) Bus Clocking . . . . . . . . . . . . 265
N+1 Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Sample MPS 1000 N+1 Redundancy System Configuration 267
TRIP Failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Directory Layout on a Secondary (Backup) Node . . . . . . . 269
Least Cost Routing Daemon . . . . . . . . . . . . . . . . . . . . . . . . 271
Redundancy Configuration Daemon (RCD). . . . . . . . . . . . 271
The Failover/Failback Process . . . . . . . . . . . . . . . . . . . . . . 273
Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . 274
Create the Secondary Node . . . . . . . . . . . . . . . . . . . . . . 274
TMSCOMM Component Configuration . . . . . . . . . . . 274
Edit the vpshosts File . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Edit the tms.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Edit TRIP and RCD Configuration Files . . . . . . . . . . . 276
Edit the gen.cfg file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
PMGR configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Media Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
First Startup After Configuration . . . . . . . . . . . . . . . . . . . . 280
Verifying N+1 Functionality . . . . . . . . . . . . . . . . . . . . . . . 283
Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Speech Server Resources in N+1 Redundancy. . . . . . . . . . 285
Pool Manager (PMGR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Resource Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Allocation/Deallocation . . . . . . . . . . . . . . . . . . . . . . . . 288
Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Avaya Media Processing Server Series System Reference Manual
Page 8 # P0602477 Ver: 3.1.11
Resource Identifier/String . . . . . . . . . . . . . . . . . . . . . . . 289
Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Port Service States . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Network Failure Detection (Pinging) . . . . . . . . . . . . . . 291
Database Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Platform Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Starting a Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Starting a Writer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Database Format Conversion . . . . . . . . . . . . . . . . . . . . . . . 293
Reader/Writer Synchronization . . . . . . . . . . . . . . . . . . . . . 293
File Size Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Call Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Listening to Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Antivirus Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Secure Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Preface
Avaya Media Processing Server Series System Reference Manual
Page 10 # P0602477 Ver: 3.1.11
Scope
The Avaya Media Processing Server Series System Reference Manual details the
procedures and parameters for configuring the Avaya Media Processing Server (MPS)
Series system for online operation in a variety of telephony environments. In addition,
this manual provides configuration parameters and basic file information for elements
common to all MPS within the network. Note, however, that though there are two
basic products available in the MPS system - a single rack-mounted version known as
the Avaya MPS Series and a cabinet enclosed network configuration which relies on
the MPS 500 - this manual deals almost exclusively with the latter.
In addition to this document, the Avaya Media Processing Server Series System
Operator’s Guide may be particularly helpful. They provide a road map through the
major functions in the daily operation and monitoring of the MPS system. For a list of
other user manuals, see the Reference Material link in PeriDoc.
Intended Audience
This manual is intended for the persons who will be configuring the MPS for a
specific site and/or maintaining it from a particular perspective. The reader should be
familiar with telecommunications and computer equipment, their functions, and
associated terminology. In addition, the reader must be familiar with the
characteristics of the specific installation site, including site-specific power systems,
computer systems, peripheral components, and telephone networks.
Some of the material covered here involves the configuration of basic and critical
MPS parameters. Small inaccuracies in the configuration of these parameters can
impede system performance. Individuals without highly specialized knowledge in this
area should not attempt to change the defaults.
This guide assumes that the user has completed an on-site system familiarization
training program conducted as part of the initial system installation. Basic knowledge
of the Solaris and/or Windows 2000 operating system(s) is also assumed.
Preface
# P0602477 Ver: 3.1.11 Page 11
How to Use This Manual
This manual uses many standard terms relating to computer system and software
application functions. However, it contains some terminology that can only be
explained in the context of the MPS system. Refer to the Glossary of Avaya Media
Processing Server Series Terminology for definitions of product specific terms.
It is not essential that this document be read cover-to-cover, as the entire contents is
not universally applicable to all MPS environments. It is essential, however, that there
is a clear understanding of exactly what information pertains to your environment and
that you can identify, locate, and apply the information documented in this manual.
Later, you can use the Table of Contents to locate topics of interest for reference and
review.
If you are reading this document online, use the hypertext links to quickly locate
related topics. Click once with your mouse while positioned with your cursor over the
hypertext link. Click on any point in a Table of Contents entry to move to that topic.
Click on the page number of any Index entry to access that topic page. Use the
hyperlinks at the top and bottom of each HTML “page” to help you navigate the
documentation. Pass your cursor over the Avaya Globemark to display the title,
software release, publication number, document release, and release date for the
HTML manual you are using.
For additional related information, use the Reference Material link in PeriDoc. To
familiarize yourself with various specialized textual references within the manual, see
Conventions Used in This Manual on page 13.
Periphonics is now part of Avaya. The name Periphonics, and variations thereof,
appear in this manual only where it is referred to in a product. (For example, a
PeriProducer application, the PERImps package, the perirev command, etc.)
Avaya Media Processing Server Series System Reference Manual
Page 12 # P0602477 Ver: 3.1.11
Organization of This Manual
This document is designed to identify the procedures and configuration parameters
required for successful MPS operations. It provides an overview of the MPS system
and proceeds to document both basic and common system parameters. The following
passages provide an overview of the information contained in each area of this
manual.
Chapter 1 - Avaya Media Processing Server Series Architectural Overview
Provides a description of the MPS system and an overview of its hardware
and software. Diagrams and describes the MPS structure, its software
processes, and identifies other system utilities.
Chapter 2 - Base System Configuration
Describes and diagrams the system directory structure and startup and
shutdown, delineates the Startup and Recovery Process (SRP), and details
MPSHOME and all required configuration files.
Chapter 3 - Common Configuration
Documents the facilities available on all (common) MPS platforms. Details
MultiMedia Format (MMF) file creation and utilization. Also covers call
simulation, alarm filtering, and exchange of data between applications, hosts,
and MPS.
Chapter 4 - Configuration Procedures and Considerations
Contains common procedures and comprehensive considerations for
modifying existing systems and adding features.
Appendix A - Process and Utility Command Summary
Lists commands for some of the processes and utilities most commonly
interacted with in the MPS system. Provides brief definitions for each and
links to more detailed information.
Appendix B - Avaya MPS Specifications
Contains physical, electrical, environmental, and interface specifications for
the MPS.
Preface
# P0602477 Ver: 3.1.11 Page 13
Conventions Used in This Manual
This manual uses different fonts and symbols to differentiate between document
elements and types of information. These conventions are summarized in the
following table.
Conventions Used in This Manual Sheet 1 of 2
Notation Description
Normal text
Normal text font is used for most of the document.
important term
The Italics font is used to introduce new terms, to highlight
meaningful words or phrases, or to distinguish specific terms from
nearby text.
system
command
This font indicates a system command and/or its arguments. Such
keywords are to be entered exactly as shown (i.e., users are not to
fill in their own values).
command,
condition
and alarm
Command, Condition and Alarm references appear on the screen
in magenta text and reference the Command Reference Manual,
the PeriProducer Users Guide, or the Alarm Reference Manual,
respectively. Refer to these documents for detailed information
about
Commands, Conditions, and Alarms.
file name /
directory
This font is used for highlighting the names of disk directories, files,
and extensions for file names. It is also used to show displays on
text-based screens (e.g., to show the contents of a file.)
on-screen field
This font is used for field labels, on-screen menu buttons, and
action buttons.
<KEY NAME>
A term that appears within angled brackets denotes a terminal
keyboard key, a telephone keypad button, or a system mouse
button.
Book Reference
This font indicates the names of other publications referenced
within the document.
cross reference
A cross reference appears on the screen in blue text. Click on the
cross reference to access the referenced location. A cross
reference that refers to a section name accesses the first page of
that section.
The Note icon identifies notes, important facts, and other keys to
understanding.
!
The Caution icon identifies procedures or events that require
special attention. The icon indicates a warning that serious
problems may arise if the stated instructions are improperly
followed.
Avaya Media Processing Server Series System Reference Manual
Page 14 # P0602477 Ver: 3.1.11
The flying Window icon identifies procedures or events that apply
to the Windows 2000 operating system only.
1
The Solaris icon identifies procedures or events that apply to the
Solaris operating system only.
2
1. Windows 2000 and the flying Window logo are either trademarks or registered
trademarks of the Microsoft Corporation.
2. Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the
United States and other countries.
Conventions Used in This Manual Sheet 2 of 2
Notation Description
Preface
# P0602477 Ver: 3.1.11 Page 15
Solaris and Windows 2000 Conventions
This manual depicts examples (command line syntax, configuration files, and screen
shots) in Solaris format. In certain instances Windows 2000 specific commands,
procedures, or screen shots are shown where required. The following table lists
examples of general operating system conventions to keep in mind when using this
manual with either the Solaris or NT operating system.
Trademark Conventions
The following trademark information is presented here and applies throughout for
third party products discussed within this manual. Trademarking information is not
repeated hereafter.
Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the United
States and other countries.
Microsoft, Windows, Windows 2000, Internet Explorer, and the Flying Windows logo
are either trademarks or registered trademarks of Microsoft Corporation.
Netscape® and Netscape Navigator® are registered trademarks of Netscape
Communications Corporation in the United States and other countries. Netscape's
logos and Netscape product and service names are also trademarks of Netscape
Communications Corporation, which may be registered in other countries.
Solaris Windows 2000
Environment $MPSHOME %MPSHOME%
Paths $MPSHOME/common/etc %MPSHOME%\common\etc
Command <command> & start /b <command>
Avaya Media Processing Server Series System Reference Manual
Page 16 # P0602477 Ver: 3.1.11
This page has been intentionally left blank.
This chapter covers:
Avaya MPS Architec-
tural Overview
1. Overview of the Avaya
Media Processing Server
Series System
2. System Architecture
3. System Utilities and
Software
Avaya Media Processing Server Series System Reference Manual
Page 18 # P0602477 Ver: 3.1.11
Overview of the Avaya Media Processing Server System
The Avaya Media Processing Server (MPS) Series products comprise hardware and
software to create a call and web-based processing environment. These systems
integrate the call processing environment with speech, telephony, data
communications, and transaction processing functions. The platform is based on the
Avaya Telephony Media Server (TMS) which provides high phone port densities and
increased user flexibility and extensibility. The basic TMS assembly provides
resources for telephony media management including switching/bridging, digital
signal processing, voice and data memory, and network interfaces. A variety of
interactive voice processing applications are accommodated, from simple information
delivery services to complex multimedia (voice/fax/data/web) call processing
implementations with local databases, multiple services, and transaction processing
functions.
The MPS system supports a wide selection of telephony and host computer
connectivity interfaces for easy integration into an existing data-
processing/communications environment. It also includes a set of easy to use object-
oriented Graphical User Interface (GUI) tools. These tools are used for:
application and vocabulary development
system configuration, control, and monitoring
collection and reporting of statistical data
access to on-line documentation and its concurrent implementations
The application development environment provides a totally graphical environment
for the entire application life cycle, and also allows typically phone-line applications
to be ported over to Internet-based Web usage. The PeriProducer GUI is the suggested
tool of choice for application development. The PeriWeb package allows these phone
line applications to be run as interactive World Wide Web apps.
The MPS systems employ industry standards and distributed processing in an open
architecture, allowing plug-in integration of future technological developments. In
addition, networking elements of the MPS support multiple LAN/WAN interfaces,
providing an environment ready for distributed computing.
This chapter of the Avaya Media Processing Server Series System Reference Manual
presents an overall view of the MPS hardware and software, describes the software
processes responsible for operations, and provides a series of diagrams that illustrate
both hardware and software relationships.
Base System Configuration on page 64, documents the process of getting the MPS
system up and running, identifies the individual configuration files, details some of
the newer processes, and describes the directory structure of the operating
environment and predefined environment variables.
Avaya MPS Architectural Overview
# P0602477 Ver: 3.1.11 Page 19
System Architecture
The MPS family is designed with a flexible hardware and software architecture that is
highly scalable. System models range from small (48 ports) to large networked
configurations of tens of thousands of ports. The same basic hardware and software
components are used for all configurations. Individual systems usually vary only in
application/transaction processor performance, capacity for additional ports (TMS’),
and optional feature software/hardware (for example, Call Progress Detection, Speech
Recognition, or Caller Message Recording).
Architecture of the MPS is based on a Sun Microsystems SPARC system processor
running the Solaris operating system or an Intel processor running Windows 2000.
The system processor is connected to one or more Telephony Media Servers (TMS).
The TMS is a flexible platform that provides switching, bridging, programmable
resources, memory, and network interfaces to execute a comprehensive set of
telephony and media functions.
Each MPS system consists of a Solaris or Windows host node running OS and MPS
software, and one or more TMS’ responsible for the bulk of the actual telephony
processing. One TMS is required for each MPS defined on the node. A multiple node
configuration is referred to as the MPS Network. The following diagrams illustrate the
two basic products available in the MPS system: a single rack-mounted version,
known as the MPS100, which is available on the Windows platform only, and a
cabinet enclosed networked configuration which relies on the MPS1000 and is
available on both the Windows and Solaris platforms. Typically, the MPS100 contains
only 2 spans (though it may contain up to 8) and only 1 Digital Communications
Controller (DCC) card, and does not support bridging outside the TMS. Conversely,
the MPS1000 is the high-capacity model, with 4 TMS’ per chassis and up to 4 chassis
per cabinet. It can support up to ten thousand ports with the ability to bridge between
any two regardless of the chassis the ports are in with respect to each other. This
manual deals almost exclusively with the MPS1000.
The flexibility inherent in the product line allows the MPS networks to incorporate
numerous different designs. For additional information and configurations, see the
Avaya Media Processing Server Series 1000 Transition Guide. For information on
using the MPS, see the Avaya System Operator’s Guide.
Though the Avaya Media Processing Server Series 1000 Transition Guide is typically
used by those migrating from a previous version of our transaction processing
systems, it also contains information of interest to those new to the product line. Such
information should be used in that context only.
Avaya Media Processing Server Series System Reference Manual
Page 20 # P0602477 Ver: 3.1.11
MPS1000 Network
MPS100
Single Media Processing Server 100 and Basic Media Processing Server 1000 Network
TMS
MPS
ASE
VOS
Windows
TMS
MPS 1
Node A
MPS
ASE
VOS
TMS
MPS 2
Node B
MPS
ASE
VOS
/