Avaya Glossary of Media Processing Server Terminology User Manual

Glossary of Avaya Media Processing Server Series Terminology (Software Release 2.1)
Avaya Business Communications Manager
Release 6.0
Document Status: Standard Document Number: P0602812 Document Version: 1.3 Date: May 2010
© 2010 Avaya Inc. All Rights Reserved.
Notices
While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes.
Documentation disclaimer
Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya, Avaya’s agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages.
Warranty
Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language, as well as information regarding support for this product, while under warranty, is available to Avaya customers and other parties through the Avaya Support Web site: http://www.avaya.com/support
Please note that if you acquired the product from an authorized reseller, the warranty is provided to you by said reseller and not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE RIGHT TO T AKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END USER"), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ("AVAYA").
Copyright
Except where expressly stated otherwise, no use should be made of the Documentation(s) and Pr oduct( s) p rovided by Avaya. All content in this documentation(s) and the product(s) pr ov id ed by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected b y copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law.
Third Party Components
Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms" ). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://support.avaya.com/Copyright.
Trademarks
The trademarks, logos and service marks ("Marks") displayed in this site, the documentation(s) and product(s) pr ovided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from A vaya or such third party which may own the Mark. Nothing contained in this site, the documentation(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-Avaya
trademarks are the property of their respective owners.
Downloading documents
For the most current versions of documentation, see the Avaya Support. Web site: http://www.avaya.com/support
Contact Avaya Support
Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://
www.avaya.com/support

Preface

Glossary of Avaya MPS Series Terminology

Scope

The Glossary of Avaya Media Processing Server (Avaya MPS) Series Terminology defines terms specific to the programming, operations, and documentation of the Avaya MPS Series system.
This document does not deal with terminology that applies to computer systems in general, unless those terms have a specific connotation in the Avaya MPS Series environment or contribute to the understanding of its terms.
This document provides only general overviews for any term or concept. For more detailed information and context, refer to the other Avaya MPS Series reference material.

Intended Audience

This manual is intended for all Avaya MPS Series users. The Glossary of Avaya MPS Series Terminology assumes that readers have attended one or more onsite Avaya MPS Series training courses.

How to Use This Manual

Use the Glossary of Avaya MPS Series Terminology to quickly look up Avaya MPS Series terms. Follow cross references to related and contrasting terms, if necessary. Many definitions also refer to additional Avaya MPS Series documentation. Refer to these documents for more details on these terms.
Initially, you should read this manual at least once, from start to finish. Later, you can use the Table of Contents to locate topics of interest for reference and review.
If you are reading this document online, use the cross-reference links (shown in blue) to quickly locate related topics. <L with your cursor over the cross-reference link. Click on any point in a Table of Contents entry to move to that topic. Click on the page number of any Index entry to access that topic page.
To familiarize yourself with various specialized textual references within the manual, see Conventions Used in This Manual on page 5.
Periphonics is part of Avaya. The name Periphonics, and variations thereof, appear in this manual only where it is referred to in a product. (For examples, a PeriProducer application, the PERImps package, the perirev command, etc.)
EFT> click once with your mouse while positioned
Page 4 # P0602812 Ver: 1.3

Organization of This Manual

The Glossary of Avaya MPS Series Terminology is in alphabetical order by term. Cross references to additional documentation and related and contrasting terms follow each definition.
Acronyms are also listed alphabetically. This manual includes the definition with the acronym; the entire term is a reference to the acronym.

Conventions Used in This Manual

This manual uses different fonts and symbols to differentiate between document elements and types of information. These conventions are summarized in the following table.
Conventions Used in This Manual Sheet 1 of 2
Notation Description
Normal text
important term
system command
command, condition
and alarm
file name / directory
on-screen field
<KEY NAME>
Book Reference
Normal text font is used for most of the document.
The Italics font is used to introduce new terms, to highlight meaningful words or phrases, or to distinguish specific terms from nearby text.
This font indicates a system command and/or its arguments. Such keywords are to be entered exactly as shown (i.e., users are not to fill in their own values).
Command, Condition and Alarm references appear on the screen in magenta text and reference the Command Reference Manual, the PeriProducer User’s Guide, or the Alarm Reference Manual, respectively. Refer to these documents for detailed information
Commands, Conditions, and Alarms.
about
This font is used for highlighting the names of disk directories, files, and extensions for file names. It is also used to show displays on text-based screens (e.g., to show the contents of a file.)
This font is used for field labels, on-screen menu buttons, and action buttons.
A term that appears within angled brackets denotes a terminal keyboard key, a telephone keypad button, or a system mouse button.
This font indicates the names of other publications referenced within the document.
cross reference
A cross reference appears on the screen in blue text. Click on the cross reference to access the referenced location. A cross reference that refers to a section name accesses the first page of that section.
The Note icon identifies notes, important facts, and other keys to understanding.
# P0602812 Ver: 1.3 Page 5
Glossary of Avaya MPS Series Terminology
Conventions Used in This Manual Sheet 2 of 2
Notation Description
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.
The flying Window icon identifies procedures or events that apply to the Windows 2000 operating system only.
The Solaris icon identifies procedures or events that apply to the Solaris operating system only.
a. Windows 2000 and the flying Window logo are either trademarks or registered
trademarks of the Microsoft Corporation.
b. Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the
United States and other countries.

Solaris and Windows 2000 Conventions

This manual depicts examples (command line syntax, configuration files, and screen shots) in Solaris format. In certain instances Windows 2000 specific commands, procedures, or screen shots are shown where required. The following table lists examples of general operating system conventions to keep in mind when using this manual with either the Solaris or Windows 2000 operating system.
a
b
Solaris Windows 2000
Environment $MPSHOME %MPSHOME%
Paths $MPSHOME/common/etc %MPSHOME%\common\etc
Command <command> & start /b <command>
Page 6 # P0602812 Ver: 1.3

Trademark Conventions

The following trademark information is presented here and applies throughout for third party products discussed within this manual. Trademarking information is not repeated hereafter.
Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.
Microsoft, Windows, Windows 2000, Internet Explorer, and the Flying Windows logo are either trademarks or registered trademarks of Microsoft Corporation.
Netscape® and Netscape Navigator® are registered trademarks of Netscape Communications Corporation in the United States and other countries. Netscape's logos and Netscape product and service names are also trademarks of Netscape Communications Corporation, which may be registered in other countries.
# P0602812 Ver: 1.3 Page 7
Glossary of Avaya MPS Series Terminology
This page has been intentionally left blank.
Page 8 # P0602812 Ver: 1.3
Glossary of Avaya Media
Processing Server Series
Terminology

Glossary of Avaya MPS Series Terminology 24-byte header

Numerics

24-byte header The host communications protocol format was used by Periphonics'
earlier generation of equipment.
In this format, a header that is 24 bytes in length precedes the actual message data. The header consists of a message ID, phone line number, status and control fields, etc.
The Avaya Media Processing Server (Avaya MPS) supports this type of message exchange format for compatibility reasons and also for the fact that this format has been proven to be efficient and effective over time. Avaya can supply an application program that implements the Avaya MPS portion of this message exchange. Internally, the system converts the 24-byte header into a PACE structure. The application program then processes these PACE commands. The 24-byte header mode is typically utilized to maintain backward compatibility with Avaya’s earlier generations of systems.
See also PAC E, host.

1TR6 An Avaya MPS-supported digital interface where signaling is

performed using a dedicated channel.
Also known as German ISDN.
For additional information, see the Avaya MPS Telephony Reference Manual.
See also digital, channel, ISDN.
Page 10 # P0602812 Ver: 1.3

Active Call

A

ABCD-bit signaling The data transmission technique used in most digital/T1 transmission

links. One bit “robbed” from each of 24 channels in every 6th frame carries dialing and controlling information.
Contrast with out-of-band signaling.
For additional information, see the Avaya MPS Telephony Reference
Manual
See also digital, channel.
ACB Application Control Block. An instance of an ACB is created every
time an application registers, and is destroyed every time an application unregisters. ACB contains both an AEQ (Application Event Queue) and an ECT (Event Callback Table).
See also AEQ, ECT.
ACD Automatic Call Distributor is a phone system that specializes in
handling incoming calls. Its functions are,
to answer calls
search the database for instructions on where to send the call
forward the call to a Voice Response Unit (VRU) that informs the caller about the processing
and then route the call to the correct location.
See also VRU.
Active Call The state of a call that is not in a Hold, Null, or Queued state. A call
that has an established connection.
# P0602812 Ver: 1.3 Page 11

Glossary of Avaya MPS Series Terminology Activity Monitor

Activity Monitor Activity Monitor is the PeriView tool that:
graphically represents PLM status for Avaya MPS systems and applications.
monitors and graphically displays linked application activity.
monitors and graphically displays host activity
Status toolbar:
Activity is depicted by a set of graphs updated in near real time. Select from four types of graphs: a pie graph, a stacked bar graph, a bar graph measuring activity by percent, and a bar graph measuring activity in absolute numbers.
For additional information, see the Avaya MPS PeriView Reference Manual.

Adaptive Differential PCM

administrative application

See also PeriView, PeriView tools, application, PLM, linked
application, host.
See ADPCM.
An auxiliary Avaya MPS program that supports other applications in the system. It is also known as an administrative program. For instance, an administrative application program determines the action to be taken when a call processing application receives a high water mark or a low water mark during Caller Message Recording. You can also use administrative applications to parameterize various aspects of a system’s operations based on the user requirements.
Generally, only administrative applications are assigned to administrative lines. They only need a call processing line if the particular application interacts with callers.
For information on configuring and assigning applications to lines, see the Avaya MPS PeriView Reference Manual.
Contrast with call processing application.
See also main application, application, high water mark, low water
mark, CMR, assign, administrative line, call processing line.
Page 12 # P0602812 Ver: 1.3

AID keys

administrative line A logical telephone line used only to run administrative applications.

There is no physical phone line connection for an administrative line.
Contrast with call processing line.
See also call processing, administrative application.

administrative program See administrative application.

ADPCM Adaptive Differential Pulse Code Modulation. The encoding

scheme used by analog Avaya MPS systems to compress the speech signal.
This format is based on hardware that is available from OKI Semi­conductor. ADPCM uses a 4-bit voice data encoding scheme. This results in a data rate of 32K bits/second.
For additional information, see the Avaya MPS PeriStudio User’s Guide.
Contrast with a-law, u-law.
See also analog, PCM.

ADSI Analog Display Services Interface. The Bellcore standard protocol

for use with screen telephones.
You can use PeriMap to create ADSI-compatible displays.
See also PeriMap.
AEQ Application Event Queue. This is used by an application to receive
events from the MX subsystem. As an event occurs, it is placed on the end of the (MX application’s) AEQ until the application is ready to process the event. The application receives service events by removing them from the front of the AEQ.
See also MX.
AID keys Attention Identifier keys. Special keystrokes that are interpreted by
the host computer, such as Program Function and Program Attention.
The set of valid AID keys varies depending on the particular protocol. In some cases, the use of these keys is equivalent to commands that send screen maps or text streams. AID keys are usually issued by applications.
See also host, application.
# P0602812 Ver: 1.3 Page 13

Glossary of Avaya MPS Series Terminology ALARM

ALARM The text-based utility used to display the alarms that are broadcast by
ALARMD.
ALARM is a non-interactive application that simply displays the alarm message text received from ALARMD running on the Avaya MPS with which ALARM is currently associated. This translation facility uses the alarm database to convert system and user-created messages to the proper format for displaying and logging.
For additional information about ALARM, see the Avaya MPS System Reference Manual.
Contrast with Alarm Viewer.

See also ALARMD.

ALARMD The alarm daemon. ALARMD is the software process responsible for
collecting alarm messages, writing them to the alarm log, and forwarding alarms to the Avaya MPS alarm viewers.
The alarm log (alarm.log) and its backup file (alarm.log.bak) are located in the directory $MPSHOME/ mpsN/log.
The Alarm Viewer and/or ALARM process displays the alarm information gathered by ALARMD.
For additional information about ALARMD, see the Avaya MPS System Reference Manual.
See also ALARM, Alarm Viewer.

Alarm Monitor Panel See AMP-2000.

Page 14 # P0602812 Ver: 1.3
ALI

Alarm Viewer The Alarm Viewer tool is used to log alarms and view live and logged

alarms.
The filtering mechanism will allow you to selectively display alarms in the Viewer. The logging facility will allow you to create user­defined historical alarm log files. You can also apply filters to control the actual alarms that display in the viewer windows.
It is also known as the Viewer.
For additional information, see the Avaya MPS PeriView Reference Manual.
Contrast with ALARM.
See also PeriView, PeriView tools.

a-law The data compression scheme used by Avaya MPS systems with an

E1/CEPT interface.
A-law is the CCITT standard for 8-bit PCM digital signals used in countries other than the U.S., Canada, and Japan. This format offers superior fidelity and dynamic range. When processed, the 8-bit signal is expanded to 13 bits. The supported transmission rate is 64K bits/ second.
For additional information, see the Avaya MPS PeriStudio User’s Guide.
Contrast with ADPCM, u-law.
See also digital.
ALI Analog Line Interface. A phone line interface to the system for upto
24 analog phone lines. It connects to the PSTN via an RJ48X connector on the front panel. Up to four ALIs can be installed in a TMS, although three is typical since one of the four TMS slots is usually occupied by an MDM. ALIs cannot be combined with a DCC in the same TMS.
See also DCC, PSTN, TMS.
# P0602812 Ver: 1.3 Page 15

Glossary of Avaya MPS Series Terminology Alphanumeric IWR

Alphanumeric IWR Alphanumeric Isolated Word Recognition. The Avaya MPS shared
resource that allows applications to recognize a vocabulary made up of digits from zero to nine, letters, and specific command words including “stop” and “clear.” Alphanumeric IWR serve applications in which numbers, letters, and certain words need to be recognized over the telephone or where touch-tone service is not available.
For an application that uses Alphanumeric IWR to achieve a high recognition accuracy rate, the recognizer must use a database of alphanumeric entries to match against the spoken input string. You can manipulate these databases from the command line or through shell scripts.
Also known as IWR_AN.
For information about configuring Alphanumeric IWR, see the Avaya MPS System Reference Manual. For information about coding applications that use Alphanumeric IWR, see the Avaya MPS Application Programming Reference Manual.
See also shared resources.

alternate key A method of accessing data in a database without using the primary

key. Alternate keys provide alternate views (and retrieval/update sequences) of the records in the file. Accessing data using an alternate key is similar to accessing a normal keyed record (that is, the alternate key is used and the base file record matching the alternate key is returned), unless records having non-unique alternate keys are involved.
Indexed files support alternate key access.
Contrast with primary key.
See also database, key, indexed.

AMP-2000 Alarm Monitor Panel 2000 is a hardware component that provides

physical environment indicators and audio device connection functions. The AMP-2000 resides physically outside of the TMS on the Avaya MPS front panel. It has several status LEDs that monitor the status of the system for major and minor alarm conditions, airflow, power, temperature, etc.
For additional information about the AMP-2000, see the Avaya MPS
System Reference Manual and the Avaya MPS PeriStudio User’s Guide.
See also Avaya MPS, TMS.
Page 16 # P0602812 Ver: 1.3
API

analog A telephone interface that supports a continuously variable signal.

That is, the signal is a wave similar to the sound that originally generated it.
The Avaya MPS supports several analog interfaces, including:
loop start
ground start
•DID
Contrast with digital.
For additional information, see the Avaya MPS Telephony Reference Manual.

Analog Display Services Interface

Analog Line Interface See ALI.

ANI Automatic Number Identification. Information obtained by an
API Application Program Interface is a set of formalized software calls
See ADSI.
application through an indial string, giving the protocol the telephone number of the party originating the call.
Contrast with DNIS.
For additional information, see the Avaya MPS Telephony Reference Manual.
and routines with which a program can access underlying network services. It provides a standard way of connecting an Avaya MPS­specific software application to more general purpose or commercial applications.
For additional information, see Avaya MPS SNMP Package User’s
Guide.
# P0602812 Ver: 1.3 Page 17

Glossary of Avaya MPS Series Terminology application

application An Avaya MPS program and its associated object code, data, and
MultiMedia files (MMF). An application is dedicated to voice processing functionality.
Use PeriProducer to write, generate, and test applications.
Use APPMAN to configure, assign, and start applications.
You can configure applications as main or linked.
For additional information about PeriProducer, see the Avaya MPS PeriProducer User’s Guide.
For additional information about APPMAN, see the Avaya MPS PeriView Reference Manual.
See also APPMAN, assign, generate, MMF, PeriProducer, main
application, linked application.

Application Control Block

Application Event Queue

Application Manager See APPMAN.

Application Program Interface

application statistics Application-specific data generated during an application’s execution

See ACB.
See AEQ.
See API.
cycle.
Application statistics must be defined within each application and identified as a stat event to the Avaya MPS Statistics Update Daemon (VSUPD).
You can create, maintain, and view application statistics with PeriReporter.
For information about defining statistics in an application, see the Avaya MPS PeriProducer User’s Guide. For information about PeriReporter, see the Avaya MPS PeriReporter User’s Guide.
Contrast with system statistics.
See also application, PeriReporter, Avaya MPS.
Page 18 # P0602812 Ver: 1.3

Application Services Environment

application type The functional level of an Avaya MPS program (that is, main or

linked).
Use the APPMAN Configure Applications tool to configure applications as linked or main.
Contrast with execution type.
See also application, APPMAN, linked application, main
application.
Application Services Environment
See ASE.
# P0602812 Ver: 1.3 Page 19

Glossary of Avaya MPS Series Terminology APPMAN

APPMAN APPMAN is the PeriView tool used to:
assign applications to phone lines (Assign/(Re)Start Lines tool)
start applications (Assign/(Re)start Lines tool)
terminate applications (Terminate/Un-Assign Lines tool)
unassign applications from phone lines (Terminate/Un-Assign Lines tool)
configure an application’s run-time environment (Configure Applications tool)
display application and Avaya MPS status information (Status tool)
control the default application assign/start order (Line Start Order During Reboot tool)
delete unnecessary application and shared library files (File Maintenance tool)
See also PeriView, PeriView tools, application, assign, start,
terminate, unassign.
ASE Application Services Environment. The group of software required
to develop and execute applications. ASE is made up of the independently running processes VENGINE, VMST, and VSUPD.
For additional information about ASE, see the Avaya MPS System Reference Manual.
See also VENGINE, VMST.
ASR Automatic Speech Recognition. Automatic Speech Recognition. It
refers to software tools/programs that are used to "recognize" spoken words.
ASR requires a VRP board. Access the ASR feature through the PeriProducer Resource block.
See also PeriProducer, shared resources, VRP.
Page 20 # P0602812 Ver: 1.3
AT M

assign To associate an application with a phone line. The assign process

copies an application’s executable (*.vex), configuration (*.acfg), and shared library (*.so) files to the appropriate location. Use the APPMAN Assign/(Re)Start Lines tool to assign applications to lines.
For information about APPMAN, see the Avaya MPS PeriView
Reference Manual.
Contrast with unassign.
See also application, APPMAN.

async See asynchronous protocol.

asynchronous host An external computer system that uses an asynchronous protocol.

See also asynchronous protocol, host.

asynchronous message delimiters

asynchronous protocol Data transmission guidelines that do not rely on timing mechanisms.

Start-of-line and end-of-line characters used on an asynchronous communications line.
A start-of-line character is optional, but an end-of-line character is required. Typically, the defaults of "{" for sol and "}" for eol are overridden with a sol specification of 0 and a eol specification of carriage return (hex 0D) or line feed (hex 15). For screen mode, sol = eol = 0.
See also asynchronous protocol, screen mode.
Message delimiters signal the start and end of each line.
The Avaya MPS supports asynchronous protocols including PACE, 24-byte header, and rawtty.
Contrast with synchronous protocol.
See also PAC E, 24-byte header, rawtty, asynchronous message
delimiters.

Asynchronous Telnet Terminal Emulation

ATM
# P0602812 Ver: 1.3 Page 21
See ATTE.
Asynchronous Transfer mode that can carry voice, video, and data, can also be used as the basis for LANs and WANs.

Glossary of Avaya MPS Series Terminology AT T E

ATTE Asynchronous Telnet Terminal Emulation. The communications
program used to manage Telnet sessions and perform VT100 emulations. Telnet refers to the standard UNIX Telnet process. It provides a TCP/IP connection to remote host systems that follow the Telnet protocol.
ATTE is present only if the Avaya MPS is configured to communicate with an ATTE host.
Up to 64 concurrent Telnet sessions are possible per ATTE process. However, this is dependent on available UNIX system resources, CPU, memory and the amount of swap space over and above application requirements.
For additional information about ATTE, see the Avaya MPS System
Reference Manual.
See also VT100, Te ln et, MPS command man page atte intro.

Attention Identifier keys See AID keys.

Page 22 # P0602812 Ver: 1.3

Avaya MPS 1000

attribute byte A data character that precedes each field definition on a formatted

screen (map).
Attribute bytes designate the field as:
protected - applications can not modify the field
unprotected - applications can modify the field
askip - the cursor skips over the field
num - numeric, right justified and zero filled
Use PeriMap to create maps and set the attribute byte.
For additional information, see the Avaya MPS PeriProducer User’s Guide.
See also PeriMap, screen mode.

Automatic Call Distributor

Automatic Number Identification

Automatic Speech Recognition

Avaya MPS Avaya Media Processing Server. The hardware and software needed

Avaya MPS 1000 Avaya Media Processing Server (Avaya MPS) 1000. A cabinet-
See ACD.
See ANI.
See ASR.
to create a call processing environment. The Avaya MPS Series is made up of a series of MPSs running on different nodes. The Avaya MPS component consists of Avaya MPS software (including ASE and VOS) and a TMS. One TMS is required for each Avaya MPS component defined on a node.
See also Avaya MPS 1000, TMS.
enclosed Avaya MPS Series network configuration, available on both the Windows2000 and Solaris platforms. The Avaya MPS 1000 contains four TMSs per chassis and up to four chassis per cabinet. It can support 10,000 ports with the ability to bridge between any two, regardless of the chassis the ports are in with respect to each other. The Avaya MPS 1000 consists of a Solaris or Windows 2000 host node running operating system and Avaya MPS software, and one or more TMSs responsible for the bulk of telephony processing.
See also TMS.
See also Avaya MPS, ASE, VOS, VENGINE.
# P0602812 Ver: 1.3 Page 23

Glossary of Avaya MPS Series Terminology Basic Map Support

B
Basic Map Support See BMS.

baud rate The communication link’s rate of data exchange expressed in bits per

second.
Avaya MPS comm. boards support baud rates from 300 to 19,200. BSC 3270 supports baud rates up to 9,600. SNA 3270 supports baud rates up to 64,000.
Use host# parameter to specify the baud rate for comm. boards.
See also comm. board, BSC 3270, SNA 3270.

Bayonet Neill Concelman

Bayonet Nut Connector See BNC.

Bisynchronous Communication

blind referral A method of call transfer that dials out to the referral party and

BMS Basic Map Support. A method of identifying IBM 3270 type screen
See BNC.
See BSC 3270.
assumes the call has been answered.
Contrast with supervised referral.
fields in the transmission of host interaction commands from an application.
PeriProducer supports creating BMS maps (using PeriMap) and integrating formatted screen interaction into application programs.
For information on creating and using BMS maps, see the Avaya MPS PeriProducer User’s Guide.
See also host, PeriMap, screen mode, application.
BNC British Naval Connector, aka Bayonet Nut Connector, aka Bayonet
Neill Concelman. Used to connect a computer to a coaxial cable in a 10BASE-T Ethernet network.
Page 24 # P0602812 Ver: 1.3

Burroughs Poll/Select

bridge See referral.

British Naval Connector See BNC.

BSC 3270 Communications software that emulates an IBM 3274 cluster

controller supporting the Bisynchronous Communications protocol.
The terminals attached to an Avaya MPS BSC 3270 controller have the same capabilities as terminals attached to an IBM 3274 controller. All 3270-based application subsystems can be interfaced through the MPS BSC 3270 controller. This includes IBM 3270 host-based subsystems, such as IMS, CICS, and TSO, as well as 3270 subsystems running in other non-IBM processors that support attachment of BSC 3270 controllers.
An Avaya MPS/BSC 3270 system emulates an IBM 3270 by implementing a data link handler, a BSC Physical Unit (PU), and one or more line unit keyboard/display devices (LUs).
Burroughs Poll/Select See Unisys Burroughs Multipoint protocol.
# P0602812 Ver: 1.3 Page 25
Glossary of Avaya MPS Series Terminology C7
C
C7 Signaling protocol used inside telephone network switches.
See also CCSS 1000/2000.

call conferencing The Avaya MPS shared resource that allows up to six callers to be

connected (bridged) simultaneously. Call conferencing requires the CDP 2000 equipped with an MSP-10 module (in a CDP slot) for each six caller party.
For additional information, see the Avaya MPS System Reference Manual.
See module, shared resources.

Call Control Manager See CCM.

call function A self-contained system function that can be accessed by

applications. Call functions can perform tasks that can not be readily accomplished by the functions in PeriProducer blocks.
Examples include:
convert-from-binary - converts a byte string from binary into ASCII format
to-upper - converts the letters in a string, or portion of a string, into upper case
format-string - takes a sequence of strings and combines them according to specified variables
Access call functions through the System block’s Call an External Function option.
For additional information, see the Avaya MPS PeriProducer User’s Guide.
See also application, PeriProducer.

Caller Message Recording

See CMR.

call processing The automated management of telephone input and output.

See also call processing line, call processing application.
Page 26 # P0602812 Ver: 1.3
CCM

call processing application

call processing line A physical telephone line capable of processing calls. A call

A main Avaya MPS program that automates the management of telephone input and output. For example, use a call processing application to answer a call, check the caller’s account number, and speak back the caller’s current balance.
To perform call processing, you must assign call processing applications to call processing lines.
For information about configuring applications and assigning applications to lines, see the Avaya MPS PeriView Reference Manual.
Contrast with administrative application.
See also main application, call processing, assign, call processing
line.
processing line is connected to a phone port on the line card.
Use call processing phone lines to run call processing applications.
Contrast with administrative line.
See also call processing, call processing application, line card.

Call Progress Detection See CPD.

Call Sponsor Server See CSS.

Card Loader Process See CLP.

CCM Call Control Manager. A multi-threaded process that resides in the
VOS sub-component of the Avaya MPS component and which can be configured based upon the degree of fault isolation a user desires. The ratio of CCM processes to the number of phone lines is configurable, but there is only one multi-threaded CCM process to support all administrative applications that require VOS services.
See also Avaya MPS, VOS.
# P0602812 Ver: 1.3 Page 27

Glossary of Avaya MPS Series Terminology CCSS 1000/2000

CCSS 1000/2000 Common Channel Signaling Server. It is Avaya software and
hardware that supports SS7 and C7 messaging.
The CCSS 1000/2000 uses a client/server architectural model where the CCSS 1000/2000 is a dedicated SPARC processor (server) accessed by the Avaya MPS systems (clients) for call control functions. The CCSS 1000/2000 interface to the clients is TCP/IP over Ethernet. The CCSS 1000/2000 is housed within the standard Avaya equipment chassis that is mounted in a standard Avaya cabinet.
See also SS7, C7, SPARC, TCP/IP.

CEPT Conference of European Postal and Telecommunications

organizations. The CEPT standard refers to the Pulse Code Modulation (PCM) interface protocols that are used in Europe.
Also known as E1.
For additional information, see the Avaya MPS Telephony Reference
Manual.
See also digital, PCM.

channel A physical communication path. Digital telephone interfaces

typically refer to phone lines as channels.

Channel Service Unit See CSU.

clocking Refers to the timing in both transmitting and receiving messages for

synchronous host communication protocols.
See also synchronous protocol, host.
CLP Card Loader Process. The VOS software that performs the image
loading of the TMS phone line and resource cards. These are the initial program loading functions for the TMS.
For additional information, see the Avaya MPS System Reference Manual.
See also VOS, resource card, line card.

CMP-1026 See comm. board.

Page 28 # P0602812 Ver: 1.3

Common Channel Signaling Server

CMR Caller Message Recording. A facility that allows applications to
capture and store spoken information from a caller. The CMR facility records the caller’s speech in a MultiMedia file (MMF). CMR is useful for gathering information from callers such as names and addresses, which would otherwise be difficult to acquire using touchtone input or a type of speech recognition.
For additional information, see the Avaya MPS System Reference
Manual and the Avaya MPS Application Programming Reference Manual.
See also MMF.

CMR token See MS token.

COMMGR The VOS process that enables application programs to communicate

with external host computers using a variety of protocols.
For additional information, see the Avaya MPS System Reference Manual.
See also VOS, host, application, process, command man page
commgr intro.

comm. board Communications Processor Circuit Board. The comm. board is the

interface to many different types of external host computers. Both asynchronous and synchronous communication protocols execute on the comm. board.
Also known as CMP-1026.
See also comm. processor, synchronous protocol, asynchronous
protocol, host.
Common Channel Signaling Server
See CCSS 1000/2000.
# P0602812 Ver: 1.3 Page 29

Glossary of Avaya MPS Series Terminology comm. processor

comm. processor Communications Processor. The comm. processor is the hardware
that provides the logic necessary for communication with a host computer.
Each comm. processor is implemented on a single comm. board.
During system initialization, each comm. processor is loaded with the appropriate software image that implements the desired communications protocol. All commands and configuration parameters specific to the protocols are passed directly to the comm. processor.
See comm. board. image file.

communications manager

communications processor

compile See generate.

See COMMGR.
See comm. processor.
Page 30 # P0602812 Ver: 1.3
Loading...
+ 94 hidden pages