Avaya Media Processing COMMGR Reference Manual
Nortel Networks Media Processing
Server Series COMMGR Reference
Manual
(Software Release 1.0)
Publication#:
Document Release:
Release Date:
P0988083
1.0
April 1, 2002
Nortel Networks Media Processing Server Series COMMGR Reference Manual
Important Notice
Nortel Networks reserves the right to make cha nges in the content s of this publ icat ion
including functions and specifications identified herein without notice.
The material contained in this document is intended for Nortel Networks personnel
and licensed customers with a non-disclosure agreement or standard contract.
In the absence of a written agreement to the contrary, Nortel Networks assumes no
liability for applications assistance, customer’s product/application/concepts, or
infringements of patents or copyrights of third parties arising from the use of systems
and architectures described herein. Nor does Nortel Networks warrant or represent
that any license, either expressed or implied, is granted under any patent right,
copyright, or other combina tion of technolo gy, architec ture, or software as might be or
is already in use.
This document should not be reproduced, disseminated, or otherwise disclosed
without prior written consent from an officer of Nortel Networks.
This document has been copyrighted by Nortel Networks and may not be duplicated.
Copyright © 2002 Nortel Networks, All Rights Reserved
Page ii Nortel Networks Confidential #P0988083 Ver. 1.0
COMMGR Reference Manual Table of Contents
Table of Contents
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
How to Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Organization of This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Conventions Used in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Solaris and Windows NT Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Trademark Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Manual (Man) Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Overview of Host Computer Communications . . . . . . . . . . . . . . . . . . . . . . . . . 2
MPS Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Protocol Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Telephone Switching Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Supported Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2. Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
The commgr.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
The vos.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
The <protocol>.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
The host#.rc File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
The vpshosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3. Configuration and Status Commands. . . . . . . . . . . . . . . . . . . . . . . . .20
Command Syntax and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Global Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Virtual Terminal Range Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Protocol Daemon Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Manager-Type Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Client/Server-Type Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . . . 24
Host Session Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Virtual Terminal Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Host Mode Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
24-Byte Header and Pace Mode Parameters . . . . . . . . . . . . . . . . . . . . . . . 28
Transaction Codes and Status-Only Messages . . . . . . . . . . . . . . . . . . 29
Header Message Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Interacting with Multiple Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Host Login Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
24-Byte Header-Specific Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Host Numeric Vocabulary Element Format . . . . . . . . . . . . . . . . . . . . 31
Call Referral Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Host Control of Voice Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Status Message Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
#P0988083 Ver. 1.0 Nortel Networks Confidential Page iii
Nortel Networks Media Processing Server Series COMMGR Reference Manual
Rawtty mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Screen Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Host Response Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Keyboard Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
AID Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Host Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Host Status Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4. Virtual Terminal (VT) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Virtual Terminal Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Virtual Terminal Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Virtual Terminal Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
VT Allocation to Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
VT Pooling Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
VT Pooling Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 7
VT Pooling Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
VT Pooling Timeout Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
VT Pooling Access Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Selecting the Current Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Example Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Removing VTs from a Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Virtual Terminal Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Host/VT Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Determining the Status of a Defined VT Pool . . . . . . . . . . . . . . . . . . . . . . 57
Displaying VT Pooling Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Resetting VT Pooling Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
A. Host Character Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Sample Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Page iv Nortel Networks Confidential #P0988083 Ver. 1.0
Preface
P
This chapter covers:
1. Scope of this manual
2. Intended audience
3. Use and organization of this
manual
4. Documentation and trademark
Conventions
5. Manual (Man) pages
Nortel Networks Media Processing Server Series COMMGR Reference Manual
Preface
Scope
The Nortel Networks Media Processing Server Series COMMGR Reference Manual
details how to configure a Nortel Networks Media Processing Server Series (MPS)
system to communicate with various types of host computer systems. This manual
provides background inf ormation a nd detail s about conf igura tion parame ters common
to most host environments, as well as information about optional MPS features that
can be used at specific sites.
This manual covers topics t hat are s pecific to the c onfigurat ion and op erations of MPS
systems. It is not inten ded to explai n general te lephon y concepts or the charact eristi cs
of specific types of host computers.
Although some application programming depends on the type of host environment in
use, this manual does not cover application programming techniques. See the
PeriProducer Reference Manual for details on application programming.
Intended Audience
This manual is intended for the staff members who configure and program the MPS
for use with specific host computers.
The reader should be familiar with telecommunications and computer equipment,
their funct ions and associated term inology. In addition, the reader must be familiar
with the characteristics of the specific installation, including on-site power systems,
computers, peripherals, and telephony components.
This manual assumes that the user has completed an on-site system familiarization
training program conduct ed as part of th e ini tial syste m in stall atio n. Basi c knowl edge
of the Solaris and/or Windows NT operating system(s) is also assumed.
Page vi Nortel Networks Confidential #P0988083 Ver. 1.0
COMMGR Reference Manual Preface
How to Use This Manual
This manual uses many standard terms relating to computer system and software
application functions. However, it contains some terminology that can only be
explained in the context of the MPS system. Refer to the Glossary of MPS
Terminology for definitions of these terms.
Initially, this manual should be read at least once from start to finish. Later, the Table
of Contents and Index can be used to locate topics of interest for reference and
review.
If this document is being viewed online, use the hypertext links to quickly locate
related topi cs. Click on ce with the m ouse while the cursor is positioned over the
hypertext link. Click on an y poi nt i n a Table of Contents entry to move to that topic.
Click on the page number of any Index entry to access that topic page. Use the
hyperlinks at the top an d bottom of each onl ine “page” as nee ded when naviga ting t he
documentation. Pass the cursor over the Nortel Globemark to display the title,
software release, publication and revision number, and release date for the manual.
For addition al related information, u se the Refere nce Material link in PeriDoc. To
become familiar with various specialized textual references within the manual, see
Conventions Used in This Manual on page ix.
Periphonics is now part of Nortel Networks. The name Periphonics, and
variations thereof, only appear in this manual where it is refers specifically to
certain product names and commands. (As examples, a PeriProducer
application, the PERImps package, the perirev command, etc.)
#P0988083 Ver. 1.0 Nortel Ne tworks Confidential Page vii
Nortel Networks Media Processing Server Series COMMGR Reference Manual
Organization of This Manual
The following briefly outlines the structure of this manual:
Chapter 1. Introduction
Provides an overview of host communications configuration and software architecture.
Chapter 2. Configuration File s
Describes the configur ation of the f iles r eleva nt to hos t commun icati ons. Sampl e configuration files are provided.
Chapter 3. Configuration and Status Commands
Describes the aspects of communi cations configurat ion common to most install ations.
The topics include: command syntax, VSH command execution, loading the
communications software, specifying the desired protocol, determining host link
availability, setting common parameters, and selecting a particular host session.
Chapter 4. Virtual Terminal (VT) Configurat ion
Describes the configuration and use of Virtual Terminals (VTs). Topics include
general configuration issues, assigning VTs to phone lines, VT Pooling, VT status
information, and application programming notes.
Appendix A. Host Character Sets
Describes the character set conversion tables for use with specific types of host
computers and applications. This is supported only for the LU6.2 and VPSTN3270
protocols.
Page viii Nortel Networks Confidential #P0988083 Ver. 1.0
COMMGR Reference Manual Preface
!
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
Notation Description
Normal text
important term
system
command
file name /
directory
on-screen field
<KEY NAME>
Book Reference
cross refer ence
Normal text font is used for most of the document.
The Italics font is us ed to in troduce new terms, to h ig hli ght meaningful word s o r p hras es , o r to
distinguish specific terms from nearby text.
This font indicates a sys tem command and/or its argum ents. Such keywords are to be entered
exactly as shown (i.e., users are not to fill in their own values).
This font is used for highlighting the names of disk directories, files, and extensions for file
names. It is also us ed t o s how displays on text-ba se d scre ens (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.
A cross reference or man page reference is shown on the screen in blue. 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. Click on the man page reference to elicit a pop-up
window displaying the subject man page.
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 can arise if the stated instructions are improperly
followed.
The flying Window icon identifies procedures or events that apply to the Windows NT
operating system only.
The Solaris icon identifies procedures or events that apply to the Solaris operating system
(2)
only.
(1): Windows NT and the flying Window logo are either trademarks or registered trademarks of the Microsoft
Corporation.
(2): Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other
countries.
(1)
#P0988083 Ver. 1.0 Nortel Networks Confidential Page ix
Nortel Networks Media Processing Server Series COMMGR Reference Manual
Solaris and Windows NT Conventions
This manual depicts examples (command line syntax, configuration files, and screen
shots) in Solaris format. In certain instances, Windows NT specific commands,
procedures, or screen shots are shown where required. The following table lists
examples of general operating system conventions to keep in mind when using this
manual with either the Solaris or NT operating system.
Solaris Windows NT
Environment $VPSHOME %VPSHOME%
Paths $VPSHOME/common/etc %VPSHOME%\common\etc
Command <command> & start /b <command>
Trademark Conventions
The following trademark information is presented here and applies throughout this
publication for discussions of third-party products. Trademark information is not
repeated hereafter.
Solaris is a tr adema rk or regist ered trade mark of Su n Micro systems , Inc. in the United
States and other countries.
Microsoft, Windows, Windows NT, Internet Explorer, the Flying Windows logo, and
Microsoft Host Inte gration Se rver 2000 ar e either t rademarks or registere d trad emarks
of Microsoft Corporation.
Netscape® and the Netscape N® and Ship's Wheel® logos are registered trademarks
of Netscape Communications Corporation in the U.S. and other countries. Netscape
Navigator is also a trademark of Netscape Communications Corporation and may be
registered outside the U.S.
GeoTel® and ICM (Intelligent Contact Management)® are registered trademarks of
Cisco Systems.
Brixton® SNA Server is a trademark of Brixton Systems.
IEX® and TotalNet® are registered trademarks of the Tekelec Company.
Page x Nor tel Networks Confidential #P0988083 Ver. 1.0
COMMGR Reference Manual Preface
Manual (Man) Pages
Manual (man) pages provide access to documentation about Solaris system
commands, MPS commands, sta tus/exception c onditions, a nd alarm inform ation. Man
pages can be displayed from any command line on Solaris systems. On NT systems,
man pages can be displayed from a DOS prompt/VSH pr ompt. Man pages app ear in a
separate browser window. The particular browser used depends on the software
installed on the sys tem and which browse r is set as the def ault. In addition , man pages
are always accessible through PeriDoc’s Search page and through hypertext links
within the documents.
To access a Man Page for:
• a Solaris system command, use the syntax man <command> (Solaris only).
• an MPS command, use the syntax mpsman <processname> <command>.
On Solaris systems on ly, enter man mpsman for a detailed des cri ption of using
MPS command manual pages.
• an MPS alarm, use the syntax mpsalarm <processname> <alarm#>.
On Solaris systems only, enter man mpsalarm for a detailed description of
using alarm manual pages, or man alarmintro for an overview of MPS
alarms and the alarm database.
• an MPS status/exception condition, use the syntax conman <condition>.
On Solaris systems on ly, enter man conman for a detailed des cri ption of using
MPS condition manual pages.
The man page scripts rely on the Windows NT registry settings for default
browser information. Older browsers do not set the registry entries required by
the man page scripts. Do not use command line man pages if you are using
browsers older than Netscape Navigator 4/Internet Explorer 4.
If you are viewing this document online, click any command highlighted in blue to
open a window displaying the manual page for that command.
#P0988083 Ver. 1.0 Nortel Networks Confidential Page xi
Nortel Networks Media Processing Server Series COMMGR Reference Manual
This page has been intentionally left blank.
Page xii Nortel Networks Confidential #P0988083 Ver . 1.0
Introduction
1
This chapter covers:
1. Communications configuration overview
2. Software architecture
Nortel Networks Media Processing Server Series COMMGR Reference Manual
1. Introduction
The Nortel Networks Media Processing Server Series (MPS) is an IVR (I nteractive
Voice Response) system with augmentations for multimedia functions and advanced
telephone switching. An MPS can function as a stand-alone services system, with its
own transaction processing and storage facilities, or be integrated into serviceprovider environments with their own central computer systems.
Overview of Host Computer Communications
In a telephony services environment, the MPS is the link between network features
and the calling community. External systems in the network connected to the MPS are
referred to as host computers. Generally, hosts are of the mini, mainframe, or
workstation classification. They provide database and transaction processing
functions, which are integrated with the voice and media features of the MPS. The
MPS can facilitate any data, voice, or telephony service that the network’s host
computers are designed to provide.
Before the advent of IVR s ystems, computer -based tran sactions invo lved having a li ve
operator enter and receive data through a terminal connected to a central computer
system. When the MPS is integrated into this kind of basic transaction processing
environment, it emulates the actions of the operator as it interacts with the caller,
host(s), and internal system resources.
Caller
The actions of the MPS are governed by applications. These are scripts containing
programmed instructions, such as for receiving caller input, providing voice output,
accessing the host, etc. MPS applications are created using PeriProducer, which is a
GUI-type editor that allows visual sequencing of application instructions. (See the
PeriProducer User’s Guide.)
Host
Telephone
8
network
Terminal
Operator
Protocol-based
interaction
Computer network
Basic Transaction Processing Environment
Database
Page 2 Nortel Networks Confidential #P0988083 Ver. 1.0
COMMGR Reference Manual Introduction
An application is activ ate d by a ssocia ting it wi th one of t he MPS tele phone l ines. The
set of lines i n the system can run multiple copies of the same application, different
applications, or any combination. When an application’s phone number is dialed, the
application activates and interacts with the caller based on it’s programmed
instructions.
If an application requires access to a host, the MPS assigns a set of internal hardware
and software resources, referred to as a Virtual Terminal (VT), to the application’s
phone line. This VT is seen by the host as an operator’s terminal. When issuing
configura tion comma nds to a VT, the VT is identified to the sy stem by a unique
service ID.
Read and write operations are performed between the VT and the host in the same
manner as is done with a stand ard ter min al, based on t he char acte rist ics of a part icula r
host communications protocol. A protocol is a standardized format for transmitting
data between computer systems. The for m at co nsi st s of command codes, data values,
delimiters, etc. that both computers can recognize. To send data to and receive data
from a host, the MPS must be configured for the appropriate protocol.
An application can communicate with up to eight hosts, each of which can use a
different protocol. Applications can easily change the host session as needed, which
means to switch from one host to the next. The particular protocol expected by each
host is set up in the MPS configuration files.
Host
Telephone
network
8
Caller
Application
MPS
Basic MPS Transaction Processing Network
Virtual
Terminal
Protocol-based
interaction
Computer ne twork
Database
#P0988083 Ver. 1.0 Nortel Ne tworks Confidential Page 3
Nortel Networks Media Processing Server Series COMMGR Reference Manual
MPS Software Architecture
The MPS host communications subsystem contains a set of processes specifically
dedicated to host i ntera ction. The host subs ystem res ides in t he V OS (Voice Operating
Software) of the MPS, and is comprised of two layers: the COMMGR
(Communications Manager) process and the protocol layer.
The COMMGR process provides a generic (i.e., protocol-independent) application
interface fo r host communications services. It mediates the interacti on between MPS
applications and the protocol-layer process(es). The COMMGR is also responsible
for the majority of data processing related to external communications, including
configuration, appl icati on-to -ho st ses sion map ping, a nd host inp ut/out put pr ocess ing.
A single COMMGR process runs on each MPS in the network.
The exact software arr angement of the protoc ol layer d epends on th e protocol type. In
this layer, there is one main process (generally a protocol server or manager process)
that handles the communications needs of all MPS applications using that protocol.
Depending on the design of a particular protocol, there might be multiple ancillary
interface processes in the protocol layer.
MPS
Solaris/NT
ASE
VOS
Host communications subsystem
VMS
MXVMT
COMMGR
Protocol
daemon
VENGINE(s)
Application(s)
VSH
CCM
System Console
Telephone
Network
Host
MPS Communications Software Architecture
Page 4 Nortel Networks Confidential #P0988083 Ver. 1.0
COMMGR Reference Manual Introduction
The system processes relevant to host communications are described below.
MPS System Software
VSH
ASE
VOS
V-shell is the command interface for MPS configuration and operations. Configuration and status
commands can be issued via the VSH tool or from the system’s configuration files. VSH receives
status information from the various system processes and displays messages on the console as
appropriate.
The Application Servic e Environment software is dedicated to providing the data and services
requested by applicat ions. The ASE exists on a separat e workstat ion, referr ed to as the applications
processor. The workstation can be eith er an open-systems Solaris or Windows NT implementation.
applications
Interactive Voice Response or multimedia script created with PeriProducer. An
application runs on a system phone line. Multiple instances of the same application
can be assigned to different lines. Each application is associated with it’s own VT.
VENGINE
Software process th at execut es an ap plicati on. A sing le VENGINE pro cess is required
for each application telephone line.
VMS
The VENGINE Message Serve r provide s a message funnel between the ASE and VOS
processes. On a node th at contains mu ltiple MPS syst ems, VMS provides conn ectivity
between the application processor and each MPS. One VMS is required for each
MPS.
MXVMT
The Media Transaction VENGINE Message Translator relays messages between the
ASE and VOS processes. One MXVMT process is required for each MPS.
The Voice Operating Software is the set of processes that provide the low- level system functions in
the MPS. These functions include telephony and host I/O, and are common to most types of
applications.
COMMGR
protocol
daemon
CCM
The Communications Manager provides a generic application interface for host
communications services. A single COMMGR is required for each MPS in the
network.
Software process that implements the particular communications protocol. The
protocol layer links the COMMGR with the host computer. With some pr otocols ( e.g.,
CCA, ATTE, etc.), the protocol dae mon invokes d river pr ograms to manage indi vidual
VT sessions.
The Call Control Manager configures and controls low-level telephony interaction.
#P0988083 Ver. 1.0 Nortel Ne tworks Confidential Page 5
Nortel Networks Media Processing Server Series COMMGR Reference Manual
Protocol Architecture
All protocols require use of the COMMGR and a server or manager proce ss specific to
each protocol. This process is called the protocol daemon . Each protocol also has
unique internal architecture and might require special hardware interfaces for the host.
For some protocols, such as certain variations of Credit Card Authorization, the
protocol layer is implemented as a server, which can be shared by the COMMGR
client processes on multiple MPS systems.
MPS
Solaris/NT
ASE
VOS
COMMGR
MPS
Solaris/NT
ASE
VOS
Protocol
COMMGR
MPS Multiple-COMMGR Architecture
server
daemon
Host
For protocols like GeoTel or IEX, the protocol layer cons ists of a s ingle ser ver proces s
without any interface processes. For some other protocols, the server software
spawns multiple interface processes, one for each application VT.
MPS
Solaris/NT
ASE
VOS
Protocol
COMMGR
server
daemon
Protocol interfaces
MPS Protocol Architecture with Support Processes
Host
Page 6 Nortel Networks Confidential #P0988083 Ver. 1.0
COMMGR Reference Manual Introduction
Depending on the protocol, the MPS interacts with the host either by modem or via
LAN/WAN-type connections (TCP/IP, Ethernet, SDLC, Token Ring, X.25 or Async).
Some environments incorporate the Brixton PU2.1 server with VPSTN3270
functionality to additionally mediate host communications.
MPS
Solaris/NT
ASE
VOS
MODEM
MODEM
MODEM
Host
MPS
COMMGR
Protocol
server
daemon
Solaris/NT
ASE
VOS
MPS
Solaris/NT
ASE
VOS
COMMGR
COMMGR
Protocol
daemon
Protocol
daemon
Brixton
PU2.1
server
VT100 or
VPSTN3270
Host
Token ring, Ethernet,
or SDLC
Host
MPS Protocol Arch ite c tur e with Various Host Connections
#P0988083 Ver. 1.0 Nortel Ne tworks Confidential Page 7
Nortel Networks Media Processing Server Series COMMGR Reference Manual
Telephone Switching Environments
In large-scale, enterprise-type networks, the MPS can be integrated with an intelligent
router system that performs call load balancing and network reporting.
This type of installation requires use of either the GeoTel or Nortel Networks’ IEX
systems. Although GeoTel and IEX use the host communications facilities of the
MPS, they are not considered host protocols in the traditional sense. Rather, they are
enterprise-type c ommuni cations protocols t hat a ll ow i nt er action between an MPS and
telephony-network-based services.
A typical call routing scenario is described below:
1. A caller dials phone number for a particular network service.
2. The telephone network requests switching instructions from the intelligent router.
3. The intelligent router sends switching instructions to telephone network.
4. The call is routed to an available MPS system.
5. If the applicat ion ca n complete t he call , the MPS s ends updated c all st atus and line
availabili ty information to the intelligent router. If the caller requires additional
assistance, the MPS sends a call routing request to the intelligent router.
6. The ICM tr ansmits the new call destination to the MPS.
7. The MPS transmits call switching instructions to the network.
8. The call is connected with a customer service agent.
Agent
8
Caller
1
48
Telephone
8
MPS Enterprise Network Environment
network
3
2
Intelligent Router System
4
7
6
MPS MPS MPS
5
Page 8 Nortel Networks Confidential #P0988083 Ver. 1.0
COMMGR Reference Manual Introduction
Supported Protocols
For the MPS to communicate with a host, the appropriate protocol software must be
configured on the MPS. The specific architecture, configuration, operation, and
features of each host protocol is documented in it’s own manual.
The following protocols are currently supported by the MPS:
Protocols Supported by the MPS
Host Protocol Connection Type MPS Protocol Name
TELNET TCP/IP ATTE (VT100 terminal emulation)
Async
24-Byte Header
PACE
rawtty
TELNET 3270 TCP/IP VPSTN327 0 (RFC1576, RF C1646)
3270 LU type 2 Ethernet (802.2)
LU type 6.2 Ethernet (802.2)
Credit Card Authorization
visa - credit
visanet - batch, credit, debit
mapp - batch, credit
edc - batch, credit
etc - credit
GeoTel ICM TCP/IP GeoTel
serial ATTE
PPI
VPSTN3270 - Solaris (requires Brixto n
Token Ring (802.5)
SDLC
X.25
Token Ring (802.5)
SDLC
X.25
MODEM CCA_SERV, CCA_MGR
TCP/IP (with POS
port device)
TCP/IP PaylinX - Vital VirtualNet (requires
PU2.1 Server)
VPSTN3270 - Windows NT (requires
Microsoft Host Integration Server 2000)
LU6.2 - Solaris (requires Brixton PU2.1
Server)
LU6.2 - Windows NT (requires Microsoft
Host Integr ation Serve r 2000)
POS_SERVER
PERIjsb, and PaylinX Java API)
IEX TCP/IP IEX
Each of these protocols allows up to 255 concurrent host sessions on each MPS, but
the actual limit depen ds on available system resourc es, CPU, memory and swap space,
and application requirements.
#P0988083 Ver. 1.0 Nortel Ne tworks Confidential Page 9
Nortel Networks Media Processing Server Series COMMGR Reference Manual
This page has been intentionally left blank.
Page 10 Nortel Networks Confidential #P0988083 Ver. 1.0
Configuration Files
2
This chapter covers:
1. The commgr.cfg File
2. The vpshosts File
3. The vos.cfg File
4. The host#.rc File
Nortel Networks Media Processing Server Series COMMGR Reference Manual
2. Configuration Files
For products that are part of the Nortel Networks Media Processing Server Series
(MPS), certain configuration files have to be installed and modified to support host
communications. These f iles are sup plied i n gener ic for m when the s ystem i s shipp ed
from the factory. For most sites, these files require only minor modifications to
configure all necessary functions of a given protocol.
For Solaris systems, the configuration files are stored in the directory
$VPSHOME/vpsN/etc/, where “N” indicates th e ID nu mb er of t he pa rticular MPS
unit.
For Windows NT systems, the configuration files are stored in the directory
%VPSHOME%\vpsN\etc\, where “N” indicates the ID number of the particular
MPS unit.
The following configu ration f iles ar e used i n every MPS i nstalla tion tha t support s host
communications:
MPS Communications Configuration Files
commgr.cfg Contains commands that set parameters specific to the
COMMGR process. (See The commgr.cfg File on page 13.)
vos.cfg Defines process names and their associated TCP/IP port
numbers. This system uses the protocol’s entry in this file to
assign an appropriate port number. (See The vos.cfg File on
page 14.)
<protocol>.cfg Contains commands for the particular protocol daemon. (See
The <protocol>.cfg File on page 15.)
host#.rc Internal configuration file for a particular host configured in the
commgr.cfg file. (See The host#.rc File on page 16.)
vpshosts Specifies the network components associated with a particular
node. (See The vpshosts File on page 17.)
The Nortel Networks Media Processing Server Series System Reference Manual
contains additional information about these files not documented here.
Page 12 Nortel Networks Confidential #P0988083 Ver. 1.0
COMMGR Reference Manual Configuration Files
The commgr.cfg File
The main host communications configuration file is called commgr.cfg. The
parameters specif ied in this file ar e parse d and inte rpret ed by the COMMGR softwa re
automatically upon system startup.
The configuration requirements of the commgr.cfg file depend on the particular
protocol. Sample commgr.cfg files are provided in each protocol features manual.
In the commgr.cfg file, commands are preceded by the “host #” syntax
construction. The “#” indicates the particular host to which the configuration
parameters will apply. (See Command Syntax and Usage on page 20.)
Up to eight logical host s can be defined. In the commgr.cfg file, there is one set of
host # commands for each defined host (i.e., a set of commands, as needed for
host 1, host 2, host 3, etc. that configure each of these hosts). An application
issues session commands, as needed, to change the host with which it is
communicating. (See Host Session Assignment on page 25.)
The commands that can be used in this file are documented in Chapter 3.
Configuration and Status Commands. These commands set parameters that
configure the host communications software. Most parameters have default values
suitable for most installations. If a parameter’s default is adequate, the correspon din g
command need not be included in the commgr.cfg file. (The commgr.cfg file
usually contains just a few commands for each defined host.)
A sample commgr.cfg configuration file for a dual-host, 96-line T1 system is
shown below.
Sample commgr.cfg File
host 1 protocol <protocol1_name>
host 1 svcid 1-48 sess 1
host 1 svcid 1-48 assignvt 1
host 2 protocol <protocol2_name>
host 2 svcid 49-96 sess 2
host 2 svcid 49-96 assignvt 49
#P0988083 Ver. 1.0 Nortel Networks Confidential Page 13
Loading...