Operator Guide MPS500

Avaya Media Processing Server System
Operator Guide
MPS 3.5
NN44100-500, 02.02
August 2010
© 2010 Avaya Inc. Copyright
All Rights Reserved. Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, or Hardware
Notice provided by Avaya. All content on this site, the documentation and the
Product provided by Avaya including the selection, arrangement and
While reasonable efforts have been made to ensure that the design of the content is owned either by Avaya or its licensors and is
information in this document is complete and accurate at the time of protected by copyright and other intellectual property laws including the
printing, Avaya assumes no liability for any errors. Avaya reserves the sui generis rights relating to the protection of databases. You may not
right to make changes and corrections to the information in this modify, copy, reproduce, republish, upload, post, transmit or distribute
document without the obligation to notify any person or organization of in any way any content, in whole or in part, including any code and
such changes. software unless expressly authorized by Avaya. Unauthorized
reproduction, transmission, dissemination, storage, and or use without
Documentation disclaimer the express written consent of Avaya can be a criminal, as well as a
“Documentation” means information published by Avaya in varying civil offense under the applicable law.
mediums which may include product information, operating instructions
Third-party components
and performance specifications that Avaya generally makes available
to users of its products. Documentation does not include marketing Certain software programs or portions thereof included in the Product
materials. Avaya shall not be responsible for any modifications, may contain software distributed under third party agreements (“Third
additions, or deletions to the original published version of Party Components”), which may contain terms that expand or limit
documentation unless such modifications, additions, or deletions were rights to use certain portions of the Product (“Third Party Terms”).
performed by Avaya. End User agrees to indemnify and hold harmless Information regarding distributed Linux OS source code (for those
Avaya, Avaya's agents, servants and employees against all claims, Products that have distributed the Linux OS source code), and
lawsuits, demands and judgments arising out of, or in connection with, identifying the copyright holders of the Third Party Components and the
subsequent modifications, additions or deletions to this documentation, Third Party Terms that apply to them is available on the Avaya Support
to the extent made by End User. Web site: http://support.avaya.com/Copyright.
Link disclaimer Trademarks
Avaya is not responsible for the contents or reliability of any linked Web The trademarks, logos and service marks (“Marks”) displayed in this
sites referenced within this site or documentation provided by Avaya. site, the Documentation and Product(s) provided by Avaya are the
Avaya is not responsible for the accuracy of any information, statement registered or unregistered Marks of Avaya, its affiliates, or other third
or content provided on these sites and does not necessarily endorse parties. Users are not permitted to use such Marks without prior written
the products, services, or information described or offered within them. consent from Avaya or such third party which may own the Mark.
Avaya does not guarantee that these links will work all the time and has Nothing contained in this site, the Documentation and Product(s)
no control over the availability of the linked pages. should be construed as granting, by implication, estoppel, or otherwise,
any license or right in and to the Marks without the express written
Warranty permission of Avaya or the applicable third party.
Avaya provides a limited warranty on its Hardware and Software
Avaya is a registered trademark of Avaya Inc.
(“Product(s)”). Refer to your sales agreement to establish the terms of
the limited warranty. In addition, Avaya’s standard warranty language, All non-Avaya trademarks are the property of their respective owners,
as well as information regarding support for this Product while under and “Linux” is a registered trademark of Linus Torvalds.
warranty is available to Avaya customers and other parties through the
Avaya Support Web site: http://support.avaya.com. Please note that if Downloading Documentation
you acquired the Product(s) from an authorized Avaya reseller outside
of the United States and Canada, the warranty is provided to you by For the most current versions of Documentation, see the Avaya
said Avaya reseller and not by Avaya. Support Web site: http://support.avaya.com.
Licenses Contact Avaya Support

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA Avaya provides a telephone number for you to use to report problems
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE or to ask questions about your Product. The support telephone number
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR is 1-800-242-2121 in the United States. For additional support
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., telephone numbers, see the Avaya Web site: http://support.avaya.com.
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; 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”).
2 Avaya Media Processing Server System Operator Guide August 2010

Contents
Chapter 1: Preface.....................................................................................................................7
Scope................................................................................................................................................................7
Intended Audience............................................................................................................................................7
Customer service..............................................................................................................................................8
Getting help from a distributor or reseller..........................................................................................................8
Getting product training.....................................................................................................................................8
Getting technical documentation.......................................................................................................................8
Getting technical support from the Avaya Web site..........................................................................................8
How to Use This Manual...................................................................................................................................9
Organization of This Manual.............................................................................................................................9
Conventions Used in This Manual...................................................................................................................11
Solaris and Windows Conventions..................................................................................................................12
Two-Button (Windows) versus Three-Button (Solaris) Mouse........................................................................13
Trademark Conventions..................................................................................................................................13
Product Nomenclature Changes.....................................................................................................................13
Copyright Information......................................................................................................................................14
HylaFAX Facsimile Software...........................................................................................................................14
Chapter 2: Introduction...........................................................................................................17
Introduction.....................................................................................................................................................17
System Operator Tasks...................................................................................................................................18
System Terminology........................................................................................................................................19
System Configurations....................................................................................................................................20
Single Media Processing Server.....................................................................................................................20
Multiple Media Processing Servers.................................................................................................................21
MPS Manager.................................................................................................................................................22
Chapter 3: System Startup, Monitoring and Shutdown.......................................................25

System Startup, Monitoring, and Shutdown....................................................................................................25
TMS Startup/Shutdown...................................................................................................................................25
Automatic Shutdown and Restart....................................................................................................................27
Routine Media Processing Server Startup......................................................................................................27
Starting/Restarting MPS Manager..................................................................................................................29
System Monitoring..........................................................................................................................................30
MPS 500 Indicators and Controls...................................................................................................................30
Ethernet Hub Indicators..................................................................................................................................31
MPS 1000 Indicators and Controls.................................................................................................................31
Alarm Viewer...................................................................................................................................................37
Statistics Data Collection and Reporting.........................................................................................................37
Logging off a Node..........................................................................................................................................38
System Shutdown...........................................................................................................................................38
Windows shutdown or restart..........................................................................................................................40
Chapter 4: Command Line Functions....................................................................................43

Command Line Functions Overview...............................................................................................................43
Command Line Interaction..............................................................................................................................43
Command Line Editing....................................................................................................................................44
Command Control...........................................................................................................................................46
Online Documentation.....................................................................................................................................48
Avaya Media Processing Server System Operator Guide August 2010 3

Chapter 5: Status Monitoring.................................................................................................49
Status Monitoring............................................................................................................................................49
The Alarm Viewer............................................................................................................................................49
Status Monitoring............................................................................................................................................51
System Date/Time...........................................................................................................................................51
Solaris Management Console.........................................................................................................................52
SRP Status......................................................................................................................................................52
Component Status..........................................................................................................................................53
Phone Line Status...........................................................................................................................................56
Span Status.....................................................................................................................................................58
RCD Status.....................................................................................................................................................65
CCM Status.....................................................................................................................................................65
Application Status...........................................................................................................................................66
VMM Status.....................................................................................................................................................68
Multimedia Format (MMF) File Status.............................................................................................................68
Host Status......................................................................................................................................................70
System Statistics Reports...............................................................................................................................72
Chapter 6: Voice Processing Applications............................................................................77

Voice Processing Applications........................................................................................................................77
Application Memory Requirements.................................................................................................................77
Additional Memory Considerations.................................................................................................................78
Activating Playback MMF Files.......................................................................................................................79
System Wide Playback MMF Files..................................................................................................................80
Application-Specific Playback MMF Files.......................................................................................................81
Assigning and Starting Application Programs.................................................................................................82
Start and Restart Line Order...........................................................................................................................84
Terminating and Unassigning Application Programs.......................................................................................85
Deactivating MMF Files...................................................................................................................................86
Updating or Replacing Playback MMF Files...................................................................................................89
Updating/Replacing a Playback MMF Playback File.......................................................................................90
Updating Elements in an Active Playback MMF File.......................................................................................92
Synchronizing MMF Files Across Nodes (ZAP Utility)....................................................................................94
Caller Message Recording..............................................................................................................................99
Creating a File for Caller Message Recording................................................................................................99
Activating Record MMF Files........................................................................................................................101
Chapter 7: Backing Up and Restoring Files........................................................................103

Backing up and Restoring Files....................................................................................................................103
Directory and File Manipulation.....................................................................................................................103
Working with Directories................................................................................................................................104
File Listing.....................................................................................................................................................105
File Removal.................................................................................................................................................106
Backup Devices and Options........................................................................................................................106
Guidelines for Backup...................................................................................................................................107
Determining Directory Size...........................................................................................................................108
Backup Tips...................................................................................................................................................109
Backup/Restore Methods..............................................................................................................................109
Disk to Disk Backup Procedure.....................................................................................................................110
Preparation for Solaris Backup......................................................................................................................110
Execution.......................................................................................................................................................112

Configure.......................................................................................................................................................113
Logging..........................................................................................................................................................114
Backing Up with tar........................................................................................................................................115
Displaying the Contents of a tar Backup.......................................................................................................116
Restoring with tar...........................................................................................................................................117
Backing up with ufsdump...............................................................................................................................117
Backing up partitions with ufsdump...............................................................................................................120
Displaying the Contents of a ufsdump Backup.............................................................................................122
Restoring with ufsrestore..............................................................................................................................122
Backing Up with cp (Copy)............................................................................................................................123
Backing Up and Restoring Multimedia Elements..........................................................................................124
Chapter 8: Troubleshooting..................................................................................................125
Troubleshooting.............................................................................................................................................125
Fault Categories............................................................................................................................................125
Isolating and Resolving Specific Problems...................................................................................................127
MMF (Vocabulary) File Troubleshooting.......................................................................................................127
File Synchronization Troubleshooting...........................................................................................................129
Host Communication Troubleshooting..........................................................................................................130
Telephone Line Troubleshooting...................................................................................................................130
Application Software Troubleshooting...........................................................................................................132
Redundancy Troubleshooting.......................................................................................................................133
Call-protect Troubleshooting.........................................................................................................................133
SRP Log File.................................................................................................................................................134
Chapter 9: MPS Directory Structure....................................................................................137

MPS Directory Structure...............................................................................................................................137
User-Specified Distribution Directory (usually /opt/vps)................................................................................143
Chapter 10: Remote Desktop Connection and pcAnywhere.............................................149

Disable pcAnywhere.....................................................................................................................................150
Enable RDC for Administration.....................................................................................................................150
Initiate an RDC Session................................................................................................................................151
Disconnect an RDC Session.........................................................................................................................152
Transferring Files in an RDC Session...........................................................................................................152
Sharing a Remote Console Session.............................................................................................................153
Enable Multiple RDC Hops from Single RDC...............................................................................................155
Mount Client Drives.......................................................................................................................................155
Setting up a Windows 2003 Server for Remote Access Through PPP.........................................................157
Setting Routing and Remote Access to Automatic.......................................................................................157
Setting Up Inbound Modem Access..............................................................................................................159
Adding a New User.......................................................................................................................................162
Setting up a Windows 2003 Client for Remote Access.................................................................................164
Verifying the Client Dial-up Connection.........................................................................................................165
Index.......................................................................................................................................167

Chapter 1: Preface
Scope
This manual provides information and procedures related to the daily operation, monitoring,
and maintenance of the Media Processing Server Series system.
Important:
All references to MPS 3.0 in this document (such as documents titles, software versions,
and illustrations) apply to all releases of MPS 3.X.
Intended Audience
The audience for this manual consists of people responsible for the monitoring and
maintenance of the Media Processing Server Series system. A user of this class is referred to
as a system operator. System operators must be familiar with telecommunications and
computer equipment, their functions, and associated terminology. In addition, they must be
familiar with site-specific telephone systems, power systems, computer systems, and
peripheral components such as terminals, modems, printers, and so on.
This guide assumes that the Media Processing Server Series system operators have
completed an on-site system briefing program as part of the initial system installation. In
addition, they should be familiar with other site-specific operating procedures relating to the
Media Processing Server Series that are due to specific application functions performed by
that platform and with any other equipment to which the Media Processing Server Series is
connected. This may include a PBX/ACD or a host computer system.
It is further assumed that the reader is already familiar with the following publications: Media
Processing Server Manager Reference Manual, Media Processing Server Reporter User
Guide, Media Processing Server Studio User Guide, and Media Processing Server Developer
User Guide.
In addition, the following publications should be consulted, as needed: MPS System Reference
Manual, MPS Telephony Reference Manual, and MPS COMMGR Reference Manual.

Preface
Customer service
Visit the Avaya Web site to access the complete range of services and support that Avaya
provides. Go to www.avaya.com or go to one of the pages listed in the following sections.
Navigation
• Getting technical documentation on page 8
• Getting product training on page 8
• Getting help from a distributor or reseller on page 8
• Getting technical support from the Avaya Web site on page 8
Getting help from a distributor or reseller

If you purchased a service contract for your Avaya product from a distributor or authorized
reseller, contact the technical support staff for that distributor or reseller for assistance.
Getting product training

Ongoing product training is available. For more information or to register, you can access the
Web site at www.avaya.com/support. From this Web site, you can locate the Training contacts
link on the left-hand navigation pane.
Getting technical documentation

To download and print selected technical publications and release notes directly from the
Internet, go to www.avaya.com/support.
Getting technical support from the Avaya Web site

The easiest and most effective way to get technical support for Avaya products is from the
Avaya Technical Support Web site at www.avaya.com/support.

How to Use This Manual
How to Use This Manual

This manual uses many standard terms relating to computer systems, software application
functions, and the Internet. However, it contains some terminology that can be explained only in
the context of the MPS Series. Refer to the Glossary of Avaya Media Processing Server Series
Terminology for definitions of MPS Series specific terms.
Initially, you should read this manual at least once, from start to finish. you are familiar with the
document, 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 cross-reference links (shown in blue) to quickly
locate related topics. Position your cursor over the cross-reference link and click once. Click
any point in a Table of Contents entry to move to that topic. Click the page number of any Index
entry to access that topic page.
To familiarize yourself with various specialized textual references within the manual, see
Conventions Used in This Manual on page 11.
Note:
Periphonics is now part of Avaya. The name Periphonics, and variations thereof, appear in
this manual only in reference to a product (for example, the PERImps package, the perirev
command, and so on).
Organization of This Manual

Chapter 1--Introduction
Example
This chapter discusses the general characteristics of the Media Processing Server Series
system and outlines general activities performed by that system's operator.
Chapter 2--System Startup, Monitoring and Shutdown
Example
This chapter describes startup operation, system-level monitoring capabilities, and
shutdown commands. Included are an overview of system hardware and Media Processing
Server Manager activities relevant to such activities.

Preface
Chapter 3--Command Line Functions
Example
This chapter describes interaction with the system from a command line perspective. It also
discusses the basics of using the Media Processing Server Manager VSH Tool and the online
documentation system.
Chapter 4--Status Monitoring
Example
This chapter discusses monitoring of individual aspects of the Media Processing Server
Series system. Included are instructions on using and interpreting the results of the Media
Processing Server Manager Alarm Viewer and Media Processing Server Reporter statistics
tool.
Chapter 5--Voice Processing Applications
Example
This chapter discusses application related prerequisites, assigning and starting applications,
activating vocabularies, working with Multimedia Format (MMF) files, and using Caller
Message Recording (CMR).
Chapter 6--Backing up and Restoring Files
Example
This chapter describes commands and procedures used for routine backup and restore
operations.
Chapter 7--Troubleshooting
Example
This chapter discusses how to use various monitoring functions to identify problems with
system operation, their possible causes, and suggested remedial actions.
Chapter 8--Printer and Modem Setup
Example
This appendix covers setup and changes to the peripheral components of the Media
Processing Server Series system.
Appendix A--MPS Directory structure
Example
This appendix shows the Media Processing Server Series file hierarchy and explains the
intended usage and functions of various directories and associated files.

Conventions Used in This Manual
Appendix B--Remote Desktop Connection
Example
This appendix provides information for Remote Desktop Connection support.
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.
Table 1: Conventions Used in This Manual
Notation Description
Normal text Normal text font is used for most of the document.
important term The Italics font introduces new terms, highlights meaningful words
or phrases, or distinguishes specific terms from nearby text.
system command This font indicates a system command and its arguments. Enter such
keywords exactly as shown (that is, do not fill in your own values).
This font highlights the names of disk directories, files, and
file name/ extensions for file names. It also shows displays on text-based
directory
screens (for example, to show the contents of a file.)
on-screen field This font indicates field labels, on-screen menu buttons, and action
buttons.
<KEY NAME> A term 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. Click 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.

Preface
Notation Description
The flying Window icon identifies procedures or events that apply to
the Windows operating system only.1
The Solaris icon identifies procedures or events that apply to the

Solaris operating system only.2
1. Windows and the flying Window logo are either trademarks or registered trademarks
of Microsoft Corporation.
2. Solaris® is a registered trademark of The Open Group in the U.S. and other countries.
Solaris and Windows Conventions

This manual depicts examples (command line syntax, configuration files, and screen shots) in
Solaris format. In certain instances Windows-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 Windows
operating system.
Solaris Windows
Environment
$MPSHOME %MPSHOME%
Paths
$MPSHOME/bin %MPSHOME%\bin
Command <command> & start /b <command>

Two-Button (Windows) versus Three-Button (Solaris) Mouse
Two-Button (Windows) versus Three-Button (Solaris)

Mouse
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® and Motif® are registered trademarks of The Open Group in the U.S. and other
countries.
Solaris, SunOS, OpenWindows, SPARC, and UltraSPARC are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and other countries.
Microsoft, MSSQL, Windows, Internet Explorer, and the Flying Windows logo are either
trademarks or registered trademarks of Microsoft Corporation.
Oracle® is a registered trademark of Oracle Corporation.
Sybase™ and SYBASE™ are trademarks of Sybase, Inc. or its subsidiaries.
Informix® and INFORMIX® are registered trademarks of Informix Corporation or its affiliates.
Product Nomenclature Changes

The following product names changed with the latest Avaya MPS software release. All other
references to the former name with respect to environment variables, directory paths, software

Preface
package names, and so on, remain the same. As an example; the PeriProducer product is
now referred to as the Media Processing Server Developer, however, its package name
remains PERIppro.
Former Product Name New Product Name

IVR Software Media Processing Server Release x.x
PeriProducer Media Processing Server Developer
PeriView Media Processing Server Manager
PeriStudio Media Processing Server Studio
PeriReporter Media Processing Server Reporter
PeriSQL Media Processing Server RDB
PeriVXML Media Processing Server VXML Browser
CTI Suite Communications Control Toolkit (CCT)
Open Signal Computing and Analysis Speech Server
Resource (OSCAR)
Copyright Information
HylaFAX Facsimile Software

Copyright (c) 1990-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. HylaFAX is
a trademark of Silicon Graphics, Inc.
Permission to use, copy, modify, distribute, and sell this software and its documentation for
any purpose is hereby granted without fee, provided that (i) the above copyright notices and
this permission notice appear in all copies of the software and related documentation, and (ii)
the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity
relating to the software without the specific, prior written permission of Sam Leffler and Silicon
Graphics.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND,
EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY
WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY
SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR
ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY

HylaFAX Facsimile Software
OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR

PERFORMANCE OF THIS SOFTWARE.

Chapter 2: Introduction
This chapter covers:
1. Introduction
2. System Operator Tasks
3. System Terminology
4. System Configurations
Introduction
The Avaya Media Processing Server (MPS) Series product lines consist of hardware and
software for performing Interactive Voice Response (IVR) and media processing functions in
call processing environments. More precisely, MPS systems integrate call processing
components with speech, telephony, data communications, and transaction processing
functions.
The heart of the MPS system is the Avaya Telephony Media Server (TMS), which provides
high phone port densities with user flexibility, scalability, 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 IVR
applications are accommodated easily, from simple information delivery services to complex
multimedia (voice/fax/data/web) call processing implementations with local databases,
multiple services, and considerable transaction processing functions.
The MPS supports a wide variety of telephony and host computer interfaces, and easily
integrates with equipment already in place at any data-processing/communications
environment. MPS systems employ industry standards and distributed processing in an open
architecture, allowing plug-in integration of future technological developments. In addition, the
MPS supports multiple LAN/WAN interfaces, providing an environment ready for distributed
computing.
The MPS is available in the following configurations:
• Media Processing Server 500
The MPS 500 consists of one Telephony Media Server (TMS) which supports 8 T1/E1
spans (up to 240 ports) or comparable capacity VoIP channels. The MPS 500 is capable of
providing full IVR functionality including fax, caller message recording, conferencing,
speech recognition and text-to-speech (using Speech Server resource servers), SQL

Introduction
database access, host screen scrape access, Communications Control Toolkit

integration, and supports building and running of an application to control a given call
• Media Processing Server 1000
A cabinet-enclosed, networked configuration, available only on the Solaris platform. It
supports four TMS units per chassis, with up to four chassis per cabinet. The MPS can
support up to ten thousand ports with the ability to bridge between any two ports
regardless of their location.
The MPS also includes a set of easy-to-use, objected-oriented, GUI tools. These tools are
used for:
• Application and vocabulary development
• System configuration, control, and monitoring
• Collecting and reporting of statistical data
• Access to online documentation
The Media Processing Server Developer application development environment provides a
complete graphical medium for the entire application life cycle. It also allows telephony-
based applications to be ported over to Internet-based Web usage.
System Operator Tasks

The primary task of the MPS system operator is to ensure the smooth daily operation of the
system. System operator tasks include:
• Keeping records and monitoring system usage and status
• Backing up and restoring system, application, and Multimedia Format (MMF) vocabulary/
fax files
• Manipulating applications
• Occasional shutting down and restarting of the system (in cases of power failure or other
system maintenance needs) if it fails to recover automatically
• Performing speech/vocabulary updates (as required)
• Performing initial problem analysis and service requests
• Working with Certified Avaya service personnel or others during hardware upgrade and
maintenance
To accomplish these tasks, an understanding of the fundamentals of the MPS is required. This
includes knowing the terminology associated with the system and the various configurations
a system can have.

System Terminology
Certified Avaya field service engineers normally perform the initial site preparation and system
installation. The installation includes configuring appropriate system and application-
execution parameters.
System Terminology
The following is a basic presentation of the terminology associated with MPS systems. For
additional information about terminology, see the Glossary of Media Processing Server Series
Terminology.
Component A unit within the system that performs a particular function, see
System Configurations on page 20.
Media Processing Server An Interactive Voice Response system comprised of various
(MPS) components that provides telephony and call processing
services.
Node A physical workstation in a Media Processing Server Series
network.
Telephony Media Server The main component within a MPS system. It provides most
(TMS) essential functions for telephony and media management.
Application Services The group of software processes used to develop and execute
Environment (ASE) voice and media applications.
Call Control Manager The primary interface between applications and the VOS
(CCM) services. It is the gateway for communication with the telephony
hardware platform.
Multimedia Format (MMF) A proprietary format for storing and retrieving audio elements
and fax data in data files. A single MMF file is physically stored
as two files. The data file (.mmd extension) contains raw audio
recordings, such data for voice, fax, TDD tones, and so on. The
index file (.mmi extension) contains the attributes and pointers
that differentiate the elements in the data file.
Media Processing Server The suite of tools designed to administer MPS network activity
Manager in a GUI environment, see Toolkit on page 22.
Startup and Recovery The software process that spawns (that is, starts up) and
Process (SRP) monitors all other MPS processes. SRP can also be used to
stop and restart these processes if they have been abnormally
terminated.
Redundancy The software process that is responsible for MPS redundancy
Configuration Daemon configuration and control.
(RCD)
Voice Memory Manager A VOS software subcomponent that provides audio and media
(VMM) management services within the VOS.

Introduction
Voice Operating Software The main software processes that provide the lower-level
(VOS) operating functions of the MPS system.
Voice Processing Series The predecessor product to the MPS. By design, a number of
(VPS) the MPS path names, software processes, environment
variables, and file fields use the term VPS. This terminology is
functionally equivalent to MPS nomenclature. In other words,
wherever file or software names show the term VPS, it is
relevant to the MPS.
$MPSHOME The home directory environment variable, set to /opt/vps by
default. This directory contains the operating system software,
subdirectories for the various installed software packages
subdirectory, symbolic links to these packages, and other
software necessary for MPS operations.
System Configurations
A MPS system setup can be a single MPS or contain multiple networked MPS systems. Media
Processing Server Manager Workstations can be added, as needed, to allow monitoring of the
system from remote locations. The MPS also supports functions between systems with
different operating system releases.
Single Media Processing Server
A Media Processing Server node is the basic building block of

a MPS network. A single MPS component consists of the TMS
hardware, and ASE and VOS software groups running on a
Solaris or Windows node. (A node is a physical workstation in
the MPS network.)
The single MPS configuration is intended for environments with
low to moderately high call volumes. This system is monitored
directly by MPS Manager. Generated statistics are available
using Media Processing Server Reporter.
Each workstation in a MPS network is identified by a node name. In the above diagram, it is
shown as "Node A." Each MPS component is identified by a unique component number. In the

Multiple Media Processing Servers
diagram, it is shown as "MPS 1." A component number must be unique across all nodes. The
convention for naming MPS network components is component_type.component_number/
node_name. Thus, "mps.1/A" is the designation of the MPS in this diagram,
Multiple Media Processing Servers

In a Media Processing Server Series network, each MPS can process calls only on its own
phone lines. Networking the systems increases the total number of available phone lines,
permits flexibility in assigning different types of applications to particular segments of the
network, and allows component monitoring from multiple nodes.
The following diagram illustrates the basic concepts of a MPS network. Although networks can
have a different components in various configurations, for illustration purposes, this example
shows a two-node Media Processing Server Series network.
Media Processing Server Manager tools reside on every node. However, MPS Reporter tools
resides only on the statistics node (shown as node "B" in this diagram). The nodes are
networked (either on a LAN or WAN) thus allowing statistics collected from node "A" to be
consolidated on node "B" (along with the statistics from node "B"). Also, either node can be
monitored through the other node's MPS Manager tools. (For more information about MPS
Reporter Tools, see the MPS Reporter User Guide.)
Figure 1: Media Processing Server Series Network
The example shows each MPS node identified by a node name ("A" and "B") and each MPS
component identified by a unique number ("1" and "2"). Thus, "mps.1/A" and "mps.2/B" are
the designations of the MPS systems in this network.

Introduction
MPS Manager
Toolkit
MPS Manager is a suite of GUI tools designed to administer Media Processing Server Series
network activity.
MPS Manager performs the following various functions:

• Defines the Media Processing Server Series network as a hierarchy of entities and
designate network perspectives from which to manipulate and view network activity.
• Launch MPS Manager tools to configure user accounts and privileges, manage
applications, monitor phone lines, view and log alarms, and monitor system activity.
• Customize operations by selecting and specifying MPS Manager properties.
Note:
See the MPS Manager Reference Manual for detailed information about MPS Manager.
Workstation Node
A MPS Manager Workstation node is a management resource for remote monitoring of the
MPS systems in the network. A MPS Manager node does not have MPS components. It
contains only the software necessary to run the MPS Manager GUI tools, but none of the
software or hardware needed for telephony functions. A MPS Manager Workstation can be
physically located anywhere on a network with component-based nodes.

MPS Manager
Figure 2: Media Processing Server Series Network — with Media Processing Server and MPS Manager
Workstation
In this example configuration, MPS Manager can be launched from any node in the network.
MPS Reporter tools, however, can only be used only on node "B." The MPS Manager
Workstation can be used to monitor both nodes, but statistics reports can only be generated
through MPS Reporter on node "B." If desired, the MPS Manager Workstation could also be
designated as the statistics node.
The MPS Manager Workstation node does not normally appear in the on-screen MPS Manager
workspace. To obtain a visual representation of this node, it has to be added to the .xtrahostsrc
file. For information about this file, see the MPS Manager Reference Manual.

Chapter 3: System Startup, Monitoring and
Shutdown
1. TMS Startup/Shutdown
2. System Monitoring
3. Logging off a Node
4. System Shutdown
System Startup, Monitoring, and Shutdown

Occasionally, the Avaya Media Processing Server Series has to be shut down and restarted
for maintenance or to recover from an unexpected failure. Also, the TMS might occasionally
require recycling, which can be done without having to stop the entire system. The following
sections contain details on these procedures, as well as those for overall system monitoring.
There are four ways to monitor the system: indicators and controls, the Alarm Viewer, MPS
Manager, and MPS Reporter.
TMS Startup/Shutdown
Power to the TMS can be applied or removed either manually using a switch on the unit or by
issuing system commands. Refer to the following table to determine the best method to use
in a given situation. For information on using the Alarm Viewer, see Alarm Viewer on page 37
and refer to the Alarm Reference Manual for detailed description of the Alarm conditions.
Command/Function Use to... Why?

TEST / ON / OFF switch Manually turn power to the Use when completely
located on the Front Control TMS on or off shutting down system or
Panel (FCP, see page 18) or performing service on the
Variable Resource Chassis TMS (See System
(VRC) Rear Panel (see page Shutdown on page 38) and
19).

System Startup, Monitoring and Shutdown

to reapply power when
finished with these steps.
S19rcd.startup Start RCD Use after the stop option (see
start below) has been invoked.
Note that S20vps.startup start
will not bring the MPS fully up
if RCD is not running.
S19rcd.startup stop Stop RCD Use when manually initiating
a MPS primary to secondary
failover (requires
S20vps.startup stop to be
executed on the primary as
well).
S20vps.startup Start SRP (including VOS) Use after the stop option (see
start and TMS hardware below) has been invoked, or
(preferred command) "gracefully" (that is, through to restart the TMS if its startup
the most efficient means as terminated abnormally (use
determined by Avaya) the Alarm Viewer to check for
causes)
S20vps.startup stop Stop SRP (including VOS) Use when performing
(preferred command) and TMS hardware maintenance on the system
"gracefully" (that is, through that requires all Media
the most efficient means as Processing Server Series
determined by Avaya) processes or the TMS to be
down (for example, modifying
the Media Processing Server
Series network), or to stop
Media Processing Server
Series processes and the
TMS if their startup
terminated abnormally (use
the Alarm Viewer to check for
causes)
srp vos.# -stop Stop VOS processes and Use if VOS processes have
TMS crashed or recycled during an
attempt to load the TMS. Use
the Alarm Viewer to check for
causes.1
srp vos.# -start Start VOS processes and Use to start the VOS and TMS
TMS after having issued the -stop
option (see above).1
srp vos.# -restart Stop and then restart the Use for same reasons as the
VOS and TMS. Can be used previous two commands
as an alternative to the -stop when there is no need to see
and -start commands the relevant alarms.1

Automatic Shutdown and Restart
In these examples, # represents the Media Processing Server with which the TMS is
associated.
Automatic Shutdown and Restart

If the TMS Routing Interface Process (TRIP) detects a CONFIG or SHUTDOWN state when
TMS is started, it shuts down and restarts the TMS hardware. All VOS processes return to the
stage in the startup sequence where attempts are made to establish connections to the
hardware ports.
State Indication Cause Status

CONFIG Another VOS is loading Severe configuration Contact Certified Avaya
the TMS error support personnel
immediately
VOS crashed/recycled Interruption of normal TMS is in an unknown
while attempting a prior loading processes due to configuration since prior
configuration an unexpected condition commands may not
within the system (that is, have completed
software or hardware successfully
fault, or loss of power)
SHUTDOW TMS was stopped/shut Operator issued a Hardware is detected in
N down manually command line order an unexpected state by
TRIP when system is
still up and running
Routine Media Processing Server Startup

Media Processing Server configuration files automate the routine startup of each system in
the Media Processing Server Series network. During on-site installation, Avaya staff customize
these configuration files for each system. These configuration files are used to:
• Activate application programs.
• Activate Multimedia Format (MMF) (vocabulary) files.
• Configure host interaction.
• Configure the default startup environment.

Performing a Media Processing Server Startup

1. On each Media Processing Server, turn the main power switch on.
2. Power up each TMS. For locations of their power switches, see Front Control
Panel on page 33 and VRC Rear Panel on page 34.
3. Return to the node that acts as the MPS Manager Workstation. The system
automatically starts a monitoring Alarm Viewer in which it displays startup
messages.
4. Enter the login name and select Session from the Options menu button. Select
either Common Desktop Environment (CDE) or OpenWindows Desktop from the
pulldown menu.
This is the desktop environment. At the next time log in, the desktop defaults to the
previous selection (as indicated by the red dot at User's Last Desktop). The default
login name is peri. The name of the node to log into (in this example MPS) appears in
the "Welcome" prompt.
5. Click the OK button (or press <Return>), then enter the password and repeat.
The default password is peri;). The selected desktop environment should now be
displayed.
The initial Alarm Viewer becomes iconified and a cmdtool window opens. The menu
buttons on this startup Alarm Viewer are inactive.
To view alarms after startup, launch a separate Alarm Viewer, see Alarm Viewer on
page 37.
6. Wait for each Media Processing Server to boot up. Use the Alarm Viewer to watch
the system load vocabularies, start processes, and initialize the TMS on each one.
After several minutes, each unit generates a "System is up" alarm.
7. Start MPS Manager. See Starting/Restarting MPS Manager on page 29.

Starting/Restarting MPS Manager
Configuration files load all the necessary software. After startup, the Media
Processing Server is ready for call processing.
Starting/Restarting MPS Manager

MPS Manager is used to complete system startup and interact with the Media Processing
Server.
If MPS Manager is exited for any reason, it can be restarted without rebooting the system.
Starting and Restarting MPS Manager
1. <RIGHT> click the desktop to display the Workspace menu.
2. <RIGHT> click *Avaya* in the Workspace pop-up menu. This menu is user-
defined and its contents may vary. To define the items on this menu, and which ones
can otherwise be launched from a command line, edit the .openwin-menu-avaya
file for the OpenWindows Desktop or the .dt/dtwmrc file for CDE, using any text-
based editor. These files are typically found in a user's /home directory.
3. From the Avaya menu, select MPS Manager.
The system displays the MPS Manager Login screen.
Note:
MPS Manager can also be started by entering periview & at any command line.
A cmdtool window opens upon initialization of the system, see Routine Media
Processing Server Startup on page 27.

System Monitoring
MPS 500 Indicators and Controls

Front Panel The chassis front panel contains no controls, connectors or visible indicators.
TMS Front Panel In addition to front panel indicators, the system components have internal
indicators useful for system maintenance and fault isolation. Located on the front panel of the
TMS are connections to a diagnostic console for troubleshooting, LED indicators for TMS
health checks, and the span input/output connector.
Table 2: TMS Front Panel Connectors and Indicators
Item Description
AUDIO RJ11 jack for connecting a telephone handset to audibly monitor an MPS
connector 500 line.
CONSOLE RS232 (9-pin DIN) port for connecting a debug terminal. Used for boot
connectors ROM and diagnostics.
LEDs 0 - 15 Provide diagnostic indications on startup.
Microswitches Reserved for future enhancement.
HUB A LEDs EXT Indicates condition on external port of HUB A. SL2 Indicates
condition on slot 2 port of HUB A. SL1 Indicates condition on slot 1 port
of HUB A. MP Indicates condition on microprocessor port of HUB A. COL
Indicates errors or collisions in HUB A.

Ethernet Hub Indicators
Item Description
HUB B LEDs EXT Indicates condition on external port of HUB B. SL4 Indicates
condition on slot 4 port of HUB B. SL3 Indicates condition on slot 3 port
of HUB B. MP Indicates condition on microprocessor port of HUB B. COL
Indicates errors or collisions in HUB B.
DCC Front Panel
Span connector RJ48M 50-pin connector connects up to eight digital spans (T1 or E1) to
PSTN.
Remote terminal RS232 (9-pin DIN) port for connecting a debug terminal. Used for boot
connector ROM and diagnostics.
Other Reserved for future enhancement.
connectors and
indicators

The dual (green and red) LED indicators for HUB A and HUB B on the front of the TMS can
display five separate conditions of the item to which they apply. The LEDs will be on steady,
or blinking in the following combinations to indicate the respective condition:
Indicator/Control Function
Steady green Receive link pulse FIFO error
Blinking green (@~ 4Hz) Transmit packet (N/A)
Steady red Reversed polarity Collision
Blinking red (@~ 4Hz) Receive packet (N/A)
Alternating red and green (@~ Partitioned out (N/A)
5Hz) P

The Media Processing Server Series systems provide a number of indicators on various
panels. The indicators give a visual status of system operation.

Fan Speed Monitor Panel

This panel provides information and control for overall cabinet cooling. Normal cooling is
maintained automatically, but this can be overridden in the event of an over temperature
(overtemp) condition (that is, a state in which a preset temperature limit is exceeded).
Table 3: Fan Speed Monitor Panel
OVER TEMP indicator Illuminates if the cabinet exceeds the predetermined safe
operating temperature of 35°C (95°F).
FAULT/MAN HS indicator Illuminates when a cooling system fault has been detected and
the fan has been switched to MANUAL HIGH SPEED (see
next).
FAN SPEED switch Two-position switch used to set cooling fan speed for cabinet
airflow.
MANUAL HIGH SPEED Use this setting when an overtemp condition is present and
continued maximum cooling effectiveness is required. Placing
the FAN SPEED switch to this setting also causes the FAULT/
MAN HS indicator to illuminate. Caution should be exercised
and service immediately performed to alleviate the overtemp
condition.
AUTO TEMP CNTRL This setting is normally used to cool the cabinet enclosure. Fan
speed is automatically adjusted for the optimum cooling
capacity. The actual fan speed when in this setting is shown by
the FAN SPEED indicators.

SYSTEM OK indicator Illuminates when all predetermined cooling and temperature
parameters have been met. An OVER TEMP or FAULT/MAN
HS condition causes this indicator to go out.
FAN SPEED indicators Illuminates in conjunction with the FAN SPEED AUTO TEMP
CNTRL setting to indicate the actual fan speed. Indicators are
self-explanatory.
Fuse Replaceable fuse for cooling system over voltage protection.
Replace with a 3 amp fast 5x20mm cartridge fuse only. Check
system for cause if fuse is blown or call Avaya service
department.
Front Control Panel

The cabinet front panel contains a standard 3.5 inch floppy disk drive, a 4mm DAT tape drive,
and an FCP (Front Control Panel) for each VRC in the system. The FCP provides separate
power controls and status indicators for each TMS (by chassis slot).
Table 4: Front Control Panel
TEST / ON / OFF Three-position rocker switch used to turn power to the TMS on or
switch (slots 1, 2, 3, off, or to test the associated power supply. (The TEST / ON / OFF
and 4) switches for slots 5 and 6 are on the VRC rear panel, see VRC Rear
Panel on page 34.
POWER ON Illuminates green when power is applied to TMS.
indicator (all slots)
NORMAL indicator Illuminates green when TMS is operating properly and there are no
(all slots) alarms or system faults.
MINOR ALARM Flashes yellow when a minor alarm is active, accompanied by an
indicator (all slots) audible indication (beep). To reset, press the RESET switch. Use as
a troubleshooting aid by viewing alarms in the Alarm Viewer, see
Alarm Viewer on page 37.
MAJOR ALARM Flashes red when a major alarm is active, accompanied by an
indicator (all slots) audible indication (beep). To reset, press the RESET switch. Use as
a troubleshooting aid by viewing alarms in the Alarm Viewer, see
RESET switch Push-button switch for resetting visual and audible alarm indications.

VRC Rear Panel

The rear panel of the VRC contains indicators, switches, and connectors for maintenance,
configuration, and connection to other system components. The following illustration shows
the VRC rear panel.
Table 5: VRC Rear Panel
Item Function
CHASSIS ID Used to assign the chassis number. Each chassis in the system is
selector switch assigned a unique number, starting at 0 and running consecutively.
EXT CLK A and BNC connectors used to obtain synchronization reference clocks for the
EXT CLK B CT bus from an external source. The CT bus is the means by which voice
connectors and audio data is transmitted throughout the TMS.
TEST / ON / Three position rocker switch used to turn power to the slot on or off, or to
OFF switches test the associated power supply.
(slots 5 and 6)
ALARM relays Used to connect to external indicators for major and minor alarms.
Common (C), normally closed (NC), and normally open (NO) contact
connections are provided.
EXTERNAL Can be used to connect to external sensors for system indication of up
SENSORS to four separate events (A,B,C,D). CAUTION: Voltage and current
relays limitations. Do not connect to line level signals.
PWR ON Illuminates green when power is applied to slot or NIC.
indicators (S5,
S6, and NIC)
NORMAL Illuminates green when the module in the associated slot or NIC is
indicators (S5, operating properly and there are no alarms or system faults.
S6, and NIC)
MINOR ALARM Flashes yellow when a minor alarm is active for the slot or NIC.
indicators (S5, Accompanied by audible indication (beep). To reset, press the RESET
S6, and NIC) switch on the FCP. Use as a troubleshooting aid - alarms are promulgated
to the Alarm Viewer, see Alarm Viewer on page 37.
MAJOR ALARM Flashes red when a major alarm is active for the slot or NIC.
indicators (S5, Accompanied by audible indication (beep). To reset, press the RESET
S6, and NIC) switch on the FCP. Use as a troubleshooting aid - alarms are promulgated
to the Alarm Viewer, see Alarm Viewer on page 37.
CSL connector Console connector, reserved for future enhancement.

Item Function
ENET A and RJ45 connectors used to connect the dual rail chassis Ethernet to the
ENET B LAN.
connectors
TMS Front Panel

In addition to front panel indicators, the system components have internal indicators useful for
system maintenance and fault isolation. Located on the front panel of the TMS are connections
to a diagnostic console for troubleshooting, LED indicators for TMS health checks, and the
span input/output connector.
Table 6: TMS Front Panel Connectors and Indicators
Item Description
AUDIO jack RJ11 jack for connecting a telephone handset for
monitoring a phone line, see AUDIO Monitor Jack on
page 36.
CONSOLE jack RS232 (9-pin DIN) port for connecting a debug terminal.
Used for boot ROM and diagnostics (procedures which are
typically handled by certified Avaya Field Engineers).
LEDs 0 - 15 and microswitches Reserved for future enhancement.
HUB A/B LEDs EXT Indicates condition on external port of hub A or B.
See Ethernet
SL1/2 Indicates condition on slot 1 or 2 port of hub A.
Hub
Indicators on SL3/4 Indicates condition on slot 3 or 4 port of hub B.
page 36.
MP Indicates condition on microprocessor port of hub A or B.
COL Indicates errors or collisions in hub A or B.
DCC Front Panel

Item Description
Span connector RJ48M 50-pin connector connects up to eight digital spans
(T1 or E1) to PSTN.
Remote terminal connector RS232 (9-pin DIN) port for connecting a debug terminal.
Used for boot ROM and diagnostics.
Other connectors and Reserved for future enhancement.
indicators
AUDIO Monitor Jack

The AUDIO monitor jack is used to monitor a single phone line. A telephone handset is
connected and the desired line can be monitored using the ccm listen command (see the Avaya
Media Processing Server Series System Reference Manual for more information). Only one
side of the conversation can be monitored at a time.
Use call monitoring (listening to actual calls) only to confirm that caller/Media Processing
Server interaction is going smoothly and that the Media Processing Server is operating
properly. Check applicable laws relating to privacy of conversations before listening to calls.

The dual green and red LED indicators for HUB A and HUB B on the front of the TMS can
display five separate conditions. The LEDs can either be lit continuously or blinking in the
following combinations to indicate a particular condition.
Table 7: Ethernet Hub Status Indicators
Conditions
Indication
EXT, SLx, MP COL
Steady green Receive link pulse FIFO error
Blinking green (@~ 4Hz) Transmit packet (N/A)

Alarm Viewer
Conditions
Indication
EXT, SLx, MP COL
Steady red Reversed polarity Collision
Blinking red (@~ 4Hz) Receive packet (N/A)
Alternating red and green (@~ 5Hz) Partitioned out (N/A)
Alarm Viewer
Media Processing Server Series software, applications, and components generate text alarm
messages to indicate their status or to alert users to possible problems. Each component in
the network stores its alarms in its default alarm log file. This allows viewing of "live" alarms
on any component as the system generates them and viewing the alarm log file of any
component.
Use the Alarm Viewer tool to monitor alarms. Filtering and Properties of alarm log files can be
applied using the corresponding buttons at the top of the Alarm Viewer window or using the
new daemon level filtering functions. Multiple alarm viewers, in any form (live or logged), can
be launched at one time. This allows comparisons amongst components to be made.
For information on launching and using the Alarm Viewer, see Alarm Viewer. See the MPS
Manager Reference Manual for a complete description of the Alarm Viewer. See the Avaya
Media Processing Server Series System Reference Manual for information on the alarm
daemons and corresponding filtering capabilities and refer to the Alarm Reference Manual for
detailed description of the Alarm conditions.
Statistics Data Collection and Reporting

Typically, a single node in a Media Processing Server Series network is designated to collect
and report statistical data. This statistical data can be used to monitor system and application
level functions and to interpret various performance parameters and milestones (such as when
and how calls are taken and handled or whether certain systems have experienced down time).
MPS Reporter is installed and resides on the node designated for statistics consolidation. Use
MPS Reporter to view and generate statistics reports.
System statistics are collected from each Media Processing Server by its VSTAT process. One
VSTAT process exists for each Media Processing Server, and resides in that component's VOS
subcomponent. System variables (used in defining system reports) are predefined.
Application statistics are generated during an application's execution cycle and collected by
each node's VSUPD process. One VSUPD process exists for each node, and resides in the
GEN subcomponent of the common component on the node.

For details on how to configure report parameters, see the MPS Reporter User Guide and
System Statistics Reports on page 72.
Logging off a Node

One can log off a Solaris node by exiting the X-Windows environment. After log off, software
operations cannot be changed, however, the Media Processing Server Series network
continues to run without any manual input.
Logging Off an On a Node
1. Close any tools that are running.
2. Click <MENU> on the desktop to pull up the Workspace menu.
3. For OpenWindows systems, select Exit... For CDE systems, select Log out...
4. The system prompts to confirm the exit. Select Exit on OpenWindows systems, OK
on CDE systems.
The system returns to the desktop login screen.
To log back onto the Solaris node X-Windows environment:
5. Select the desired desktop environment from the Options menu button of the
desktop login screen, or click OK to return to the previous environment setup. (For
more information, see the related subordinate steps on page 13).
Note:
Avaya ships Solaris Media Processing Server Series systems with a Sun station
as the node. OpenWindows and CDE are trademarked products presently used
by Sun to simulate an X-Windows environment. If the environment is not a Sun
workstation, events may vary from the above descriptions.
System Shutdown
After the Certified Avaya personnel starts the system for the first time, there is rarely a need
to shut down or restart the system. Most changes to the applications and Multimedia files can
be made while the system is in normal operation. However, the MPS may have to be shut down
to upgrade the hardware or software, or relocate the system.
Use MPS Manager to stop the applications, then stop the TMS and Central Processing Unit
(CPU).

System Shutdown
Shutting Down the Media Processing Server

1. Select all the Media Processing Servers. Select the domain, then select the
Application Manager (APPMAN).
2. Select Terminate from the Action list. Select the Terminate (soft terminate by default)
and Unassign checkboxes in the Action item list. This allows any calls in progress
to terminate normally or continue up until the value of the kill timer has expired.
Note:
Failure to terminate the applications softly can cause the IVR to hang up on callers
currently dialed into the system.
3. Select the APPLY button. Wait for the Terminate/Unassign Lines Progress window
to reach 100%.
4. Close all tools that are running.
5. Shut down power to the TMS systems. For locations of their power switches, see
Front Control Panel on page 33 and VRC Rear Panel on page 34.
6. In any command tool, log in as "root."
a. From the command line enter su.
b. Enter the root password (____________).
7. Enter halt. This command has been modified by Avaya to perform a controlled
shutdown, taking down system processes and functions in the proper sequence
and timing.
8. Wait for the ROM prompt ( ok> ).
Note:
If the halt command has been executed and the system does not respond,
execute the halt.orig command instead.
9. Toggle off the main power switches.
Before powering off the system, if it is desired to restart it, enter boot at the ROM
prompt and press <ENTER>. Proceed with the login instructions outlined at Logging
off a Node on page 38. Remember to power up the TMS units if they have been
shut down.
To restart the system after power down, see Routine Media Processing Server
Startup on page 27. Normally and by default the Media Processing Server Series
system is designed to automatically boot when powered up. If the system does not
perform in this manner and stops at the ROM prompt:
• log in as "root."
• enter su.
• enter the root password (____________).
• enter the reboot command.

Avaya has altered the reboot command to first perform a controlled shutdown, then
bring the system up gracefully. A message will be displayed that the original Solaris
reboot command has been renamed to reboot.orig.
Note:
The system memory can be "flushed" before rebooting by entering the reset
command from the ROM prompt. This ensures that there are no processes still
in memory prior to the system coming back up.
If there is a fire or some other emergency, and time allows, damage to the Media
Processing Server can be limited by following step 5. through step 9. above and
unplugging the unit. If the situation does not allow time for all the above (it can take
up to five minutes), the system can simply be unplugged. If the emergency persists,
it is wise to leave the area.
Windows shutdown or restart

If you are performing a shutdown or restart operation of a Windows system through a remote
desktop client, there is one additional step for each operation. See the notes in the following
procedures for more information.
The shutdown and restart are done through the command line or the Windows interface.
Important:
A remote shutdown of a machine requires an on-site person to bring that machine backup.
Restart Windows
1. Stop all Avaya services through Windows Computer Management.
a. Go to Start, Settings, Control Panel.
b. Double-click Administrative Tools, and then double-click Computer
Management.
c. In the console tree, click Services.
d. In the details pane, right-button click on an Avaya service, such as Avaya
License Service.
e. From the menu, select Stop.
f. Repeat for all Avaya services.
Each Avaya service begins with the word "Avaya".
2. Restart Windows.
You can use the command prompt or the Start button.
a. To use the command prompt:

Windows shutdown or restart
i. Select Start, Run.

ii. In the Run command line, enter shutdown /r /f /c "Comment".
Note:
You can use the /d switch to provide a reason for restart.
Note:
For a remote restart operation, the/f switch is required to ensure that
all applications are closed without console interaction.
b. To use the Start button:
i. Select Start, Shut Down.
ii. In the Shut Down Windows dialog box, select Restart.
Note:
For a remote restart operation, the following step is required to ensure
that all applications are closed without console interaction. In the Shut
Down Windows dialog box, under Shutdown Event Tracker, clear the
Planned checkbox.
Select OK.
Shutdown Windows
1. Stop all Avaya services through Windows Computer Management.
a. Go to Start, Settings, Control Panel.
b. Double-click Administrative Tools, and then double-click Computer
Management.
c. In the console tree, click Services.
d. In the details pane, right-button click on an Avaya service, such as Avaya
License Service.
e. From the menu, select Stop.
f. Repeat for all Avaya services.
Each Avaya service begins with the word "Avaya".
2. Shutdown Windows.
You can use the command prompt or the Start button.
a. To use the command prompt:
i. Select Start, Run.
ii. In the Run command line, enter shutdown /s /f /c "Comment".

Note:
You can use the /d switch to provide a reason for restart.
Note:
For a remote restart operation, the/f switch is required to ensure that
all applications are closed without console interaction.
b. To use the Start button:
i. Select Start, Shut Down.
ii. In the Shut Down Windows dialog box, select Shut down.
Note:
For a remote restart operation, the following step is required to ensure
that all applications are closed without console interaction. In the Shut
Down Windows dialog box, under Shutdown Event Tracker, clear the
Planned checkbox.
Select OK.

Chapter 4: Command Line Functions
1. Command Line Interaction

2. Online Documentation
Command Line Functions Overview

This chapter provides the information needed to interact with the Avaya Media Processing
Server, use the documentation package, and locate reference material.
Although most interaction with the system is through GUI tools like MPS Manager or MPS
Developer, command line interaction is needed to issue certain status and call monitoring
commands and to interact with the operating system. This section describes these command
tool operations.
Command Line Interaction

A command line is the system command interpreter. It reads commands and interprets them
as requests to execute tasks. Commands can be entered in the Media Processing Server VSH
command line. Access a VSH command line by opening a command/shell tool on the Solaris
desktop. The MPS Command Reference Manual contains details about using the VSH
Command Line.
Access is available to several command lines. The two most important are:
Type Default Prompt Description Use for:

Media Processing Avaya • all Solaris
Server shell vsh#<component_type>. command
<component_number>/ commands
<node_name> {N} -> shell to the local
node
• all
component/
Media

Command Line Functions
Type Default Prompt Description Use for:
Processing
Server
Series
commands
Command Tool <username>@node_name {N} (or, Solaris • all Solaris

if $HOME for user is not set...) command commands
node_name% shell (csh) to the local
node
• starting
component
tools
See the Media Processing Server Series Command Reference Manual for a detailed
explanation of the MPS command shell, and the Solaris system documentation for a detailed
explanation of the Solaris command shell.
It is possible to move between command windows at any time. For information, see Command
Control on page 46.
If a Media Processing Server Series command is entered in a Solaris command tool, the
system sends an error message and returns to the prompt. For example, if ccm shake status
is entered at a Solaris command shell, the following results:
Command Line Editing

The Media Processing Server Series uses standard C-shell (csh) conventions for command
line editing. This section is a quick look at some common command line editing techniques.
See a Solaris guide for a comprehensive discussion of these conventions.
In the default configuration mode, the Media Processing Server shell prompt is:
vsh#<component_type>.<component_number>/<nodename>{N}-> where
<component_type> is the current component type, <component_number> is the current
component number, <nodename> is the local node, and N is an up to three-digit number the
system increments for each command entered, if no prompt is visible, press <RETURN>. This
should cause the Media Processing Server to display a prompt (unless the system is already
performing some other action and is not available for immediate command processing).

Command Line Editing
The following information pertains to command line editing:

• The system only receives and executes console commands after the <RETURN> key is
used.
• The system maintains a command history buffer that contains the last 100 commands
executed. Display this buffer to the console by entering history at any command line.
• Commands can be executed from the history buffer by using the number of the command
preceded by an exclamation point (!). The command number is in the prompt within the
braces ({ }). For example, !95 repeats command number 95.
• The command number increments for each new command entered at the console. After
more than 100 commands have been entered, the system removes the oldest command
from the history buffer.
• Repeat the last command executed by entering !!.
• Change any character string in a previous command to a different string by entering
^oldstring^newstring at the command prompt. If the last character in newstring is a space,
use a concluding ^. For example, ^24^25 changes the first occurrence of string 24 in the
last command to 25 and re-executes the command with the new value. Also, if the
command cp<oldname> <newname> is entered (note the missing space), enter ^cp^cp
^ to correct the command.
The following is a sample console interaction that uses the basic command editing functions. If
viewing this manual online, click a description below to find out more about the corresponding
command.

Note:
Commands can be entered in the Media Processing Server shell using the VSH Command
Line. For information about using the VSH Command Line, see the MPS Command
Reference Manual.
Command Control
Individual control can be exercised over each component in the network, as well as over how
each component executes the commands entered. Components are outlined at System
Configurations on page 20.
Issuing Commands to a Component
Issue commands to any component in the network through the command line for that
component. The Media Processing Server shell command line may be accessed in one of two
ways: through the VSH Command Line.
To access the Media Processing Server shell from a Solaris shell, rsh to any component node,
then enter vsh and press <RETURN>. If this is done at a Media Processing Server node, the
shell prompt of the lowest numbered component displays. Select the desired component to
elicit its shell prompt.
The default Media Processing Server shell prompt indicates the current component type and
component number (that is, the component that is local to the node) as well as the node from
which the tool was launched. If more than one MPS component is configured for the node,
there is no initial prompt. Instead vsh requests you to select a component from a list (similar
to the comp vsh command, below).

Command Control
The comp command identifies the currently configured components along with their status.
"Local " indicates the component is connected to this node. "Remote " indicates the component
is connected to another node in the network. See the Media Processing Server Series System
Reference Manual for a detailed discussion of the Media Processing Server Series network.
All Solaris commands entered in a Media Processing Server shell are issued to the local node
regardless of the current component. For example, if the current component is vas.1 and
grouse is the name of the current node, but the VSH Command Line was launched on node
is9509, ls lists the files in the directory on is9509, not on grouse. To identify the local node
when connected to a component remote to that node, enter the hostname command at the
prompt.
Foreground and Background Commands
The Media Processing Server handles command execution like a standard operating system.
That is, the system executes commands in the order they are entered. When entering standard
commands, the Media Processing Server runs each command to completion before it displays
a prompt for the next command.
Commands can also be executed in the background by following the command with an
ampersand (&). In this mode, the Media Processing Server takes the input and begins
processing, but does not wait for the command to complete. Instead, it immediately displays
a prompt. For example, MPS Manager can be launched in the background and then another
command can be immediately issued.

Online Documentation
Avaya documentation is available online in PDF format. On an MPS, this documentation is
accessed using a Web browser by entering the address http://localhost and clicking the
Documentation hyperlink. To access the documentation from another network location (for
example, from a development workstation), enter the MPS IP address in the address field of
a Web browser.
To check for updates to the latest documentation, go to http://www.avaya.com and click the
Support and Training link.
Note:
Adobe Reader must be installed to view the documentation in PDF. Obtain a free version of
Adobe Reader from http://www.adobe.com.

Chapter 5: Status Monitoring
1. The Alarm Viewer

2. Status Monitoring
3. System Statistics Reports
Status Monitoring
This chapter provides the information needed to:
• Audit overall system performance
• Monitor component functionality
• Monitor phone line events
• Report system statistics
Developer, command line entries are needed to issue some status and call monitoring
commands. This section also describes these operations. For specifics concerning interaction
with the system as a whole, see Command Line Interaction on page 43.
The Alarm Viewer

The system software processes of the Avaya Media Processing Server Series generate text
alarm messages that indicate their status or alert users to possible problems. Each component
in the network stores its alarms in its default Alarm Log File. This allows:
• viewing of alarms on any component as the system generates them (live alarms), and
• viewing of the alarm log file of any component.
The following steps explain how to use the Alarm Viewer tool to monitor alarms.

Status Monitoring
Viewing Alarms
1. Start MPS Manager.
Note:
Before launching the Alarm Viewer, use the Alarm Filter to determine which
alarms to view.
2. Start the Alarm Filter.
a. <LEFT> click the Alarm Filter icon.
Define the alarms that actually display in the Alarm Viewer by setting the
filtering properties. Alternatively, load a previously saved viewer
configuration file (contains filter definitions). See the MPS Manager
Reference Manual for a complete description of the Alarm Filter.
b. Select Choose Log in the Alarm Filter window to select user defined
Historical Alarm Log files.
Note:
Specific alarm log files must be selected before they can be displayed in the Alarm
Viewer.
3. Start the Alarm Viewer.

<LEFT> click the Alarm Viewer icon.
Live alarms display as the generated alarms are received by the Alarm Viewer from alarm
daemons.
Default alarm log files display in the order in which they are selected in the Logged Alarms
Filter. See the MPS Manager Reference Manual for a complete description of the Alarm Viewer.
Note:
Alarms are generated by the alarmd daemon. If alarm filtering has been instituted at this
level or that of alarmf (an intermediate filter daemon), the Alarm Viewer only receives those
alarms that pass the filtering criteria. For detailed information see the Media Processing
Server Series System Reference Manual.
Note:
For more information, see Monitoring Component Status on page 53.

Status Monitoring
The log file for each component can also be accessed from the Media Processing Server shell.
Both the default log file and its backup are in the directory $MPSHOME/common/log, where
the file names for the specific components are in the format
alarm_type.component_type.component_number.log, where alarm_type is ether "alarm",
"info", or "warning". The default log is .log and its backup is .log.bak. The .log file is created
when the system boots. The .log.bak file is created when the preconfigured file size is
exceeded. Use standard commands or editors to view and edit these files.
Refer to the Alarm Reference Manual for detailed description of the Alarm conditions, error
causes, and remedial actions.
The alarms that the Media Processing Server generates can be customized by modifying
records in the alarm database, located in $MPSHOME/common/etc. Additional information
concerning the alarm database can also be found in the MPS Command Reference Manual.
Status Monitoring
The Media Processing Server has many built-in functions for monitoring system and line status.
With these functions, the status of components, spans, external hosts, phone lines, MMF files,
applications, the Call Control Manager (CCM), the Voice Memory Manager (VMM), the
Redundancy Configuration Daemon (RCD), and the Startup and Recovery Process (SRP) can
be easily monitored. Standard commands can also be used to display and modify the system
date and time.
System Date/Time
To check the system date and time, enter date at any Solaris or Media Processing Server shell
command line. The super-user can use date to modify the system date and time. See the
Solaris system documentation for more information.
Although it is not necessary to alter the system date for daylight savings time, users are often
unaware of this. In this regard, it is not recommended to change the system time by issuing
the date command directly. If the time is set back by issuing the date command, cron will have
difficulty performing scheduled tasks, all of which will become queued up until cron itself
terminates. Evidence of this can usually be detected in the /var/cron/log file. If the system time
is adjusted to a point prior to the start time of cron, its jobs are not rescheduled correctly. The
correct method to alter the system date is to stop cron, issue the date command, and restart
cron as shown below:
/etc/rc2.d/S75cron stop date <new_date/time> /etc/rc2.d/S75cron start

Status Monitoring
Note:
If the time or date on the system was recently changed, be sure that the clocks on all the
communicating systems are synchronized. Non-synchronized system times can adversely
affect statistics collection.
Solaris Management Console

Solaris Management (SMC) Console provides a scheduler GUI. This allows to set up cron jobs
using a GUI instead of editing the crontabs file manually.
Follow the steps to edit a list of existing crons:
• On the console, (as any valid user such as peri or root) open a command window and
execute: /usr/scam/bin/USMC
• Allow several minutes for the SMC to initialize and configure itself.
• At the welcome screen, expand this computer icon.
• Select the services option.
• Enter the user in the login prompt (this is the cron user you plan to manage—peri or root).
• The existing crons will be listed and you can add/delete/modify the jobs as desired.
SRP Status
The Startup and Recovery Process (SRP) functions as the parent of all MPS system
processes. SRP spawns the relevant programs at system startup, performs watchdog duties
for each TMS and VOS process, acts as a topology database server; spawns and terminates
VENGINE applications, and restarts abnormally terminated programs.
The status of SRP can be obtained (as well as that of other processes and applications) or
process groups and applications at a VSH command line (on a particular node) with the
following commands:
Command syntax Report

srp -status SRP status for the (specified) node
srp -gstatus SRP group status for the specified node

Component Status
The MPS Command Reference Manual contains details about using the VSH Command Line.
See the Media Processing Server Series System Reference Manual for detailed descriptions
and examples.
Component Status
The status of components can be considered the highest level of overall system monitoring.
A component status of "down" can be indicative of more serious problems somewhere within
the system. These problems can then be located using more specific means (see the
paragraphs that follow as well as the MPS Manager Reference Manual.
Monitoring Component Status
1. From the Command Line:
The most generalized means of checking overall component status is through use of
the VSH command line.
a. rsh to the node that contains the components to be monitored (use the
vsh command to access the VSH command line).
b. Enter comp and press <RETURN>. This command identifies the
currently configured components along with their status.
2. Using MPS Manager:
Components supported by MPS Manager include MPS, Speech Server, MTS,
CCSS, CSS, VAPI, RTR, SNTRY, DCS, CTXCOMM, and TMSCOMM (for an

Status Monitoring
overview of these components see the MPS Manager Reference Manual). The
means of monitoring each varies, however.
Basic information that applies to monitoring of all components in MPS Manager
includes interpretation of colors resident on component icons in relation to
component state. State is a representation of a MPS Manager tool attempting to
contact some Media Processing Server Series process. In the case of tree objects,
MPS Manager tools (Application Manager and Status tools) attempt to contact SRP
(Startup and Recovery Process). Until contact is confirmed, the state of the
component is defined as Unreachable, as no information is available. Unreachable
components display as black objects in the workspace (assuming the tree is
expanded to display its components). A component will be considered Unreachable
for the window of time that it takes to return a response to the tool requesting either
initial contact or any contact after contact is lost.
Components acknowledge contact with the tool on an individual basis. A component
is no longer considered Unreachable when it returns information to the tool about
its state, which will be either Up or Down according to SRP. Components in an Up
state (identified by SRP as RUNNING) display as green objects. Components in a
Down state (identified by SRP as anything other than RUNNING) display as red
objects.
Components are represented by icons at the tree level. The following are examples
of these icons:
MPS tmscomm Speech Server
Note:
For complete information on how colors, icons, and states apply to MPS Manager, and for
further information regarding SRP, see the MPS Manager Reference Manual.
Monitoring Components
Select the Desired Component. <RIGHT> click the icon next to a component to display
various properties. Properties are different depending on the component type selected.
The following represents a list of properties for an MPS.

Component Status
Multiple pieces of information about a component can also be displayed. For example,
selecting a components span, then the spans lines in use, then the lines attributes
produces the following output.

Status Monitoring
For complete information on this and other items concerning MPS Manager, see the
MPS Manager Reference Manual.
Phone Line Status

The status of the phone lines can be displayed with the Line Status tool.
Monitoring Phone Line Status Using MPS Manager
Launch the Line Status tool. Select a node or component from the MPS Manager navigation
pane, then select the Line Status tool.
The Line Status tool, shown below, displays the physical state of phone lines for a specific
period of time. Phone line status indicates what is actually happening on the line during a time
period. The current phone line status for MPS and applications can be monitored.

Phone Line Status
Phone line status is defined by seven color coded activity states, which display along the y-
axis of each graph.
The Line Status tool quantifies and displays each the following phone line states: Connected,
Ready, Referral, Busy, Down, No Answer, and Unreachable. These six phone line states are
defined in the following table.
Phone Line State Color Description

Connected Green The monitor detects ongoing interaction
between the or MPS's phone lines and
callers, indicating calls are in progress on
these lines.
Ready Yellow The monitor detects the or MPS's phone
lines are in service and ready to take calls.

Status Monitoring
Phone Line State Color Description

Referral Orange Detected activity is dependent upon the type
of referral method that has been instituted—
either a hook flash or digital referral method.
Hook Flash Referral The monitor detects the MPS's phone lines
are in the process of referring the call to an
operator.
Digital Referral Activity can be in one of the two following
states:
• The lines are in the process of referring to
operators.
• The callers are interacting with operators
Busy Purple The monitor detects the MPS's phone lines

are in an in-service-busy state and not able
to take calls.
Down Red The monitor is able to contact the or MPS's
phone lines, but detects the lines are not able
to receive calls, indicating that these lines
can be faulty.
No Answer Blue The line is Idle and the state is set to no
answer.
Unreachable Black Phone line status has been queried for its
state and no message has been received by
the Monitor (basically, a missed response).
Also, it could mean that SRP did not respond
to information about the phone line from the
Monitor. The Monitor needs to query SRP
about how it should contact the CCM (Call
Control Manager) process, before it can
actually contact CCM.
Span Status
Span status can be monitored from the command line. Monitoring can also be accomplished
through the MPS Manager Span Status tool, which provides graphical representations of
various aspects of a digital span.
Monitoring Span Status From the Command Line
To determine span status from the command line, first switch to the node on which the
component that contains the spans to be checked is located, see Issuing Commands to a
Component on page 46. Next, enter the command dlt and select the component that contains
the spans from the list of configured components (this list only displays if there is more than

Span Status
one local component other than common or tmscomm configured on the node). After the node
has connected to both tcad and trip (two processes needed to develop the information), enter
spanstatus <n>, <n-n>, or <all>, where <n> is the number of the span in question, <n-n> is a
series of spans, and <all> is all spans configured on that node. The span status report displays
as follows:
Monitoring Span Status Using MPS Manager

Span Status is available for each digital Media Processing Server defined for the domain in
the Activity Monitor's workspace. A Span Status tool can be launched for a single Media
Processing Server or for multiple Media Processing Servers; a window opens for each
selected.
Note:
The information applies to digital phone lines only and is available for Media Processing
Servers with either all digital lines, or a combination of digital and analog lines. However,
the information does not apply to the analog phone lines.
To launch the Span Status tool:
Launch the Span Status tool. Select a component from the MPS Manager navigation pane,
then select the Span Status tool.

Status Monitoring
Use the Span Status tool to display the state of digital spans (physical phone lines), graphically,
on a per component basis. Span Status is available for each component defined for the domain.
This is a display tool only.
Span status is updated, by default, at 15 second intervals. This interval is specified by the MPS
Manager Data Provider software.
Span status displays only for (digital) physical phone (call processing) lines, which are capable
of processing calls. Span status does not display for logical (administrative) phone lines, which
are unable to process calls and to which administrative applications are, typically, assigned.
Therefore, administrative applications are not listed in the Applications scrolling window, unless
they are assigned to physical lines, which are digital.
The Span Status displays the component name and state; the name of the spans (A, B, C, and
so on) and their states; and the phone lines and applications that are associated with each
span.
Span dividers are lines that identify the boundaries between individual spans in the Lines
display area. When you position the cursor over a line, the phone line number displays under
the Lines display area.
The date and time of the last update of information to this window displays in the lower left
corner of the Component Span Status window.
The Component Span Status tool displays the following information.
• Component: The node name and component number of the component used to launch
the Component Span Status tool displays in the format nodename:comp_number. In this

Span Status
example, is9501:101 (MPS 101 on node is9501) was used to launch the tool. The current
state of the component (Up, Down, Unreachable) is identified by the color coded symbols
defined in Key area of the window, labeled States.
When you launch Component Spans status with a component configured only with analog
phone lines, the Span Status window indicates some information about the component.
However, the message in the Spans display area indicates that no spans have been
detected. In the following illustration, the Span Status tool was launched with an analog
MPS (is7501:1).
• Spans: Span information indicates the span state, span name, and phone line range
associated with the span. The current state of the span (Red Alarm, Purple Alarm, Blue
Alarm, Yellow Alarm, Unreachable, Up, Disabled, Unknown) is identified by the color
coded symbols defined in Key area of the window, labeled States.
• Lines: The Lines display area identifies information about the spans that are associated
with phone lines. Span dividers are the black lines that define the boundaries between
the individual spans. When the cursor is over an line, the line number displays under the
Lines display area.
The current phone line state is indicated by the color coded symbols defined in Key area of
the window and labeled States.
The applications associated with a line (if any) are also identified by color coded symbols
defined in the Key area of the window, labeled Applications.

Status Monitoring
• Key: The Key display area is used to associate the color coded symbols for Applications
and States with the Span Status display.
- Applications: The Applications display scrolling window identifies all applications (if
any) that have been assigned to the component. Each application is associated with
a specific color. Each line to which an application is assigned displays with a colored
background, which matches one of the application colors displayed in the
Applications scrolling window. The application names and the phone lines to which
they are assigned can be identified by matching the color sets.
Note:
Because span status displays only for (digital) physical phone lines, administrative
applications are not listed in the Applications scrolling window, unless they are
assigned to (digital) physical lines.
- States: The States display scrolling window identifies the range of possible
component, Span, and Phone Line states. These symbols are used to indicate the
current state of the component, each span, and each of the digital, physical phone
lines associated with the spans in the Lines display area. Phone Line, Span, and
component states are defined in the following table.
Table 8: Component Span Status States
Symbol State Applies To Description

Connected Phone Line Phone line state in which
interaction is detected
between the MPS's phone
lines and callers,
indicating that calls are in
process on these lines.
No Answer Phone Line The line is Idle and the
state is set to no answer.
Referral Phone Line Detected activity is
dependent upon the type
of referral method that has

Span Status

been instituted (hook flash
or digital).
Busy Phone Line Phone line state in which
the MPS's phone lines are
in an in-service-busy state
and not able to take calls.
Down MPS One or more component-
specific processes have
either been interrupted or
are not yet fully
operational.
Phone Line Phone line state in which
the MPS's or MPS's
phone lines are not able to
receive calls.
Unreachable Span The state of the span is
unknown because the
span is unreachable.
MPS The state of the MPS is
unknown. No information
is available. Once
information is available,
the state of the MPS is
either Down or Up.
Phone Line Phone line state in which
the MPS cannot be
contacted therefore,
phone line state cannot be
determined.
Ready Phone Line Phone line state in which
the MPS's phone lines are
in service and ready to
take calls.
Up Span MPS The Span is in service.
MPS All MPS-specific
processes are fully
operational.
Disabled Span The span has been
intentionally disabled from
the MPS.
Yellow Alarm Span The span is in a yellow
alarm state. The span is

Status Monitoring

receiving a yellow alarm
from the remote end.
This indicates that the far
end is not able to receive
your signal but you are
receiving a signal from the
remote end.
The span requires
attention.
Red Alarm Span The span is in a red alarm
state, which indicates that
the span is out of sync.
A red alarm indicates the
span has lost the ability to
synchronize with the
remote equipment. The
span has, effectively, lost
the incoming signal.
The span requires
attention.
Blue Alarm Span The span is in a blue alarm
state. The span is
receiving a blue alarm
from the remote end. This
means you are receiving a
pattern of all ones.
Typically, a blue alarm
indicates that the remote
end is in a maintenance
mode.
Purple Alarm Span The span is in a purple
alarm state. The span is
receiving a purple alarm
from the remote end. This
means you are receiving a
pattern of all ones on
channel 16).
Typically, a purple alarm
indicates that the remote
end is in a maintenance
mode.
Unknown Span The state of the span is
unrecognized. It does not
comply with the definition
of any other State listed in
this scrolling window.

RCD Status
RCD Status
The Redundancy Configuration Daemon (RCD) is responsible for redundancy (N+1) system
configuration and control, as well as system startup (startupMode) configuration for Call-
Protect. RCD is started using /etc/rc3.d/S19rcd.startup on Solaris, and services on Windows.
RCD must be running on every MPS node. RCD will apply for a CallProtect license when its
startupMode is set to "CallProtect" or "cp". A general status report that summarizes
configuration and state information can be obtained from a Media Processing Server VSH
command line using the following commands:

rcd status General N+1 and Call-protect configuration
and licensing information, as well as the
current RCD state.
rcd xlsreplic Current licensing information for the specific
process.
The version of RCD that is running on the system can be obtained by entering the command
rcd version on a Media Processing Server VSH command line.
For information about using the VSH Command Line, see the MPS Command Reference
Manual.
CCM Status
The Call Control Manager (CCM) is the primary interface between applications and VOS
services and is the gateway for communication with the telephony hardware. A status report
for the system, a line, or a range of lines on a Media Processing Server VSH command line
can be obtained using the following commands:

ccm status ccm st Overall CCM status for the system, including
process startup, work thread statuses, and
the state of each line CCM knows about.
ccm {phone:<line#-line#>} CCM line status reports as above for each
status c<line#-line#> st line in the specified range.
ccm {phone:<line#>} status CCM status for the specified line, including
c<line#> st line states, CCM related configuration
parameters, and queue sizes.

Status Monitoring
These commands can be entered in the Media Processing Server shell using the VSH
Command Line. For information about using the VSH Command Line, see the MPS Command
Reference Manual.
The version of CCM that is running on the system can be obtained by entering the command
ccm version in a Media Processing Server VSH command line.
Application Status
Use the APPMAN (Application Management) Status tool to check the status of any application
assigned to a Media Processing Server. For information about working with applications, see
Voice Processing Applications on page 77.
Checking the Status of Applications
Using MPS Manager
Launch the Application Management Tool.
Select a component from the MPS Manager navigation pane, then select the
Application Management tool.
Icons displayed in the Applications and Locations scrolling windows are cues to
application, phone line, and component information. These icons symbolize:
administrative applications that are configured to execute completely before other
applications are started; linked applications; applications configured not to start at

Application Status
reboot; coded components; and, coded call processing and administrative phone lines.
The color of component and application icons indicate their state.
The shape of phone line icons indicates phone line type. The color of phone line icons indicate
the state of the application. This information is summarized in the following tables.
Shape Description
Call Processing (Physical) Line; capable of processing calls. Call
processing applications are assigned to these lines.
Administrative (Logical) Line; incapable of processing calls.
Administrative applications are assigned to these lines.
Color Description
Green An application is assigned to a phone line and is in the process of
executing (running).
Blue An application was assigned to a phone line but it is not currently
executing (not running). The application:
• was assigned but not started,
• has completed its execution cycle, or
• has terminated but has not been unassigned from the phone line.
Yellow The phone line has been selected, but no application has been assigned
to the phone line.

Status Monitoring
The Locations window lists all configuration options for the lines associated with the selected
components. Placing the cursor over a particular location, indicates the status of the
parameters for the application. In addition, the following icons may appear to indicate
configuration selections.
Shape Description
Administration applications that are configured to Wait for Exit display
with an initialization icon. Wait for Exit is an Execution option that is
configured by the Configure Application tool.
Applications that are configured not to restart during reboot display with
a blue (no restart) application icon. Start on Reboot is an Execution option
configured by the Configure Application tool.
See the MPS Manager Reference Manual for specific details regarding the Application
Management and Application Configuration tools.
VMM Status
The Voice Memory Manager (VMM) is a process that resides in the VOS subcomponent of the
Media Processing Server component and provides media management services for the VOS.
The VMM status report indicates initialization and connection states and static and dynamic
thread configurations, if any. This report can be obtained from a VSH command line with the
following command:

vmm status or vmm st Overall VMM status for the system
The version of VMM running on the system can be obtained by entering the command vmm
version at a VSH command line.
Multimedia Format (MMF) File Status

The Media Processing Server uses MMF files to store audio elements and fax data. The audio
elements can be:
• Vocabularies (that is, spoken prompts in applications)
• Items recorded by an application (that is, the Caller Message Recording [CMR] feature,
see Caller Message Recording on page 99.

Multimedia Format (MMF) File Status
Checking the Status of Audio Elements From the Command Line

Enter the following commands in a Media Processing Server VSH Command Line to display
a variety of status reports for MMF files.

vmm mmfstatus Status of all activated (loaded) MMF files,
including the system-wide record file
vmm refstatus <mmf_file> Element play statistics for <mmf_file>,
including outstanding play/record requests
The MPS Manager Command Manual contains details about using the VSH Command Line.
Using MPS Manager
1. Launch the MPS Control Center Tool.
2. Select the MMF Configuration Tool. Double <LEFT> click MMF Configuration and
select the desired Node and Component to view the MMF status.
The status of the MMFs are displayed. For more information about the MMF
Configuration tool, see the MPS Manager Reference Manual.

Status Monitoring
Host Status
The Host Status tool can be used to display the state of any communication link to a host.
Information about the state of phone lines configured to use a host's Virtual Terminals, as well
as the terminals themselves is also available.
Monitoring Host Status
Using MPS Manager
1. Select a Component. Select a component from the MPS Manager navigation pane.
2. Select the Host Status tool.
The state of the hosts, as well as their (numerical) "name" and protocol being used,
can be determined in the Hosts: field of the tool. State is a representation of a MPS
Manager tool attempting to contact some Media Processing Server Series process:
the Host Status Tool attempts to contact the commgr (Communications Manager)
process.

Host Status
Host states can be one of the following as indicated by a colored icon, shown in the table below
and which appears in the State field shown above. VT states are also indicated by a colored
icon: in this case they are shown in the VTs: field when the Host Status tool Index By: selection
is set to VT.
Table 9: Component Host Status States

Up Host Media Processing Server
Series protocol software has
determined that the remote
host is available for
communication.
VT Media Processing Server
determined that a given VT can
be used to establish a session
with the remote host.
Down Host Media Processing Server
determined that the remote
host is not available for
communication.
VT Media Processing Server
determined that a given VT can

Status Monitoring

not be used to establish a
session with the remote host.
Host The state of the host is not
known, as it is unreachable.
Unreachable
VT The state of the VT is not
known, as it is unreachable.
Unassigned VT VT The phone line is not currently
associated with a VT. However,
at some other point in time it
can be associated with a VT as
a result of pooling. For
information about pooling VTs,
see the Media Processing
Server Series COMMGR
Reference Manual.
Unknown Host The state of the host is
comply with the definition of
any other state listed in this
scrolling window.
VT The state of the VT is
comply with the definition of
any other state listed in this
scrolling window.
System Statistics Reports

The Media Processing Server automatically gathers system statistics for monitoring activity on
a single MPS or across the entire MPS network.
Use MPS Reporter Tools to display system statistics reports as described in the following
procedure.
Note:
MPS Reporter Tools run on a single node within a network, but can collect and report
statistics network-wide.
Generating System Statistics Reports
Statistics reports can be generated and viewed on demand. This report can also be printed
as a hard copy or printed to a file.

To generate the report:

1. Launch MPS Reporter. Select MPS Reporter from the Start menu on a Windows
platform or by entering MPS Reporter on a UNIX or Windows command line.
2. From the MPS Reporter window, open a file. Use the File Open icon or the menu
path File—Open Report (use the Report Definition... option to select predefined
reports). The Report Definition window displays.
3. From the Report Definition window, select the desired report. This can be one of
the seven predefined system reports or a report that has been defined and saved
by someone else. Click OK.

Status Monitoring
Report (File) Name Definition

PhoneDetail.prd Detail Phone Line Statistics Report. Phone line usage is
reported for selected or all Media Processing Servers
and phone lines, for a specified date range. Totals reflect
usage per individual Media Processing Server.
PhoneSum.prd Summary Phone Line Statistics Report. Data is
collectively summarized for selected or all phone lines,
then reported for selected or all Media Processing
Servers, for a specified date range. Data for each Media
Processing Server is summarized on a single line. Totals
reflect usage inclusive of all Media Processing Servers.
PhoneAcc.prd Accumulated Summary Phone Line Statistics Report.
Data is summarized collectively for the time period
specified by the user for selected or all phone lines, then
reported for selected or all Media Processing Servers for
the specified date–time range.
SpanDetail.prd Detail Span Statistics Report. Data is reported for each
span on selected or all Media Processing Servers, for a
specified range.
SpanSum.prd Summary Span Statistics Report. Data is collectively
summarized for all spans, for selected or all Media
Processing Servers, then reported for a specified date
range. Data for each Media Processing Server is
summarized on a single line. Totals reflect span activity
inclusive of all Media Processing Servers.
HostDetail.prd Detail System Statistics Report. Data is reported for
selected or all Media Processing Servers and external
hosts for a specified date range.

Report (File) Name Definition

HostSum.prd Summary System Statistics Report. Data is cumulatively
summarized for each external host for selected or all
Media Processing Servers, then reported for a specified
date range. Data for each Media Processing Server is
summarized on a single line. Totals reflect system
activity inclusive of all Media Processing Servers.
4. Set the scope of the report. Use the Report Scope icon or the menu path Setup—
Report Scope.... Enter the requirements in the Report Scope window.
5. Generate the report. Use the Generate icon or the menu path File—Generate.

Chapter 6: Voice Processing Applications
1. Application Memory Requirements

2. Activating Playback MMF Files
3. Assigning and Starting Application Programs
4. Terminating and Unassigning Application Programs
5. Deactivating MMF Files
6. Updating or Replacing Playback MMF Files
7. Caller Message Recording
Voice Processing Applications

This chapter provides the information needed to:
• Start and stop applications
• Work with vocabularies
• Set up Caller Message Recording (CMR)
Developer, a command line is needed to issue some commands and to perform system-
related application maintenance. This section also describes these operations. For specifics
concerning interaction with the system as a whole, see Command Line Interaction on page
43.
For information on monitoring application and Multimedia Format (MMF) file status, see Status
Monitoring on page 51.
Application Memory Requirements

An important consideration to make before assigning and running applications is their impact
on overall system performance. One of the greater aspects of this impact is the amount of

memory an application requires during its execution. The following formula accurately
calculates an application's memory requirements.
Note:
This formula only addresses application overhead and does not include other system
components or custom features that are part of the native operating system (OS) software.
The total memory requirements to run N instances of an application, which uses Indexed
Sequential Access Method (ISAM) databases (ISAM significantly reduces memory
requirements), is calculated as follows:
(150K + WS) * N + (APP)
where WS is the total length in KB of all Working Storage items in the application, N is the
Number of phone lines running the application, and APP is the size of the APPlication .vex
file in KB.
If the application does not use ISAM databases, the memory requirements formula changes
as follows:
(200K + WS) * N + (APP) + 500K
To determine the amount of memory needed for an application's Working Storage (WS), use
the following vexdump command:
vexdump -v appname | grep Values
Additional Memory Considerations

If an application uses Shared Memory, the above memory requirements increase by 150K +
total length of all shared memory items.
If an application uses Hashed Sequential Access Method (HSAM) databases, the actual file
size in bytes of each HSAM file must be added to the total size of the .vex file. Adding memory to
HSAM applications improves overall performance.
If an application executes the LINK command, the total length of all linked-to .vex files which
can be in memory simultaneously, must be added to the total size of the .vex file.
Example:
An application with a 300K .vex file, running on 48 lines, not using ISAM and linking to two
different 100K size applications, with a total of 20K working storage requires:
(200 + 20) * 48 + (300 + 100 + 100) + 500 = 12M
Use this worksheet as a guide to computing application memory requirements:

Activating Playback MMF Files
(If ISAM) (If HSAM) (If no

ISAM)
+@
+
150K ~~~~ #_of_lines_running HSAM_files'_size
( * (.vex_file ) + 500K
+WS) 200K _app ~~~~ + @ linked-
_size
to_files'_size
(If no ISAM) (If LINK)
Activating Playback MMF Files

A playback MMF file can be activated either for a particular application or for all applications
in the system. Normally, commands in the VMM-MMF configuration file ($MPSHOME/mpsN/
etc/vmm-mmf.cfg) activate the MMF files when the system boots. MMF files can also be
activated from the MPS command shell. This is useful for testing new applications and
configurations. MMF files activated from a command shell are not reactivated if the system is
restarted.
See the Media Processing Server Series System Reference Manual for configuration details
and an explanation of MMF files and hash tables.
There are two methods for activating MMF files:
• For backward compatibility, the activation of MMF files during system initialization is done
by processing the vmm-mmf.cfg configuration file and activating each listed MMF file in
the specified manner (record, system-wide, application-specific, and so on). This
activation method has several drawbacks. When running with a secondary node backing
up several nonhomogeneous nodes, VMM has to activate the same MMF files that were
active on the primary system. Keeping these files up to date on the secondary node is
difficult due to the fact that the files can be located anywhere on the primary system.
Another drawback is that anytime a new MMF file is added, a configuration file must be
modified to ensure that on restart the MMF will be loaded.
• The newer method was introduced in MPS software release 2.1. It requires all MMF files to
be in the $MEDIAFILEHOME directory (or one of its subdirectories—see the diagram on
the next page). Upon initialization, VMM activates all MMF files in the
$MEDIAFILEHOME/mpsN directory. Each mpsN directory contains system and digitTable
subdirectories. The system subdirectory contains the MMF files to be activated system-
wide. The digitTable subdirectory contains the dtmf MMF file (dtmf.mmi and dtmf.mmd).
The use of the digitTable subdirectory replaces the tonetable entry in the file vmm.cfg.
There is also a subdirectory for each application for application-specific MMF files. Both
the system and application directories have two subdirectories named record and default.
The record subdirectory stores the MMF file into which data is recorded by default. (This
should be the only file in that subdirectory.) The default subdirectory contains the default
MMF (for playing) if one is needed. This eliminates the need for the vmm-mmf.cfg
configuration file and provides a well-defined location from which a secondary node can

periodically update its MMF files. To ensure backward compatibility, VMM still attempts
to process the vmm-mmf.cfg file after activating any files in $MEDIAFILEHOME. The
processing of the vmm-mmf.cfg and the tonetable entry in the vmm.cfg files is not
supported for systems with secondary nodes.
Note:
The N+1 redundancy configuration does not support the use of vmm-mmf.cfg or the
tonetable entry in vmm.cfg.
Note:
VMM loads all files in $MEDIAFILEHOME/mpsN/ and its subdirectories. In the case that
there is more than one file in the record/default directory, the last file activated in the directory
will be designated as the default record/play MMF. After activating all files, VMM attempts
to process the vmm-mmf.cfg file (if one is present). VMM is informed about which MPS it is
running on by TRIP, so that when a secondary node is taking over for a primary, the correct
file is loaded.
When adding a new file inside of $MEDIAFILEHOME, the file does not become active until the
system is restarted. Use the vmm mmfload command to activate the file immediately without
restarting.
System Wide Playback MMF Files

A playback MMF file can be activated such that all applications on the system can access it.
Activating System-Wide Playback Multimedia Files
1. Open a shell on the Media Processing Server that will be running the applications,
see Command Control on page 46.
2. Assign the applications to the desired lines and start them, see Assigning and
Starting Application Programs on page 82.

Application-Specific Playback MMF Files
3. Change location ( cd ) to the directory where the desired MMF file exists, see
Working with Directories on page 104. Alternatively, the path to this location can
be supplied in the vmm mmfload command shown in the next step.
4. Allow the applications to access the MMF file using the vmm mmfload command.
Use the syntax vmm mmfload <mmfname>[,system], where <mmfname> is either
the name of the file to be loaded (if in its directory) or the path to the file. Special
permissions or privileges are not needed to use this command. (It is not necessary
to specify the "system" parameter as this is the default.)
Application-Specific Playback MMF Files

An MMF file can be activated such that only a specific application can access it. Included in
this procedure is the creation of a hash table. A hash table is a data structure which resides in
system memory (as opposed to voice data memory). When the MMF file is activated, VMM
enters the names of all vocabulary elements in that file into a hash table. When an application
references an element by name (instead of referencing the element by index number), VMM
uses the hashing scheme to locate the recorded contents of that element. A hash table can
function for the entire system or just one application.
It takes several steps to activate a playback MMF file for a particular application:
• create the hash table for the application (that is, initialize the application)
• activate the MMF file for the application
• assign the application to phone lines and start it (using APPMAN)
Activating Application-Specific Playback Multimedia Files
1. Place the MMF file in a directory under $MEDIAFILEHOME.
2. Open a shell on the Media Processing Server that will be running the application,
see Command Control on page 46.
3. Create the application-specific hash table using the vmm appinit <appname>
command. See the Media Processing Server Series System Reference Manual for
a detailed description of hash tables.
a. To have the application look in the application-specific hash table before
the system hash table, use the syntax vmm hashfirst <appname>,local
b. To have the application look in the system hash table before the
application-specific hash table, use the syntax vmm hashfirst
<appname>,system
Note:
System hash tables are used in relation to applications to contain such common
and frequently accessed elements as DTMF tones (dtmf) and numeric elements
(numset), and therefore reduce the size of the application hash table (large tables
can negatively impact system performance).

4. Allow the application to access the MMF file by using the vmm mmfload command.
Use vmm mmfload <mmfname>,<appname> to activate an MMF file in the
application-specific hash table. Use vmm mmfload <mmfname>,system to activate
an MMF file in the system hash table.
Note:
When loading an MMF for a specific application, if the application has not already
been initialized, VMM will initialize it using the default setting for hashfirst (which is
local).
5. Assign the application to the desired lines and start it, see Assigning and Starting
Application Programs on page 82.
The vmm hashfirst command can be used to change the hashfirst sequence after
an MMF file is activated (that is, without deactivating the MMF file). For example, if
the command vmm hashfirst <appname>,local was used, the command vmm
hashfirst <appname>,system can be used to change the hashfirst sequence. For
all systems, hashfirst commands must be placed in the vmm-mmf.cfg file.
Note:
The following information is for backward compatibility on non N+1 systems:
The command vmm mmfload <mmfname> loads the specified MMF file into the
system hash table. To load the MMF into an application hash table, specify the
application name in the command vmm mmfload <mmfname>,<appname>. In a
development environment, the application can be started, and then the command
vmm mmfload <mmfname> can be applied. In a production environment, the
mmfload commands should be placed in the file $MPSHOME/mpsN/etc/vmm-
mmf.cfg.
Caution:
Do not place any mmfload commands in the VMM configuration file $MPSHOME/
mpsN/etc/vmm.cfg. Be sure they are placed into the proper file (VMM-MMF
configuration file) as outlined above!
For additional information, see the Media Processing Server Series System
Reference Manual.
Assigning and Starting Application Programs

To run an application program, first assign it to a phone line (that is, bind the application) and
then start the application. In most circumstances, use the APPMAN (Application Management)
tool to assign and start applications. APPMAN allows setting up the applications and saving
the current configuration. If the system shuts down, the applications return to this configuration.
Applications can be assigned to MPS components. For information about components, see
System Configurations on page 20.

APPMAN automatically creates a default configuration for each application. The applications
run-time environment can be customized using the Application Configuration tool.
See the MPS Manager Reference Manual for information about creating and using custom
configurations.
1. Launch the Application Management Tool.
2. Select the Application. Either select an existing application (#1 and #2) from the
Tree Choose list or add a new application (#3) to the Applications window of the
APPMAN tool.
3. Select the Locations. Select individual or multiple nodes and components (#4) and
add them (#5) to the Locations window.
4. Assign and Start the Application. Select the application (#6), the locations (#7) and
the Assign and Start checkboxes (#8). Select the Apply button.

After the system assigns and starts the application, the phone line icons turn green.
See the MPS Manager Reference Manual for a complete description of MPS
Manager and the Application Management tool.
Applications can also be assigned and started from a MPS command shell. See the
Command Reference Manual, for a detailed command descriptions.
Start and Restart Line Order

Phone lines are assigned, started, and restarted, in the order listed under Locations in the
Assign/(Re)Start Lines window. This list can be reordered, if necessary, by using the up and
down arrows below the Locations window.
Reordering Selected Application Locations
1. Select one or more locations in the Locations window. <LEFT> click to select an
entry. <RIGHT> click the Select—None menu path to clear all selected entries
before selecting individual locations.
2. Use the up and down arrows to reorder selected listings. Items move one position
with each <LEFT> mouse click. Multiple selections move up or down together.
Repeat the previous steps for any items that have to be moved within the Locations
window.

Terminating and Unassigning Application Programs
Note:
Do not perform step #3 to modify the line start order for the current session only.
To define a default line start order for future system bootups, continue with step
#3.
3. Select the Reorder checkbox and click Apply. This applies the reorder changes for
future system bootups.

In most circumstances, use APPMAN to terminate and unassign applications. However,
applications can also be terminated from a Media Processing Server shell. See tappman in
the Command Reference Manual, for command description.
1. Launch the Application Management Tool.
2. Select the Locations. Select individual or multiple nodes and components (#1) and
add them (#2) to the Locations window.

3. Choose the Lines to Terminate. Select the locations for termination in the Locations
window (#3).
4. Terminate and Unassign. Select the Terminate and Unassign checkboxes (#4) and
click the Apply button.
Note:
By default, the Media Processing Server uses a soft termination. A soft
termination waits for callers to hang up before terminating each application.
See the MPS Manager Reference Manual for a complete description of MPS
Manager, the Application Management Tool, and Terminating/Unassigning Lines.
Deactivating MMF Files

When activated, MPS MMF files (both playback and record) take up space in Voice Data
Memory (VDM). Since this space is limited, applications should be deactivated when they are
no longer required. VDM status can be obtained from the VMM Cache Status Report, which
is displayed by entering the command vmm cachestatus either in an MPS shell or the VSH
Command Line.
Note:
The vmm repconfig command can be used to display configuration information for VDM (as
well as how much VDM is in the system) however, it does not indicate usage. The vmm

Deactivating MMF Files
cachestatus command is preferred because it shows how much VDM is actually in use (as
well as other useful information).
If an attempt is made to deactivate a file currently being accessed by one or more applications,
VMM does not deactivate the file immediately. Instead, VMM places the file in a deactivation
queue. If any application tries to make any new references to an MMF file in the deactivation
queue, the reference fails and VMM generates an alarm. When all prior references to elements
in the file have completed, VMM deactivates the file.
While outstanding references to an MMF file are being satisfied, it is possible to deactivate
another MMF file.
Deactivating Multimedia Format Files using the MMF Configurator Tool
1. Launch the MPS Control Center.
2. Select the Node and Component Double <LEFT> click MMF Configuration in the
MPS Control Center.
In the Component Selector window, select the Node: and the Component:
containing the MMF files to Unload. Select OK to start the MMF Configurator Tool.
3. Select the MMF files to Unload. Select the files and <LEFT> click Unload MMF(s). To
prevent them from loading on startup, clear the box Load At Start.

Deactivating Multimedia Format Files using the Command Line

1. Open a Media Processing Server shell on the Media Processing Server that
contains the unneeded MMF file, see Command Control on page 46.
2. Enter the vmm mmfunload command.
• To unload an MMF file that was available to all applications in the system-
wide hash table, use the syntax vmm mmfunload <mmfname>,system (It is
not necessary to specify the "system" parameter as this is the default.)
• To unload the MMF file from a particular application (application-specific hash
table), use the syntax vmm mmfunload <mmfname>,<appname>
• To unload all MMF files available system wide or to a specific application, use
the applicable prior command and substitute the option all for <mmfname>
3. Move the file out of $MEDIAFILEHOME or it will be activated next time the system is
(re)started. Also, remove its name from the vmm-mmf.cfg file (if this file is used).
Note:
When unloading an MMF, if only the MMF name is specified, the MMF will be
unloaded from the system hash table by default.
To determine if an MMF has been deployed system-wide or for a particular
application, issue the vmm mmfstatus command in an MPS VSH command line.
The last two columns indicate system (Sys) or application (App) usage.
vsh.11@tms1000 {1} -> vmm mmfstatus

===========================================================
VMM: MMF Status Report
===========================================================
System-Wide Default MMF: None
System-Wide Record MMF: /mmf/peri/cmrdata
SCSI EAP EAPs Space

Updating or Replacing Playback MMF Files
MMF Path PERMS ID Capacity Loaded Used HWM LWM Sys App
/mmf/peri/dtmf
RDWR 3 48 23 58% 90% 70% Y 0
/mmf/peri/cmrdata
RDWR 3 2048 0 99% 90% 70% N 3
A "Y" under Sys denotes that the MMF is available system wide. An "N" indicates it is not
available system wide. A number under App indicates the number of applications using that
MMF. A zero (0) indicates it has not been loaded on an application-specific basis.
If the MMF file is available for several applications or system wide, it must be deactivated for
each application or the entire system. That is, the file has to be deactivated for each mmfload,
mmfrec or mmfdefault command issued.
Use the vmm appremove <appname> command to remove an application from the application
hash table (this negates the effect of the vmm appinit command). Any open application-
specific MMF files are deactivated when the application is removed. This command cannot be
used in the vmm.cfg file.
See the MPS System Reference Manual for a detailed description of hash tables. The MPS
Command Reference Manual contains details about using the VSH Command Line.
Updating or Replacing Playback MMF Files

During system initialization, MPS configuration files set up the MMF files used by applications
to produce speech. MMF files have to be updated in the following circumstances:
• a new vocabulary file on disk becomes available.
• a new vocabulary file is created with MPS Studio.
• one or more elements in the vocabulary have been updated (for example, a message of
the day or weather update application).
The entire MMF file can be updated (see Updating/Replacing a Playback MMF Playback
File on page 90) or individual elements updated without interrupting service ( see Updating
Elements in an Active Playback MMF File on page 92). Also, any or all identical MMFs across
a LAN or WAN can be updated using the Zero Administration for Prompts (ZAP) utility (Solaris
only), see Synchronizing MMF Files Across Nodes (ZAP Utility) on page 94. This automated
synchronization facility provides a means of administering updates to and maintaining
consistency among all active instances of a particular MMF residing on different nodes of a
network.

Updating/Replacing a Playback MMF Playback File

There are three methods for replacing MMF elements and files:
• The preferred online method ensures continuous customer service. This is used to
replace speech elements in the MMF. For additional information, see Replacing a
Playback Multimedia File (Online) (Preferred) on page 90.
• The alternative online method also ensures continuous customer service, but involves
changing the VMM-MMF configuration file (if used). The system may page from disk
(access data from the hard drive) some elements that were previously in Voice Data
Memory. For additional information, see Replacing a Playback Multimedia File (Online) on
page 91.
• The offline method can cause applications to temporarily construct fragmented phrases
(that is, for a brief time the application will not speak prompts located in the file being
updated), but does not involve any changes to the VMM-MMF configuration files. For
additional information, see Replacing a Playback Multimedia File (Offline) on page 92.
Replacing a Playback Multimedia File (Online) (Preferred)
This procedure updates existing speech elements in an MMF. Any elements that exist in the
original MMF, but are not in the new MMF, will still be present after the update.
1. Open a shell on the MPS running the application. For additional information, see
Command Control on page 46.
2. Copy the new MMF file to the Media Processing Server. The new MMF file must
have a different name than the one being replaced.
• If the file is on a disk, use the cp command to copy both the .mmi and the .mmd
files to the MMF files directory.
• If the file was created in MPS Studio, make sure it is in the MMF files directory.
3. Create a Vgen incremental file which represents the MMF file.
• Make sure there is enough disk space in the Multimedia file directory.
• Use the syntax mmf2def1 -v<vgen_inc_name> <mmf_name> where
<mmf_name> is the name of the MMF file copied in step 2. This generates the
file <vgen_inc_name>.def1.
• If no Vgen incremental filename is specified, one is created with the same
filename and the .def1 extension.
4. Update the existing MMF (vocabulary) file with the temporary Vgen incremental file
created in step 3.
From the Media Processing Server shell, use the syntax vmm mmfupdate
<mmf_name>,<vgen_inc_name.def1> where mmf_name is the active MMF file
and vgen_inc_name.def1 is the Vgen incremental file created in step 3.

Updating/Replacing a Playback MMF Playback File
Replacing a Playback Multimedia File (Online)

1. Open a Media Processing Server shell on the Media Processing Server running the
application. For additional information, see Command Control on page 46.
2. Copy the new MMF file into the $MEDIAFILEHOME directory on the Media
Processing Server. The new MMF file must have a different name than the one
being replaced.
3. Activate the new MMF file.
• To add the new MMF file to an application specific hash table, use the syntax
vmm mmfload <newvocab>,<appname>
• To allow all applications on the Media Processing Server to use the MMF file,
use the syntax vmm mmfload <newvocab>,system
4. Deactivate the original MMF file.
• To unload an MMF file that was available to all applications on the system
(system wide hash table), use the syntax vmm mmfunload
<originalvocab>,system
• To unload the MMF file from a particular application (application specific hash
table), use the syntax vmm mmfunload <originalvocab>,<appname>
If the MMF file is available for several applications or system wide, it must be
deactivated for each application or the entire system. That is, the file has to be
deactivated for each mmfload, mmfrec or mmfdefault command issued.
Use the VSH command line to issue the vmm mmfload and mmfunload commands.
For more information see Activating Playback MMF Files on page 79 and
Deactivating MMF Files on page 86 respectively.
5. Move the original file out of the $MEDIAFILEHOME directory.
6. If the VMM-MMF configuration file is being used, then edit the file to reflect the new
vocabulary name. Use a text editor to modify and save $MPSHOME/mpsN/etc/
vmm-mmf.cfg. Replace the line containing the original MMF file with a line for the
new MMF file.
If the MMF files have elements with the same name, the applications continue to
access elements without corrupting concatenated phrases. However if the voice
data memory is limited, activating <newvocab> before deactivating <originalvocab>
may cause the system to page some elements from disk. This can happen even
when the original was entirely in voice data memory.

Replacing a Playback Multimedia File (Offline)

1. Open a Media Processing Server shell on the Media Processing Server running the
application. For additional information, see Command Control on page 46.
2. Deactivate the original MMF file.
• To unload an MMF file that was available to all applications on the system
(system wide hash table), use the syntax vmm mmfunload
<originalvocab>,system
• To unload the MMF file from a particular application (application specific hash
table), use the syntax vmm mmfunload <originalvocab>,<appname>
If the MMF file is available for several applications or system wide, it must be
deactivated for each application or the entire system. That is, the file has to be
deactivated for each mmfload, mmfrec or mmfdefault command issued.
3. Copy the new MMF file over the original MMF file. Use the same name as the original
MMF file.
4. Activate the new MMF file (now named <originalvocab>).
• To add the new MMF file to an application specific hash table, use the syntax
vmm mmfload <originalvocab>,<appname>
• To allow all the applications on the Media Processing Server to use the MMF
file, use the syntax vmm mmfload <originalvocab>,system
With this method, applications that access the vocabulary generate alarms and may
speak corrupted phrases until the new vocabulary is activated.
Note:
The original MMF must be deactivated before the new file is activated. This frees
space in voice data memory and allows the system to use it for the new MMF.
Use the VSH command line to issue the vmm mmfload and mmfunload commands.
For more information, see Activating Playback MMF Files on page 79 and
Deactivating MMF Files on page 86 respectively.
Updating Elements in an Active Playback MMF File

Use MPS Studio to add or modify specific elements in a vocabulary file without interrupting
customer service.

Updating Elements in an Active Playback MMF File
Use this procedure to:

• update the audio data of the elements online, and
• modify the elements data within the MMF file
Note:
Activities such as digitizing elements are processing-intensive; therefore, it is suggested that
such procedures be performed during times of low system activity.
The ZAP utility provides an automated means of updating and rectifying multiple active copies
of identical MMF files across a network without putting an undue burden on network facilities,
see ZAP and MMF files on the MPS on page 95.
Updating Elements in a Vocabulary
1. Launch MPS Studio. Start MPS Studio from the command line or from the Start
menu on a Windows platform.
2. Open the playback MMF file to be modified. Since this vocabulary is active, the file is
Read-only.
3. Select the elements to be modified.
4. Export the elements to a temporary file (for the purposes of this example, name it
temp1). Specify MMF (MPS Studio) for the file format.
5. Unload the current (active) file from MPS Studio.
6. Open the previously created MMF file (temp1 created in step 4.)
7. Modify the elements. New elements can be added or previous recordings updated
as needed.
8. Rename and save the file (for example, temp2).
9. Export all of the elements that have been modified to a temporary file. Specify VGEN
Incremental for the file format and the appropriate encoding for the type of telephone
interface (for a digital system, select u-law encoding: for an analog system, select
adpcm encoding). The name chosen for step 4. (temp1) can be used or choose a
new name (recommended) (for example, temp3) and append the VGEN
Incremental filename extension (.def1, resulting in temp3.def1 for example).
10. Exit from or iconify MPS Studio.
11. Enter the following command from the Media Processing Server shell:
vmm mmfupdate <MMF_filename>,<export_file.def1>
where:
• <MMF_filename> specifies the base name of the loaded (active) MMF file to
be updated, and

• <export_file.def1> specifies the name of the file that has the elements to be
incorporated into <MMF_filename>. This was the last file exported from MPS
Studio (in step 9.). The path name to the file has to be included if it is not in
the present working directory. In addition, the VGEN Incremental filename
extension (.def1) is required.
The process is now complete. All subsequent use of the file by applications
will access the updated recordings.
For an offline file, simply load it into MPS Studio and process it normally.
For details about using MPS Studio, see the MPS Studio User Guide.
Synchronizing MMF Files Across Nodes (ZAP Utility)

In some configurations, applications across multiple nodes use the same MMF files. The Zero
Administration for Prompts (ZAP) utility automates the process of administering updates to and
maintaining consistency between all activated instances of an MMF file across the network. It
determines if a set of files contains identical elements and provides the capability to
synchronize the files. ZAP can modify MMF files on all nodes list in a vpshosts file or in an
alternate file; individual nodes or Media Processing Servers; groups of Media Processing
Servers; or specific elements within an MMF file.
ZAP also generates reports illustrating the differences between the source and target MMF
files, and the results of modifications made to the target MMF files. By default these log files
are created whenever ZAP is used, and are never overwritten. While administration of these
files is left to the discretion of the user, this can eventually lead to disk saturation if files are not
off-loaded or deleted. To reduce this need for manual intervention, use the -C option to combine
these files into a corresponding consolidated log file.
A synchronization distribution log file is generated by the node originating the synchronization
request. An update results log file is generated by remote (target) nodes. Each of these nodes
also contains a synchronization status log file. These files are stored in the $MPSHOME/
common/log directory of the reference node. The synchronization distribution log file is named
in the format zap.distribute.refnode.mmf_name.selected_elements.MMDDCCYY, where
refnode is the name of the node originating the synchronization request, mmf_name indicates
the base name of the reference MMF file, selected_elements is the name or EAP numbers
that have been selected for updates, and MMDDCCYY indicates the date the file was
generated. This log file contains information regarding the distribution and completion status
for all MMF file synchronization requests, information on which nodes were not notified of the
updates (and the reason thereof), and errors encountered during the synchronization process.
Note:
If all elements within an MMF have been selected for updating, the selected_elements
portion of the log file name appears as ALL_ELEMENTS.

The update results log file is named in the format

zap.results.target_node.mps#.mmf_name.selected_elements, where target_node is the
name of the remote node where the synchronization has occurred, mps# is the number of the
Media Processing Server on which the target MMF file is located, mmf_name indicates the
base name of the reference MMF file, and selected_elements is the name or EAP numbers
that have been selected for updates. The file contains information on modifications made to
the MMF file, as well as errors encountered due to inconsistencies between the reference and
target MMFs. If an MMF contains multiple elements with duplicate names, ZAP uses only the
first duplicate element from the source MMF file to update the target MMF file; therefore, only
this first element needs to be updated and maintained. The element which appears first in the
target MMF file (that is, with the lowest EAP number) is updated; however, none of the
remaining duplicated elements is. The update results log file indicates that multiple elements
with the same encoding are present in the MMF file.
The synchronization status log file is named in the format
zap.status.refnode.mmf_name.selected_elements.MMDDCCYY, where refnode is the name
of the reference node where synchronization was initiated, mmf_name indicates the base
name of the reference MMF file, selected_elements is the name or EAP numbers that have
been selected for updates, and MMDDCCYY indicates the date the file was generated. The
state of the synchronization process for each target node is contained in this file.
Upon completion of the zap process, all synchronized MMF files contain identical elements
and data, even though the elements may be stored at different positions within the file. This
utility presently updates only active instances of the MMF file identified by the reference file.
ZAP and MMF files on the MPS
In an MPS system, when ZAP updates any MMF file, it is required that there exists a copy of
that MMF file for each component in the system. The directory should be created for each of
the MPS components on the MMF partition and all the files, that ZAP operates on, be duplicated
under these directories. Make sure that the /opt/vps/mpsN/etc/vmm-mmf.cfg files on the
system are updated to reflect the change in the file locations.
For example:
On an MPS 500 (with components mps1 and mps2), the MMF "myPrompts" needs to be
updated periodically by ZAP. Hence, the following directories must be created:
/mmf/mps1 /mmf/mps2
The MMF "myPrompts" must be copied into each of these directories. The files $MPSHOME/
mpsN/etc/vmm-mmf.cfg must have the following line added: mmfload /mmf/mpsN/myPrompts
Note:
Ensure that any previous references to the MMF in vmm-mmf.cfg file are removed
ZAP by Proxy (Using Groups)
By default, ZAP connects from a local (reference) node to all remote (target) nodes. Where
multiple LANs exist, which in turn contain multiple nodes that need to be updated by ZAP,
network traffic can be further reduced and performance improved by having ZAP function on
a proxy basis. In this case ZAP updates one Media Processing Server for a particular node

in a group (LAN): each of the other Media Processing Servers on this node, and one Media
Processing Server on each of the other nodes in the group, are updated remotely from this
"locally updated" (proxy) Media Processing Server. This functionality requires the presence
of a user-defined zap.networks.cfg file.
The zap.networks.cfg file must contain every node in the network since this file is used to
determine the topography of the network. Typically, each LAN is defined as a group. In all
cases, the following syntax rules must be followed:
• Groups are defined by using the term [GROUP] on its own line. All nodes that follow will be
construed as belonging to that group until ZAP encounters another [GROUP] tag or the
end of the file.
• Only one node can be listed per line, and each node can belong to only one group.
• There can be no empty groups, and no node may appear ahead of the first group.
• A pound sign (#) precedes commented data. This symbol must appear at the beginning
of a line (comments entire line) or have at least one space before it.
• Blank lines are ignored.
The zap.networks.cfg file must be placed into the $MPSHOME/common/etc directory. By
default, only the Media Processing Servers listed in the vpshosts file on the reference node
are addressed. If any node in any group contains Media Processing Servers that are not in
this file, those components are not updated.
Note:
If all target nodes have not been updated to use the latest ZAP release or have security in
place that does not allow remote ZAP sessions to complete correctly, the -L option must be
used to ensure compatibility. This command line option forces all applicable components on
all nodes to be updated directly from the local (reference) node, and prevents any remote
ZAP processes from occurring, thereby overriding any zap.network.cfg files that have been
defined
Updating a Specific Element
By default ZAP compares each target MMF with the designated MMF on the reference node
and transmits to each one those elements which are different. In instances where the element
that has changed is known, ZAP can be directed to update only that element and ignore any
other comparison of the file. This can increase significantly to the speed at which ZAP
functions.
The -e option is used to update a specific element. If specifying an element name that contains
spaces, it must be enclosed in quotes. To combine multiple element updates in one command,
define a plain text file list of elements, with one element per line and no quotes, and use it with
the -E option instead. However, never use the -e and -E options together.
See the Media Processing Server Series System Reference Manual for details on as well as
advanced uses of ZAP.

Zap a Multimedia File

1. Designate a master MMF file as a reference file. This file can exist on any node in
the network.
2. Make additions, deletions, and modifications to this designated file only, preferably
using MPS Studio, see Updating/Replacing a Playback MMF Playback File on
page 90, Updating Elements in an Active Playback MMF File on page 92, and the
MPS Studio User Guide.
Note:
All changes affecting the particular MMF file must be made to the designated
reference file in order for the ZAP utility to be effective. ZAP also requires the /
etc/vpsrc.sh file on every node that will be synchronized. This file is usually
present as part of the standard Media Processing Server Series installation.
3. To ZAP all nodes in the $MPSHOME/common/etc/vpshosts file on the host node,
use the command line syntax zap <mmf_name> from the command line of the host
node on which the reference file resides, and where <mmf_name> indicates the
path and name of the reference file noted in step 1.
To ZAP all Media Processing Servers in the $MPSHOME/common/etc/vpshosts file
of a specific node, use the command line syntax zap -n <node_name>
<mmf_name> from the command line of the host node on which the reference file
resides, and where <node_name> indicates the target node.
To ZAP a specific Media Processing Server, use the command line syntax zap -v
<mps#> <mmf_name> from the command line of the host node on which the
reference file resides, and where <mps#> indicates the desired Media Processing
Server.
To ZAP all Media Processing Servers in an alternate vpshosts file, use the command
line syntax zap -f <filename> <mmf_name> from the command line of the host node
on which the reference file resides, and where <filename> indicates the name (if
located in the present working directory) or path and name of the alternate file.
Note:
The alternate file must be in the same format of the actual vpshosts file.
To ZAP MMF files using a pre-existing MAC file (file created from master MMF and
used as a reference throughout synchronization), use the command line syntax zap
-m <filename> from the command line of the host node on which the reference file
resides, and where <filename> indicates the name or path and name of the MAC
file.
The option/argument pairs above and that follow may be used in combination in a
single command. They may also be used in conjunction with the following:

Option Description
The delay interval (in minutes) for each retry
-d <delay> attempt. The minimum allowable value is 10
minutes (default is 30)
Number of times to again attempt a
-r <retries> synchronization if a remote node fails to
respond or MAC file cannot be transmitted
(default is 3)
Specifies the date and time that the sync should
-t <timespec> be executed. The time is specified as one, two,
Examples: or four digit numbers (where one and two digit
-t 11pm -t 5am numbers are hours and four digit numbers are
Wednesday -t 11:59pm hour and minute, separated by a colon). The
march11 AM/PM identifier can be appended to the time,
otherwise 24 hour time is assumed (that is, 6:00
is 6 AM, 18:00 is 6 PM). The date is optional and
is specified as either the month name and day
number or the day of the week. The current date
is assumed if no date is specified
-A Generate alarms upon completion (whether
successfully or not) of synchronization of each
Media Processing Server.
Zap Multimedia Files on a Proxy Basis

the network.
3. Define a zap.networks.cfg file, see ZAP by Proxy (Using Groups) on page 95.
4. Issue the zap <mmf_name> command from the command line of the host node on
which the reference file resides, and where <mmf_name> indicates the path and
name of the reference file noted in step 1.
To ZAP all nodes in a specific group, use the command line syntax zap -G
<group_number> <mmf_name> from the command line of the host node on which
the reference file resides, and where <group_number> indicates the group as
defined in the zap.networks.cfg file and identified in ascending sequential order
starting at 1.
Zap a Specific Element
the network.

Caller Message Recording
3. Determine the element name or number that needs to be updated.
4. Issue the zap -e {@ <EAP_number> | <"Element Name">} <mmf_name> command
from the command line of the host node on which the reference file resides, and
where <mmf_name> indicates the path and name of the reference file noted in step
1. If specifying an element name that contains spaces, it must be enclosed in
quotes.
To ZAP multiple specific elements in one command, issue zap -E <filename>
<mmf_name> from the command line of the host node on which the reference file
resides, and where <filename> indicates the name (if located in the present working
directory) or path and name of the plain text element list file.
Note:
Elements can be listed by EAP number preceded by the @ sign or by name. Do
not use quotes, even if there is a space in the name. Only one element must be
listed per line.
Caution:
Do not use the upper case -E option with the lower case -e option: these two must
not be combined.
Caller Message Recording

Caller Message Recording (CMR) allows an application to record messages from the caller
and save them in an MMF file. For details about the CMR feature and MMF files, see the Media
Processing Server Series System Reference Manual.
Before an application can use CMR, an MMF file has to be created (see Creating a File for
Caller Message Recording on page 99) and activated (see Activating Record MMF Files on
page 101).
Note:
Caller Message Recording (CMR) is an Avaya licensed feature and requires the appropriate
licensing permissions prior to its use!
Creating a File for Caller Message Recording

Use a Media Processing Server shell to create an MMF file to use for Caller Message
Recording.

Creating a Multimedia Format File for CMR

1. Open a Media Processing Server shell on the Media Processing Server that will
hold the MMF file. For additional information, see Command Control on page 46.
2. Use the syntax mkmf <mmf_file> where <mmf_file> is a descriptive name for the
MMF file.
This command creates an expandable MMF file with the system default settings
(2048 elements, 2048 data blocks). Alternatively...
3. Use MPS Studio to create the MMF file. To create a new MMF file:
a. Start MPS Studio.
b. Select File—New. This opens the New File window.
c. Use the New file window to navigate to the directory where the new file
is to be created.
d. Add the name of the new file to the path in the Selection field. The .mmi
extension is not needed.
e. Click the OK button. The File Definition window appears.
f. Optionally, specify different parameter values for the # of Elements and
Data Capacity fields if the defaults are inappropriate.
g. Click the Apply button to proceed with creating the file. At this point, the
system physically creates the new MMF file on the system disk in the
Activating Record MMF Files
specified directory. The file is automatically opened for immediate use.

Elements may now be added and recorded.
See the Media Processing Server Series Command Reference Manual, for details about mkmf.
Consult the Media Processing Server Series System Reference Manual for details about CMR
and MMF files. Refer to the MPS Studio User Guide for information on developing and
manipulating MMF files in a graphical environment.
Activating Record MMF Files

Use a Media Processing Server shell to activate the record MMF file for a specific application or
for all applications on the system.
Activating Record Multimedia Files
1. Open a Media Processing Server shell on the Media Processing Server that holds
the MMF file. For additional information, see Command Control on page 46.
2. Activate the record MMF file with the vmm mmfrec command.
• To allow a specific application to record into an MMF file, use the syntax vmm
mmfrec <mmf_file>,<app_name> where <mmf_file> is an empty MMF file and
<app_name> is the name of the application that will record into <mmf_file>.
The file should be placed in the appropriate subdirectory under
$MEDIAFILEHOME. (Only a single MMF file should exist in each record
directory.)
• To allow all applications in the same MPS component on the Media Processing
Server to use an MMF file for recording, use the syntax vmm mmfrec
<mmf_file>[,system] where <mmf_file> is an empty MMF file. (It is not
necessary to specify the "system" parameter as this is the default.) The file
should be placed in the $MEDIAFILEHOME/mpsN/system/record directory.
The vmm mmfrec command activates the specified MMF file automatically. A
separate mmfload command is not needed.
MMF files can take up a considerable amount of disk space. If it is decided to use
a different MMF file for recording, deactivate the unused MMF file. For more
information see Deactivating MMF Files on page 86. See the Media Processing
Server Series System Reference Manual for details about CMR and MMF files.
Chapter 7: Backing Up and Restoring Files
1. Directory and File Manipulation

2. Backup Devices and Options
3. Guidelines for Backup
4. Backup/Restore Methods
5. Backing Up and Restoring Multimedia Elements
6. Backing Up and Maintaining a Mirrored System Drive
Backing up and Restoring Files

System and vocabulary files have to be backed up on a regular basis to ensure uninterrupted
service. This section details backup options and procedures on Solaris systems and briefly
discusses the Avaya Media Processing Server Series directory structure. (Refer to a standard
Solaris guide for more details on Solaris/UNIX topics.) This chapter also discusses the backup
and maintenance of systems which are equipped with an optional mirroring configuration.
Directory and File Manipulation

The files on the Media Processing Server Series system are organized into tree-structured
directories and subdirectories like the ones on many personal and mini computers. Each
directory generally contains files that are related to a common function, though the number of
files in a directory varies. The base directory is the root directory.
For the layout of the Media Processing Server directory structure, see MPS Directory
Structure on page 137.
Note:
Any Solaris commands entered in a Media Processing Server shell are issued to the local
Solaris node regardless of the current component. For example, if the current component
is vas.1 and grouse is the name of the current node, but the VSH Command Line was
launched on node is9509, ls lists the files in the directory on is9509, not on grouse.
Backing Up and Restoring Files
Working with Directories

Enter commands to move around the directory tree and interact with the Media Processing
Server. Think of the logical location on the directory tree as being "in" that directory. This
directory is the present working directory(pwd), also referred to as the current working directory.
Enter pwd at a command line to display the full name of the present directory. The full name
of the directory is the path name. It includes the directory names leading from the root to the
present working directory (that is, the path).
The Media Processing Server Series system uses a slash character (/) to separate directory
names. The root directory is always indicated as /.
When a leading slash character (/) is used to specify a directory, it implies the full path name.
When in the root directory, the leading slash can be omitted in the path name when identifying a
directory one level lower down in the tree.
Move between directories with a change directory (cd) command. Use the syntax cd
<pathname> to change from the present working directory to the specified directory.
• The pathname may be either a full pathname from the root (starts with a leading /) or a
relative name to directories further down on the directory tree (starts without a leading /).
• Use the command cd / to move to the root directory from any other directory.
• To specify the parent directory (that is, the directory that contains the present working
directory), use the.. indicator. For example, to move up to the parent directory, use the
command cd...
• If a pathname is not specified, the system defaults to the present working directory.
• Use the tilde (~) to return to the home directory by typing in cd ~ and pressing <RETURN>.
To determine the value of the home directory, enter echo $HOME at the command line.
The following illustrates these commands. If viewing this manual online, click an explanation
below to find out more about the corresponding command.
File Listing
File Listing
Use the list command (ls) to display a list of files in a directory. Modify the output of ls by adding
switches. Common ls commands are:
command meaning
ls lists all the files in the working directory,
except hidden files
ls -l lists all the files in the directory with their size,
the time they were last modified, and their file
permissions
ls -a lists all the files in the working directory,
including hidden files
See the illustration on page 99 for examples of these commands.

If a pathname is specified in the ls command, the system lists only the files in that directory. In
addition, the switches can be combined (that is, ls -al).
File Removal
Use the remove command (rm) to remove an unnecessary file. Use the syntax rm -i <filename>.
Caution:
If files are removed, they cannot be recovered unless there is a backup copy.
Other commands can be used to remove (empty) directories. However, all the directories on
the Media Processing Server are important to the system.
Caution:
Do not remove any directories without consulting the local Media Processing Server Series
support staff and application developers. Never remove any system-level directories unless
instructed to do so during system upgrades.
To remove a directory, use the command rmdir -i <directory_name>. To remove a directory
and all its files and subdirectories, use the command rm -ir <directory_name>.
Caution:
The -i switch shown above causes the system to provide a warning prompt before removal of
any directories or files. It is important to use this switch when using the rm and rmdir
commands; otherwise, the result may be the removal of such files without prompting.
For more information about these options and possible scenarios, refer to the Solaris
documentation of these commands.
Backup Devices and Options

To perform routine backups, the Media Processing Server is delivered with a 4mm Digital Audio
Tape (DAT) drive and an internal hard drive.
Each device has a unique logical name:
Device Name Capacity Used For

4mm DAT drive 20 GB (150 meters) - weekly backup
/dev/rmt/0 DDS4 (systems with a of all system and
SUN Blade or SUN Fire application files
application processor)
internal drive varies with varies with system daily or weekly
system configuration backup of all
configuration
Guidelines for Backup
Device Name Capacity Used For

system and
application files
Note:
Tapes have a write-protect feature, which must be disabled for the media to store additional
data. For details, see the instructions included with the media.
Guidelines for Backup

At a minimum, back up the system files weekly to ensure uninterrupted service from the Media
Processing Server. If any extensive changes are made in the interim, back that file system up
immediately afterward. Perform backups when the system is relatively inactive (off-peak). For
ease of use and accountability, Avaya suggests backing up each slice (file system) on its own
tape.
Note:
In the following passages, the term vps is used in the discussions of path names,
environment variables, and file fields. This terminology is equivalent to Avaya Media
Processing Server nomenclature and directly relevant to MPS systems.
Table 10: Command Summary
To back up... to... change directory use...

to...
system files tape tar cvf /dev/rmt/0 /opt
/opt
ufsdump 0cf /dev/rmt/
0 /opt
1
Multimedia files tape tar cvf /dev/rmt/0 /

/<mmfdirectory>
<mmfdirectory> ufsdump
0cf /dev/rmt/0
<mmfdirectory>
1
Multimedia VGEN MPS Studio. For additional

(vocabulary) incrementa information, see Backing Up and
elements l format Restoring Multimedia Elements on
page 124.
user files tape tar cvf /dev/rmt/0 /
/opt/home
opt/home ufsdump 0cf /
dev/rmt/0 /opt/home
To back up... to... change directory use...

to...
1
application files 2 tape tar cvf /dev/rmt/0 /

/opt/vps/mpsN/
apps opt/vps/mpsN/apps
or
ufsdump 0cf /dev/rmt/
0 /opt/vps/mpsN/apps1
operating system tape ufsdump 0cf /dev/rmt/0
3 /
<file_sys_name>
1
mirrored system tape mirrorbu

drive4 N/A
1. The examples shown are for backup on a local machine. For information about using
ufsdump remotely, see Backing up with ufsdump on page 117..
2. Systems running database and CMR applications require more frequent backups of
these files. CMR and associated database files must be backed up together while the
applications that use them are NOT running.
3. The entire operating system might not fit on one tape if using the tar command, see
Backing Up with tar on page 115. If there is a potential space problem, use the ufsdump
command, which can span multiple volumes of media Backing up with ufsdump on
page 117. To determine if a directory will fit on a single tape, see Determining Directory
Size on page 108.
4. Refer to the MPS Disk Mirroring Configuration and Recovery manual for more
information.
Determining Directory Size

To determine if a backup tape has enough space to hold a specific directory, use the du
command to display the directory's size. For example, to determine the size of the system files
directory /opt, execute the following command:
du -ks /opt
The -k option displays the size of the directory in kilobytes; the -s option suppresses the output
from listing all individual files contained in the directory.
To determine the amount of disk space allocated to a particular file system, use the df
command. The resulting output provides the total amount of space in kilobytes, the number of
kilobytes used and available, and the amount of space used as a percentage of total available
space.
Backup Tips
Backup Tips
• Keep a supply of sequenced and labeled tapes on hand.
• Store backup media in a safe place. This media needs to be obtainable by service
personnel if restoration of data is required.
• Write the date and names of files backed up on the label of each tape.
• Keep a log of backups, including dates and file names.
• Handle backup media carefully. Follow all instructions included with the media.
• Enable write protection on the tapes or disks after the backup. Follow the instructions
included with the media.
Backup/Restore Methods
The following are the methods for the backup and restoration of files. (See Guidelines for
Backup on page 107.)
Method Used For For Information

disk to disk The clone.pl script to backup data from one Disk to Disk Backup
disk to another, on non-mirrored systems Procedure on page 110.
where no tape drive is present, and a backup
disk is available.
tar Transferring files to a tape or an internal Backing Up with tar on
drive. Use tar to archive files to a single 'tar' page 115.
file. The tar command does not perform any
file compression or span multiple media.
ufsdump Transferring files to a tape, internal drive or Backing up with
ufsrestore disk, or diskette. Whereas the ufsdump ufsdump on page 117.
command does not perform file
compression, it does detect end of media
and span multiple copies. This is useful for
very large file backups.
cp (copy) Backing up individual files or file groups to Backing Up with cp
other internal drives or directories. (Copy) on page 123.
MPS Studio Backing up select elements in Multimedia Backing Up and
files. Restoring Multimedia
Elements on page 124.
Method Used For For Information

mirrorbu Backup script to create a full backup of the Refer to the MPS Disk
mirrored system drive. Mirroring Configuration
and Recovery manual for
more information.
Disk to Disk Backup Procedure

The following procedures describe how to use the clone.pl script to backup data from one disk
to another, on non-mirrored systems where no tape drive is present, and a backup disk is
available. All backups should be conducted when the system is as quiet as possible. It is best to
run backups in single-use mode, if possible.
Preparation for Solaris Backup

1. Reconfigure boot to ensure all device files have been created for all connected
disks:
Note:
This step is not needed on every backup, it is only required when new devices
are added to ensure the system sees them.
# touch /reconfigure
# reboot
or
at the ok prompt: boot -r
2. Run backup script with -h option to get information on the drives in the system and all
the command options. The following is the output of running clone.pl -h on a typical
system.
# perl clone.pl -h
Sample output
Usage:
-L # Set DEBUG Logging Level (1-4):
1-INFO 2-WARN 3-ERROR 4-INFO&Console.
Default level: ERROR
-D #Set DAT Level (1-2):
1-detail 2-high level.
Default level: detail
Preparation for Solaris Backup
-p 'PARTITIONS' Set partitions to be

backed up or recovered
Delimiters: space ',' ';' and '.'
Each partition specified from root,
i.e. begun w. '/'
Enclose [PARTITIONS] within single
quotes, not the back quote.
-d driveSet drive name for backup or recovery
-s driveSet drive name for system when booted
off CD
-b on/offSet backup on/off
-r on/offSet recovery on/off
Mandatory: recovery ON works only
backup set OFF
Restore to root or /usr requires all
applications to be down
-v #Get the version of this script
and perhaps a reboot.
-f fullSet full disk to be backed up
Mandatory: '-f full' needed for entire
disk backup
-hPrint this usage message
3. Select a drive as the target backup drive.

Find one from the list, in the output of perl clone.pl -h
Example:
System drives information:

System drive:c0t3d0. The mount slices:c0t3d0s0 c0t3d0s6 c0t3d0s4 c0t3d0s7
c0t3d0s5.
Corresponding partitions:/ /usr /var /mmf /opt.
The swap slice:c0t3d0s1.
All the potential backup drive(s):c0t0d0 c0t1d0
c0t2d0 c1t0d0 c1t3d0.
4. To perform a ufsdump and ufsrestore backup, perform step 1 under Execution on

page 112.
5. For tar backups, format the target backup drive.
Make sure the backup disk is partitioned equally or bigger than the system disk, use
the format command. Partitioning the backup drive is a 'one time' event, but
whenever performing the tar backup the backup slices should be cleared with the
newfs command below. For each formatted slice, except the swap slice, execute
newfs to create a mountable ufs.
Example:
# newfs /dev/rdsk/c0t0d0s0
Do not execute newfs on the backup swap slice, for example: c0t0d0s1 or the 's2'
slice c0t0d0s2.
Execution
There are various command options when running clone.pl to backup data from disk to disk.
To get help on the clone.pl script refer to step 2 on page 110 under Preparation for Solaris
Backup on page 110.
1. Backup Entire Disk – The '-f' option determines which method to use, either ufsdump
and ufsrestore for drives of the same geometry or tar for drives with different
geometry.
Performing an entire disk backup on a system with only one target drive available.
#perl clone.pl -f full
Performing an entire disk backup on a system with more than two drives. There are
two ways to specify the backup drive. Either specify the target drive in the command
line or configure it in the clone.cfg file. Below is a sample command line for the first
case.
#perl clone.pl -f full -d c0t1d0
To configure clone.pl using the clone.cfg file, see Configure on page 113 below.
2. Backup Partitions using tar. For any backup not using ufsdump and ufsrestore,
complete step 5 on page 111 under Preparation for Solaris Backup on page 110
for formatting and creating a file system on partitions.
Performing a partition backup: the command below shows how to backup partitions
(using tar) /var /usr on backup drive:c0t0d0 with all the debug options on.
#perl clone.pl -p ' /var /usr ' -L 4 -d c0t0d
The command below will backup the entire disk using tar. It is an entire disk backup
because all partitions on the system drive are chosen. When backing up the root
partition (/) the boot block is automatically installed. This method of tar backup is
the safest for backing up a system still running in multiuser mode (system up), this is
due to tar's ability to copy "open files".
Note:
It best to perform this backup process during a "quiet" time as to not impact
system performance.
#perl clone.pl -p '/ /var /opt /usr /mmf' -L 4 -d c0t0d
3. Recover Partitions using tar.
Recover partitions /var and /usr.
#perl clone.pl -b off -r on -p '/var /usr' -L 4 -d c0t0d0
Configure
4. Recover Files
Recovery of files using the clone.pl script is the same as step 3 on page 112 under
Execution, this restores the entire partition to recover the needed files. Otherwise,
to obtain individual files mount the backup partition with the files you wish to recover
and copy them back to the original location manually.
5. Recover Partitions/Files/Root when booted off CD
If the system drive is corrupted, boot the system off the CD and do the recovery. If
clone.cfg is saved, copy clone.cfg to /tmp. Otherwise, manually mount the slices on
the system drive before executing clone.pl.
Recover partitions /var /usr and root, when clone.cfg is in /tmp.
#perl clone.pl -b off -r on -p '/ /var /usr' -L 4
Recover partitions /usr and root, when no clone.cfg exists.

#mount /dev/dsk/c0t0d0s0 /tmp/ c0t0d0s0 #mount /dev/dsk/
c0t0d0s6 /tmp/ c0t0d0s6 #perl clone.pl -b off -r on -p '/ /
usr' -L 4
Configure
The clone.cfg file contains a list of all system and backup drives and all mounted slices
information of the most recent backup procedure. The configuration file is created automatically
after the successful completion of a clone.pl operation. If $MPSHOME is set then the clone.cfg
file is stored in /opt/vps/common/etc/clone.cfg. Otherwise, the file is located in the /tmp
directory. The content of this file can be changed.
#
# Example clone.cfg file.
#
# Note the backup drive specified in command line options
# has high priority.
#
# TYPEDRIVE
#
systemc0t0d0
#
backupc0t1d0
#
# Mounted slices information
#
# TYPEMOUNTED ONFILESYSTEM
mountedfs/c0t0d0s0
mountedfs/usrc0t0d0s6
mountedfs/varc0t0d0s4
mountedfs/optc0t0d0s5
mountedfs/mmf2c0t1d0s5
#
# End of clone.cfg file.
Once the system is successfully backed up, save the clone.cfg file in case the system drive
was totally corrupted.
Logging
1. Clone.dat
Data file clone.dat is created during the backup or recovery operation, recording
every clone operation. If $MPSHOME is set then the clone data file is stored in /opt/
vps/common/log/clone.dat. Otherwise, the file is located in the /tmp directory. A
sample clone.dat file is shown below.
Mon Mar 15 14:54:08 2004: ---------Start procedure logging ---------

Mon Mar 15 14:54:10 2004: OPTION -D DAT logging level set to HIGH
Mon Mar 15 14:56:53 2004: ---------Start procedure logging ---------
Mon Mar 15 14:56:55 2004: OPTION -D DAT logging level set to DETAIL
Mon Mar 15 14:56:55 2004: Current directory:/var
Mon Mar 15 14:56:55 2004: tar cvf -. 2>/opt/vps/common/log/tarc.out|(cd /
mnt/c0t1d0s4; tar xvfBp - >/opt/vps/common/log/tarx.out)
Mon Mar 15 15:00:54 2004: a./ 0K
Mon Mar 15 15:00:54 2004: a./lost+found/ 0K
Mon Mar 15 15:00:54 2004: a./sadm/ 0K
.
.
.
Mon Mar 15 15:01:06 2004: x./crash, 0 bytes, 0 tape blocks
Mon Mar 15 15:01:06 2004: x ./crash/tb020, 0 bytes, 0 tape blocks
Mon Mar 15 15:01:06 2004: Successfully tared /var to <c0t1d0s4>
There are two levels for this type of logging which can be specified using the -D #
option on the command line. To set the logging level, refer to step 2 on page 110
under Preparation for Solaris Backup on page 110.
2. Clone.log
The clone.log file, records debug information. The logging file is created during the
backup or recovery operation. If $MPSHOME is set the clone.log file is stored in /
opt/vps/common/log/clone.log. Otherwise, the file is located in the /tmp directory. A
sample clone.log file is shown below.
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition </var> will be

added to the following list
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition list <>
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition list updated as </
var>
Mon Mar 15 14:56:55 2004: grep_dir: The direct directory under root is </
var> for partition </var>
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition </var> will be
added to the following list
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition list <>
Mon Mar 15 14:56:55 2004: add_to_partitions: Partition list updated as </
var>
Mon Mar 15 14:56:55 2004: filter_partitions_input: Existing partitions
specified </var>!
Backing Up with tar
Mon Mar 15 14:56:55 2004: filter_partitions_input: Valid partitions under

root </var>
Mon Mar 15 14:56:55 2004: grep_dir: The direct directory under root is </
var> for partition </var>
Mon Mar 15 14:56:55 2004: get_mount_sliceID: Slice <#4> found for
partition </var>
Mon Mar 15 14:56:55 2004: tar_nonrt_sli: Backup </var> on <c0t1d0s4>
Mon Mar 15 14:56:55 2004: do_mount: Successfully mounted c0t1d0s4 to /mnt/
c0t1d0s4
Mon Mar 15 14:56:55 2004: tar_nonrt_sli: Current directory:/var
Mon Mar 15 14:56:55 2004: tar_nonrt_sli: This will take a little bit while
to finish
Mon Mar 15 14:56:55 2004: crt_nonroot_arch: tar cvf -. 2>/opt/vps/common/
log/tarc.out|(cd /mnt/c0t1d0s4; tar xvfBp - >/opt/vps/common/log/tarx.out)
Mon Mar 15 15:01:00 2004: wfiledat: Successfully saved operation file</opt/
vps/common/log/tarc.out> into /opt/vps/common/log/clone.dat.
Mon Mar 15 15:01:06 2004: wfiledat: Successfully saved operation file</opt/
vps/common/log/tarx.out> into /opt/vps/common/log/clone.dat.
Mon Mar 15 15:01:06 2004: crt_nonroot_arch: Successfully tared /var to
<c0t1d0s4>
Mon Mar 15 15:01:23 2004: do_umount: Successfully umount file system:/mnt/
c0t1d0s4
Mon Mar 15 15:01:23 2004: tar_nonrt_sli: Taring is done for </var> on
<c0t1d0s4>
Mon Mar 15 15:01:23 2004: main: Successfully backuped file system:c0t0d0
to c0t1d0. Done!
Mon Mar 15 15:01:23 2004: write_cfg: Created
/opt/vps/common/etc/clone.cfg containing backup/system drives and
partitions's info.
There are four levels for this type of logging which can be specified using the -L #
option on the command line. To set the logging level, refer to step 2 on page 110
under Preparation for Solaris Backup on page 110.
3. Saving Old Log Files
When the size of a log file exceeds 1000 KB, the clone.pl script saves the file to
file.date. If there is a file called file.date, then the current file.date is renamed as
file.date.old and the new file is saved as file.date. New logging files are created for
future use.
Backing Up with tar

The tar command combines and saves files to a tape or internal drive.
Note:
tar does not support multivolume backups. If there is a need to make backups beyond the
capacity of the media, split the job into several backups (that is, back up individual partitions)
or use the ufsdump command. For information on using this utility that does span multiple
media (and which is especially useful for large backups), see Backing up with ufsdump on
page 117. To determine if a directory will fit on a single tape or disk, see Determining
Directory Size on page 108.
Caution:
Do not backup to a medium that contains useful files. The tar command overwrites existing
files.
Backing Up with tar
1. To make a tape-based backup:
a. Label the tape.
b. Insert the tape into the drive.
2. Log in as root.
a. From any command line enter su.
3. Move to the directory where the files are located (the source directory). See Working
with Directories on page 104.
4. Enter the tar command.
• To backup to a tape, use the syntax tar cvf /dev/rmt/0 <sourcefiles>.
• To backup to the present working directory, use the syntax tar cvf
<archivefile.tar> <sourcefiles>. Use cp to place the tar file in an alternate
directory or drive.
Use a descriptive file name with the .tar extension for <archivefile.tar> (for example,
oldvocabs.tar). This command combines and saves the source files in the archive
file <archivefile.tar>.
Specify either individual files or entire directories to be backed up. Backups can also
be made to an alternate directory or internal drive. See the Solaris system
documentation or details about the tar and cp commands.
Displaying the Contents of a tar Backup

Display the table of contents for each backup to ensure that it is readable and complete.
Displaying the Contents of a tar Backup
1. To display a tape backup, insert the tape into the drive.
2. Log in as root.
• To verify the contents of a tape, enter tar tvf /dev/rmt/0.
Restoring with tar
• To verify the contents of an internal drive, move to the directory that contains
the tar file and use the syntax tar tvf <archivefile.tar> where <archivefile.tar>
is the tar file.
This command verifies each file stored in the archive file and prints its name and
size to the screen.
The contents of a tar file in an alternate directory can also be verified. See the Solaris
system documentation for details about the tar command.
Restoring with tar

Use the tar command to restore selected files or the entire backup.
Restoring Files with tar
1. If restoring a tape backup, insert the tape into the drive.
2. Log in as root.
3. Move to the directory where the files will be located (destination directory).
• To restore files from a tape, enter tar xvf /dev/rmt/0.
• To restore files from an internal drive, use cp to place the tar file in the
destination directory and use the syntax tar xvf <archivefile.tar> where
<archivefile.tar> is the tar file.
See the Solaris system documentation for details about the tar command, and for
details and examples on using cp.
Backing up with ufsdump

Use ufsdump to transfer files to a tape, internal drive or disk, or diskette. Whereas the ufsdump
command does not perform file compression, it does detect end of media and span multiple
volumes. This is useful for very large file backups. The systems provides prompting when a
media source is full and an additional volume is needed.
Caution:
When running ufsdump , the file system must be inactive, otherwise, the output of ufsdump
may be inconsistent and restoring files correctly may be impossible. A file system is
considered inactive when it is unmounted or the system is in single-user mode.
A file system is not considered inactive if one tree of the file system is dormant while another
has files or directories under modification.
See the Solaris ufsdump documentation for important information concerning overlapping
partitions if dumping to disk.
Backing Up with ufsdump (locally)
1. If backing up to a tape:
a. Label the tape.
b. Insert the tape into the appropriate drive.
2. Access a Solaris command shell.
a. Click <MENU> on the desktop.
b. In the Workspace pop-up menu, click <MENU> on Programs.
c. From the Programs menu, select Command Tool... .
3. Log in as root.
4. Move to the directory where the files are located (source directory), see Working
with Directories on page 104. Files must be contained in the same file system that is
local to the system where ufsdump is being run.
5. Enter the ufsdump command. Typically, the syntax used is:
ufsdump <options> <arguments> <files_to_dump>
where <options> is a single string of one-letter options, <arguments> may be
multiple strings associated with the options as determined by order, and
<files_to_dump> specifies either the files, directories, or an entire file system to back
up. For further information. see the table entry.
Backing Up with ufsdump (across a network)
1.
Caution:
Performing a ufsdump across a network may cause network degradation. Check
with your network administrator first prior to attempting the backup.
Files can be backed from one machine in a network to a devices elsewhere in
network.
Follow step 1 . through step 4. Place the media into the drive of the machine that
will store the backups. Access the Command Tool on the machine containing the
files to be backed up.
2. Enter the ufsdump command, using the following syntax:
ufsdump <options>f <machine:device> <files_to_dump>
where <options> is a single string of one-letter options (of which f must be used for
network backup), <machine:device> represents the name of the machine and the
Backing up with ufsdump
device ID on that machine where the files are to be dumped, and <files_to_dump>
specifies either the files, directories, or an entire file system to back up.
Since ufsdump is normally run by root, the name of the local machine must appear in
the /.rhosts file of the remote machine. The f argument can also be specified as
user@machine:device, in which case ufsdump attempts to execute as the specified
user on the remote machine. In this case, the specified user must have a .rhosts
file on the remote machine, which allows the user invoking the command from the
local machine to access the remote machine.
There are several important options that should be considered when using ufsdump. The
following are not the only options, but can be considered the most important from the standpoint
of backing up Media Processing Server Series-related information:
<argument> Definition
0-9 Dump level of files. This can be used for comparative
purposes during multiple or incremental dumps. A
level 0 dump copies the entire file system to the dump
file destination media.
a <filename> Archive file. Creates a dump table of contents in the
backup (archive) file, the name of which must be
specified. This table of contents can later be used by
ufsrestore to determine whether or not a file or
directory exists on the backup. If this option is not
used, ufsrestore can still read the contents of the
backup directly from the media rather than the archive
file. It is highly suggested that only Field Engineers use
ufsrestore.
c Cartridge. Sets the defaults for cartridge tapes instead
of the standard half-inch reel. This option should
always be used when backing up to a Media
Processing Server Series tape drive!
D Diskette. Dump to diskette. This option is case
sensitive and should always be used when backing up
to a diskette!
f <filename> Dump file. Specifies a file to dump to, instead of /dev/
rmt/0: the file name must be specified. If the file is
specified as (-), the backup is dumped to the terminal.
If the name of the file is of the form machine:device,
the dump is performed at the specified machine over
the network. If the file is specified as
user@machine:device, ufsdump attempts to execute
as the specified user on the remote machine. See step
2. on page 110, for important information
regarding .rhosts files and network backups.
S Size estimate. Determines the amount of space in
bytes needed for the backup without actually
performing the transfer. Allows the operator to
<argument> Definition
determine how many volumes of media will be needed
for the dump. This option is case sensitive!
v Verify. After each tape or diskette is written, the
contents of the media are verified against the source
file system. If any discrepancies are found, the system
will prompt for a new media and the dump/
verification process will be repeated.
If no options are provided, the default definition of ufsdump is 9uf /dev/rmt/0 <files_to_dump>.
• To backup to a local tape, use the following command as a minimum (other options may be
added at the user's discretion):
ufsdump 0cf /dev/rmt/0 <files_to_dump>
• To backup to another local device, substitute that device name for /dev/rmt/0 in the
above example, and change the device options as applicable (that is, for a floppy backup,
change option c to D).
• To backup to a tape device on another machine in a network, use the following command
as a minimum:
ufsdump 0cf <machine:/dev/rmt/0> <files_to_dump>
• To backup to a tape device as a particular user on another machine in a network, use the
following command as a minimum:
ufsdump 0cf <user@machine:/dev/rmt/0 > <files_to_dump>
• To backup to another remote device, substitute that device name for /dev/rmt/0 in the
above examples, and change the device options as applicable (that is, for a floppy backup,
change option c to D).
Note:
There are important considerations regarding .rhosts files when performing a remote backup
over a network. See step 2. on page 110, for additional information.
For complete definitions of these and other options, including pertinent usage and
ramifications, please see the Solaris ufsdump documentation.
Backing up partitions with ufsdump

Use ufsdump to backup all partitions on a non-mirrored system drive.
Caution:
This is the only backup type that a "Certified Avaya Field Engineer" is authorized to use to
restore or replace a damaged drive.
Backing up partitions with ufsdump
Note:
The file system must be inactive during ufsdump.
Backing Up Partitions with ufsdump
1. Determine the number of tapes required. Execute df -k and add up the usage for
all the displayed system disk slices, to determine how may tapes are required. The
space allocation listed under the "used" heading are in KB when the -k option is
used. Backup all system disk slices shown in the df command output, with the
exception of swap. Swap does not need to be backed up because it contains
temporary data. The mmf file systems may or may not be on the system disk,
however, they should also be backed up.
2. Check for keyboard/mouse. Ensure that the system has either a console/keyboard/
mouse connected or a laptop connected to "ttya" if you are bringing the system
down to single user mode.
3. Boot system. Boot the system as single user or login as super user and have the
system in an inactive state. (no calls or disk I/O taking place.)
4. Backup filesystems. Dump the filesystems to one or more tapes as determined in
step 1. above. The example below illustrates the commands used to dump the four
slices of a standard MPS boot drive on a single tape, your disk configuration may
differ: (All the commands below use "ZEROs" not "OHs" )
# ufsdump 0ucf /dev/rmt/0n /dev/rdsk/c0t3d0s0 (Wait for the prompt to return prior
to issuing each command below) # ufsdump 0ucf /dev/rmt/0n /dev/rdsk/c0t3d0s4 #
ufsdump 0ucf /dev/rmt/0n /dev/rdsk/c0t3d0s5 # ufsdump 0ucf /dev/rmt/0n /dev/
rdsk/c0t3d0s6
The example above uses the "n" option to stop the tape from rewinding. This allows
each dump to be stacked on a single tape. To use a separate tape for each dump,
remove the "n" and at the end of each dump replace the tape.
5. Rewind the tape. When all dumping for this particular tape is complete, rewind the
tape with:
# mt -f /dev/rmt/0 rew
6. Eject the tape and label the cover. Write the date, hostname, and slice dump order
on the label, and store the tape and partition table information in a safe and
accessible location.
7. Additional backups. If necessary, continue dumping to additional tapes. The
following is an example for dumping an MMFdisk:
# ufsdump 0ucf /dev/rmt/0 /dev/rdsk/c0t0d0s1
Displaying the Contents of a ufsdump Backup

Display the table of contents for each backup to ensure that it is readable and complete, and
that a particular media volume contains the files and directories to be extracted.
Displaying the Contents of a ufsdump Backup
1. Insert the backup media into the appropriate drive.
2. Log in as root.
3. Enter the ufsrestore command with the following options:
• To verify the contents of a tape directly, enter ufsrestore tf /dev/rmt/0. By not
supplying any file names, the root directory is listed, resulting in a list of all files
on the media.
• To verify the contents of a tape that was backed up with the archive file option,
enter ufsrestore taf <archive_file> /dev/rmt/0
• To verify the contents of other media, substitute that media device name for /
dev/rmt/0 in the above examples.
These commands verify each file stored in the archive file and prints its name to the
screen.
Restoring with ufsrestore

The ufsrestore command loads files, that were previously backed up with the ufsdump
command, from tape into the current directory. The directory must be a stable file system. The
following is an example of restoring an entire ufsdump file from a dump tape (/dev/rmt/0) to /opt.
Restoring with ufsrestore
1. Insert the backup media into the appropriate drive.
2. Log in as root.
3. Change to the directory where the ufsdump file should be restored to, in this
example, /opt.
cd /opt
Backing Up with cp (Copy)
If the system was booted from a CD, then mount the disk slice to restore to, for
example:
mount /dev/dsk/c0t3d0s5/mnt
cd /mnt
4. Make sure the tape is positioned at the beginning, so it can skip to the desired
location.
mt -f /dev/rmt/0 rew
5. To determine if /opt is in the 3 rd dump file on the tape, list the table of contents on
the tape to see if it resembles, /opt.
ufsrestore tfs /dev/rmt/0n 3
Note:
The norewind flag is required on the tape device.
6. Rewind to the beginning of the tape.
7. Run ufsrestore , starting at the 3rd file (assuming /opt was the 3rd file on the tape).
ufsrestore rfs /dev/rmt/0n 3
Note:
The norewind flag is required on the tape device.
8. When the restore is complete, remove the following file:
rm restoresymtable
9. Rewind and eject the tape.
Backing Up with cp (Copy)

The Solaris cp command copies individual files or groups of files. Use this command to back
up crucial files to alternate directories and to copy files between directories.
See the Solaris system documentation for details and examples about using cp.
Backing Up and Restoring Multimedia Elements

Use MPS Studio to back up crucial elements in Multimedia (vocabulary) files. This procedure is
only efficient if one or two elements in an MMF file are extensive or critical. If more than a few
elements have to be backed up, back up the entire file with cp or tar.
Backing up Multimedia Elements
1. Launch MPS Studio. From the command line enter: MPS Studio &
2. Open the Multimedia file with the elements to be backed up.
3. Select the elements.
4. Export the elements to a Vgen incremental backup file.
a. Select Vgen incremental format.
b. For a digital system, select u-law encoding. For an analog system, select
adpcm encoding.
5. Use any of the backup methods described earlier to back up (store) the Vgen
incremental file.
For details about using MPS Studio, see the MPS Studio User Guide.
If selected elements are backed up to a Vgen incremental file, these elements can
be restored in the Media Processing Server shell.
Restoring Multimedia Elements
1. Open a Media Processing Server 1000 shell on the system that contains the
vocabulary file. For additional information, see Command Control on page 46. Use
the restore procedure appropriate for the backup method used on the elements to
restore the Vgen incremental backup file.
2. Update the existing Multimedia file with the Vgen incremental backup file. Use the
syntax vmm mmfupdate <existingvocab>,<backfile.def1> where <existingvocab>
is the existing vocabulary file and <backfile.def1> is the Vgen incremental backup
file.
Chapter 8: Troubleshooting
1. Fault Categories
2. Isolating and Resolving Specific Problems
3. SRP Log File
Troubleshooting
This section discusses categories of faults that may occur, some common fault conditions,
causes, and suggested actions. Follow these suggestions before contacting Avaya technical
support.
Fault Categories
Faults on the Media Processing Server fit in the following general categories:
• Vocabulary files
• File synchronization
• Host communication
• Telephone lines
• Application software related
• Redundancy
• Call-protect
Perform the following checklist actions to isolate problems. If necessary, supplement this
procedure with site-specific actions to verify proper operation of other connecting telephone
and computer systems. Use these guidelines only in the proper context of overall system-
level problem determination.
Use this procedure after Avaya has completed the initial/upgrade installation and the system
has been in an operational state with application software.
Troubleshooting
1. Verify the operation of the system with the following actions:
To verify that... Perform this action...

System console is active and able to Move the mouse pointer into a
accept commands command window and press <Return>
on the keyboard. The system should
respond with the command prompt.
System answers calls and performs Call the system and make sure that it
normally processes calls normally. Make both
normal and error-laden calls to verify all
the functions.
System is processing calls in a normal Check the Alarm Viewer for alarm
manner and is not generating any messages generated by incoming
alarms due to errors calls. Also examine the alarm log file to
check for recent messages, seeThe
Status of startup and recovery Use the following status commands
processes, phone lines, voice memory, and check for normal/abnormal results:
application programs, host lines, and
• srp status
vocabularies are within acceptable
limits. • ccm status
• vmm status
• vmm mmfstatus
• vmm appstatus
• rcd status
For additional information, see Status
Monitoring on page 51.
Operating parameters for the system Check the front and rear panel
are normal indicators on the cabinet, TMS, and
VRC. For locations and functions, see
MPS 500 Indicators and Controls on
page 30.
Redundancy is properly configured and Follow the Redundancy verification
working. procedure outlined in the "Verifying
Failover and Failback" section of the
MPS System Reference Manual.
Call-protect is properly configured and Utilize the following vsh commands to
working. verify configuration:
To verify that the system is configured
and licensed for Call-protect startup
mode use: rcd status
To verify, after a failure, that the VOS
actually performed Call-protect use: trip
status
Isolating and Resolving Specific Problems
To verify that... Perform this action...

Follow the Call-Protect verification
procedure outlined in the "Verifying
Call-Protect" section of the MPS
System Reference Manual.
2. If it is possible, isolate the problems into one of the Categories of Faults. Refer to
the common symptoms, cause, and actions for that category.
3. If the problem cannot be isolated or repaired, or if it continues to occur, contact
Certified Avaya Support Personnel. Have the following information available:
• A description of the problem, including any error messages.
• The number of lines taking calls when the problem occurred.
• The system's serial number.
• The remote access telephone number.
Isolating and Resolving Specific Problems

This guide discusses commonly occurring problems across a variety of systems and
configurations. Therefore, it may or may not address problems at a specific site.
Try to isolate the problem into one of the Categories of Faults. Referring directly to that section.
Always check the Alarm Viewer and Alarm Log files for pertinent messages when using these
sections, see The Alarm Viewer on page 49.
Note:
Analyze the causes in the order they appear in the tables.
MMF (Vocabulary) File Troubleshooting

Refer to the MPS Studio User Guide for a detailed description of creating and troubleshooting
vocabularies. The following addresses problems activating, deactivating, monitoring, and
updating vocabularies.
Some problems that appear to be related to vocabulary files may be related to the application or
system configuration.
Troubleshooting
Table 11: Vocabulary Files Troubleshooting:
Condition Cause Action

An MMF file Invalid MMF file name. Verify the file name.
(vocabulary) file
cannot be File is corrupted. Run mfck -f or MMF should be restored from
activated the backup or copied from another MPS with
a valid copy
An MMF file Invalid application or Verify the application and file names.
(vocabulary) file MMF file name.
cannot be
deactivated
There is no Invalid MMF file name. Verify the file name.
output for the
status of a MMF file is not activated. Activate the MMF file, see Activating
vocabulary file Playback MMF Files on page 79.
The application Hash table contains Edit the vocabulary file or create an
speaks incorrect elements with the same application-specific hash table, see
vocabulary name. Activating Playback MMF Files on page 79.
items
Online updates The MMF file was opened First, deactivate the Multimedia (vocabulary)
cannot be read-only. file, see Deactivating MMF Files on page 86.
performed Make sure it is not open in MPS Developer,
MPS Studio, or another MPS component on
the same node. Then, activate the file, see
Activating Playback MMF Files on page 79.
New elements The MMF file is static and Delete unused elements from the MMF file.
cannot be does not contain enough See the MPS Studio User Guide.
recorded available space.
The MMF file is dynamic, Delete unnecessary files from the file system
but the file system is 98% where the MMF file resides, see File
full. Removal on page 106.
An MMF file The MMF file is static. A static MMF file cannot be expanded.
(vocabulary) file
cannot be There is not enough disk Delete unnecessary files from the file system
expanded space on the file system. where the MMF file resides, see File
After expansion, the file Removal on page 106.
system must have at least
2% available space.
The application The elements have not Activate the MMF file, see Activating
does not speak been loaded (that is, Playback MMF Files on page 79.
the elements activated).
File Synchronization Troubleshooting

All the elements There is not enough voice • Remove any elements not used by
do not fit into memory. applications. See the MPS Studio User
VDM when the Guide.
MMF file is
loaded (that is, • Set the vmm loadall command to off. This
(activated) allows only elements with a lock flag set to
be loaded into VDM (limits total number of
elements loaded).
• Set the vmm preload option to
accommodate the loadall command (see
previous bullet). If loadall is off, set preload
to all. If loadall is on, the number of
seconds to preload into VDM should be
kept small if this condition occurs.
The preload and loadall commands are set
in the $MPSHOME/mpsN/etc/vmm-
mmf.cfg file (see the note under SRP Log
File on page 134. If this file is modified,
VMM must be stopped and restarted for the
changes to take effect, see TMS Startup/
Shutdown on page 25.
• Adjust system voice memory size. Use the
vmm pagesize <n_kbytes> command to
set the size of a single segment of VDM.
The smaller the size, the more efficient use
of VDM, but the greater the use of system
memory.
• Lock the most commonly spoken elements
into voice memory and page the remaining
elements from cache.
• Use the vmm vdmmaxlock <n%>
command to stipulate the maximum
percentage of VDM to use for locked
elements. The default (50%) is highly
recommended.
File Synchronization Troubleshooting

Automated MMF file synchronization is provided for all active, designated files through use of
the Zero Administration for Prompts (ZAP) utility, see Synchronizing MMF Files Across Nodes
(ZAP Utility) on page 94. This utility generates faults and exception conditions as part of its
function. While some causes can be general in nature and not directly attributable to the utility
Troubleshooting
itself, understanding the situation surrounding them can help alleviate possible repetition of
the condition.
Host Communication Troubleshooting

Since each application communicates directly with the host, problems that arise may be logical
(that is, software or protocol related) rather than absolute (that is, the physical interface).
Table 12: Host Communication Troubleshooting

MPS is not The host is down. Wait for the host to start up.
communicating
with the host The host is up, but all Bring up all appropriate host applications.
terminals (VTs) are down.
The protocol software is Call for maintenance service.
not functioning properly.
Host went down The application does not Verify that the application properly handles
and came up but handle the host-up host up/down status messages.
the MPS is not condition properly.
responding
Host error The application code Verify and correct the application host
message contains incorrect host access sequences.
(COMMGR) access commands.
occurred during
application run There is not enough delay Two send requests without an intervening
time time between the host receive request causes an error.
send and host receive
calls.
Note:
For additional information on working with applications, see the MPS Developer User Guide.
For additional host-specific issues, refer to the Media Processing Server Series COMMGR
Reference Manual.
Telephone Line Troubleshooting

The Media Processing Server telephone lines are either analog or digital. Some of the
conditions in the following table do not apply to both types of lines. In some cases, application
program logic may terminate calls in progress.
Telephone Line Troubleshooting
For additional information pertaining to telephone lines, see the Media Processing Server
Series Telephony Reference Manual.
Table 13: Telephone Line Troubleshooting

A phone line or A CCM software module It is possible (but unlikely) that one CCM
group of phone has failed. process exists for each phone line. In this
lines are down case, the failure of an individual CCM leads
to the same for its corresponding line. The
CCM module should be restarted
automatically by SRP. If has not restarted,
restart the MPS. See Routine Media
Processing Server Startup on page 27.
The lines exist solely in Assign and start the applications. See
the pool line.in and the Assigning and Starting Application
application is not running. Programs on page 82.
A span is not working Contact the local MPS Series support staff.
properly.
Line does not The phone line is not Check the phone line connection.
answer connected.
incoming calls
There is no application Assign and start an application on the line.
assigned to the line. See Assigning and Starting Application
Programs on page 82.
The signalling protocol is Check the configuration of the signaling
improperly configured protocol.
(digital system only).
Incoming line The active application is Start the application. See Assigning and
stays in a busy terminated (or not Starting Application Programs on page 82.
state started).
There is no application Assign and start an application on the line.
assigned to the line. The See Assigning and Starting Application
default state is busy. Programs on page 82.
The application keeps the Check the coding of the application to
state of the physical determine how it handles the condition of the
phone line in the not-in- line when not in service. Otherwise, try
service condition. stopping and restarting the application.
SeeTerminating and Unassigning
Application Programs on page 85and
Assigning and Starting Application
Programs on page 82.
The line is not working. Replace the physical component containing
the line.
System does not There is no active call on Call in to the line and restart logging.
display logging the line.
Troubleshooting

Call cannot be There are no active calls Call in to the line (wait for an active call).
monitored on the lines.
The telephone handset is Use a different telephone handset.
faulty.
The ccm listen command Issue the ccm listen in/out command. See
was not issued correctly. the Media Processing Server Series System
Reference Manual for details.
Application Software Troubleshooting

The application software on Media Processing Server Series systems is diverse. Often,
problems are specific to a site or a particular program.
Table 14: Application Software Related Troubleshooting

Application does The application is not Start the application. See Assigning and
not answer started. Starting Application Programs on page 82.
incoming calls
The application is not Attach call-processing applications to
attached to a physical physical phone lines. See Assigning and
phone line. Starting Application Programs on page 82.
The application does not Add proper code to application. (See the
contain coding to answer MPS Developer User Guide.)
calls.
Caller is The MMF file is not loaded See Activating Playback MMF Files on
disconnected into Voice Data Memory. page 79.
prematurely
either at the start Some vocabulary See Updating or Replacing Playback MMF
or during the call elements are corrupted or Files on page 89.
do not exist.
Application The application code Review the application code. See the MPS
speaks the references the wrong Developer User Guide.
wrong items.
vocabulary
elements There are two like-named • Edit the MMF files so that all elements in
MMF files in the the same hash table have unique names.
application or system See Updating or Replacing Playback MMF
hash table. Files on page 89. For a detailed description
Redundancy Troubleshooting
of hash tables, see the Media Processing

Server Series System Reference Manual.)
• Deactivate the MMF file with the duplicate
elements. See Deactivating MMF Files on
page 86.
An application, Some commands and The application has to be recoded to

ported from functions (for example, accommodate new comparable commands
VPS/is to MPS those pertaining to plm) or functions, or to remove those no longer
3.03.5, does not from previous software supported. (For more information, see the
execute releases are not Media Processing Server Series Transition
properly. supported in the MPS Guide and MPS Developer User Guide.)
environment.
Redundancy Troubleshooting
Table 15: Redundancy Troubleshooting

Secondary The primary node is still Restart the failed software components on
(standby) node up but some software the primary.
does not take components on the
control. primary have failed.
The secondary attempted Address the configuration related issues that
to take control and failed 4 prevented the secondary from taking over for
times in a row, causing it the primary, and then restart RCD on the
to remove that primary secondary.
from its list of nodes for
which it is standby.
Call-protect Troubleshooting
Table 16: Call-protect Troubleshooting

The system did The system is not Modify the rcd.cfg file to set the startupMode
not recover configured for Call- to CallProtect.
calls, bridges, or protect startup mode.
Troubleshooting

conferences The system is not properly Make sure the license server is configured
after a failure. licensed for Call-protect. with enough CallProtect licenses to support
the number of MPS nodes that are expected
to perform call-protect.
The application is not Modify the application to support Call-
coded for Call-protect. protect.
The system did not Verify that the TMS rebooted. Verify the
recover quickly enough duration that it took for the MPS to startup
resulting in the TMS after the failure. Contact certified Avaya
rebooting. support personnel.
The system did not Contact certified Avaya support personnel.
recover quickly enough
resulting in line/bridge/
conference resources
being automatically freed.
SRP Log File

The Startup and Recovery Process (SRP) maintains a continuous record of processes
monitored by SRP in the file $MPSHOME/common/log/srp.log.
This log file includes dates and times for process spawning, fatal alarms, and start/stop
application requests
The srp_state.log file, located in the same directory, maintains a history of process state
changes, including the date and time the change in state occurred.
For the complete Solaris Media Processing Server directory tree, see MPS Directory
Structure on page 137.
Note:
In the following passages, the term vps is used in discussions of path names, environment
variables, and file fields. This terminology is equivalent to MPS nomenclature. That is,
mentions of "VPS" are applicable to "MPS."
Viewing the SRP Log Files
1. Open a command shell on the component to be investigated. For additional
information, see Command Control on page 46.
2. Change to the directory holding the SRP log file. Enter cd $MPSHOME/common/
log.
3. Enter the more or page command followed by either srp.log or srp_state.log as
applicable (an underscore must be used between the words srp and state). A portion
SRP Log File
of the file equal to the size of the command window will display, followed by a prompt
indicating how much of the file has already been viewed.
4. Press the space bar to scroll the screen.
5. Optionally, use the tail command. By default, this command displays the last 10
lines of a file: thus, it becomes useful when only the most recent input to the srp
files is of interest (the data in these files is sorted in ascending order).
See the Solaris system documentation for a detailed description of the more, page,
and tail commands.
The following is an example of the SRP log file:
The following is an example of an SRP state log file:
For more general information about these two files, see the MPS Command Reference Manual.
Chapter 9: MPS Directory Structure
1. Solaris Directory Structure

2. System software home directory $MPSHOME (/opt/vps)
3. User-Specified Distribution Directory (usually /opt/vps)
MPS Directory Structure

During the install process on Solaris systems you are prompted for the target install directory
and MPSHOME. The MPSHOME directory contains the common and component directories,
while the target install directory contains package specific data. The default directory for both
MPSHOME and the target install directory is /opt/vps. During the installation process, the /opt/
vps directory and the environment variable $MPSHOME are created (if they do not already
exist).
Each Avaya software package for major system functions (for example, MPS Studio, MPS
Manager, licensing files, and so on) is stored in its own subdirectory under the packages
directory. During software installation, the option is presented to specify the location of the
packages directory. The directory under which the packages directory is installed is referred
to as the user-specified distribution directory. By default, the distribution directory is set to the
same path as the system directory, /opt/vps.
When the Avaya software packages are installed, symbolic links to their locations are created
in /opt/vps.
Note:
The following is important information about the naming conventions for installation
directories:
• The value of $MPSHOME on an existing system should never be changed by any user
or system administrator.
• It is highly recommended that the default (/opt/vps) be used as the user-specified
distribution directory location, unless there is a specific reason to change it. This can
make external troubleshooting easier.
• The command echo $ <VARIABLE> displays the value of a specified environment

variable. For example, to see the value of the system software home environment
variable, enter echo $MPSHOME.
• Individual software packages are stored in directory names of the form <name>X.X.X or
<name>X.XX. This naming convention is used to identify particular packages and their
version numbers.
• This appendix provides documentation only of the essential MPS directory structure.
Depending on site requirements, there may be additional or fewer directories than are
presented here. Also, the order in which the directories are shown might be different
than on the site's installed MPS systems.
Note:
For windows installations, the target install and MPSHOME default is [Program Files]\Avaya
\SelfService. MPSHOME contains the target distribution as well as the common and
component directories. The MPSHOME setting can be displayed in the My Computer
properties environment panel or on the command line using set %MPSHOME%.
Figure 3: Windows Directory Structure
Figure 4: Solaris Directory Structure
All system-level software is installed in the directories identified below. The directory structure
must not be altered, or the system might not be able to find necessary files.
System software home directory $MPSHOME (/opt/vps)

$MPSHOME (/opt/vps) System directory containing subdirectories for the operating
system files and symbolic links to the various packages installed
on the system.
bin Contains the executable files for the installed software packages.
common Files available for use by all MPS systems.
etc Configuration, administration, and alarm
database files.
log SRP, file transfer, alarm, and ZAP log files.
include Header files for compiling user call functions.
System software home directory $MPSHOME (/opt/vps)

stats Binary files for statistics collection and data files
created by statistics-gathering scripts (including
logs and status files).
vps_sched Scheduling files.
zap Temporary files used during ZAP execution.
defaults Contains template configuration files.
commonetc Template configuration files for the common
component.
componentet Template configuration files for the mps and
c tmscomm components (in their respective
directories within componentetc).
lib Shared library files.
mpsN Files specific to a single MPS. The value of N indicates the MPS
system number. One mpsN directory exists on each MPS system.
The number zero (0) cannot be used.
apps Working directory for application files. When an
application is started, copies of its VENGINE
executable (*.vex) and configuration (*.acfg) files
are placed in this directory. SRP starts
applications from this directory. This directory
also contains subdirectories for shared user
libraries.
etc Configuration and administration files.
log Log files.
stats Statistics files and shell scripts.
tmscommN Files for bridging between and within MPS components. The
value of N indicates the tmscomm component number. The
number zero (0) cannot be used.
apps Library subdirectory. Not used at the present
time.
etc Contains the vos.cfg configuration file, which
starts the Network Interface Controller Daemon
(NCD) at system startup.
log Log files.
stats Statistics files and shell scripts.
PERI<name> Symbolic links to the subdirectories under the packages directory.
User-Specified Distribution Directory (usually /opt/vps)

The particular path used as the distribution directory is set up when the system-level software is
installed. By default, it is set to /opt/vps. The distribution directory contains a lower-level
subdirectory named packages. All Avaya software packages are stored in their own
subdirectories under packages. When a particular package is installed, a symbolic link in
$MPSHOME is set up by the system to reference that package.
Note:
The following is important information about the subdirectories and files in the distribution
directory:
• The information provided here discusses only the essentials of the distribution
subdirectory structure. Depending on site requirements, there may be additional or
fewer directories than are shown here.
• Some of the distribution subdirectories contain a lower-level log subdirectory. Log files
are used by the system internally and should never be modified with command line
functions or text editors.
• If a particular software package has been upgraded since its initial installation, its
subdirectory might contain a patches subdirectory and patchlog file. The patches
subdirectory contains lower-level subdirectories and files necessary for implementing
the patch(es), and the patchlog file lists the results of the installation of the patch(es).
Patches and patch logs are not discussed further in this appendix.
User-Specified Packages Directory (usually /opt/vps/packages)

packages Home directory for all installed Avaya Media Processing
Server software packages.
aseX.X.X Files for the Application Services Environment (ASE)
software. ASE is the runtime environment for MPS
Developer.
copy Stubs for statistics folders (*src, VSUPD
documents).
etc Sample configuration and administration
files.
include Files for user CALL functions (*.h).
link Sample .vex and .ppr files.
log MPS Reporter log files containing
information about applications and
collected system statistics. These files
should never be modified by the user.
shmem Shared memory files (for file-based
shared memory, if any).

stats Application statistics files.
brdgeX.X.X Software for the tmscomm component. It supports bridging
functions of the Media Processing Server system.
ccxmlX.X.X Configuration files, took kit, and directories for CCXML
processes and utilities.
etc Contains default configuration files.
HTML_XSL Contains Interpreter Web interface files.
sample_app Contains sample CCXML applications.
distX.X.X Directories and files for the Apache Web server.
apache MPS configured Web server files.
conf Default configuration files.
dist-bin Perl scripts.
etc Shell scripts.
log Web server log files.
docX.X.X Directories and files that support online documentation for the
MPS.
web Location of documentation support files.
htdocs HTML intro pages to access the library of
manuals or to start MPS Manager.
docfiles Location of manuals in pdf format.
fftX.X.X Field factory test scripts that test the MPS and Speech Server
components.
fftests Directory of field factory test scripts.
PERIfw A system library that enables platform-independent process
execution.
bin Executable file for PeriFrameWork.
lib Libraries for PeriFrameWork.
globlX.X.X Globally accessed directories and files, including libraries
and binaries used by all other packages.
include Files for user CALL functions (*.h).
misc Alarm database files and SRP
environment variable scripts.
sample Sample alarm files created through alarm
API.

hostpX.X.X Directories, files, and protocol software for communicating
with host computers.
etc Host protocol configuration files and
character sets.
misc Reserved for future use.
iexToolkit IEX MPS Developer tool kit files.
htmlsX.X.X Directories and files for the HTML Service daemon, which are
used to retrieve files from the Web and serve them to
applications.
ca Contains security certificates.
etc HTMLS Daemon configuration files.
ssl Contains Secure Socket Layer (SSL)
certificates and keys.
jsbX.X.X Directories and files for the Media Processing Server Java
Services Bridge, which allows applications written in MPS
Developer to access Java services.
com Subdirectories containing Java class
files.
docs MPS Java Services Bridge manuals.
etc MPS Java Services Bridge configuration
files.
etc-sample Additional configuration files.
misc Sample applications utilizing the MPS
Java Services Bridge.
mpsX.X.X Directories and files used by MPS processes and utilities.
etc Configuration files related to Least Cost
Router (LCR) daemon.
misc Startup and miscellaneous files required
for MPS functions and administration.
sample Sample MPS Developer applications.
verification Contains scripts and files for automated
verification of MPS functionality.
pdpX.X.X Directories and files used by the MPS Manager Data
Provider, which collects statistics and alarm data from nodes/
components in a MPS Manager network.
etc Configuration files for PERIpdp.
lib Libraries for PERIpdp.

perlX.X.X Directories and files used to integrate the Perl programming
language into the Avaya software.
bin Perl runtime environment executable.
lib Libraries and scripts for PERIperl.
plicX.X.X Directories containing files for licensing MPS software
packages.
etc Default location for the license file. Also
contains the license package log file.
pproX.XX Tool kit and configuration files, and directories for MPS
Developer processes and utilities.
conv Files used to convert apps from different
versions of MPS Developer.
icons48 Application-specific icons.
info User interface object help text files.
sample Sample MPS Developer application files.
prptX.X.X Directories and files used by MPS Reporter, which is the
statistics reporting and management interface.
etc Configuration and administration files.
images Graphics files used in tools.
launch Executable files to launch MPS Reporter
from MPS Manager.
lib MPS Reporter shared libraries.
reports Standard system report files.
stats Statistics-gathering scripts and log files.
pstuX.X.X Directories and files used by MPS Studio processes and
utilities. MPS Studio is the GUI tool used to create, manage,
and edit speech vocabularies stored in Multimedia Format
(MMF) files.
samples Contains sample audio files.
rdbX.X.X Directories and files used by MPS RDB for interaction with
Relational Data Base Management Systems.
snmpX.X.X Directories and files used by PeriSNMP processes and
utilities. PeriSNMP allows the control and monitoring of MPS
systems through a standard protocol, development of custom
applications, and integration of MPS products into existing
TCP/IP networks controlled by third-party management tools.

etc Stores MIB and configuration files during
installation.
misc Stores SNMP agent startup files during
installation.
tlktX.X.X Contains directories and files for Protocol Tool kits used by
MPS Developer applications.
cas Contains files for the CAS protocol tool kit
and sample applications.
dpnss Contains files for the DPNSS protocol
tool kit and sample applications.
h323 Contains files for the h323 protocol tool
kit and sample applications.
q931 Contains files for the q931 protocol tool
kit and sample applications.
sip Contains files for the SIP protocol tool kit
ss7 Contains files for the SS7 protocol tool kit
tmsX.X.X Directories and files used by the Telephony Media Server
(TMS) processes and utilities.
bin Solaris executable binaries and files, and
image files.
cfg Protocol configuration and image
definition files.
etc TMS data files.
lib TMS shared libraries.
misc Keyboard macro scripts and other files
used by Certified Avaya personnel for
testing purposes.
site-cfg Protocol configuration files and TMS
system configuration files copied to the
$MPSHOME/common/etc/tms directory.
viewX.X.X Directories and files used by MPS Manager, for running the
graphical tools used for system administration, operation,
and control.
comps Component JAR (Java ARchive) files.
etc Configuration files and subdirectory
containing current software tools images.

lib MPS Manager shared libraries.
treeplugins Plugin files for MPS Manager tools.
vxmlX.X.X Configuration files, took kit, and directories for VoiceXML
processes and utilities.
audio Contains sample audio file used by the
sample VoiceXML applications. The files
contained in this directory are copied to a
location behind the Apache web server
when the PERIvxml package is installed.
cache Contains the disk cache for VoiceXML
pages.
config Contains configuration files and default
settings.
etc Contains sample configuration files, and
environment settings for Solaris.
oscar Contains Speech Server related
configuration files. These files are used
by the vxml_oscar_setup.pl perl script.
samples Contains sample VoiceXML applications
vxmltoolkit Contains the MPS Developer toolkit for
interoperability with VoiceXML.
xmlcX.X.X Directories and files used by the Extensible Markup
Language (XML) call function, which provides access to XML
and HTML documents.
lib Contains libraries for the PERIxmlc
package.
samples Contains sample applications.
Chapter 10: Remote Desktop Connection and
pcAnywhere
pcAnwhere was the default method for remote support for Windows machines before the
Services for UNIX (SFU) set of utilties became available on the Windows platform. With the
introduction of SFU, Remote Desktop Connection (RDC) is the default method for remote
access on Windows machines.
All Windows Speech Servers and Application Processors that have SFU installed use RDC for
remote support and PPP for modem connections. Typically, these systems are manufactured
beginning with the MPS 3.0 Windows Beta release. For these systems, RDC is enabled by
default. If RDC is disabled, you must enable it before it can be used for support. You can use an
ethernet connection or modem for remote access. If a modem connection is required, the
Speech Server must be properly configured for PPP modem access.
Caution:
Symantec pcAnywhere cannot be installed, for any reason, on a node where the SFU utilities
reside. Installing pcAnywhere creates a conflict between pcAnywhere and the Avaya
software that produces system errors.
To determine if SFU is installed, you can check either of the following:
• By default, nodes that have the SFU utilities installed display the following shortcut on the
desktop.
• You can determine if SFU is installed by following the menu path Start > Programs >
Windows Services for Unix > C Shell.
If SFU resides on a node, pcAnywhere must not be used on that node.
The following provides an outline of the RDC topics covered in this section.
• Disable pcAnywhere on page 150
• Enable RDC for Administration on page 150
• Initiate an RDC Session on page 151
• Disconnect an RDC Session on page 152
• Transferring Files in an RDC Session on page 152
Remote Desktop Connection and pcAnywhere
• Sharing a Remote Console Session on page 153

• Enable Multiple RDC Hops from Single RDC on page 155
• Mount Client Drives on page 155
• Setting up a Windows 2003 Server for Remote Access Through PPP on page 157
• Setting up a Windows 2003 Client for Remote Access on page 164
Disable pcAnywhere
If pcAnywhere is enabled on your system, disable pcAnywhere by performing the following
steps:
1. Follow the menu path Start > Settings > Control Panel > Administrative Tools >
Services.
2. From Services, change the pcAnywhere Host Service to disabled.
Enable RDC for Administration

To enable RDC for administration, perform the following steps:
1. Log on to the system as an Administrator.
2. From the Control Panel, double-click System
3. From the Remote tab, select Allow users to connect remotely to your computer.
4. Click Ok.
The following graphic displays the Remote Desktop selection.
Initiate an RDC Session
Initiate an RDC Session

To initiate an RDC session, perform the following steps:
1. If necessary, establish a remote network connection to the remote product server
network, using either a VPN or a Remote Access Service (RAS) connection).
2. Open Remote Desktop Connection on the local computer by following the menu
path Start > Programs > Accessories > Communications > Remote Desktop
Connection.
3. In the Computer field, enter the computer name or IP address you want to connect
to.
4. Click Connect. The Log on to Windows dialog box is displayed.

5. At the Log on to Windows dialog box, enter the user name, password, and domain (if
required).
6. Click Ok.
Disconnect an RDC Session

To disconnect an RDC session, perform either of the following procedures.
Disconnect RDC Method 1
1. In the Remote Desktop Connection window, click Start, and then click Shut Down.
2. When the Shut Down Windows dialog box appears, click Log Off <username>.
3. Click Ok.
Disconnect RDC Method 2
1. In the Remote Desktop Connection window, click Start.
2. Click Log Off.
3. When the Log Off Windows dialog appears, click Log Off.
Transferring Files in an RDC Session

Before a file can be transferred between a local computer (the computer that is launching the
Remote Desktop Connection and making the remote support connection session) and the
remote system, the local disk drives on your local computer must be shared and made available
in the Remote Desktop Connection session.
To transfer a file in an RDC session, perform the following steps:
1. Open Remote Desktop Connection on your local computer.
2. Click Options in the Remote Desktop Connection window.
3. Click the Local Resources tab.
4. Select the Disk drives check box under the Local devices.
Sharing a Remote Console Session
5. Click Connect to start the Remote Desktop Connection session. If a Remote

Desktop Connection Security Warning dialog box is displayed, click Ok.
6. From the Remote Desktop Connection window, open My Computer (double-click
the My Computer icon or click Start > My Computer) on the remote system. When
Windows Explorer opens on the remote system, the drives on the remote server
and the drives on the local computer in the format of “<driveletter>" on
"<computername>" are displayed.
7. If you are transferring a file from the local computer to the remote system, do the
following:
a. From the Windows Explorer window of the local computer, select the file
you want to transfer.
b. Copy and paste the file to the target folder of the the remote system.
8. If you are transferring a file from the remote Symposium product server to the local
computer, do the following:
a. From the Windows Explorer window of the remote system, select the file
you want to transfer.
b. Copy and paste the file to the target folder on the local computer.
Sharing a Remote Console Session

The Remote Desktop Connection session on the local computer can be shared with the logged
on console session on the remote system (for example, a remote support engineer wants to
show the local technician on how to do something).
To share a remote console session, perform the following steps:

1. On the remote system, logon as an administrator.
2. Select Start > Run and enter gpedit.msc.
3. Click Ok.
4. When the Group Policy Object Editor dialog windows, double-click Administrative
Templates from Computer Configuration.
5. Double-click Windows Components.
6. Double-click Terminal Services.
7. Select and double-click Set rules for remote control of Terminal Services user
sessions from the Terminal Services Setting window.
8. Select Enable.
9. Select the desired rule from the Option list box.
If you select Full Control without user’s permission or View without user’s
permission, the Remote Desktop Connection session joins the logged on console
session without permission of the logged on user. Avaya recommends that you
select Full Control with user’s permission or View with user’s permission to ensure
that a Remote Desktop Connection session can join the console session with
permission of the logged on user.
10. Click Ok and close the Group Policy Object Editor.

11. Open a command prompt and enter gpupdate /force to activate the group policy.
Enable Multiple RDC Hops from Single RDC
12. On the local computer, initiate a Remote Desktop Connection session without
connecting to the console session.
13. Logon to the Remote Desktop Connection and connect to the remote system.
14. On the successfully connected Remote Desktop Connection session, open a
command prompt windows and enter shadow 0 to initiate console session sharing.
15. If the group policy on the remote system is set to Full Control with user’s permission
or View with user’s permission, the logged on console user on the remote system
is prompted to accept the connection request. Click Yes to accept the request.
The original Remote Desktop Connection logged on session is put on hold and your Remote
Desktop Connection display and keyboard are shared with the logged on console session on
the remote system.
If you log off a shared console Remote Desktop Connection session, the logged on console
user is logged off and you return to your original logged on Remote Desktop Connection
session.
If you disconnect a shared console Remote Desktop Connection session without logging off
the shared console session (for example, close the Remote Desktop Connection windows on
your local computer), your original logged on Remote Desktop Connection prior the shared
console session remains on hold. You should reconnect to the original Remote Desktop
Connection session and log off the session.
Enable Multiple RDC Hops from Single RDC

To enable multiple RDC hops from a single RDC session, perform the following steps:
1. From an existing RDC session, click Start > Run.
2. Enter mstsc and click Ok to enable RDC to connect to other systems.
Mount Client Drives

To mount client drives, do the following:
1. Open Remote Desktop Connection on the local computer.
2. Click Options in the Remote Desktop Connection Window.
3. Click the Local Resources tab.
4. Select the Disk drives check box under the Local devices.
5. Use Windows Explorer to view the local drives that are mounted on remote nodes.
The following diagram is an example.
Setting up a Windows 2003 Server for Remote Access Through PPP
Setting up a Windows 2003 Server for Remote Access

Through PPP
Before setting up a client for remote access you must ensure the modems for both the client
and the server platforms are properly installed, including the software driver. Only after
ensuring the modems are properly installed, can you set up the server for remote access.
Use the following procedures to set up the server for remote access.
Setting Routing and Remote Access to Automatic

Perform these steps to set the remote access of the server to automatic.
1. On the desktop, right-click My Computer and select Services and Applications.
2. The Computer Management window appears.
3. Select Services. The Services window appears.

4. Scroll down and select Routing and Remote Access.
5. The Routing and Remote Access Properties (Local Computer) window appears.
6. Click the General tab.

7. From the Startup type menu, select Automatic.
Note:
By default, Avaya sets the startup type to manual because it controls modem
access. Set this property to automatic only if you want to make PPP modem
connections to this platform.
Setting Up Inbound Modem Access
8. If necessary, click the Start button to start the service.

9. Click Apply and then click Ok.
10. Returning to the Services window, Routing and Remote Access is now set to
Automatic.
11. Close the Computer Management window.

Perform these steps to set up the inbound modem access for the server.
1. From the Start menu, go to Administrative Tools > Routing and Remote Access.
2. Select <Computer> (local) > Ports.
3. Ensure that the <computer> (local) icon displays a green up-arrow. The following
graphic is an example.
4. Right-click Ports and select Properties. The Ports Properties window appears.
5. Select Modem.
6. Click Configure. The Configure Device window appears.
7. Check the Remote access connections (inbound only) box.

8. Click OK.
This configures the device and returns you to the Ports Properties window.
9. Click Apply and then click OK.
Returning to the Ports section of the Routing and Remote Access window, the Used
By parameter is now set to RAS.
10. Right click <computer> (local) and select Properties. The <computer> (local)
Properties window appears.
11. Click the IP tab.

This process configures the IP space used by both the client and the server for ppp
connections.
12. Click Add or Edit. The Edit Address Range window appears.
13. In the Start IP address field, enter 10.7.101.250.
14. In the End IP address field, enter 10.7.101.251.

15. In the Number of addresses field, 2 automatically appears.
16. Click OK. This returns you to the <computer> (local) Properties window.
18. Close the Routing and Remote Access window.
Adding a New User

Perform the following steps to add a new user.
1. On the desktop, right-click My Computer and go to Manage > Local Users and
Groups > Users.
2. Right-click User and select New User. The New User window appears.
3. In the User name field, enter perippp.
Adding a New User
4. In the Description field, enter ppp user.

5. In the Password field, enter pPCON#1.
6. In the Confirm password field enter pPCON#1.
7. If User must change password at next login is checked, remove the check from the
box by clicking it.
8. Check the Password never expires box.
9. Click Create and then click Close.
This returns you to the Computer Management window.
10. Right-click perippp user and select Properties.

The perippp Properties window appears.
11. Click the Dial-in tab.
12. Check Allow access.

The Windows 2003 server is now setup for remote access through PPP.
Setting up a Windows 2003 Client for Remote Access

Before setting up a client for remote access you must ensure the following prerequisites are
met:
• The modems and software drivers for both the client and the server platforms must be
properly installed.
• The MPS 3.03.5 server must be configured to receive PPP connections to successful
verify operation of the client.
After ensuring the prerequisites are met, use the following procedure to set up a client to dial
into a Windows-based application server.
1. On the desktop, right-click My Network Places and select Properties from the menu.
2. Click Make New Connection.
The Connection Wizard window appears.
3. Click Next to continue.
The Network Connection Type window appears.
4. Select Dial-up to private network and click Next.
The Phone Number to Dial window appears.
5. In the Phone Number field, enter the dial-up phone number.
6. Click Next.
The Connection Availability window appears.
7. In the Connection Availability window, select For all users.
8. Click Next.
The Completing the Network Connection Wizard window appears.
9. In the Completing the Network Connection Wizard field, enter the name of the
connection (Dial-up Connection for example).
10. Click Finish.
You are now ready to verify the dial-up connection.
Verifying the Client Dial-up Connection
Note:
If you do not want to verify the dial-up connection now, click cancel.
11. Enter the following username and password in the fields provided.
User name: perippp
Password: pPCON#1
12. Click Dial. The following window appears.
The Dial-up connection is verified. The platform now resides on the server 10.7.x.x
subnet. You can now use RCD for a GUI interface.
Verifying the Client Dial-up Connection

To verify the client dial-up connection, perform the following steps.
Note:
If you verified the client dial-up connection when you set up the client dial-up, you do not
have to perform this procedure. This procedure is only for users who have not verified the
client dial-up connection.
1. On the desktop, right-click My Network Places and select Properties.
2. Click Dial-up Connection.
The Connect Dial-up Connection window appears.
3. Enter the following username and password in the fields provided.
User name: perippp
Password: pPCON#1
4. Click Dial.
The Connection Complete window appears.
The Dial-up connection is verified. The platform now resides on the server 10.7.x.x
subnet. You can now use RCD for a GUI interface.
Index
A ufsdump .............................................................120
bind. see assign .........................................................82
accessing a Media Processing Server shell
from a Solaris shell ..............................................46 C
accumulated summary phone line statistics report .... 72
activate
applications ..........................................................82 Call Control Manager (CCM)
system wide vocabulary files ...............................79 monitoring CCM status ........................................65
see also status monitoring ...................................82 call-protect troubleshooting ......................................133
alarms Caller Message Recording (CMR) ......................99, 101
alarm database, modifying ...................................51 activate a Multimedia file for ...............................101
alarm log file .........................................................49 creating a Multimedia file for ................................99
alarm viewer .........................................................49 CCM. see Call Control Manager (CCM) .....................65
customizing ..........................................................51 ccxmlX.X.X ...............................................................143
live and logged ...............................................37, 49 Central Processing Unit (CPU) ...................................38
application memory requirements ..............................77 checking for problems ................................................49
Application Services Environment (ASE) ...................20 CMR see Caller Message Recording .........................99
application statistics ...................................................37 commands
applications background and foreground .................................46
application programs ...........................66, 82, 84, 85 command control .................................................46
activate ..........................................................82 command line
configure ........................................................82 editing ............................................................44
deactivate ......................................................85 interaction ......................................................43
reordering ......................................................84 file listing ............................................................105
status .............................................................66 issuing ..................................................................46
application software troubleshooting ..................132 communication link .....................................................70
arrows, up and down ..................................................84 see also host ........................................................70
ASE. see Application Services Environment ..............20 components
assign .........................................................................82 icons .....................................................................53
monitoring component status .........................53, 72
monitoring components ........................................53
B
states defined .......................................................53
background commands ..............................................46 status monitoring from command line ..................53
see also commands .............................................46 status monitoring using MPS Manager ..........53, 72
backing up ....................106, 107, 109, 115–117, 122–124 configuration files ..................................................27, 82
cp .......................................................................123 default ..................................................................82
devices and options ...........................................106 controls, panel ......................................................30, 31
guidelines ...........................................................107 conventions
methods .............................................................109 manual .................................................................11
Multimedia elements ..........................................124 copy ..........................................................................123
restore ................................................................117 see also backing up ...........................................123
tar .......................................................................115 current component .....................................................46
ufsdump ..............................................................117 current Media Processing Server
ufsrestore ...........................................................122 status ...................................................................46
verify ...........................................................116, 122 current working directory
vocabulary elements ..........................................124 See also present working directory (pwd) ..........104
backing up partitions customer service ..........................................................8
D file listing and removal ..............................................105
file synchronization
date, checking ............................................................51 troubleshooting ...................................................130
deactivate, applications ..............................................85 files, configuration .................................................27, 82
defining component states .........................................53 foreground commands ...............................................46
detail phone line statistics report ................................72 see also commands .............................................46
detail span statistics report .........................................72 front panel .............................................................30, 31
detail system statistics report .....................................72
directory structure ......................................104, 137, 143 G
MPSHOME .........................................................137
bin ................................................................137 Graphical User Interface (GUI) .............................19, 22
common .......................................................137
defaults ........................................................137
lib .................................................................137 H
mpsN ...........................................................137
PERI(name) .................................................137 hash table ...................................................................81
tmscommN ..................................................137 see also vocabulary files ......................................81
packages ............................................................143 history .........................................................................44
PERIase ......................................................143 host
PERIbrdge ...................................................143 communication troubleshooting ..................130, 133
PERIdoc ......................................................143 monitoring host status ..........................................70
PERIfft .........................................................143 HostDetail.prd .............................................................72
PERIfw .........................................................143 HostSum.prd ..............................................................72
PERIglobl .....................................................143 How To
PERIhostp ...................................................143 activate a Multimedia file for recording ...............101
PERIhtmls ....................................................143 activate application-specific Multimedia files .......81
PERIjsb ........................................................143 activate system wide Multimedia files ..................80
PERImps .....................................................143 back up multimedia elements .............................124
PERIpdp ......................................................143 back up partitions with ufsdump .........................120
PERIperl ......................................................143 back up with tar ..................................................115
PERIplic .......................................................143 back up with ufsdump (across a network) ..........117
PERIppro .....................................................143 back up with ufsdump (locally) ...........................117
PERIprpt ......................................................143 check the status of applications ...........................66
PERIpstu .....................................................143 check the status of audio elements ......................68
PERIrdb .......................................................143 create a Multimedia Format file for CMR .............99
PERIsnmp ...................................................143 customize alarms .................................................51
PERItlkt ........................................................143 deactivate Multimedia Format files using the
PERItms ......................................................143 Command Line ........................................86
PERIview .....................................................143 deactivate Multimedia Format files using the MMF
PERIxmlc .....................................................143 Configurator Tool .....................................86
distributor .....................................................................8 generate statistics reports ....................................72
documentation ..............................................................8 log off/back onto a node .......................................38
monitor alarms .....................................................49
monitor component status ....................................53
E monitor host status ...............................................70
monitor phone lines ..............................................56
editing, command line ................................................44 monitor span status ..............................................58
exit, X-windows ..........................................................38 reorder selected application locations ..................84
replace a vocabulary (offline) ...............................90
F replace a vocabulary (online) ...............................90
restart MPS Manager ...........................................29
faults, categories ......................................................125 restore files with tar ............................................117
restore multimedia elements ..............................124 MPS Reporter Tools, launching ...........................72
restore with ufsrestore ........................................122 Span Status tool, launching .................................58
shut down the system ..........................................38 starting .................................................................29
start up the system ...............................................27 MPS Reporter Tools
start/restart MPS Manager ...................................29 generating reports ................................................72
update elements in a vocabulary .........................92 launching ..............................................................72
verify a tar backup ..............................................116 Multimedia elements
verify a ufsdump backup ....................................122 backing up ..........................................................124
view alarms ..........................................................49 Multimedia files
view the SRP log file ..........................................134 deactivating ..........................................................86
zap a Multimedia File ...........................................94 monitoring ............................................................68
zap a specific element .........................................94 status of ...............................................................68
zap Multimedia Files on a proxy basis .................94 synchronizing across nodes .................................94
multitasking ................................................................46
I
N
indicators, panel ....................................................30, 31
network architecture ...................................................19
node
L and workstation ..............................................19, 20
launching defined ............................................................19, 20
Application Management tool ...............................66 node, log on/off ...........................................................38
Host Status tool ....................................................70
MPS Reporter Tools .............................................72 O
Span Status tool ...................................................58
launching MPS ReporterTools ....................................72 Online documentation ................................................48
link, communication ....................................................70
see also host ........................................................70 P
listing, files ................................................................105
local ............................................................................46 phone line
log files, SRP ............................................................134 monitoring ............................................................56
log on/off .....................................................................38 status ...................................................................56
logoff ...........................................................................38 troubleshooting ...................................................130
PhoneAcc.prd .............................................................72
PhoneDetail.prd ..........................................................72
M
PhoneSum.prd ...........................................................72
Media Processing Server Series network power-up state, normal ...............................................31
naming conventions .............................................20 present working directory (pwd) ...............................104
overview ...............................................................17 see also current working directory .....................104
Media Processing Server Shell .......................43, 46, 48 pwd
memory requirements ................................................77 see also current working directory .....................104
MMF see present working directory (pwd) ..................104
See also Multimedia files .....................................94
monitoring R
alarms ..................................................................49
see also status monitoring ...................................49 RCD status .................................................................65
monitoring RCD status ...............................................65 rebooting the system ..................................................38
monitoring system parameters .............................30, 31 recording a message. see Caller Message Recording ...
MPS Manager ................................22, 29, 58, 66, 70, 72 99
Application Management tool, launching .............66 rectifying MMFs ..........................................................92
Host Status tool, launching ..................................70 Redundancy Configuration Daemon (RCD) ...............51
redundancy troubleshooting .....................................133 time ......................................................................51
remote ........................................................................46 VMM .....................................................................68
remote desktop client vocabulary files ....................................................68
shutdown Windows ..............................................40 status, Media Processing Server ................................46
removing, files ..........................................................106 stop applications. see applications, application
reordering applications assignment/starting ...............84 programs, terminate ......................................85
replacing vocabulary files .....................................89, 94 summary phone line statistics report ..........................72
reseller .........................................................................8 summary span statistics report ...................................72
restart Windows ..........................................................40 summary system statistics report ...............................72
restarting the system ..................................................38 system
restore. see backing up ............................................117 date, checkingtime, checking ...............................51
restoring generate statistics reports for ...............................72
methods .............................................................109 overview ...............................................................17
rebooting ..............................................................38
S restarting ..............................................................38
startup ..................................................................27
shell statistics ...............................................................37
types ....................................................................43 system shutdown .................................................38
shutdown tasks for system operator .....................................18
system ..................................................................38 time, checking ......................................................51
SMC ...........................................................................52 system monitoring .................................................30, 31
SpanDetail.prd ............................................................72
spans
status monitoring T
from command line ........................................58
tar
using MPS Manager ................................58, 65
backup ................................................................115
SpanSum.prd .............................................................72
restore ................................................................117
SRP
verify ...................................................................116
log files ...............................................................134
telephone line. see phone line ..................................130
see also Startup and Recovery Process (SRP) ....
Telephony Media Server (TMS) ..................................20
52
terminate, application programs .................................85
start applications. see applications, application
TMS. see Telephony Media Server ............................20
programs, assign and start ............................82
training .........................................................................8
Startup and Recovery Process (SRP)
troubleshooting ...........................125, 127, 130, 132, 133
monitoring SRP status .........................................52
application software ...........................................132
startup, system ...........................................................27
call-protect ..........................................................133
states of components .................................................53
file synchronization .............................................130
statistics
host communication ....................................130, 133
application ............................................................37
redundancy ........................................................133
system ..................................................................37
telephone line .....................................................130
statistics reports .........................................................72
vocabulary files ..................................................127
generating ............................................................72
status monitoring .................51–53, 56, 65, 66, 68, 70, 72
applications ..........................................................66 U
CCM .....................................................................65
components ....................................................53, 72 ufsdump
date ......................................................................51 backup ................................................................117
host ......................................................................70 backup partitions ................................................120
Multimedia files ....................................................68 options for ...........................................................117
phone line ............................................................56 verify ...................................................................122
RCD .....................................................................65 ufsrestore ..................................................................122
SRP ......................................................................52 unassign .....................................................................85
up and down arrows ...................................................84 monitoring VMM status ........................................68
updating vocabulary files ...........................89, 90, 92, 94 Voice Operating Software (VOS) ................................20
elements, one or more .........................................92 VOS. see Voice Operating Software (VOS) ...............20
replace entire file ..................................................90
using MPS Manager ...................................................22
W
V Windows
restart ...................................................................40
VDM. see Voice Data Memory (VDM) ........................86 shutdown ..............................................................40
verify, backup .....................................................116, 122 workstation
viewing alarms ............................................................49 and node ........................................................19, 20
VMM. see Voice Memory Manager (VMM) ................68 defined ............................................................19, 20
vocabulary files
activate system wide ............................................79
backing up elements in ......................................124 X
deactivate .............................................................86
X-windows, exiting ......................................................38
monitoring ............................................................68
replacing ..............................................................90
status of ...............................................................68 Z
troubleshooting ...................................................127
updating and replacing ...................................89, 94 ZAP ..........................................................89, 92, 94, 130
updating elements in ............................................92 troubleshooting ...................................................130
Voice Data Memory (VDM) .........................................86 Zero Administration for Prompts
Voice Memory Manager (VMM) See ZAP ...............................................................89

Operator Guide MPS500

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Operator Guide MPS500

Uploaded by

Copyright:

Available Formats

Avaya Media Processing Server System

Licenses Contact Avaya Support

2 Avaya Media Processing Server System Operator Guide August 2010

Chapter 3: System Startup, Monitoring and Shutdown.......................................................25

Chapter 4: Command Line Functions....................................................................................43

Avaya Media Processing Server System Operator Guide August 2010 3

Chapter 6: Voice Processing Applications............................................................................77

Chapter 7: Backing Up and Restoring Files........................................................................103

4 Avaya Media Processing Server System Operator Guide August 2010

Chapter 9: MPS Directory Structure....................................................................................137

Chapter 10: Remote Desktop Connection and pcAnywhere.............................................149

Avaya Media Processing Server System Operator Guide August 2010 5

Avaya Media Processing Server System Operator Guide August 2010 7

Getting help from a distributor or reseller

Getting product training

Getting technical documentation

Getting technical support from the Avaya Web site

8 Avaya Media Processing Server System Operator Guide August 2010

How to Use This Manual

Organization of This Manual

Chapter 2--System Startup, Monitoring and Shutdown

Avaya Media Processing Server System Operator Guide August 2010 9

Chapter 3--Command Line Functions

Chapter 4--Status Monitoring

Chapter 5--Voice Processing Applications

Chapter 6--Backing up and Restoring Files

Chapter 8--Printer and Modem Setup

Appendix A--MPS Directory structure

10 Avaya Media Processing Server System Operator Guide August 2010

Appendix B--Remote Desktop Connection

Conventions Used in This Manual

The Caution icon identifies procedures or events that require special

Avaya Media Processing Server System Operator Guide August 2010 11

The Solaris icon identifies procedures or events that apply to the

Solaris and Windows Conventions

Command <command> & start /b <command>

12 Avaya Media Processing Server System Operator Guide August 2010

Two-Button (Windows) versus Three-Button (Solaris)

Product Nomenclature Changes

Avaya Media Processing Server System Operator Guide August 2010 13

Former Product Name New Product Name

HylaFAX Facsimile Software

14 Avaya Media Processing Server System Operator Guide August 2010

OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR

Avaya Media Processing Server System Operator Guide August 2010 15

This chapter covers:

Avaya Media Processing Server System Operator Guide August 2010 17

database access, host screen scrape access, Communications Control Toolkit

System Operator Tasks

18 Avaya Media Processing Server System Operator Guide August 2010

Avaya Media Processing Server System Operator Guide August 2010 19

Single Media Processing Server

A Media Processing Server node is the basic building block of

20 Avaya Media Processing Server System Operator Guide August 2010

Multiple Media Processing Servers

Figure 1: Media Processing Server Series Network

Avaya Media Processing Server System Operator Guide August 2010 21

MPS Manager performs the following various functions:

22 Avaya Media Processing Server System Operator Guide August 2010

Avaya Media Processing Server System Operator Guide August 2010 23

This chapter covers:

System Startup, Monitoring, and Shutdown

Command/Function Use to... Why?

Avaya Media Processing Server System Operator Guide August 2010 25