Reference for ROLM 9751 CBX (Release 9005)
CallPath Services
Reference for
ROLM 9751 CBX (Release 9005)
SC38-3056
2 Jun 19975639-A14
5622-959
5622-958
S370-79
| Note |
|---|
|
Before using this information and the product it supports, be sure
to read the general information under "Notices".
|
Fourth Edition (April 1996)
This edition applies to Version 1
Release 1.2
of the IBM CallPath SwitchServer/2
licensed program, Program Number 5639-A14,
Version 1
Release 1.2
of the CallPath Server/2
licensed program, Program Number 5622-959,
and Version 1
Release 1.2
of the CallPath Developers
Toolkit licensed program, Program Number 5622-958,
and to all subsequent
releases and modifications until otherwise indicated in new editions.
Order publications through your IBM representative or the
IBM branch office serving your locality.
Publications are not stocked at the address given below.
Forms for readers' comments appear
at the front and back of this publication.
If the forms have been removed, address your comments to:
IBM Corporation
Information Development, Department CGMD
P.O. Box 12195
Research Triangle Park, NC 27709-9990
U.S.A.
When you send information to IBM, you grant IBM a nonexclusive
right to use or distribute the information in any way it
believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1992, 1996. All rights reserved.
Note to U.S. government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule contract with IBM Corp.
Notices
Figures
About This Book
Chapter 1. Introduction
Chapter 2. Installation and Configuration for CallPath SwitchServer/2
Chapter 3. Installation and Configuration for CallPath Server/2
Chapter 4. ROLM 9751 CBX Functions
Chapter 5. Partially Supported Program Calls
Chapter 6. Partially Supported Set Program Calls
Chapter 7. Partially Supported Messages
Chapter 8. Feature Formats and Codes
Chapter 9. Problem Determination
Chapter 10. Example Program Call and Message Flows
Chapter 11. Glossary
Index
- Hardware Configuration for the ROLM 9751 CBX and SwitchServer/2 Connection
- Switch Connection Configuration Window Example (Inbound and Outbound Selected)
- RIC Card Selection Window Example
- Port Configuration Window Example
- INBOUND Baud Rate Window Example (9600 Baud Selected)
- OUTBOUND Dialer Number Window Example
- OUTBOUND Timeout Values Window Example
- Hardware Configuration for the ROLM 9751 CBX (Release 9005) and CallPath Server/2 Connection
- Switch Connection Configuration Window Example (Inbound and Outbound Selected)
- RIC Card Selection Window Example
- Port Configuration Window Example
- INBOUND Baud Rate Window Example (9600 Baud Selected)
- OUTBOUND Dialer Number Window Example
- OUTBOUND Timeout Values Window Example
- Switch Connection Configuration Window Example (Inbound and Outbound Selected)
References in this publication to IBM products,
programs, or services do not imply that IBM intends
to make these available in all countries in which IBM
operates.
Any reference to an IBM product, program, or service
is not intended to state or imply that only IBM's
product, program, or service may be used.
Any functionally equivalent product, program, or service that
does not infringe any of IBM's intellectual
property rights may be used instead of the IBM
product, program, or service.
Information in this document describing capabilities of the
ROLM 9751 computerized branch exchange (referred to as the
ROLM 9751 CBX (Release 9005)) is based on information supplied by the switch
manufacturer and is for planning purposes only.
Evaluation and verification of operation of the ROLM 9751 CBX (Release 9005) in
conjunction with other products or IBM products
described in this document is the user's responsibility.
IBM may have patents or pending patent applications
covering subject matter in this document.
The furnishing of this document does
not give you any license to these patents.
You can send license inquiries,
in writing, to
IBM Corporation,
IBM Director of Licensing,
208 Harbor Drive,
Stamford,
CT,
United States,
06904.
This book is intended to help you write applications to run
in an environment containing IBM
CallPath SwitchServer/2 or IBM CallPath Server/2.
It describes the support provided by the ROLM 9751 CBX (Release 9005).
This book lists the functions supported by the CallPath
Services application program interface (API) and
indicates which of those functions can be requested by a
program when that program is communicating with a ROLM 9751 CBX (Release 9005).
This book documents General-Use programming interfaces and
associated guidance information provided by
the CallPath environment you are running.
General-Use programming interfaces allow the customer
to write programs that request the services of
the CallPath environment you are running.
Note: Except where there is a need to differentiate between CallPath SwitchServer/2
and CallPath Server/2, the term Server/2 will be used in place of
the phrases "CallPath SwitchServer/2 and CallPath Server/2".
The following terms, denoted by an asterisk ((*)),
used in this publication, are trademarks or service marks of
the IBM Corporation in the United States or other
countries:
| CallPath
| CallPath SwitchServer/2
| IBM
|
| NetView
| Operating System/2
| OS/2
|
| Personal System/2
| PS/2
| SwitchServer
|
| SwitchServer/2
|
|
|
The following terms, denoted by a double asterisk
((**)), used in this publication,
are trademarks of other companies as follows:
| CallBridge
| ROLM Systems and Siemens AG
|
| CBX
| ROLM Systems
|
| ROLM
| ROLM Systems
|
| ROLMphone
| ROLM Systems
|
System Monitor Input/Output Card (SMIOC)
This book provides application program reference information
for developing telephony applications using
IBM CallPath** Services in
connection with the ROLM**
9751 computerized branch exchange (CBX**).
In this book, the switch is referred to as the ROLM 9751
CBX.
The following individuals should read this book:
- Telecommunications personnel responsible for installing
and configuring the ROLM 9751 CBX (Release 9005) and
CallPath Server/2*
connections
- Application programmers who design or manage programs
used with CallPath Services and the ROLM 9751 CBX (Release 9005)
This book provides switch-specific information and is designed
to be read with
CallPath Services Programmer's Reference,
GC31-6824,
and
Using CallPath SwitchServer/2,
SC34-2406.
This book is organized as follows:
- Chapter 1. "Introduction", describes the contents of the
book and the naming and notational conventions used in CallPath Services.
- Chapter 2. "Installation and Configuration for CallPath SwitchServer/2", provides information for installing
and configuring the ROLM 9751 CBX (Release 9005) hardware and software.
Read it along with the installation information in
Using CallPath SwitchServer/2.
- Chapter 3. "Installation and Configuration for CallPath Server/2", provides installation and configuration
information for the ROLM 9751 CBX (Release 9005) hardware and software that is used
with CallPath Server/2.
- Chapter 4. "ROLM 9751 CBX Functions", provides quick-reference
tables showing the ROLM 9751 CBX (Release 9005) support for CallPath Services program
calls and messages.
- Chapter 5. "Partially Supported Program Calls", describes the CallPath Services
program calls that are partially supported by the ROLM 9751 CBX (Release 9005).
- Chapter 6. "Partially Supported Set Program Calls", describes the CallPath Services
Set program calls that are partially supported by the ROLM 9751 CBX (Release 9005).
- Chapter 7. "Partially Supported Messages", describes the CallPath Services
messages that are partially supported by the ROLM 9751 CBX (Release 9005).
- Chapter 8. "Feature Formats and Codes", describes the level of support
for the feature_data parameter of the
Invoke_Feature program call and the "feature_data"
field of the Feature_Invoked call-progress event message.
- Chapter 9. "Problem Determination", provides problem determination
information specific to the ROLM 9751 CBX (Release 9005).
- Chapter 10. "Example Program Call and Message Flows", provides examples that show
sequences of information flow from the ROLM 9751 CBX (Release 9005).
This book also includes a glossary of terms and abbreviations
and an index.
This section describes the terms used for mouse actions and the
highlighting conventions used in this book.
The following are standard terms used throughout
this book when referring to mouse actions
for the OS/2, MOTIF, and &smit. interfaces:
- click
- A single, quick press and release of
mouse button 1.
- double-click
- Two quick, successive, press and release of
mouse button 1.
- enter
- When you are asked to enter information, type the information
and press the Enter key.
Pressing the Enter key submits the data you typed.
When you do not need to press the Enter key,
you are instructed
just to type the information.
- select
- To click on
the specified
menu, menu option, or window element.
The following highlighting conventions are used in this book:
- Italics
- Identify the following:
- Emphasis in text
- Variable parameters requiring
actual names or values
- Bold
- Identifies
the following types of information:
- Names predefined by CallPath Server:
- Commands
- Directories
- Filenames
- Flags
- Information that
you should type as shown
- Keys that you should press
- Bold Italics
- Identify new terms defined in the text
and in the Glossary
- Monospace
- Identifies examples of output, including the following:
- Messages from the system
- Specific data values
- Text displayed on panels
- "Quotation Marks"
- Identify field names
Use the following IBM CallPath Services publications
along with this book:
-
CallPath Services Programmer's Reference, GC31-6824
-
Using CallPath SwitchServer/2, SC34-2406
Also, the following IBM CallPath Services publications
may be useful to you:
-
CallPath CICS and CallPath SwitchServer/2 General Information, GC34-2401
-
CallPath CICS/MVS Application Programming Reference, SC34-2402
-
CallPath CICS/VSE Application Programming Reference, SC34-2409
-
Using CallPath CICS/MVS, SC34-2404
-
Using CallPath CICS/VSE, SC34-2405
-
CallPath for Workstations General Information, GC38-3051
-
CallPath for Workstations Planning, Installation, and Problem Determination Guide, SC38-3052
-
CallPath Toolkit for OS/2 and DOS Application Programming Guide, SC38-3053
-
CallPath Toolkit for OS/2 and DOS Programmer's Reference, SC38-3054
-
Application System/400:
CallPath/400 Overview and Installation Planning Guide,
SC33-1365
-
Application System/400:
CallPath/400 Programmer's Reference, SC33-1366
-
AIX CallPath/6000 General Information, GC30-3575
-
AIX CallPath/6000 Planning, Installation, and Problem
Determination Guide,
SC30-3569
-
AIX CallPath Toolkit/6000 Programming Guide and
Reference,
SC30-3571
Other IBM publications that may be useful to you
include:
-
Operating System/2 Extended Edition Version 1.3 Getting Started, 84X0841,
provided with the OS/2 program product
-
Operating System/2 Extended Edition Version 1.3 System Administrator's Guide for Communications, S01F-0261
-
Operating System/2 Extended Edition Version 1.3 User's Guide Volume 1: Base Operating System, 15F7297,
provided with the OS/2 program product
-
Operating System/2 Programming Tools and Information, 64F0275
In addition, you should consult the ROLM service and
configuration documentation for your ROLM 9751 CBX (Release 9005).
The following items are new or have changed since the last edition
of this book:
- New installation information has been added
for using the ROLM 9751 CBX (Release 9005) with CallPath Server/2.
- The level of support for some program call parameters
and message fields has changed.
- New system messages have been added to the System Message Data in
Chapter 9. "Problem Determination".
The ROLM 9751 computerized branch exchange
(CBX) is a digital telecommunications system.
In this book, the system is referred to as the ROLM 9751 CBX (Release 9005).
The ROLM 9751 CBX (Release 9005) interfaces with IBM CallPath Services
host computers through IBM
CallPath SwitchServer/2* or CallPath Server/2.
CallPath Services is IBM's architecture for
computer-telephone system communications.
It defines an application program interface (API)
that enables host applications to communicate with telephone
systems--in this book, the ROLM 9751 CBX (Release 9005).
The CallPath Services API enables new or existing host
applications to provide advanced switching functions through the
integration of voice and data processing capabilities.
CallPath SwitchServer/2 connects the ROLM 9751 CBX (Release 9005) to one or more CallPath Services
host computers.
It performs protocol conversion between CallPath Services requests and
messages and ROLM 9751 CBX (Release 9005) protocols.
CallPath SwitchServer/2 isolates the CallPath Services host computer from the specific
communications formats and protocols that are required to
interface with the ROLM 9751 CBX (Release 9005), while allowing the ROLM 9751 CBX (Release 9005) to
interface concurrently with multiple CallPath Services host computers.
CallPath Server/2 is a CallPath Services computer designed for use in client/server networks.
CallPath Server/2 can be either directly connected to the ROLM 9751 CBX (Release 9005) or through
CallPath SwitchServer/2.
When connected directly to the ROLM 9751 CBX (Release 9005), CallPath Server/2 performs the
protocol conversion between CallPath Services requests and messages and
ROLM 9751 CBX (Release 9005) protocols.
When connected to the ROLM 9751 CBX (Release 9005) through CallPath SwitchServer/2, CallPath Server/2 uses the protocol
conversion services of CallPath SwitchServer/2.
Except where there is a need to differentiate between CallPath SwitchServer/2
and CallPath Server/2, the term Server/2 will be used in place of
the phrases "CallPath SwitchServer/2 and CallPath Server/2".
This book provides switch-specific information for the ROLM 9751 CBX (Release 9005).
It describes the level of support provided by the ROLM 9751 CBX (Release 9005) for the
program calls and messages that make up the CallPath Services API.
It specifies which parameters are fully supported, partially
supported, or not supported.
Full details of all architected program calls and messages
are given in
CallPath Services Programmer's Reference.
You should also refer to the CallPath Services programming guide for your
host computer system, as it may define a lesser level of
support for the architecture.
This book also identifies any deviation from the procedures
described in
Using CallPath SwitchServer/2
for installation, administration, or problem determination
required when using CallPath Services in conjunction with the ROLM 9751 CBX (Release 9005).
Many national telecommunications authorities impose restrictions
on the operation of automatic call-dialing equipment.
For example, the frequency and number of attempts that may be
made to call a number in the public telephone network are defined.
The ROLM 9751 CBX (Release 9005), CallPath SwitchServer/2, and CallPath Server/2
do not enforce these restrictions.
The application developer must ensure that each application
complies with the restrictions by following these steps:
- Contact the IBM Support Center to find out the
regulations for the country or countries in which the application
is to be used.
- Notify the switch vendor of the details of the operation
of the application that may be subject to constraint.
- Request a confirmation from the switch vendor that the
application will comply with the restrictions.
Once the confirmation is received, the switch vendor
is liable to the Telecommunications Authority as long as
the application
functions as
stated in the notification.
Introduction
Throughout this book, the names of actual program calls,
messages, parameters, call profile characteristics, variables,
and parameter or characteristic values that make up the CallPath Services
API are represented by pseudonyms.
The pseudonyms are used to simplify understanding and to
aid readability.
For example, the program call STLMAKE is used by
a program to establish a telephone call; its pseudonym in this
book is Make_Call.
Where possible, pseudonyms are made up of complete names.
If a pseudonym is composed of more than one word, the words
are connected with an underscore (_).
Any phrase in the book that contains an underscore is a pseudonym.
To aid in distinguishing the various types of pseudonyms,
the following naming and notational conventions are used:
Program calls and Set program calls
have both an actual program call name and a pseudonym.
Actual program call names are made up entirely of capital letters.
The first three characters of all CallPath Services program call names
are "STL" to indicate that the program calls
are associated with the CallPath Services API.
For example, the program call STLRCV is used by
a program to receive messages.
The pseudonym for STLRCV is Receive.
Pseudonyms for program calls begin with a capital letter,
as does each portion of the pseudonym that follows an underscore.
For example, Initialize_Call_Profile is the pseudonym
for the actual program call name of STLINIT.
Parameters on program calls contain no capital
letters except those used for abbreviations and appear with a
common highlight style (for example, call_profile_ID).
Call profile characteristics contain no capital
letters except those used for abbreviations and appear with
a common highlight style (for example, switch_ID).
Variables are defined by a program and are
used to hold the values of parameters or characteristics.
For example, party_one is one of the parameters on
the Make_Call program call.
When a program issues a Make_Call program call, it must
specify a variable that contains the value required by the
party_one parameter.
The name of the variable could be party_one,
P1, or anything else the program wishes to use.
Variables contain no capital letters except those used
for abbreviations and appear with a common highlight style
(for example, party_two).
In many cases, the parameter used on a program call, which
corresponds to a program variable, has the same name as a
call profile characteristic.
Whether a name refers to a parameter, a program variable, or
a call profile characteristic is determined by context.
In all cases, the value used for the three remains the same.
To indicate that a variable has been set to a particular
value, this book either says so explicitly
or uses "function" notation.
For example, an automatic_answer of
STL_NO_ANSWER may also appear as
automatic_answer(STL_NO_ANSWER).
Values used for parameters, characteristics,
and variables represent actual integer values that are to be
placed into the variable. All values appear with a common
highlight style (for example,
STL_MONITOR_DIRECTORY_NUMBER).
The pseudonyms begin with the STL prefix to indicate
that the values are associated with the CallPath Services API.
For example, STL_OK is the pseudonym for an actual
integer value that can be returned in the variable that represents
the return_code parameter on program calls.
For a list of the integer values that are placed in the
variables, see
CallPath Services Programmer's Reference.
Messages are represented by both an informal
pseudonym and by a formal pseudonym.
A formal pseudonym represents a parameter or variable value.
For example, the informal pseudonym for the message that indicates
to a program that a party has become an active participant in a
telephone call is Call_Connected.
The formal pseudonym for Call_Connected is
STL_CALL_CONNECTED_MSG.
When a program issues a Receive program call and is returned
a Call_Connected message, the program is informed that
the message is a Call_Connected message by means of the
message_code parameter on Receive.
The program, when it issues the Receive program call, provides
a variable to represent the message_code parameter.
The CallPath Services subsystem places into the supplied variable a value
that indicates the message that is being returned in another
variable on the program call.
In this example, where a Call_Connected message is returned
to the program, the pseudonym associated with the returned
message_code parameter is
STL_CALL_CONNECTED_MSG and represents
the integer value that is actually placed into the variable.
(In this case, the integer value is 1.)
The informal pseudonyms associated with messages begin with a
capital letter, as does each portion of the name that follows
an underscore.
For example, Call_Alerting is used in place of the pseudonym
for the message_code parameter value of
STL_CALL_ALERTING_MSG.
STL_CALL_ALERTING_MSG, in turn, is used
in place of the actual message code value (in this case, an
integer value of 0).
As shown, formal pseudonyms associated with messages appear
in a common highlight style (for example,
STL_CALL_ALERTING_MSG).
To provide a complete example of how pseudonyms are used in
this book, suppose a program uses the Set_Automatic_Answer
program call to modify the call profile characteristic of
automatic_answer to a value of
STL_NO_ANSWER.
- The real name of the program call (as known by the CallPath Services
subsystem) for Set_Automatic_Answer is STLSAA
(see "STLSAA (Set_Automatic_Answer)"). STLSAA has a parameter
list of call_profile_ID,
automatic_answer, and return_code.
CallPath Services Programmer's Reference
contains a description of all the CallPath Services program calls, including
the syntax and semantics of the variables used for each call.
-
The automatic_answer variable that goes into the
call as a parameter is a 32-bit integer.
CallPath Services Programmer's Reference
provides a complete description of all variables.
-
The value of STL_NO_ANSWER that is placed
into the automatic_answer parameter on the call
to STLSAA is defined as an integer value of 1.
CallPath Services Programmer's Reference
shows the integer and pseudonym values defined for each variable.
-
Finally, the return_code value STL_OK
that is returned to the program on the call means that the
program call completed successfully.
The meaning of each CallPath Services return_code value is
provided in
CallPath Services Programmer's Reference.
Note: Pseudonym value names are not actually passed to the CallPath Services
subsystem as a string of characters.
Instead, the pseudonyms are merely used in this book to
represent the integer values that are passed to the program calls.
The pseudonym value names are used to aid readability of the text.
Programs should use translates and equates (depending on the
language) to aid the readability of the code.
For example, a program equate could be used to define
STL_NO_ANSWER as meaning an integer value of 1.
The actual program code would then read (as previously described)
that automatic_answer is replaced with
STL_NO_ANSWER.
The end result, however, is that an integer value of 1 is placed
into the variable.
This chapter provides installation and configuration
information for the ROLM 9751 CBX (Release 9005) hardware and software that is used
with CallPath SwitchServer/2.
Note: If you want to install CallPath Server/2, see Chapter 3. "Installation and Configuration for CallPath Server/2".
This chapter also
lists the additional hardware and software
required for the connection of CallPath SwitchServer/2 to the ROLM 9751 CBX (Release 9005).
Use this information with the installation instructions in
Using CallPath SwitchServer/2.
Figure 1 shows
the hardware configuration for the
ROLM 9751 CBX (Release 9005) and CallPath SwitchServer/2 connection.
Figure 1. Hardware Configuration for the ROLM 9751 CBX and SwitchServer/2 Connection
To use the ROLM 9751 CBX (Release 9005) with CallPath SwitchServer/2, the following hardware
and software are required:
- Hardware Requirements
- ROLM 9751 CBX (Release 9005), Model 10, 40, 50, or 70, with the following:
- System Monitor Input/Output Card (SMIOC)
Interconnect Box, Part Number 96D1553
- SMIOC, Part Number 98D0083
- SMIOC cable (EIA-232-D cable for
Inbound connection), Part Number 97D0035
- Outbound Dialer Interface (ODI) card
(required for an application to place outbound calls and
answer phones through the API),
Part Number 98D3918
Note: For application programs that issue an Answer_Call
program call for parties specified in a previous Make_Call
program call, a minimum of two ODI cards (and
associated cables) is required.
- ODI cable
(RS-422-A cable for Outbound connection):
- Part Number 98D3941 for Model 10
- Part Number 98D3942 for Model 40, 50, or 70
Note: The ODI interface cable is a custom cable with a
female 25-pin D connector (DB25) on one end and a
50-pin Amphenol connector on the other end (Outbound requires
one per ODI link).
Refer to the ROLM service and configuration
documentation for installing cables to the ROLM 9751 CBX (Release 9005).
Contact your ROLM 9751 CBX (Release 9005) installation agent for installation,
configuration, and upgrade changes to your ROLM 9751 CBX (Release 9005) hardware.
- Software Requirements
- Release
9005.1.75, 9005.1.78, 9005.1.79, or 9005.1.81
system software, with the
CallBridge**
for CallPath
feature
Contact your ROLM 9751 CBX (Release 9005) installation agent for installation,
configuration, and upgrade changes to your ROLM 9751 CBX (Release 9005) software.
To use CallPath SwitchServer/2 with the ROLM 9751 CBX (Release 9005),
the following hardware and software are required:
- Hardware Requirements
- An IBM Personal Computer (IBM PC) or compatible,
with an 80486** or higher processor
running at 66 Megahertz (MHz) or higher,
with the following minimum configuration:
- 16 megabytes (MB) of random access memory (RAM)
- 100MB fixed disk
- Adequate number of expansion slots to support the following:
- Communication card to the PBX (1 to 5 slots)
- Communication card to the CallPath host (if needed)
- Memory expansion board or boards (if needed)
- PC monochrome or color display
- Pointing device supported by the operating system version
you are running
- One or more Realtime Interface Co-Processor (RIC)
Multiport/2 cards with 1MB of
RAM (one for Inbound and up to four for Outbound),
Part Number 16F1820
- RIC Multiport/2 eight-port RS-422-A
interface board
for the Outbound connection (per installed Outbound
RIC card), Part Number 15F8852
(For details on the card and slot assignments and installation
instructions, see "Step 3: Installing the Hardware for the Switch and Host Connections to CallPath SwitchServer/2".)
- A RIC Multiport/2 eight-port EIA-232-D
interface board for the Inbound connection, Part Number 09F1952
(For details on the card and slot assignments and installation
instructions, see "Step 3: Installing the Hardware for the Switch and Host Connections to CallPath SwitchServer/2".)
- Multiport/2 Interface Cable Adapter (one for each RIC
card), Part Number 00F5531
- CallPath SwitchServer/2-to-host connectivity hardware;
see Using CallPath SwitchServer/2
Note: If you are using a PS/2 machine,
refer to the documentation included with your machine
for additional information about hardware options.
- Software Requirements
- Each CallPath SwitchServer/2 requires the following software:
- IBM Operating System/2*
(OS/2*)
Version 2.1 or higher, (including OS/2 Warp* Version 3.0)
and the latest Corrective Services Diskettes (CSDs)
- Communications Manager/2* Version 1.1 or higher,
and the latest CSDs
- CallPath SwitchServer/2-to-host connectivity software;
see Using CallPath SwitchServer/2
- CallBridge Link Manager program diskette
It is recommended that your
CallPath SwitchServer/2
PC
be dedicated to
running CallPath SwitchServer/2 and the programs listed in "CallPath SwitchServer/2 Hardware and Software Requirements".
During the CallPath SwitchServer/2 installation process, the CONFIG.SYS file is
automatically modified to include the following:
PRIORITY=ABSOLUTE
LIBPATH=C:\CPSS2;C:\GATEWAY\SWITCH;
DPATH=C:\CPSS2;C:\CPSS2\DATA;C:\GATEWAY\SWITCH;C:\GATEWAY\SWITCH\DATA;C:\GATEWAY\TEXT;
DEVICE=C:\GATEWAY\SWITCH\ICARICIO.SYS
PATH=C:\CPSS2;C:\GATEWAY\SWITCH;
IOPL=YES
During the CallPath SwitchServer/2 installation process,
the STARTUP.CMD file
is updated
to start CallPath SwitchServer/2 automatically.
No additional changes need to be made to the STARTUP.CMD file.
Following is an overview of the procedure for installing
and configuring the ROLM 9751 CBX (Release 9005) for use with CallPath SwitchServer/2:
- Step 1:
- Installing the ROLM 9751 CBX (Release 9005) hardware and software
- Step 2:
- Installing OS/2
- Step 3:
- Installing the hardware for the switch and host connections
- Step 4:
- (Ref #1.)Installing the CallPath SwitchServer/2 program
- Step 5:
- Installing CallBridge Link Manager
- Step 6:
- Installing Communications Manager/2
This procedure is described in detail in the following sections.
When you have completed these tasks, return to
Using CallPath SwitchServer/2 to configure
communications for the host connections.
Contact your ROLM 9751 CBX (Release 9005) representative to have the switch
installed and configured.
Install the OS/2 Base Operating System
according to the instructions in your OS/2 documentation.
Note: Install the latest Corrective Services Diskettes (CSDs) for OS/2.
After the ROLM 9751 CBX (Release 9005) hardware and Release 9005 system software is installed,
you are ready to install the CallPath SwitchServer/2-to-host connectivity hardware
and the RIC Multiport/2 card in the
PC.
See the documentation that accompanied your
adapter for instructions on installing
CallPath SwitchServer/2-to-host connectivity hardware.
After the ROLM 9751 CBX (Release 9005) hardware and
software are installed, you are ready to install the
RIC Multiport/2 cards in the
PC.
For ease of field support, the following card and slot assignments
are recommended:
| Slot
| Card
|
| 8
| Disk Controller
|
| 7
| Multiprotocol Adapter, Token Ring Adapter, or
X.25 Interface Co-Processor
|
| 6
| Outbound RIC
|
| 5
| XGA Adapter (if installed)
|
| 4
| Outbound RIC
|
| 3
| (empty)
|
| 2
| Inbound RIC
|
| 1
| (empty)
|
Notes:
- The first available slot after slot position 1
is designated for Inbound only.
- Any non-CallPath RIC cards must be installed in slot
numbers greater than any of the CallPath RIC cards.
- The PC
can have up to five RIC cards (one for Inbound
and four for Outbound).
To use four Outbound cards, move the Inbound card to slot 1 and use
slots 2 and 3 for an Outbound card.
- The SMIOC and the ODI connections can be
installed in any port (0-7) of the Multiport/2 cable adapter.
- Only one SMIOC port in the ROLM 9751 CBX (Release 9005) can be configured to
have the Inbound enabled.
|
To install the RIC Multiport/2 cards in the
PC,
do the following:
- Turn off the PC and unplug all cords and cables.
- Remove the cover from the PC system unit.
- Remove the PC expansion slot covers for the slots
that you plan to use to install the RIC Multiport/2 cards.
- Assemble the RIC Multiport/2 cards with the
RIC Multiport/2 eight-port interface boards
(Inbound and Outbound have different RIC Multiport/2
eight-port interface boards).
Refer to the documentation provided with the RIC
Multiport/2 cards for detailed assembly instructions.
- Install the RIC Multiport/2 cards in the expansion
slots by pressing the cards into the slot connectors until the
cards click into place.
- Secure the cards in the slots by tightening the screws.
- Connect a RIC Multiport/2 cable adapter to the connector
on each RIC Multiport/2 card that you installed in the
PC.
If you have questions, contact your IBM service representative.
- Replace the PC
cover and reconnect the cords and
cables that were unplugged in Step 1.
Note: If you are using a PS/2 machine,
refer to the documentation included with your machine
for additional information about hardware options.
To install CallPath SwitchServer/2 on the PC, do the following:
- Insert CallPath SwitchServer/2 program Diskette 1 in drive A.
- Open an OS/2 full-screen session.
- Enter a: to make drive A the current drive.
- Enter install.
A message informs you that the transfer utility program is
running, and the version level and modification level of the
CallPath SwitchServer/2 program are displayed.
Messages also prompt you to print the TIPS.TXT
set of instructions included with CallPath SwitchServer/2.
You will be informed that the necessary directories are about
to be created and that changes will be made to the
CONFIG.SYS and
STARTUP.CMD files.
- Select one of the following:
- n to stop the installation
- y to continue with the installation
The necessary directories are created and the files copied to them.
- Follow the instructions if you are prompted for additional diskettes.
After all the files are copied, a prompt asks if you want to update
the CONFIG.SYS file.
- Enter one of the following:
- y to update the CONFIG.SYS
- n to continue without updating the file
Changes to the CONFIG.SYS file do not take effect until
you restart your system.
A prompt asks whether you want you want to update the
STARTUP.CMD file.
- Enter one of the following:
- y to update the STARTUP.CMD file
- n to continue without updating
A prompt asks whether you want CallPath SwitchServer/2 to start automatically
when a critical error occurs.
- Enter one of the following:
- y to restart on errors
- n for the program to stop when an error occurs
Changes to the STARTUP.CMD file do not take effect
until you restart your system.
A prompt asks whether you want to view the
README.TXT file.
- Enter one of the following:
- y to display and view the README.TXT
file
- n to continue without displaying the
README.TXT file
The Installation Complete message is displayed.
- Remove the program diskette from drive A.
Continue with "Backing Up the CallPath SwitchServer/2 Program".
To back up the CallPath SwitchServer/2 program, do the following:
- Get two blank 3.5-inch, high-density diskettes
that have been formatted to 1.44MB.
- Open an OS/2 full-screen session.
- Enter c: to make drive C the current drive.
- Enter
cd\cpss2
to change to the CallPath SwitchServer/2 directory.
- Enter backss2 to start the backup utility program.
- Insert one of the blank diskettes into drive A.
- Enter y in response to the prompt to begin backing up.
- Follow the displayed instructions for inserting additional
diskettes if prompted to do so.
The message Backup
completed is displayed when the process is complete.
The OS/2 command prompt is displayed as well.
- Remove the backup diskette from the drive.
- Label the diskette or diskettes.
The CallBridge Link Manager program enables you to establish
communications between the CallPath SwitchServer/2
PC and the ROLM 9751 CBX (Release 9005).
When the ROLM 9751 CBX (Release 9005) and the PC are connected, Inbound
or both Inbound and Outbound capabilities are established.
These capabilities
enable you to have intelligent answering and coordinated data transfer
(Inbound) and computer-assisted dialing (Outbound).
WARNING: CallPath SwitchServer/2 must be installed on your
PC before
installing CallBridge Link Manager.
Following is an overview of the tasks required for installing
and configuring communications between CallPath SwitchServer/2 and the ROLM 9751 CBX (Release 9005):
- Installing the CallBridge Link Manager program
- Selecting the switch connection
- Configuring the RIC card
- Configuring the port number
- Selecting the inbound baud rate
- Specifying the outbound dialer number
- Specifying the outbound timeout values
- Processing the ROLM 9751 CBX (Release 9005) connection configuration
Tasks related to installing and configuring communications
between the ROLM 9751 CBX (Release 9005) and CallPath SwitchServer/2 include the following:
- Backing up the ROLM 9751 CBX (Release 9005) software
- Modifying the ROLM 9751 CBX (Release 9005) connection configuration
- Reinstalling the CallBridge Link Manager Program
These tasks are described in more detail in the sections
that follow.
To install CallBridge Link Manager on your PC, do the following:
- Insert the CallBridge Link Manager program diskette in drive A.
- On an OS/2 full-screen session, enter
a: to make drive A the default drive.
- Enter cblminst to install the CallBridge Link Manager program.
A message informs you that the installation of the CallBridge Link Manager
program has started.
The directory C:\GATEWAY will be created and the
files on the installation program copied to it.
A message asks if you wish to continue.
- Enter y to continue with the installation.
The installation program runs and ensures that the necessary
directories are created on the fixed disk.
As each program is copied, a confirmation message is displayed
on your screen.
After all the files and directories are copied onto your fixed
disk and the CONFIG.SYS file is updated (as shown in
"Checking the CONFIG.SYS File"), the Switch Connection Configuration window,
shown in Figure 2, is displayed.
Continue with "Selecting the Switch Connection".
The Switch Connection Configuration window
in Figure 2
enables you to
configure the connections to the ROLM 9751 CBX (Release 9005) for Inbound only, or for both
Inbound and Outbound.
Configuring the connection to the ROLM 9751 CBX (Release 9005) for Inbound enables the host
application to locate and display customer information on an
agent's terminal.
Configuring the connection to the ROLM 9751 CBX (Release 9005) for Outbound enables the host
application to place calls to a group of customers in a customer
database.
Figure 2. Switch Connection Configuration Window Example (Inbound and Outbound Selected)
+--------------------------------------------------------------------------------+
| Help |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Switch Connection Configuration |
| |
| Select a choice and press ENTER. |
| |
| |
| 2 1. INBOUND |
| 2. INBOUND and OUTBOUND |
| |
| |
| |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To select the switch connection,
do the following:
Continue with "Configuring a RIC Card".
The RIC Card Selection window, shown in
Figure 3, enables
you to select a card slot number for configuration or to
view a card slot number that was previously configured.
The card slot number is the slot on the back of the
PC
to which the RIC Multiport/2 interface cable
is connected.
The RIC Card Selection Status list
near the center of the window
indicates the status of the card slot numbers that have been
previously selected.
An I or O before each
RIC Card Selection Status number
indicates that the card slot number is configured for
Inbound (I) or Outbound (O).
Only one card slot number can be configured for Inbound.
Figure 3. RIC Card Selection Window Example
+--------------------------------------------------------------------------------+
| Help |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| RIC Card Selection |
| |
| Type a Card Slot Number to configure or view. 2 (1-8) |
| |
| Indicate if card is to be SELECTED(1) or UNSELECTED(2). 1 (1/2) |
| |
| Indicate if card is an INBOUND(1) or OUTBOUND(2) slot. 1 (1/2) |
| |
| Then press ENTER. |
| RIC Card Selection Status |
| |
| _ 1 |
| I 2 |
| _ 3 |
| _ 4 |
| _ 5 |
| _ 6 |
| _ 7 |
| _ 8 |
| |
| I = INBOUND O = OUTBOUND |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To configure a RIC card, do the following:
- In the first selection field, type the card slot number
that you want to configure or view.
The cursor moves to the "Indicate if card is SELECTED(1) or
UNSELECTED(2)" field.
- Do one of the following:
- Enter one of the following:
- 1 if the selected card slot number is to be
Inbound
- 2 if the selected card slot number is to be Outbound
The Port Configuration window is displayed.
Continue with "Configuring the Port Number".
The Port Configuration window, shown in Figure 4,
enables you to select a port number for configuration or to view
a port number that was previously configured. The port
number is the number of the port slot on the RIC Multiport/2
interface cable that is connected to the ROLM 9751 CBX (Release 9005).
The Port Selection Status list indicates the status of the
port numbers that have been previously selected.
An S before each Port Selection Status number
indicates that the port number is selected.
Only one port number can be selected and configured for Inbound.
Figure 4. Port Configuration Window Example
+--------------------------------------------------------------------------------+
| Help |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Port Configuration for Card Slot 2 |
| |
| |
| Type a Port Number to configure or view. 0 (0-7) |
| |
| Indicate if port is to be SELECTED(1) or UNSELECTED(2). 1 (1/2) |
| |
| Then press ENTER. |
| |
| Port Selection Status |
| |
| S 0 9600 BAUD |
| _ 1 |
| _ 2 |
| _ 3 |
| _ 4 |
| _ 5 |
| _ 6 |
| _ 7 |
| |
| |
| S = SELECTED |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To configure or view the port number, do the following:
- In the first selection field, type the number of the port
that you want to configure or view.
The cursor moves to the "Indicate if port is to be SELECTED(1) or
UNSELECTED(2)" field.
- Do one of the following:
- Press Enter to process your selections, then
do one of the following:
The INBOUND Baud Rate window in Figure 5
enables you to select a baud rate, which
is the line speed of the ROLM 9751 CBX (Release 9005) that is associated with a specific port.
The baud rate can be 9,600 or 19,200.
Figure 5. INBOUND Baud Rate Window Example (9600 Baud Selected)
+--------------------------------------------------------------------------------+
| Help |
|- - - - - - - - - - - - - - - *------------------------------------* - |
| Port Configurat| INBOUND Baud Rate | |
| | | |
| |Select a BAUD RATE and press ENTER. | |
| Type a Port Number to configu| | |
| | 1 1. 9600 baud | |
| Indicate if port is to be SEL| 2. 19200 baud | |
| | | |
| Then press ENTER. | | |
| |F1=Help F12=Cancel | |
| Port Selecti*------------------------------------* |
| |
| S 0 9600 BAUD |
| _ 1 |
| _ 2 |
| _ 3 |
| _ 4 |
| _ 5 |
| _ 6 |
| _ 7 |
| |
| |
| S = SELECTED |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To select the inbound baud rate, do the following:
- In the selection field, type one of the following:
- 1 to use the 9,600 baud rate (the default value)
- 2 to use the 19,200 baud rate
- Press Enter to return to the Port Configuration window
so that you can view the selected baud rate.
- Press F3 to return to the RIC Card Selection window.
- Proceed to "Processing the ROLM 9751 CBX Connection Configuration"
to complete the configuration process.
The OUTBOUND Dialer Number window
in Figure 6 lets you select
the dialer number that is configured on the ROLM 9751 CBX (Release 9005).
Use the dialer number configured on the ROLM 9751 CBX (Release 9005) for each ODI
interface card.
Figure 6. OUTBOUND Dialer Number Window Example
+--------------------------------------------------------------------------------+
| Help |
| - - - - - - - - - - - - - - *--------------------------------------*- |
| Port Configura| OUTBOUND Dialer Number for Port 4 | |
| | | |
| | Type number and press ENTER. | |
| Type a Port Number to config| | |
| | Dialer number 230 (1-999999) | |
| Indicate if port is to be SE| | |
| | | |
| Then press ENTER. | | |
| | F1=Help F12=Cancel | |
| Port Select*--------------------------------------* |
| |
| 0 |
| 1 |
| 2 |
| 3 |
| 4 |
| S 5 240 |
| S 6 245 |
| 7 |
| |
| |
| S = SELECTED |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To specify the outbound dialer number, do the following:
- In the selection field, type the outbound dialer number that is local
to the ROLM 9751 CBX (Release 9005).
The dialer number must consist of numeric
characters in the range of 1 through 999999.
Do not use leading zeros in the dialer number.
- Press Enter to return to the Port Configuration window
so that you can view the selected dialer number.
- Do one of the following:
The OUTBOUND Timeout Values window
in Figure 7 lets you specify the values
for Calling Party Timeout and Called Party Timeout.
Calling Party Timeout is the length of time in seconds that
CallPath SwitchServer/2 waits for a connection from the calling party before giving
a positive response to the request and a Call_Rejected event message.
Called Party Timeout is the length of time in seconds that
CallPath SwitchServer/2
waits for a connection from the called party before giving a positive
response to the request and a Call_Rejected event message.
Figure 7. OUTBOUND Timeout Values Window Example
+--------------------------------------------------------------------------------+
| Help |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| OUTBOUND Timeout Values |
| |
| Type Timeout Values (seconds) and press ENTER. |
| |
| |
| Calling Party Timeout 60 (1-255) seconds. |
| |
| Called Party Timeout 40 (1-255) seconds. |
| |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To specify the outbound timeout values, do the following:
- In the first selection field, type the number of seconds you want
for Calling Party Timeout and press the Tab key.
The default is 60 seconds.
If you want to use the default, press the Tab key.
The cursor moves to the "Called Party Timeout" field.
- Enter the number of seconds you want for Called Party Timeout.
The default is 40 seconds.
- Press Enter.
- Press F3.
- Press F3 to return to the Switch Connection Configuration
window so that you can complete the configuration process.
Continue with "Processing the ROLM 9751 CBX Connection Configuration".
When you have completed the configuration,
do the following to process it:
- Press F3 to save your configuration data
and enable the installation
to complete.
- When the message ROLM CallBridge link support installation
complete is displayed on the OS/2 full screen,
remove the CallBridge Link Manager program diskette from the A drive.
Continue with "Backing Up CallBridge Link Manager".
At this point, it is advisable to make a backup copy of
CallBridge Link Manager.
You need a blank 3.5-inch, high-density diskette,
formatted to 1.44MB.
To make a backup copy of
CallBridge Link Manager, do the following:
- Open an OS/2 full-screen session.
- Enter C: to make
drive C the current drive.
- Enter cd\gateway
to make C:\GATEWAY the current directory.
- Insert the blank, formatted backup diskette into drive A.
Ensure that the diskette is write-enabled.
- Enter cblminst to run the transfer utility program.
A message informs you that the CallBridge Link Manager program files will be
saved on the diskette in drive A, and asks if you want to continue.
- Enter y to copy the files to the diskette.
The files are saved to the backup diskette.
As each file is copied, a confirmation message is displayed.
If your backup procedure requires more than one diskette, the
transfer utility program prompts you as necessary.
When the backup process is complete, the message Backup
complete is displayed and the OS/2 prompt is redisplayed.
- Remove the diskette and label it.
Store the original program diskette in a secure place.
Continue with "Step 6: Installing Communications Manager/2".
You can modify the ROLM 9751 CBX (Release 9005) connection configuration data at any time.
Follow the instructions in
Using CallPath SwitchServer/2 and in "Selecting the Switch Connection".
You may need to reinstall CallBridge Link Manager.
You can repeat the installation process, using either a
new distribution diskette or a backup program diskette.
To reinstall CallBridge Link Manager, follow the procedures described in
"Step 5: Installing CallBridge Link Manager", but note the following differences in
the procedure:
- While the installation program runs, the messages indicate
that the directories already exist on the fixed disk, rather than
being created.
- The CONFIG.SYS file is already updated.
- Starting with the Switch Connection Configuration window,
values from the initial installation appear in
the selection fields in the windows.
Enter the selections you want over the existing values.
If you are reinstalling from a backup diskette, you do not need
to make another backup copy of the diskette.
However, if you are installing a new version of CallBridge Link Manager from a
distribution diskette, follow the
instructions for making a backup copy after installation.
To install Communications Manager/2
Version 1.1, do the following:
- Insert Diskette 1 of Communications Manager/2 into drive A.
- Type a:cmsetup on the command line of an
OS/2 full-screen session and press Enter.
The Communications Manager/2 copyright window is displayed.
- Select OK.
- Select Continue....
The Target Drive Selection window is displayed.
- Select the target drive and press Enter.
- If a version of Communications Manager/2 has already been installed
on the PC,
a window appears asking whether you want to
update the previous version. Select OK. The
Communications Manager/2 Setup window is displayed.
- Open an OS/2 window.
- Use the OS/2 COPY command to copy an existing
configuration file from the CPSS2 CallPath directory to
one of your own directories in the CMLIB Communications
directory.
The CPSS2 CallPath directory contains these example
user configuration files:
- CPSS2TR
- Configuration for host connection through an IBM token ring
network
- CPSS2SD
- Configuration for host connection through an SDLC link
- CPSS2X2
- Connection for host connection through an IBM X.25 network
- CPSS2EN
- Configuration for host connection through an Ethernet network
For each example configuration there are four file
types with the following extensions:
.cfg
.cf2
.ndf
.sec
You can copy the example configuration files from the
C:\CPSS2
directory into the C:\CMLIB
directory, or create your own.
For example, enter the following to
copy the token ring configuration files:
copy c:\cpss2\cpss2tr.*
c:\cmlib
You can then modify the required profiles using your copy of the
configuration files as a model.
If this CallPath SwitchServer/2 will connect to CallPath/2 or CallPath/6000
as a host, use the notes concerning CallPath/2 in
Using CallPath SwitchServer/2.
- Select Setup...
from the Communications
Manager Setup window.
- Insert the Communications Manager/2 diskettes as prompted.
- Select the configuration file you copied
in Step 8.
A window is displayed asking whether the configuration file will be
used on this workstation.
- Select OK, then select
YES.
- Refer to Using CallPath SwitchServer/2 to complete the configuration
for your host.
This chapter provides installation and configuration
information for the ROLM 9751 CBX (Release 9005) hardware and software that is used
with CallPath Server/2.
Note: If you want to install CallPath SwitchServer/2
for the communication link to the ROLM 9751 CBX (Release 9005),
see Chapter 2. "Installation and Configuration for CallPath SwitchServer/2".
This chapter also lists
the additional hardware and software
required for the connection of CallPath Server/2 to the ROLM 9751 CBX (Release 9005).
Use these instructions with the installation instructions in the
CallPath Server Planning, Installation,
and Problem Determination Guide.
Figure 8 shows
the hardware configuration for the
ROLM 9751 CBX (Release 9005) and CallPath Server/2 connection.
Figure 8. Hardware Configuration for the ROLM 9751 CBX (Release 9005) and CallPath Server/2 Connection
To use the ROLM 9751 CBX (Release 9005) with CallPath Server/2, the following hardware
and software are required:
- Hardware Requirements
- ROLM 9751 CBX (Release 9005), Model 10, 40, 50, or 70, with the following:
- System Monitor Input/Output Card (SMIOC)
Interconnect Box, Part Number 96D1553
- SMIOC, Part Number 98D0083
- SMIOC cable (EIA-232-D cable for
Inbound connection), Part Number 97D0035
- Outbound Dialer Interface (ODI) card
(required for an application to place outbound calls and
answer phones through the API),
Part Number 98D3918
Note: For application programs that issue an Answer_Call
program call for parties specified in a previous Make_Call
program call, a minimum of two ODI cards (and
associated cables) is required.
- ODI cable
(RS-422-A cable for Outbound connection):
- Part Number 98D3941 for Model 10
- Part Number 98D3942 for Model 40, 50, or 70
Note: The ODI interface cable is a custom cable with a
female 25-pin D connector (DB25) on one end and a
50-pin Amphenol connector on the other end (Outbound requires
one per ODI link).
Refer to the ROLM service and configuration
documentation for installing cables to the ROLM 9751 CBX (Release 9005).
Contact your ROLM 9751 CBX (Release 9005) installation agent for installation,
configuration, and upgrade changes to your ROLM 9751 CBX (Release 9005) hardware.
Note: If you are using a PS/2 machine,
refer to the documentation included with your machine
for additional information about hardware options.
- Software Requirements
- Release
9005.1.75, 9005.1.78, 9005.1.79, or 9005.1.81
system software, with the CallBridge
for CallPath feature.
Contact your ROLM 9751 CBX (Release 9005) installation agent for installation,
configuration, and upgrade changes to your ROLM 9751 CBX (Release 9005) software.
To use CallPath Server/2 in a direct connection with the ROLM 9751 CBX (Release 9005) switch,
the following hardware and software are required
in addition to the base CallPath Server/2
hardware and software requirements
that are described in the Planning, Installation,
and Problem Determination Guide:
- Hardware Requirements
- For the IBM Personal Computer (IBM PC) running
CallPath Server/2:
- One or more Realtime Interface Co-Processor (RIC)
Multiport/2 cards with 1MB of
RAM (one for Inbound and up to four for Outbound),
Part Number 16F1820
- RIC Multiport/2 eight-port RS-422-A
interface board
for the Outbound connection (per installed Outbound
RIC card), Part Number 15F8852
(For details on the card and slot assignments and installation
instructions, see "Installing the RIC Multiport/2 Cards".)
- A RIC Multiport/2 eight-port EIA-232-D
interface board for the Inbound connection, Part Number 09F1952
(For details on the card and slot assignments and installation
instructions, see "Installing the RIC Multiport/2 Cards".)
- Multiport/2 Interface Cable Adapter (one for each RIC
card), Part Number 00F5531.
- An adequate number of expansion slots to support the following:
- Communication card to the CBX
- Communication card to the client workstations
- Memory expansion board or boards (if needed)
- Adapter for connection to token ring or Ethernet LAN to
connect to the client workstations
Refer to the ROLM service and configuration
documentation for installing cables to the ROLM 9751 CBX (Release 9005).
Contact your ROLM 9751 CBX (Release 9005) installation agent for installation,
configuration, and upgrade changes to your ROLM 9751 CBX (Release 9005) hardware.
- Software Requirements
- Each CallPath Server/2 requires the following additional software:
- CallPath Server/2 Direct-Attached IBM Telephone System Connection for the ROLM 9751 CBX (Release 9005)
product diskettes (hereafter called switch-dependent code feature)
- CallBridge Link Manager program diskette
The OS/2 CONFIG.SYS
file can be updated automatically
during CallPath Server/2 installation.
After you install CallPath Server/2, you can add a statement to
the STARTUP.CMD file to start the CallPath Server Management Facility
automatically whenever the PC is restarted.
During the CallPath Server/2 installation process, the CONFIG.SYS file is
automatically modified to include the following
for the ROLM 9751 CBX (Release 9005):
PRIORITY=ABSOLUTE
LIBPATH=C:\CPSS2;C:\GATEWAY\SWITCH;
DPATH=C:\CPSS2;C:\CPSS2\DATA;C:\GATEWAY\SWITCH;C:\GATEWAY\SWITCH\DATA;C:\GATEWAY\TEXT;
DEVICE=C:\GATEWAY\SWITCH\ICARICIO.SYS
PATH=C:\CPSS2;C:\GATEWAY\SWITCH;
IOPL=YES
After installing CallPath Server/2 and completing the
configuration for CallPath Server/2 and the connection to the ROLM 9751 CBX (Release 9005),
you can start the CallPath Server Management Facility automatically
each time the PC
is restarted by adding the following line
to the STARTUP.CMD file:
csasrvr
If the first CallPath Server/2 installation diskette contains a
README or TIPS file,
read it before installing CallPath Server/2.
Following is an overview of the procedure for installing and
configuring CallPath Server/2 and the communication links with the
ROLM 9751 CBX (Release 9005):
- Step 1:
- Installing and configuring OS/2
- Step 2:
- Installing and configuring
TCP/IP
hardware and software
- Step 3:
- Installing CallPath Server/2
- Step 4:
- Restarting the CallPath Server/2 computer
- Step 5:
- Starting the CallPath Server Management Facility and configuring CallPath Server/2
- Step 6:
- Installing and configuring
CallPath Server/2-to-ROLM 9751 CBX (Release 9005) communications
- Step 7:
- Restarting the CallPath Server/2 computer
- Step 8:
- Starting CallPath Server/2 and the ROLM 9751 CBX (Release 9005)
This procedure is described in detail in the following sections.
Note: If you are modifying an existing ROLM 9751 CBX (Release 9005) configuration,
start with Step 6.
Make sure that OS/2 is installed and running before
installing CallPath Server/2.
Note: Install the latest Corrective Services Diskettes (CSDs) for OS/2.
Install and configure TCP/IP for the communications between
the CallPath Server/2 computer
and the client workstations.
Different procedures are required for TCP/IP installation and
configuration depending on your operating environment.
After installing OS/2, install the networking hardware, and
install and configure TCP/IP for communications between the
CallPath Server/2 computer and the clients.
When configuring TCP/IP,
select to autostart the PortMapper from TCP/IP configuration so
that it will start whenever OS/2 is started.
When installing TCP/IP, use the following procedure:
- If given the option, do not select to install LAPS (or MPTS).
- If given the option, do not select to Configure Network Connection.
- Select to autostart the PortMapper from the TCP/IP configuration so
that it will start whenever OS/2 is started.
- Select the loopback interface when Configuring the
Network Interface Parameters.
This can be done from the TCP/IP Configuration panels or it
can be done by manually editing the TCP/IP files.
To edit the TCP/IP files manually, you must first know their location.
The location was specified in the CONFIG.SYS file
during TCP/IP installation.
You can obtain this information by entering set etc
at the command prompt or by viewing the CONFIG.SYS file.
For example, in the CONFIG.SYS file, you might see
the following:
- set etc=c:\mptn\etc
- or
- set etc=c:\tcpip\etc
The location of the TCP/IP files is the directory specified
just before \etc in the
set etc statement in the CONFIG.SYS file;
in this case, either c:\mptn or c:\tcpip.
This directory will be referred to as <tcp_dir>
in the remaining steps.
To select the loopback interface, do the following:
- Change to the <tcp_dir>\bin directory.
- Edit the SETUP.CMD file to include the
TCP/IP loopback address by adding the following statement to
the end of the file:
ifconfig lo 127.0.0.1
- Assign an alias hostname to the loopback address.
This can be done from the TCP/IP Configuration panels for hostnames
or it can be done manually, as follows:
- Change to the <tcp_dir>\etc directory.
- Edit the HOSTS file to assign an alias for the
loopback address by adding the following statement to the end
of the file:
- 127.0.0.1 XYZ (where XYZ is the alias)
Note: Be sure to use an editor that does not embed null characters,
since this interferes with TCP/IP processing of the HOSTS file.
CallPath Server/2 comes with an Installation Utility
that copies selected CallPath Server/2 component files to
the directory and path you specify, decompresses them,
and if you want,
makes the necessary modifications to the CONFIG.SYS and
STARTUP.CMD files for you.
The Installation Utility also backs up the original
CONFIG.SYS file to a
CONFIG.nnn
file during the installation process,
where nnn is 000 to 999.
To install CallPath Server/2, do the following:
- (For diskette installation only) Insert
CallPath Server/2 product diskette 1 in the source disk drive.
- At the OS/2 command prompt, enter
<drive>:install,
where <drive>
is one of the following:
- Drive letter of the diskette drive containing product diskette 1
- Drive letter and path where CallPath Server/2 files were previously installed
- Select CallPath Server/2.
(CallPath Server/2
is the default selection for first-time installation
and is required.)
- Click on OK to accept the selection.
- Follow the prompts.
See the CallPath Server Planning, Installation, and Problem
Determination Guide for detailed instructions on installing
CallPath Server/2.
To activate the CallPath Server/2 installation,
restart the CallPath Server/2 computer.
Following is an overview of the tasks required for
starting the CallPath Server Management Facility and configuring CallPath Server/2:
- Starting the CallPath Server Management Facility
- Configuring CallPath Server/2
- Starting the CallPath Server/2 subsystem to confirm that
the CallPath Server/2 configuration works
These tasks are described in more detail in the
following sections.
If you encounter errors or problems when trying to start
CallPath Server/2, see the CallPath Server Planning, Installation, and
Problem Determination Guide.
To start the CallPath Server Management Facility, do one of the following:
- Enter csasrvr at the OS/2 command prompt.
- Double-click on the CallPath folder on the OS/2
desktop and then double-click on the CallPath Server/2 icon.
Once CallPath Server/2 is started,
the CallPath Server Management Facility window and the Product Information window
are displayed.
If password protection was enabled, the Administrative Password window
is also displayed and the password must be entered to gain access
to the CallPath Server Management Facility configuration functions.
To enter the password and gain access to the CallPath Server Management Facility,
type the password, then click on OK.
Note: The default password, until you change it, is password.
See the CallPath Server Planning,
Installation, and Problem Determination
Guide
for a description of the CallPath Server Management Facility window and
how to use the window's features.
CallPath Server/2 requires certain operating parameters before it can
communicate with client applications.
The following are the minimum parameters you must enter:
- Maximum number of applications capable of connecting to the
server at the same time
- Maximum number of concurrent users allowed
to access CallPath Server/2
To configure CallPath Server/2, do the following:
- Display the Set Server Configuration window
in one of the following ways:
- From the CallPath Server Management Facility menu bar
- Select the Configuration menu.
- Select the Server menu option.
- From the CallPath Server icon
- Select the CallPath Server icon
using the mouse menu button.
- Select Configuration.
- Enter new maximum values for the following fields
(see the CallPath Server Planning, Installation, and Problem
Determination Guide for information on
tuning the CallPath Server/2 parameters in this window):
- Number of concurrent applications
- The maximum number of applications that will be running
at the same time.
- Number of concurrent users
- Set to the number of authorized concurrent users.
Contact your purchasing organization if you do not know
this number.
- Click on OK to accept the CallPath Server/2 configuration values.
The new configuration values take effect the next time
CallPath Server/2 is started.
After starting the CallPath Server Management Facility,
start the CallPath Server/2 subsystem
in one of the following ways:
- From the CallPath Server Management Facility window:
- Select the Administration menu option from
the menu bar.
- Select the Server menu option.
- Select Start.
- Click on one of the following in response
to the confirmation message:
- Yes to start the CallPath Server/2 subsystem
- No to return to the CallPath Server Management Facility window
without starting the CallPath Server/2 subsystem
- Select Yes from the confirmation message window.
- From the CallPath Server icon:
- Click on the CallPath Server icon.
- Select Start.
- Click on one of the following in response
to the confirmation message:
- Yes to start the CallPath Server/2 subsystem
- No to return to the CallPath Server Management Facility window
without starting the CallPath Server/2 subsystem
If you are installing CallPath Server/2 for the first time,
you should try starting
the CallPath Server/2 subsystem
to make sure that the configuration works.
If you cannot start
the CallPath Server/2 subsystem, see the
CallPath Server Planning, Installation, and
Problem Determination Guide.
Following is an overview of the tasks required for installing
and configuring communications between CallPath Server/2 and the
ROLM 9751 CBX (Release 9005):
- Installing the ROLM 9751 CBX (Release 9005)
- Installing the RIC Multiport/2 Card in the PC
- Installing CallBridge Link Manager
- Installing the ROLM 9751 CBX (Release 9005) switch-dependent code feature
- Setting up the CallPath Server/2 communication parameters
These tasks are described in more detail in the following sections.
Contact your ROLM 9751 CBX (Release 9005) representative to have the switch
installed and configured.
Continue with "Installing the RIC Multiport/2 Cards".
After the ROLM 9751 CBX (Release 9005) hardware and software are installed,
you are ready to install the
RIC Multiport/2 cards in the PC.
For ease of field support, the following card and slot assignments
are recommended:
| Slot
| Card
|
| 8
| Disk Controller
|
| 7
| Multiprotocol Adapter, Token ring Adapter, or
X.25 Interface Co-Processor
|
| 6
| Outbound RIC
|
| 5
| XGA Adapter (if installed)
|
| 4
| Outbound RIC
|
| 3
| (empty)
|
| 2
| Inbound RIC
|
| 1
| (empty)
|
Notes:
- The first available slot after slot position 1
is designated for Inbound only.
- Any non-CallPath RIC cards must be installed in slot
numbers greater than any of the CallPath RIC cards.
- The PC can have up to
five RIC cards (one for Inbound
and four for Outbound).
To use four Outbound cards, move the Inbound card to slot 1 and use
slots 2 and 3 for Outbound cards.
- The SMIOC and the ODI connections can be
installed in any port (0-7) of the Multiport/2 cable adapter.
- Only one SMIOC port in the ROLM 9751 CBX (Release 9005) can be configured to
have the Inbound enabled.
|
To install the RIC Multiport/2 cards in the PC,
do the following:
- Turn off the PC and unplug all cords and cables.
- Remove the cover from the PC system unit.
- Remove the PC expansion slot covers for the slots
that you plan to use to install the RIC Multiport/2 cards.
- Assemble the RIC Multiport/2 cards with the
RIC Multiport/2 eight-port interface boards
(Inbound and Outbound have different RIC Multiport/2
eight-port interface boards).
Refer to the documentation provided with the RIC
Multiport/2 cards for detailed assembly instructions.
- Install the RIC Multiport/2 cards in the expansion
slots by pressing the cards into the slot connectors until the
cards click into place.
- Secure the cards in the slots by tightening the screws.
- Connect a RIC Multiport/2 cable adapter to the connector
on each RIC Multiport/2 card that you installed in the
PC.
If you have questions, contact your IBM service representative.
- Replace the PC
cover and reconnect the cords and
cables that were unplugged in Step 1.
Note: If you are using a PS/2 machine,
refer to the documentation included with your machine
for additional information about hardware options.
Use the CallPath Server/2 Installation Utility
to install the ROLM 9751 CBX (Release 9005) switch-dependent code feature
on the PC running CallPath Server/2.
To install the ROLM 9751 CBX (Release 9005) switch-dependent code feature,
do the following:
- (For diskette installation only) Insert
CallPath Server/2 product diskette 1 in the source disk drive.
- At the OS/2 command prompt, enter
<drive>:install,
where <drive>
is one of the following:
- Drive letter of the diskette drive containing product diskette 1
- Drive letter and path where CallPath Server/2 files were previously installed
- Select Switch Dependent to
install the ROLM 9751 CBX (Release 9005) switch-dependent code feature.
Note: CallPath Server/2 must be installed before you
install the ROLM 9751 CBX (Release 9005) switch-dependent code feature.
- Click on OK to accept the selection.
- Follow the prompts.
See the
CallPath Server Planning, Installation, and Problem
Determination Guide for detailed instructions on installing
CallPath Server/2.
Continue with "Installing CallBridge Link Manager".
The CallBridge Link Manager program allows you to establish
communications between the PC and the ROLM 9751 CBX (Release 9005).
When the ROLM 9751 CBX (Release 9005) and the PC are connected, Inbound
or both Inbound and Outbound capabilities are established.
These capabilities
enable you to have intelligent answering and coordinated data transfer
(Inbound) and computer-assisted dialing (Outbound).
WARNING:
The switch-dependent code feature must be installed on your PC before
installing CallBridge Link Manager.
To install CallBridge Link Manager on your PC, do the following:
- Insert the CallBridge Link Manager program diskette
into drive A.
- On an OS/2 full-screen session, enter
a: to make drive A the default drive.
- Enter cblminst to install the CallBridge Link Manager program.
A message informs you that the installation of the CallBridge Link Manager
program has started.
The directory C:\GATEWAY is created and the
files in the installation program are copied to it.
A message prompts you to continue.
- Enter y to continue with the installation.
The installation program runs and ensures that the necessary
directories are created on the fixed disk.
As each program is copied, a confirmation message is displayed
on your screen.
After all files and directories are copied to your fixed
disk and the CONFIG.SYS file is updated (as shown in
"Updating the CONFIG.SYS File"), the Switch Connection Configuration window
(Figure 9) is displayed.
Continue with "Selecting the Switch Connection".
The Switch Connection Configuration window
in Figure 9
lets you
configure the connections to the ROLM 9751 CBX (Release 9005) for Inbound only, or for both
Inbound and Outbound.
Configuring the connection to the ROLM 9751 CBX (Release 9005) for Inbound enables the host
application to locate and display customer information on an
agent's terminal.
Configuring the connection to the ROLM 9751 CBX (Release 9005) for Outbound enables the host
application to place calls to a group of customers in a customer
database.
Figure 9. Switch Connection Configuration Window Example (Inbound and Outbound Selected)
+--------------------------------------------------------------------------------+
| Help |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Switch Connection Configuration |
| |
| Select a choice and press ENTER. |
| |
| |
| 2 1. INBOUND |
| 2. INBOUND and OUTBOUND |
| |
| |
| |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To select the switch connection,
do the following:
Continue with "Configuring the RIC Card".
The RIC Card Selection window, shown
in Figure 10,
lets you select a card slot number for configuration or to
view a card slot number that was previously configured.
The card slot number is the slot on the back of the
PC
to which the RIC Multiport/2 interface cable is connected.
The RIC Card Selection Status list
near the center of the window
indicates the status of the card slot numbers that have been
previously selected.
An I or O before each
RIC Card Selection Status number
indicates that the card slot number is configured for
Inbound (I) or Outbound (O).
Only one card slot number can be configured for Inbound.
Figure 10. RIC Card Selection Window Example
+--------------------------------------------------------------------------------+
| Help |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| RIC Card Selection |
| |
| Type a Card Slot Number to configure or view. 2 (1-8) |
| |
| Indicate if card is to be SELECTED(1) or UNSELECTED(2). 1 (1/2) |
| |
| Indicate if card is an INBOUND(1) or OUTBOUND(2) slot. 1 (1/2) |
| |
| Then press ENTER. |
| RIC Card Selection Status |
| |
| _ 1 |
| I 2 |
| _ 3 |
| _ 4 |
| _ 5 |
| _ 6 |
| _ 7 |
| _ 8 |
| |
| I = INBOUND O = OUTBOUND |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To configure a RIC card, do the following:
- In the first selection field, type the card slot number
that you want to configure or view.
The cursor moves to the "Indicate if card is SELECTED(1) or
UNSELECTED(2)" field.
- Do one of the following:
- Enter one of the following:
- 1 if the selected card slot number is to be
Inbound
- 2 if the selected card slot number is to be Outbound
The Port Configuration window is displayed.
Continue with "Configuring the Port Number".
The Port Configuration window,
shown in Figure 11,
lets you select
a port number for configuration or to view
a port number that was previously configured.
The port number is the number of the port slot on the RIC Multiport/2
interface cable that is connected to the ROLM 9751 CBX (Release 9005).
The Port Selection Status list indicates the status of the
port numbers that have been previously selected.
An S before each Port Selection Status number
indicates that the port number is selected.
Only one port number can be selected and configured for Inbound.
Figure 11. Port Configuration Window Example
+--------------------------------------------------------------------------------+
| Help |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Port Configuration for Card Slot 2 |
| |
| |
| Type a Port Number to configure or view. 0 (0-7) |
| |
| Indicate if port is to be SELECTED(1) or UNSELECTED(2). 1 (1/2) |
| |
| Then press ENTER. |
| |
| Port Selection Status |
| |
| S 0 9600 BAUD |
| _ 1 |
| _ 2 |
| _ 3 |
| _ 4 |
| _ 5 |
| _ 6 |
| _ 7 |
| |
| |
| S = SELECTED |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To configure or view the port number, do the following:
- In the first selection field, type the number of the port
that you want to configure or view.
The cursor moves to the "Indicate if port is to be SELECTED(1) or
UNSELECTED(2)" field.
- Do one of the following:
- Press Enter to process your selections, then
do one of the following:
- If you selected an Inbound card slot number on the RIC
Card Selection window, the INBOUND Baud Rate window is displayed.
Proceed to "Selecting Inbound Baud Rate".
- If you selected an Outbound card slot number on the RIC
Card Selection window, the OUTBOUND Dialer Number window is displayed.
Continue with "Specifying Outbound Dialer Number".
The INBOUND Baud Rate window
(Figure 12)
enables you to select a baud rate, which
is the line speed of the ROLM 9751 CBX (Release 9005) that is associated with a specific port.
The baud rate can be 9,600 or 19,200.
Figure 12. INBOUND Baud Rate Window Example (9600 Baud Selected)
+--------------------------------------------------------------------------------+
| Help |
| - - - - - - - - - - - - - - -*-----------------------------------*- - |
| Port Configurat| INBOUND Baud Rate | |
| | | |
| |Select a BAUD RATE and press ENTER.| |
| Type a Port Number to configu| | |
| | 1 1. 9600 baud | |
| Indicate if port is to be SEL| 2. 19200 baud | |
| | | |
| Then press ENTER. | | |
| |F1=Help F12=Cancel | |
| Port Selecti*-----------------------------------* |
| |
| S 0 9600 BAUD |
| _ 1 |
| _ 2 |
| _ 3 |
| _ 4 |
| _ 5 |
| _ 6 |
| _ 7 |
| |
| |
| S = SELECTED |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To select the inbound baud rate, do the following:
- In the selection field, type one of the following:
- 1 to use the 9,600 baud rate (the default value)
- 2 to use the 19,200 baud rate
- Press Enter to return to the Port Configuration window
so that you can view the selected baud rate.
- Press F3 to return to the RIC Card Selection window.
- Proceed to "Processing the ROLM 9751 CBX Connection Configuration"
to complete the configuration process.
The OUTBOUND Dialer Number window
(Figure 13)
lets you select
the dialer number that is configured on the ROLM 9751 CBX (Release 9005).
Use the dialer number configured on the ROLM 9751 CBX (Release 9005) for each ODI
interface card.
Figure 13. OUTBOUND Dialer Number Window Example
+--------------------------------------------------------------------------------+
| Help |
|- - - - - - - - - - - - - - -*--------------------------------------*- |
| Port Configura| OUTBOUND Dialer Number for Port 4 | |
| | | |
| | Type number and press ENTER. | |
| Type a Port Number to config| | |
| | Dialer number 230 (1-999999) | |
| Indicate if port is to be SE| | |
| | | |
| Then press ENTER. | | |
| | F1=Help F12=Cancel | |
| Port Select*--------------------------------------* |
| |
| 0 |
| 1 |
| 2 |
| 3 |
| 4 |
| S 5 240 |
| S 6 245 |
| 7 |
| |
| |
| S = SELECTED |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To specify the outbound dialer number, do the following:
- In the selection field, type the outbound dialer number that is local
to the ROLM 9751 CBX (Release 9005).
The dialer number must consist of numeric
characters in the range of 1 through 999999.
Do not use leading zeros in the dialer number.
- Press Enter to return to the Port Configuration window
so that you can view the selected dialer number.
- Do one of the following:
- To configure another port number, proceed to "Configuring the Port Number".
- To specify Outbound timeout values for Calling Party Timeout
and Called Party Timeout, press F3 on the Port Configuration
window, and press F3 again on the RIC Card
Selection window.
The OUTBOUND Timeout Values window is displayed.
Continue with "Specifying the Outbound Timeout Values".
The OUTBOUND Timeout Values window
(Figure 14) lets you
specify the values
for Calling Party Timeout and Called Party Timeout.
Calling Party Timeout is the length of time in seconds that
CallPath Server/2 waits for a connection from the calling party before giving
a positive response to the request and a Call_Rejected event message.
Called Party Timeout is the length of time in seconds that the CallPath Server/2
waits for a connection from the called party before giving a positive
response to the request and a Call_Rejected event message.
Figure 14. OUTBOUND Timeout Values Window Example
+--------------------------------------------------------------------------------+
| Help |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| OUTBOUND Timeout Values |
| |
| |
| Type Timeout Values (seconds) and press ENTER. |
| |
| |
| |
| Calling Party Timeout 60 (1-255) seconds. |
| |
| Called Party Timeout 40 (1-255) seconds. |
| |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
To specify the outbound timeout values, do the following:
- In the "Calling Party Timeout" field,
type the number of seconds you want
for Calling Party Timeout and press the Tab key.
The default is 60 seconds.
If you want to use the default, just press the Tab key.
The cursor moves to the "Called Party Timeout" field.
- Enter the number of seconds you want for Called Party Timeout.
The default is 40 seconds.
- Press Enter.
- Press F3.
- Press F3 to return to the Switch Connection Configuration
window so that you can complete the configuration process.
- Do one of the following:
When you have completed the configuration process,
do the following to process the configuration:
- Press F3 to save your configuration data
and allow the installation to complete.
- When the message ROLM CallBridge link support installation
complete is displayed on the OS/2 full screen,
remove the CallBridge Link Manager program diskette from the A drive.
- Restart the system so that the new configuration takes effect.
Continue with "Backing Up CallBridge Link Manager".
At this point, it is advisable to make a backup copy of
CallBridge Link Manager.
You need a blank 3.5-inch, high-density diskette,
formatted to 1.44MB.
To make a backup copy of
CallBridge Link Manager, do the following:
- Open an OS/2 full-screen session.
- Enter C: to make
drive C the current drive.
- Enter cd\gateway
to make C:\GATEWAY the current directory.
- Insert the blank, formatted backup diskette in drive A.
(Ensure that the diskette is write-enabled.)
- Enter cblminst to run the transfer utility program.
A message informs you that the CallBridge Link Manager program files will be
saved on the diskette in drive A, and asks if you want to continue.
- Enter y to copy the files to the diskette.
The files are saved to the backup diskette.
As each file is copied, a confirmation message is displayed.
If your backup procedure requires more than one diskette, the
transfer utility program prompts you as necessary.
When the backup process is complete, the message Backup
complete is displayed
and the OS/2 prompt is redisplayed.
- Remove the diskette and label it.
Store the original program diskette in a secure place.
Continue with "Setting Up ROLM 9751 CBX (Release 9005) Communication Parameters".
Before CallPath Server/2 can communicate with the ROLM 9751 CBX (Release 9005),
the switch connection must be configured by recording
the following information in CallPath Server/2:
- Switch description
- The name to be used in the CallPath Server Management Facility for the switch
- Auto-start
- Whether CallPath Server/2 should start communications with the switch
automatically when the
CallPath Server/2 subsystem is started
- Restart on failure
- Whether CallPath Server/2 should restart communications with the switch
automatically after a fatal error has terminated communications
between CallPath Server/2 and the switch
To configure the ROLM 9751 CBX (Release 9005) in CallPath Server/2 for a local connection,
do the following:
- Start the CallPath Server Management Facility.
See "Starting the CallPath Server Management Facility" for instructions.
- Display the CallPath Server Management Facility Set Switch Configuration window
in one of the following ways:
- From the CallPath Server Management Facility menu bar:
- Select the Configuration menu.
- Select the Switch Connection menu option.
- Select
On file.
- Select the switch from the scrollable list box.
- From the switch icon:
- Click on the Switch icon
using the mouse menu button.
- Select the Configuration option.
- Select
On file.
- Select ROLM 9005 from the scrollable list box.
The Switch Configuration window is displayed.
- Enter the description for the switch in the
Switch description field.
- Select Auto-start if you want ROLM 9751 CBX (Release 9005) to
start automatically when
the CallPath Server/2 subsystem starts.
- Select Restart on failure if you want
ROLM 9751 CBX (Release 9005) to restart when there is a failure in communications
between it and CallPath Server/2.
- Click on the Switch type field.
- Click on ROLM 9005.
CallPath Server/2 suspends CallPath Server Management Facility processing and displays
the Switch Connection Configuration window shown in
Figure 15.
Figure 15. Switch Connection Configuration Window Example (Inbound and Outbound Selected)
+--------------------------------------------------------------------------------+
| Help |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| Switch Connection Configuration |
| |
| Select a choice and press ENTER. |
| |
| |
| 2 1. INBOUND |
| 2. INBOUND and OUTBOUND |
| |
| |
| |
| |
|F1=Help F3=Exit F10=Action F12=Cancel |
+--------------------------------------------------------------------------------+
|
The Switch Connection Configuration window also displayed when
you installed the ROLM 9751 CBX (Release 9005)
switch-dependent code feature.
- Do one of the following:
- Press F12 if you have already configured the
ROLM 9751 CBX (Release 9005) switch connection during installation.
- Go to "Configuring the RIC Card" if you have not already configuring a RIC card
for CallPath Server/2.
- Go through each configuration window
to verify the original settings, and if necessary,
make changes to them.
After verifying the last configuration window,
control passes back to the CallPath Server Management Facility.
- Click on one of the following:
- OK
to save the configuration information and
return to the CallPath Server Management Facility window.
- Apply to save the configuration information
and keep the window open to configure another switch.
- If you reconfigured an existing switch connection,
exit the CallPath Server Management Facility and restart the PC.
To activate the CallPath Server/2 configuration,
restart the CallPath Server/2 computer.
Following is an overview of the tasks required for
manually starting
CallPath Server/2 and the ROLM 9751 CBX (Release 9005) switch connection.
Some of
these tasks may not be required if you selected autostart
options when configuring CallPath Server/2 and the ROLM 9751 CBX (Release 9005) switch connection.
- Start CallPath Server Management Facility
- Start the CallPath Server/2 subsystem
- Start the ROLM 9751 CBX (Release 9005) switch connection
These tasks are described in more detail in the following sections.
If you encounter errors or problems,
see the CallPath Server Planning, Installation, and
Problem Determination Guide.
To start CallPath Server/2 Management Facility, do
one of the following:
- Enter csasrvr at the OS/2 command prompt.
- Double-click on the CallPath folder on the OS/2
desktop and then double-click on the CallPath Server/2 icon.
Once CallPath Server/2 is started,
the CallPath Server Management Facility window and the Product Information window
are displayed.
If password protection was enabled, the Administrative Password window
is also displayed and the password must be entered to gain access
to the CallPath Server Management Facility configuration functions.
To enter the password and gain access to the CallPath Server Management Facility,
type the password, then click on OK.
Note: The default password, until you change it, is password.
See the CallPath Server Planning, Installation, and Problem Determination
Guide
for a description of the CallPath Server Management Facility window and
how to use the window's features.
After starting the CallPath Server Management Facility,
start the CallPath Server/2 subsystem
in one of the following ways:
From the CallPath Server Management Facility window:
- Select the Administration menu option from
the menu bar.
- Select the Server menu option.
- Select Start.
- Click on one of the following in response
to the confirmation message:
- Yes to start the CallPath Server/2 subsystem
- No to return to the CallPath Server Management Facility window
without starting the CallPath Server/2 subsystem
- Select Yes from the confirmation message window.
From the CallPath Server icon:
- Click on the CallPath Server icon.
- Select Start.
- Click on one of the following in response
to the confirmation message:
- Yes to start the CallPath Server/2 subsystem
- No to return to the CallPath Server Management Facility window
without starting the CallPath Server/2 subsystem
If you cannot start
the CallPath Server/2 subsystem,
see the CallPath Server Planning, Installation, and
Problem Determination Guide.
After starting the CallPath Server Management Facility and CallPath Server/2,
start your switch connection in one
of the following ways:
- From the CallPath Server Management Facility window menu bar:
- Select the Administration menu.
- Select the Switch Connection menu option.
- Select Start.
- Select the switch.
- Click on one of the following in response to
the confirmation message:
- Yes to start the switch
- No to return to the CallPath Server Management Facility window
without starting the switch
- From the CallPath Server Management Facility window switch icons:
- Click on the Switch icon.
- Select Start.
- Click on one of the following in response to
the confirmation message:
- Yes to start the switch
- No to return to the CallPath Server Management Facility window
without starting the switch
This chapter shows the relationship between the CallPath Services program
calls and messages and the ROLM 9751 CBX (Release 9005) messages.
It lists all program calls and messages in quick-reference tables to
provide an overall picture of the level of support provided by the ROLM 9751 CBX (Release 9005).
Not all values defined by the architecture are supported by the
ROLM 9751 CBX (Release 9005).
This chapter also lists special considerations and limitations for
using the CallPath Services API with the ROLM 9751 CBX (Release 9005).
The tables
in this chapter
show the program calls and messages
that are fully supported, partially supported, or not supported
by the ROLM 9751 CBX (Release 9005)
from the standpoint of the programming interface.
- Fully supported
- means that the overall function and all
parameters and their associated values are supported
- Partially supported
- means that the overall function is
supported, but not all parameters or characteristics and their
associated values are supported
- Not supported
- means that the overall function is not supported
Note: For more information about switch real-time limitations,
see "Special Considerations and Limitations"
and the description for each program call and message.
Reminder: Except where there is a need to differentiate between CallPath SwitchServer/2
and CallPath Server/2, the term Server/2 will be used in place of
the phrases "CallPath SwitchServer/2 and CallPath Server/2".
Refer to CallPath Services Programmer's Reference
for complete information on the program calls and messages.
You should be aware that other restrictions in support of the
program calls and messages may be imposed by your host software.
For example, CallPath Server/2 supports both Version 0 and
Version 1
features
of the CallPath Services Architecture while CallPath SwitchServer/2 only
supports Version 0 features.
Refer to the programming guide for your CallPath Services host
software for details.
An error occurs
if a program issues a program call that is not supported by
the ROLM 9751 CBX (Release 9005) or that contains a parameter value that is not
supported by the ROLM 9751 CBX (Release 9005).
Similarly, an error occurs
if a program issues a program call that uses a
call profile characteristic and the value
associated with
that characteristic is not supported by the ROLM 9751 CBX (Release 9005).
The program is informed of these types of errors by
one of the following:
-
A
return_code
value of STL_RQ_NOT_SUPPORTED_BY_SWITCH
-
A negative Response message with a
sense_code
value of
STL_RQ_NOT_SUPPORTED_BY_SWITCH
The Response may contain additional information regarding the
unsupported program call or parameter value, if available.
Note: If a program issues an Initialize_Call_Profile program call and
one or more of the initialized values associated with the call profile
are not supported by the ROLM 9751 CBX (Release 9005), the Initialize_Call_Profile is
accepted and processed normally. The same is true if a program issues
a Set program call to modify a call profile characteristic to a value
that is not supported by the ROLM 9751 CBX (Release 9005); the Set program call is accepted
and processed normally. The program is informed of the error when it
issues a program call that uses the affected characteristic (as
just described).
The following table shows the ROLM 9751 CBX (Release 9005) level of support for the
CallPath Services program calls.
See Chapter 5. "Partially Supported Program Calls",
for a detailed description of each
partially supported program call.
Table 1. Program Calls Supported by the ROLM 9751 CBX (Release 9005)
| Program Calls
| Fully Supported
| Partially Supported
| Not Supported
|
|
| Add_Party
|
|
|
|
|
| Alternate_Call
|
|
|
|
|
| Answer_Call
|
|
|
|
|
| Conference_Call
|
|
|
|
|
| Create_Program_Name (1)
|
|
|
|
|
| Delete_Call_Profile (1)
|
|
|
|
|
| Disconnect
|
|
| "STLDISC (Disconnect)"
|
|
| Extend_Call
|
|
| "STLXTND (Extend_Call)"
|
|
| Hold_Call
|
|
|
|
|
| Identify_Program_Description
(1)
|
|
|
|
|
| Identify_Program_Name (1)
|
|
|
|
|
| Identify_Program_Version
(1, 2)
|
|
|
|
|
| Identify_Server_Name
(1)
|
|
|
|
|
| Immediate_Transfer
|
|
|
|
|
| Initialize_Call_Profile (1, 3)
|
|
| "STLINIT (Initialize_Call_Profile)"
|
|
| Invoke_Feature
|
|
| "STLINVK (Invoke_Feature)"
|
|
| Make_Call
|
|
| "STLMAKE (Make_Call)"
|
|
| Monitor (4)
|
|
| "STLMON (Monitor)"
|
|
| Monitor_System_Messages (1)
|
|
|
|
|
| Park_Call
|
|
|
|
|
| Pick_Call
|
|
|
|
|
| Provide_Indicator
|
|
|
|
|
| Query_ACD_Information
|
|
|
|
|
| Query_Call_Parties
|
|
|
|
|
| Query_Hardware_Status
|
|
|
|
|
| Query_Party_Status (4)
|
|
|
|
|
| Receive (1)
|
|
| "STLRCV (Receive)"
|
|
| Redirect_Call
|
|
|
|
|
| Register_Ownership (1,5)
|
|
|
|
|
| Reject_Call
|
|
|
|
|
| Release_Program_Name (1)
|
|
|
|
|
| Retrieve_Call
|
|
|
|
|
| Return_Control
|
|
|
|
|
| Send_Device_Data
|
|
|
|
|
| Transfer_Call
|
|
| "STLTRAN (Transfer_Call)"
|
|
| Trigger
|
|
|
|
|
Notes:
- This program call is not switch dependent.
It is processed entirely by the host computer and does not
cause a request to be sent to
Server/2.
- The program version
must be set to
"0" for use with CallPath SwitchServer/2, but may
be set to "1" for use with CallPath Server/2 to take
advantage of enhanced CallPath Services Architecture support.
- Although Initialize_Call_Profile is considered a
fully supported program call, some initialized characteristics
in the call profile must be modified using Set program calls.
Other initialized characteristics are ignored because the ROLM 9751 CBX (Release 9005)
does not support that overall function.
For details, see "STLINIT (Initialize_Call_Profile)".
- Monitor and Query_Party_Status are processed by Server/2.
No request flows to the ROLM 9751 CBX (Release 9005) as a result of these program calls.
When the program issues a Query_Party_Status program call,
Server/2 creates a Party_Status message in reply.
If Server/2
is already aware of connections involving this party,
it returns the already-existing connection ID or IDs associated
with that party.
If Sever/2
is unaware of a connection involving this party, it
assumes that activity involving that party was initiated manually
through a telephone.
To accommodate this situation,
Sever/2
creates two new connection
IDs to represent connections that are assumed to be associated
with the party.
This latter function facilitates the mixing of program call
activity with manual telephone activity.
- Server/2 provides no support for Register_Ownership. Host
computers provide a partial implementation of the function.
Consult your host documentation to determine any limited support
that may be supplied from the host computer.
|
The following table shows the ROLM 9751 CBX (Release 9005) level of support for the
CallPath Services Set program calls.
See Chapter 6. "Partially Supported Set Program Calls",
for a detailed
description of the partially supported Set program calls.
| Set Program Calls
| Fully Supported
| Partially Supported
| Not Supported
|
|
| Set_Add_Party_Direction
|
|
|
|
|
| Set_Automatic_Answer (1)
|
|
| "STLSAA (Set_Automatic_Answer)"
|
|
| Set_Billed_Party (2)
|
|
|
|
|
| Set_Call_Type (2)
|
|
|
|
|
| Set_Called_Party_Alerting_Time (2)
|
|
|
|
|
| Set_Disconnect_Execution_Option(2)
|
|
|
|
|
| Set_Extend_Purpose
|
|
| "STLSEP (Set_Extend_Purpose)"
|
|
| Set_Held_Call_Connection (2)
|
|
|
|
|
| Set_Held_Call_Recording (2)
|
|
|
|
|
| Set_Holding_Party_Callback
|
|
|
|
|
| Set_Holding_Party_Calling
|
|
|
|
|
| Set_Make_Call_DND_Override (1)
|
|
| "STLSMCD (Set_Make_Call_DND_Override)"
|
|
| Set_Make_Call_Forward_Override (1)
|
|
| "STLSMCF (Set_Make_Call_Forward_Override)"
|
|
| Set_Make_Call_Notification (2)
|
|
|
|
|
| Set_Make_Call_Party_Order (2)
|
|
|
|
|
| Set_Monitor_Tracking
|
|
|
|
|
| Set_Parking_Party_Calling
|
|
|
|
|
| Set_Party_Specification (2)
|
|
|
|
|
| Set_Remaining_Parties_Option (2)
|
|
|
|
|
| Set_Return_Response
|
|
|
|
|
Notes:
- This Set program call must be issued to modify the
(Ref #2.)
initialized setting of a call profile characteristic before any
program call that references that characteristic is issued.
- Only the initialized value of the related characteristic for
this Set program call is supported by the ROLM 9751 CBX (Release 9005). To avoid
the risk of a subsequent program call being rejected, do not
change the value of this characteristic from that set by the
Initialize_Call_Profile program call. This Set program
call is not described in this book. Refer to
"STLINIT (Initialize_Call_Profile)" for detailed information.
|
The following table shows the ROLM 9751 CBX (Release 9005) level of support for the
CallPath Services messages.
See Chapter 7. "Partially Supported Messages",
for a detailed description of each
partially supported message.
The following are special considerations and limitations for
using the CallPath Services API with the ROLM 9751 CBX (Release 9005).
- Unsupported Telephony Features.
Call-progress event messages are not generated by the ROLM 9751 CBX (Release 9005)
when the following telephony features are invoked:
- Callback camp-on
- Automatic camp-on
- Executive Override
- Hold on Hold
- Attendant Console (ATC)
- The flow of call-progress event messages is unpredictable
when a call to an ATC has been parked on an
extension and left to expire.
- When a call is transferred to an ATC, the
connection IDs
associated with the parties in the call are
discarded and new connection IDs are created.
- The ROLM 9751 CBX (Release 9005) does not allow a party to place an ATC
on hold.
- Automatic Call Distribution (ACD).
When working with multiple queues, a call to an ACD
group that has no available agents can overflow to another
ACD group (if this option is configured at the
switch).
The
Server/2
program receives no information from the ROLM 9751 CBX (Release 9005)
switch indicating what the original ACD group
was if an overflow occurs.
When an agent becomes available, the
Server/2
program sets
the last ACD group to be the ACD
group from which the call was routed.
- Overload Condition.
An overload condition will exist for some CallPath program calls
(Alternate_Call, Answer_Call, Disconnect, Extend_Call,
Invoke_Feature,
Make_Call,
and Transfer_Call)
if the number of these outstanding program calls exceeds
one and one-half times the number of active
ODI
cards/ports.
The maximum number of outstanding program calls is 99.
This condition will persist until 20 percent of these current
outstanding CallPath program calls have been responded to by
the ROLM 9751 CBX (Release 9005).
- PhoneMail.
The flow of call-progress event messages
is unpredictable when a call
to an
ACD
group with no
available agents overflows to PhoneMail.
- Call Pick.
After a call to an extension that is on hold
(with automatic
camp-on) has been picked, there is a normal flow of messages.
However, the ROLM 9751 CBX (Release 9005) does not send a Disconnected call-progress
event message
if the party on hold abandons the telephone call.
- Answer_Call Program Call.
Only
ROLMphones**
are supported for agent extensions.
Extensions must be configured on a single ROLMphone.
- Disconnect Program Call.
See "Special Considerations and Limitations for Disconnect".
- Make_Call Program Call.
See "Special Considerations and Limitations for Make_Call".
- Monitor Program Call.
See "Special Considerations and Limitations for Monitor".
This chapter describes the program calls provided by CallPath Services
that are partially supported by the ROLM 9751 CBX (Release 9005).
(The Set program calls are described in Chapter 6. "Partially Supported Set Program Calls".)
Partially supported means that the overall function is
supported, but not all parameters and their associated
values are supported.
The level of support for parameters is shown for each call.
Refer to
CallPath Services Programmer's Reference
for complete information on all program calls.
You should also refer to the CallPath Services programming reference for your
host computer system.
See Chapter 10. "Example Program Call and Message Flows", for examples of program calls.
A program uses the Disconnect (STLDISC) program
call to remove a party from the current telephone call.
A Disconnect simulates an on-hook for the specified party.
In a call with only two parties, both parties will be
disconnected.
In a call with three or more parties, only the specified
party will be disconnected.
If the party (P1) has a single party (P2) on hold, the
party (P2) will ring the party (P1) or, if the party's
(P1) phone is in automatic answer mode, the party (P2) will
be reconnected with the party (P1).
The following tables show the ROLM 9751 CBX (Release 9005) support for Disconnect:
| Related Calls
| Notes
|
|
| Set_Disconnect_Execution_Option
|
|
|
| Set_Remaining_Parties_Option
|
|
|
| Set_Return_Response
| Fully supported
|
|
| Parameters
| Notes
|
| party_ID
| Fully supported
|
| call_profile_ID
| Fully supported
|
| request_tag
| Fully supported
|
| return_code
| Fully supported
|
| Parameters
| Notes
|
| program_data_length
| Value is 0
|
| program_data
| Not supported
|
The following are special considerations and limitations when
using the Disconnect program call:
- The target of a Disconnect program call must be a
directory number associated with a ROLMphone.
ACD pilot numbers, PhoneMail numbers, ATC
numbers, and external numbers are not supported as targets of
a Disconnect request.
- The target of a Disconnect request must be in a connected
state and not on hold. Attempts to disconnect a telephone
that is in the alerting state or on hold will fail.
A program uses the Initialize_Call_Profile
(STLINIT) program call to initialize values for
various call profile
characteristics before the actual
program call is requested.
The set of telephone call characteristics that are initialized
is referred to as a call profile.
The set of initialized values is described
in CallPath Services Programmer's Reference.
Certain call profile characteristic values set by
Initialize_Call_Profile are not valid for the ROLM 9751 CBX (Release 9005).
The appropriate Set program calls must be issued after each
Initialize_Call_Profile to set an acceptable value, as follows:
For the following call profile characteristics, only the
initialized values are supported:
- billed_party (initialized value is null)
- call_type (initialized value is STL_VOICE)
- called_party_alerting_time (initialized value is 0)
- disconnect_execution_option (initialized
value is STL_DSC_UNCONDITIONAL)
- held_call_connection (initialized value
is STL_CONNECT_TO_SWITCH_DEFAULT)
- held_call_recording (initialized value
is null)
- make_call_notification (initialized value is
STL_MC_NORMAL_CALL_PROGRESS)
- make_call_party_order (initialized value is
STL_CONNECT_PARTY_ONE_FIRST)
- party_specification (initialized value is
STL_DIRECTORY_NUMBER)
- remaining_parties_option (initialized
value is STL_REMAINING_CONDITIONAL)
For the following call profile characteristic, the initialized
value and at least one other value are supported:
extend_purpose can be set to
STL_EXTEND_UNSPECIFIED (initialized value),
STL_EXTEND_ALTERNATE, or
STL_EXTEND_TRANSFER
The following call profile characteristics are not
supported:
- add_party_direction
- holding_party_callback
- holding_party_calling
- parking_party_calling
All other call profile characteristics are fully supported.
For detailed information, refer to the individual Set program
calls in this book and
in CallPath Services Programmer's Reference.
A program uses the Invoke_Feature (STLINVK)
program call to invoke a switch feature for the telephone
associated with the specified party.
The following tables show the ROLM 9751 CBX (Release 9005) support for Invoke_Feature:
| Related Calls
| Notes
|
| Set_Return_Response
| Fully supported
|
| Parameters
| Notes
|
| call_profile_ID
| Fully supported
|
| feature_code
|
|
|
STL_ACCOUNT_CODE
| Not supported
|
| STL_AGENT_ACTIVITY
| Supported
|
| STL_CALL_WAITING
| Not supported
|
| STL_CAMP_FOR_CALLBACK
| Not supported
|
| STL_CLASS_OF_SERVICE
| Not supported
|
| STL_DO_NOT_DISTURB
| Supported
|
| STL_FORWARD
| Supported
|
| STL_MUTE
| Not supported
|
| STL_SPEAKER
| Not supported
|
| STL_SWITCH_SPECIFIC
| Not supported
|
| feature_data_length
| Value is 0 to 512
|
| feature_data
| Used when feature_data_length > 0; partially
supported, See page Chapter 8. "Feature Formats and Codes"
|
| request_tag
| Fully supported
|
| return_code
| Fully supported
|
A program uses the Make_Call (STLMAKE) program
call to establish a two-party telephone call.
For successful execution of the
function, the connections associated with both parties must
be in the Idle state.
(For a full description of connections and connection states,
see CallPath Services Programmer's Reference.)
If the called party is external, it may not be possible to
distinguish between ringing, busy, and connected status.
If the called party is external and a trunk is selected
successfully, a positive response is expected-even if
the party is busy or does not answer.
However, if a trunk cannot be selected, a positive response is
returned, followed by a Call_Rejected call-progress event message.
A Make_Call request proceeds as follows:
A connection to party_one is attempted first.
If the connection is established (that is, party_one
answers the telephone), the connection to party_two
is attempted.
Note: The ROLM 9751 CBX (Release 9005) provides a function called Call Time Monitoring,
in which a party being rung is timed.
If the timer expires before the called party answers, then
the ROLM 9751 CBX (Release 9005) abandons the call.
The parties specified in a Make_Call request are always
subject to Call Time Monitoring, the duration of which is set
to a value configured on your
Server/2.
See "Specifying the Outbound Timeout Values" for more details.
The following tables show the ROLM 9751 CBX (Release 9005) support for Make_Call:
| Parameters
| Notes
|
| party_one_length
| Value is 1 to 6
|
| party_one
| Fully supported
|
| party_two_length
| Value is 1 to 22
|
| party_two
| Fully supported
|
| call_profile_ID
| Fully supported
|
| account_code_length
| Value is 0
|
| account_code
| Not supported
|
| party_one_ID
| Fully supported
|
| party_two_ID
| Fully supported
|
| request_tag
| Fully supported
|
| return_code
| Fully supported
|
| Parameters
| Notes
|
| program_data_length
| Value is 0 to 256
|
| program_data
| Fully supported
|
The following are special considerations and limitations when
using the Make_Call program call:
- An ATC is not supported as one of the parties
in a Make_Call.
- To ensure accurate call-progress event messages, the
calling or called party must be configured with ROLM 9751 CBX (Release 9005)
CallPath class of service (CPTH).
- Make_Call does not support the system speed feature
for the calling party.
If the system speed feature is used
for the calling party in a Make_Call, the results are a
positive response to the request and a Call_Rejected event
message with a reason of invalid directory number.
- Make_Call does not support calling or called parties
that are station-forwarded (or any off-site forwarding) to
an external number.
- Make_Call does not support either party in a Make_Call
program call to be busy-forwarded to PhoneMail.
- Outbound (computer-assisted dialing) does not support
application-controlled division of call requests among attached
ODIs (which may be on different nodes) according to
numbering plan or any other criteria.
In a medium to large call center, several CBX
nodes can be in use with one or many ACD groups.
Inbound agents, outbound agents, and trunks should be in
the same node.
It is desirable to have the outgoing calls placed within
the same node as the agent handling the call.
Since Outbound is not aware of the numbering plan, there is
no simple means to ensure that requests are always initiated
on the proper node.
The problem is further complicated when ACD
groups are used.
When Outbound is given the ACD pilot number on a
request, it has no method to determine where the agent
actually resides.
- Dialing the remote party prior to calling the local party
is not supported by the ROLM 9751 CBX (Release 9005).
Therefore, party_one must always be identified
as a local ROLM 9751 CBX (Release 9005) party.
- Predictive dialing is not supported by the ROLM 9751 CBX (Release 9005).
- A PhoneMail pilot number is not supported as one of the
parties in a Make_Call.
- A pilot number is not supported as a called party in a Make_Call.
STLMON (Monitor)
A program uses the Monitor (STLMON) program call to indicate
that it wishes to be sent certain call-progress event messages as a
result of telephone call activity involving specified resources.
The following tables show the ROLM 9751 CBX (Release 9005) support for Monitor:
| Related Calls
| Notes
|
| Set_Monitor_Tracking
| Fully supported
|
| Set_Return_Response
| Fully supported
|
| Parameters
| Notes
|
| resource_length
| Fully supported
|
| resource
| Fully supported
|
| monitor_resource_type
|
|
| STL_MONITOR_PILOT_NUMBER
| Not supported
|
| STL_MONITOR_AGENT_IDENTIFIER
| Not supported
|
| STL_MONITOR_DIRECTORY_NUMBER
| Supported
|
| STL_MONITOR_GROUP
| Supported
|
| list_size
| Fully supported
|
| event_list
|
|
| STL_CALL_ALERTING_EVENT
| Supported
|
| STL_CALL_ALTERNATED_EVENT
| Not supported
|
| STL_CALL_CONFERENCED_EVENT
| Supported
|
| STL_CALL_CONNECTED_EVENT
| Supported
|
| STL_CALL_HELD_EVENT
| Supported
|
| STL_CALL_PARKED_EVENT
| Supported
|
| STL_CALL_PICKED_EVENT
| Supported
|
| STL_CALL_REJECTED_EVENT
| Supported
|
| STL_CALL_ROUTED_EVENT
| Supported
|
| STL_CALL_TRANSFERRED_EVENT
| Supported
|
| STL_DATA_COLLECTED_EVENT
| Not supported
|
| STL_DISCONNECTED_EVENT
| Supported
|
| STL_FEATURE_INVOKED_EVENT
| Supported
|
| STL_INDICATOR_PROVIDED_EVENT
| Not supported
|
| STL_NETWORK_REACHED_EVENT
| Supported
|
| STL_RESOURCE_DELETED_EVENT
| Not supported
|
| STL_SETUP_EVENT
| Not supported
|
| rank_list
| Fully supported
|
| mode
| Fully supported
|
| call_profile_ID
| Fully supported
|
| request_tag
| Fully supported
|
| return_code
| Fully supported
|
CallPath Services event messages are generated based on the ROLM 9751 CBX (Release 9005) event
messages.
Because of the way events are generated by the ROLM 9751 CBX (Release 9005), the
following considerations and limitations apply when using
the Monitor program call:
- ROLM 9751 CBX (Release 9005) CallPath Class of Service (CPTH) and Event Messages:
The ROLM 9751 CBX (Release 9005) begins sending call-progress event messages to the
Server/2
when a call is made to an agent or pilot number
configured with CPTH.
The ROLM 9751 CBX (Release 9005) continues to send
call-progress event messages as long as the agent,
or any other agent configured with CPTH,
is involved with the call.
The ROLM 9751 CBX (Release 9005) stops sending call-progress event messages when
there is no longer an agent with CPTH involved with the
call.
Also, call-progress event messages
are not sent when an agent having CPTH
calls a party that does not have CPTH.
The following table identifies the three ROLM 9751 CBX (Release 9005) CallPath party types
and their corresponding telephony equipment:
- A ROLM 9751 CBX (Release 9005) CallPath caller is a party that initiates a call to a valid
configured ROLM 9751 CBX (Release 9005) CallPath called party or inherits the status
from another ROLM 9751 CBX (Release 9005) CallPath caller (for example, through a transfer).
- An initial ROLM 9751 CBX (Release 9005) CallPath called party is a party that is valid to be
configured with CPTH and is the first recipient of a call.
- A ROLM 9751 CBX (Release 9005) CallPath called party is any called party allowed to be
part of a ROLM 9751 CBX (Release 9005) CallPath call.
Any equipment not included in this table is not allowed.
| Equipment
| ROLM 9751 CBX CallPath Caller
| Initial ROLM 9751 CBX CallPath Called Party
| ROLM 9751 CBX CallPath Called Party
|
| Normal extension--including
voice response unit (VRU)
extension
| Yes
| Yes
| Yes
|
| Trunk
|
|
|
|
| Direct inward dialing
| Yes
| No
| Yes
|
| Direct
| Yes
| No
| Yes
|
| Tie
| Yes
| No
| Yes
|
ACD
group pilot
| N/A
| Yes
| Yes
|
| Hunt group pilot
| N/A
| Yes
| Yes
|
| PhoneMail extension
| N/A
| Yes
| Yes
|
ATC
| Yes
| No
| No
|
The only monitor group resource
(STL_MONITOR_GROUP) supported is
by
Server/2,
which allows a host to request notification of
all call-progress event messages reported by the ROLM 9751 CBX (Release 9005).
Server/2
records the application program's request and, until
the request is turned off or until the application program
ends,
Server/2
routes all call-progress event messages to that
application program.
monitor_tracking can be set to STL_TRACK_CALL.
- Multiple-Appearance Processing:
A multiple-appearance extension, which is an extension
number that is assigned to more than one telephone, is treated
by the ROLM 9751 CBX (Release 9005) as a single party.
For example, when party-one appearance "a" (P1a) calls
party two (P2), where P2 is an initial ROLM 9751 CBX (Release 9005) CallPath called
party, then P1a becomes a ROLM 9751 CBX (Release 9005) CallPath caller, and the call
is a ROLM 9751 CBX (Release 9005) CallPath call.
When party-one appearance "b"
(P1b) goes off-hook and enters the conference, no
new call tracking is involved with it.
If P1a goes idle (since it was a ROLM 9751 CBX (Release 9005) CallPath caller), its status
as a ROLM 9751 CBX (Release 9005) CallPath caller is inherited by P1b.
The call between P1b and P2 remains a ROLM 9751 CBX (Release 9005) CallPath call.
- Attendant Console Processing:
Although ATCs are not valid initial
ROLM 9751 CBX (Release 9005) CallPath called parties, they can often be catalysts for
ROLM 9751 CBX (Release 9005) CallPath calls.
If an ATC calls an initial ROLM 9751 CBX (Release 9005) CallPath called party,
the call becomes a ROLM 9751 CBX (Release 9005) CallPath call.
If an ATC is a ROLM 9751 CBX (Release 9005) CallPath caller connected to two other
parties and it exits the call, its status as a ROLM 9751 CBX (Release 9005) CallPath caller will
be inherited by one of the two parties.
The new connection between these parties becomes a ROLM 9751 CBX (Release 9005) CallPath call.
- Call Transfer Processing:
Upon completion of a call transfer, if the transferred-from party
has CPTH, then the transferred-to party is treated
as a ROLM 9751 CBX (Release 9005) CallPath caller.
- Conference Processing:
If the conference originator is the only ROLM 9751 CBX (Release 9005) CallPath caller when
it drops out of the conference, then the call is no longer
treated as a ROLM 9751 CBX (Release 9005) CallPath call.
However, if the party that
called the conference originator has CPTH, then the
ROLM 9751 CBX (Release 9005) continues to track the call after the conference originator
has dropped out of the call.
This is true as long as a ROLM 9751 CBX (Release 9005) CallPath caller is involved in the call.
- CallPath Services Event Synthesis:
Depending on the sequence of call-progress event messages
from the ROLM 9751 CBX (Release 9005), certain CallPath Services event messages are synthesized
to reflect the proper movement, or CallPath Services connection state, or
the parties involved in a given call.
(For some examples, see "Incoming Call: To ACD Pilot Number, Queued, Assigned to Agent", and "Conference Call".)
If a call-progress event message contains a directory number
and it is received from the ROLM 9751 CBX (Release 9005) while the
Server/2
is involved
in another call, the call is placed on hold.
Placing the call on hold generates a Call_Held event message
if the directory number involved is being monitored.
- Resource Limitations:
- A maximum of 3000 resources can be monitored at any given time.
- A maximum of 3000 active outstanding two-party calls can be
maintained by the
Server/2
call model database.
- To ensure the appropriate flow of events for monitoring,
the resource being monitored must be a valid resource on the
ROLM 9751 CBX (Release 9005) and configured for CPTH.
STLRCV (Receive)
A program uses the Receive (STLRCV) program call
to receive a message sent to the program.
The following table shows the ROLM 9751 CBX (Release 9005) support for Receive:
| Parameters
| Notes
|
| message_buffer_length
| Value is 0 to 32 767
|
| message_buffer
| Used when
message_buffer_length > 0
|
| wait_time
| Fully supported
|
| returned_buffer_length
| Value is 0 to 32 767
|
| message_code
|
|
| STL_ACD_INFORMATION_MSG
| Not supported
|
| STL_CALL_ALERTING_MSG
| Supported
|
| STL_CALL_ALTERNATED_MSG
| Not supported
|
| STL_CALL_CONFERENCED_MSG
| Supported
|
| STL_CALL_CONNECTED_MSG
| Supported
|
| STL_CALL_HELD_MSG
| Supported
|
| STL_CALL_PARKED_MSG
| Supported
|
| STL_CALL_PARTIES_MSG
| Not supported
|
| STL_CALL_PICKED_MSG
| Supported
|
| STL_CALL_REJECTED_MSG
| Supported
|
| STL_CALL_ROUTED_MSG
| Supported
|
| STL_CALL_TRANSFERRED_MSG
| Supported
|
| STL_DATA_COLLECTED_MSG
| Not supported
|
| STL_DISCONNECTED_MSG
| Supported
|
| STL_FEATURE_INVOKED_MSG
| Supported
|
| STL_HARDWARE_STATUS_MSG
| Not supported
|
| STL_INDICATOR_PROVIDED_MSG
| Not supported
|
| STL_NETWORK_REACHED_MSG
| Supported
|
| STL_PARTY_STATUS_MSG
| Supported
|
| STL_REQUEST_INSTRUCTION_MSG
| Not supported
|
| STL_RESOURCE_DELETED_MSG
| Not supported
|
| STL_RESPONSE_MSG
| Supported
|
| STL_SETUP_MSG
| Not supported
|
| STL_SWITCH_STATUS_MSG
| Supported
|
| more_messages_flag
| Fully supported
|
| return_code
| Fully supported
|
STLTRAN (Transfer_Call)
A program uses the Transfer_Call (STLTRAN)
program call to transfer the party in an existing held
telephone call to a new party.
Transferring a call is a two-step process.
Prior to issuing the Transfer_Call program call, the
program must have issued an Extend_Call program call.
The Transfer_Call program call causes the requesting party
to be removed from its relationship with the held call and
the new call, with the party remaining in the held call
joined to the target of the second call.
The following tables show the ROLM 9751 CBX (Release 9005) support for
Transfer_Call:
| Related Calls
| Notes
|
| Set_Billed_Party
|
|
| Set_Return_Response
| Fully supported
|
| Parameters
| Notes
|
| transferring_party_ID_1
| Fully supported
|
| transferring_party_ID_2
| Fully supported
|
| call_profile_ID
| Fully supported
|
| account_code_length
| Value is 0
|
| account_code
| Not supported
|
| request_tag
| Fully supported
|
| return_code
| Fully supported
|
A program uses the Extend_Call (STLXTND) program
call to extend an existing telephone call.
Extend_Call places the party or parties in the call,
minus the requesting party, on hold, with the requesting
party as the holding party.
Extend_Call further attempts a second call between the
requesting party and the specified new party.
The following tables show the ROLM 9751 CBX (Release 9005) support for Extend_Call:
| Related Calls
| Notes
|
| Set_Billed_Party
|
|
| Set_Called_Party_Alerting_Time
|
|
| Set_Extend_Purpose
| Partially supported; see page "STLSEP (Set_Extend_Purpose)"
|
| Set_Held_Call_Connection
|
|
| Set_Held_Call_Recording
|
|
| Set_Return_Response
| Fully supported
|
| Parameters
| Notes
|
| requesting_party_ID_1
| Fully supported
|
| new_party_length
| Value is 1 to 22
|
| new_party
| Fully supported
|
| call_profile_ID
| Fully supported
|
| account_code_length
| Value is 0
|
| account_code
| Not supported
|
| requesting_party_ID_2
| Fully supported
|
| new_party_ID
| Fully supported
|
| request_tag
| Fully supported
|
| return_code
| Fully supported
|
| Parameters
| Notes
|
| program_data_length
| Value is 0 to 256
|
| program_data
| Fully supported
|
This chapter describes the Set program calls provided by
CallPath Services that are partially supported by the ROLM 9751 CBX (Release 9005), excepting those where
only the initialized value of the call profile characteristic is
supported. These Set program calls are identified in the table in
"Set Program Calls Supported by the ROLM 9751 CBX".
Partially supported means that the overall function is supported,
but not all parameters and their associated values are supported.
The level of support for parameters is shown for each call.
The purpose of Set program calls is to modify the call profile
characteristic values that are initialized by the
Initialize_Call_Profile program call.
The following Set program calls must be issued after each
Initialize_Call_Profile to override the initialized call
profile characteristic values that are not valid for the ROLM 9751 CBX (Release 9005):
- Set_Automatic_Answer
- Set_Make_Call_DND_Override
- Set_Make_Call_Forward_Override
Refer
to CallPath Services Programmer's Reference
for complete information on all Set program calls.
You should also refer to the CallPath Services programming reference
for your host computer system.
Set_Automatic_Answer (STLSAA) is used by a
program to modify the automatic_answer characteristic
for a given call profile.
The automatic_answer characteristic specifies
whether automatic answering is to take place on behalf of the
party specified in the party_one parameter of the
Make_Call program call.
Set_Automatic_Answer overrides the value that was assigned
by the Initialize_Call_Profile program call.
Note: This Set program call must be issued following an
Initialize_Call_Profile program call and
before a Make_Call program call.
The following table shows the ROLM 9751 CBX (Release 9005) support for
Set_Automatic_Answer:
| Parameters
| Notes
|
| call_profile_ID
| Fully supported
|
| automatic_answer
|
|
| STL_ANSWER
| Not supported (initialized value)
|
| STL_NO_ANSWER
| Supported
|
| STL_SWITCH_DEFAULT_ANSWER
| Not supported
|
| return_code
| Fully supported
|
Set_Extend_Purpose (STLSEP) is used by a program to set
the extend_purpose characteristic for a given
call profile.
The extend_purpose characteristic specifies the
purpose for requesting that a telephone call be extended.
Set_Extend_Purpose overrides the value
that was assigned by the Initialize_Call_Profile
program call.
Note: A program is allowed to change the extend_purpose
characteristic at any time.
The following table shows the ROLM 9751 CBX (Release 9005) support for
Set_Extend_Purpose:
| Parameters
| Notes
|
| call_profile_ID
| Fully supported
|
| extend_purpose
|
|
| STL_EXTEND_UNSPECIFIED
| Supported (initialized value)
|
| STL_EXTEND_TRANSFER
| Supported
|
| STL_EXTEND_ALTERNATE
| Supported
|
| STL_EXTEND_CONFERENCE
| Not supported
|
| return_code
| Fully supported
|
Set_Make_Call_DND_Override (STLSMCD)
is used by a program to modify the
make_call_DND_override characteristic for
a given call profile.
The make_call_DND_override characteristic
specifies whether the "do not disturb" (DND)
setting on a party's telephone is overridden by a
Make_Call program call.
Set_Make_Call_DND_Override overrides the value that
was assigned by the Initialize_Call_Profile program call.
Note: This Set program call must be issued following an
Initialize_Call_Profile program call and before a
Make_Call program call.
The following table shows the ROLM 9751 CBX (Release 9005) support for
Set_Make_Call_DND_Override:
| Parameters
| Notes
|
| call_profile_ID
| Fully supported
|
| make_call_DND_override
|
|
| STL_NO_DND_OVERRIDE
| Supported
|
| STL_PARTY_ONE_DND_OVERRIDE
| Not supported (initialized value)
|
| STL_PARTY_TWO_DND_OVERRIDE
| Not supported
|
| STL_DND_OVERRIDE
| Not supported
|
|
STL_SW_DEF_DND_OVERRIDE
| Not supported
|
| return_code
| Fully supported
|
Set_Make_Call_Forward_Override (STLSMCF)
is used by a program to modify the
make_call_forward_override characteristic
for a given call profile.
The make_call_forward_override characteristic
specifies whether the forwarding setting on a party's
telephone is overridden by a Make_Call program call.
Set_Make_Call_Forward_Override overrides the value
that was assigned by the Initialize_Call_Profile program call.
Note: This Set program call must be issued following an
Initialize_Call_Profile program call and
before a Make_Call program call.
The following table shows the ROLM 9751 CBX (Release 9005) support for
Set_Make_Call_Forward_Override:
| Parameters
| Notes
|
| call_profile_ID
| Fully supported
|
| make_call_forward_override
|
|
| STL_NO_FORWARD_OVERRIDE
| Supported
|
| STL_PARTY_ONE_FORWARD_OVERRIDE
| Not supported (initialized value)
|
| STL_PARTY_TWO_FORWARD_OVERRIDE
| Not supported
|
| STL_FORWARD_OVERRIDE
| Not supported
|
|
STL_SW_DEF_FORWARD_OVERRIDE
| Not supported
|
| return_code
| Fully supported
|
This chapter describes the messages provided by CallPath Services that are
partially supported by the ROLM 9751 CBX (Release 9005).
Partially supported means that the overall function is supported,
but not all fields and their associated values are supported.
The level of support for fields is shown for each message.
Refer
to
CallPath Services Programmer's Reference
for complete information on the four types of
messages: call-progress
event messages, response messages, reply
messages, and system messages.
You should also refer to the CallPath Services programming
reference for your host computer system.
The
"timestamp"
field, which is used on every message,
uses the Time_And_Date structure, which is
partially supported.
The Time_And_Date structure is described on
"Time_And_Date".
The level of support for Party_Structure, which
is used by many fields of the messages, is described in
"Party_Structure".
The Call_Alerting call-progress event message tells a
program that a telephone call has been assigned to a telephone,
and the telephone is being alerted.
The following tables show the ROLM 9751 CBX (Release 9005) support for Call_Alerting:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
calling_party_info
| STRUCTURE (Party_Structure);
|
call_type
|
|
|
STL_VOICE
| Supported
|
|
STL_DATA
| Not supported
|
billed_party_length
| Value is 0
|
billed_party
| Not supported
|
call_extension_indicator
|
|
|
STL_CALL_EXTENSION_UNKNOWN
| Not supported
|
|
STL_CALL_EXTENSION
| Supported
|
|
STL_NO_CALL_EXTENSION
| Supported
|
|
STL_CALL_EXTENSION_TO_TRANSFER
| Supported
|
track_call_party_length
| Value is 0 to 32
|
track_call_party
| Used when
track_call_party_length > 0
|
alerting_party_count
| Value is 0 or 1
|
alerting_party_list
| STRUCTURE (Party_Structure);
used when alerting_party_count > 0;
|
| Fields
| Notes
|
program_data_length
| Value is 0 to 256
|
program_data
| Fully supported
|
alert_reason
|
|
|
STL_ALERT_NOT_SPECIFIED
| Supported
|
|
STL_CALL_BACK
| Not supported
|
The Call_Conferenced call-progress event message tells a
program that a held telephone call has been retrieved, and
the parties in the previously held telephone call have been
joined or conferenced with the parties in a second, active
telephone call.
The following tables show the ROLM 9751 CBX (Release 9005) support for Call_Conferenced:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
requesting_party_1_info
| STRUCTURE (Party_Structure);
|
requesting_party_2_info
| STRUCTURE (Party_Structure);
|
billed_party_length
| Value is 0
|
billed_party
| Not supported
|
track_call_party_length
| Value is 0 to 32
|
track_call_party
| Used when
track_call_party_length > 0
|
| Fields
| Notes
|
existing_party_count
|
Value is 0
|
existing_party_list
| Not supported
|
The Call_Connected call-progress event message tells a
program that a party has become an active participant in
a telephone call in one of two ways:
- The party answers a telephone that is being alerted.
- The party retrieves a held call.
The following tables show the ROLM 9751 CBX (Release 9005) support for Call_Connected:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
connecting_party_info
| STRUCTURE (Party_Structure);
|
call_type
|
|
|
STL_VOICE
| Supported
|
|
STL_DATA
| Not supported
|
billed_party_length
| Value is 0
|
billed_party
| Not supported
|
call_extension_indicator
|
|
|
STL_CALL_EXTENSION_UNKNOWN
| Not supported
|
|
STL_CALL_EXTENSION
| Supported
|
|
STL_NO_CALL_EXTENSION
| Supported
|
|
STL_CALL_EXTENSION_TO_TRANSFER
| Supported
|
track_call_party_length
| Value is 0 to 32
|
track_call_party
| Used when
track_call_party_length > 0
|
existing_party_count
| Value is 0 to 7
|
existing_party_list
| STRUCTURE (Party_Structure);
used when existing_party_count > 0;
|
| Fields
| Notes
|
program_data_length
| Value is 0 to 256
|
program_data
| Fully supported
|
connect_reason
|
|
|
STL_CONNECT_NOT_SPECIFIED
| Supported
|
|
STL_OVERRIDE
| Not supported
|
|
STL_RECONNECT
| Not supported
|
|
STL_ADD_PART_RCV_ONLY
| Not supported
|
The Call_Held call-progress event message tells a program that a
telephone call has been placed on hold by one of the parties
in the call.
The following table shows the ROLM 9751 CBX (Release 9005) support for Call_Held:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
holding_party_info
| STRUCTURE (Party_Structure);
|
hold_info
| STRUCTURE
|
|
holding_party_calling
|
|
|
STL_CALLS_NOT_PERMITTED
| Supported
|
|
STL_CALLS_PERMITTED
| Supported
|
|
STL_SWITCH_DEFAULT_CALLING
| Not supported
|
|
holding_party_ID_2
| Used when holding_party_calling is
STL_CALLS_PERMITTED
|
|
holding_party_callback
|
|
|
STL_NO_CALLBACK
| Supported
|
|
STL_CALLBACK
| Supported
|
|
STL_SWITCH_DEFAULT_CALLBACK
| Not supported
|
track_call_party_length
| Value is 0 to 32
|
track_call_party
| Used when
track_call_party_length > 0
|
held_party_count
| Value is 1 to 7
|
held_party_list
| STRUCTURE (Party_Structure);
|
The Call_Parked call-progress event message tells a program
that a telephone call has been transferred by a party in the
call to a target party and placed on hold without ringing the
target party's telephone.
The party that requested the park function has implicitly
disconnected from the call
(no Disconnected call-progress event message is sent for
the implicit disconnect of the parking party).
The remaining party or parties in the call have been placed
on hold at the directory number of the target party.
The connection ID specified by parking_party_ID_2
is created for use in the next call originated by the party
that requested the park function.
The following table shows the ROLM 9751 CBX (Release 9005) support for Call_Parked:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
parking_party_info
| STRUCTURE (Party_Structure);
|
target_party_info
| STRUCTURE (Party_Structure);
|
park_info
| STRUCTURE
|
|
parking_party_calling
|
|
|
STL_CALLS_NOT_PERMITTED
| Not supported
|
|
STL_CALLS_PERMITTED
| Supported
|
|
STL_SWITCH_DEFAULT_CALLING
| Not supported
|
|
parking_party_ID_2
| Used when parking_party_calling is
STL_CALLS_PERMITTED
|
track_call_party_length
| Value is 0 to 32
|
track_call_party
| Used when
track_call_party_length > 0
|
held_party_count
| Value is 1
|
held_party_list
| STRUCTURE (Party_Structure);
|
The Call_Picked call-progress event message tells a program
that one of the following has occurred:
- An incoming telephone call has been answered by a party at a
directory number that is different from the directory number of the
party being alerted.
- A held telephone call has been retrieved from hold by a party at a
directory number that is different from the directory number at which
the call is being held.
The following table shows the ROLM 9751 CBX (Release 9005) support for Call_Picked:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
connecting_party_info
| STRUCTURE (Party_Structure);
|
picked_from_party_info
| STRUCTURE (Party_Structure);
|
call_type
|
|
|
STL_VOICE
| Supported
|
|
STL_DATA
| Not supported
|
billed_party_length
| Value is 0
|
billed_party
| Not supported
|
track_call_party_length
| Value is 0 to 32
|
track_call_party
| Used when
track_call_party_length > 0
|
existing_party_count
| Value is 1
|
existing_party_list
| STRUCTURE (Party_Structure);
|
The Call_Rejected call-progress event message tells a
program that a host computer-initiated telephone call
(Make_Call) could not be completed.
Information on the rejection of the telephone call is
contained in the message.
The following table shows the ROLM 9751 CBX (Release 9005) support for Call_Rejected:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
called_party_info
| STRUCTURE (Party_Structure);
|
calling_party_info
| STRUCTURE (Party_Structure);
|
reject_reason
|
|
|
STL_REASON_UNKNOWN
| Not supported
|
|
STL_REASON_BUSY
| Supported
|
|
STL_REASON_INVALID_DIR_NUM
| Supported
|
|
STL_REASON_DEV_OUT_OF_SERVICE
| Supported;
also used when a telephone is in do-not-disturb (DND) mode
|
|
STL_REASON_DO_NOT_DISTURB_SET
| Not supported
|
|
STL_REASON_RING_NO_ANSWER
| Supported;
only used when the calling party does not answer
|
|
STL_REASON_FACILITIES_UNAVAIL
| Not supported
|
|
STL_REASON_PREFIX_ERROR
| Not supported
|
|
STL_REASON_DIR_NUM_CHANGE
| Not supported
|
|
STL_REASON_CALL_INCOMPLETE
| Not supported
|
error_indication
| Fully supported
|
track_call_party_length
| Value is 0 to 32
|
track_call_party
| Used when
track_call_party_length > 0
|
The Call_Routed call-progress event message tells a program that
an incoming telephone call has been routed to the called party.
Decisions concerning the status of the telephone, or telephones,
associated with the called number have not yet been made.
Therefore, if the telephone is busy, or has
DND
or forwarding in effect, a Call_Routed message is sent
prior to this determination.
After these decisions are made concerning the status of the
telephone or telephones, additional event messages are sent.
The following tables show the ROLM 9751 CBX (Release 9005) support for Call_Routed:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
calling_party_info
| STRUCTURE (Party_Structure);
not always used;
|
routed_from_party_info
| STRUCTURE (Party_Structure);
not always used;
|
call_type
|
|
|
STL_VOICE
| Supported
|
|
STL_DATA
| Not supported
|
route_reason
|
|
|
STL_DIRECT_ROUTE
| Supported
|
|
STL_DRCT_PREFIX_ERROR_ROUTE
| Not supported
|
|
STL_DRCT_DIR_NUM_CHANGE_ROUTE
| Not supported
|
|
STL_DRCT_FACIL_UNAVAIL_ROUTE
| Not supported
|
|
STL_DRCT_CALL_INCOMPLETE_ROUTE
| Not supported
|
|
STL_DRCT_INVALID_DIR_NUM_ROUTE
| Not supported
|
|
STL_DRCT_UNKNOWN_ROUTE
| Not supported
|
|
STL_FORWARD_ROUTE
| Supported
|
|
STL_RNA_FORWARD_ROUTE
| Supported
|
|
STL_RNA_FORWARD_ADD_ROUTE
| Supported
|
|
STL_DND_FORWARD_ROUTE
| Supported
|
|
STL_BUSY_FORWARD_ROUTE
| Supported
|
|
STL_FROM_PILOT_ROUTE
| Supported
|
|
STL_QUEUE_CLEANUP_ROUTE
| Supported
|
|
STL_TO_QUEUE_ROUTE
| Supported
|
|
STL_IMMEDIATE_TRANSFER_ROUTE
| Not supported
|
call_extension_indicator
|
|
|
STL_CALL_EXTENSION_UNKNOWN
| Not supported
|
|
STL_CALL_EXTENSION
| Supported
|
|
STL_NO_CALL_EXTENSION
| Supported
|
|
STL_CALL_EXTENSION_TO_TRANSFER
| Supported
|
track_call_party_length
| Value is 0 to 32
|
track_call_party
| Used when
track_call_party_length > 0
|
routed_to_party_count
| Value is 1
|
routed_to_party_list
| STRUCTURE (Party_Structure);
|
| Fields
| Notes
|
program_data_length
|
Value is 0 to 256
|
| program_data
| Fully supported
|
The Call_Transferred call-progress event message tells a
program that a telephone call has been transferred from one party to
another.
The following tables show the ROLM 9751 CBX (Release 9005) support for Call_Transferred:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
transferring_party_1_info
| STRUCTURE (Party_Structure);
|
transferring_party_2_info
| STRUCTURE (Party_Structure);
|
billed_party_length
| Value is 0
|
billed_party
| Not supported
|
track_call_party_length
| Value is 0 to 32
|
track_call_party
| Used when
track_call_party_length > 0
|
| Fields
| Notes
|
remaining_party_count
|
Value is 0
|
remaining_party_list
| Not supported
|
The Disconnected call-progress event message tells a program
that a party's connection within a telephone call has
changed to the Idle state.
(For a full description of connections and connection states,
see
CallPath Services Programmer's Reference.)
The ROLM 9751 CBX (Release 9005) sends this message, for example, when a party
physically hangs up a telephone to end a call.
The following tables show the ROLM 9751 CBX (Release 9005) support for Disconnected:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
disconnecting_party_info
| STRUCTURE (Party_Structure);
|
track_call_party_length
| Value is 0 to 32
|
track_call_party
| Used when
track_call_party_length > 0
|
other_disconnected_party_count
| Value is 0 or 1
|
other_disconnected_party_list
| STRUCTURE (Party_Structure);
used when other_disconnected_party_count >
|
| Fields
| Notes
|
remaining_party_count
|
Value is 0
|
remaining_party_list
| Not supported
|
disconnect_reason
|
|
|
STL_DISCONNECT_NOT_SPECIFIED
| Supported
|
|
STL_ABANDON
| Not supported
|
The Feature_Invoked call-progress event message tells a
program that a party has invoked a telephone feature.
The switch sends this message when a party physically enters
a feature code or accesses a feature button on a telephone.
Feature_Invoked is sent after the feature is invoked, but
before the feature has been executed.
The following tables show the ROLM 9751 CBX (Release 9005) support for Feature_Invoked:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
feature_code
|
|
|
STL_ACCOUNT_CODE
|
Supported
|
|
STL_AGENT_ACTIVITY
| Not supported
|
|
STL_CALL_WAITING
| Not supported
|
|
STL_CAMP_FOR_CALLBACK
| Not supported
|
|
STL_CLASS_OF_SERVICE
| Not supported
|
|
STL_DO_NOT_DISTURB
| Not supported
|
|
STL_FORWARD
| Not supported
|
|
STL_MUTE
| Not supported
|
|
STL_SPEAKER
| Not supported
|
|
STL_SWITCH_SPECIFIC
| Not supported
|
feature_data
| STRUCTURE;
see the following table
|
| Feature Data
| Notes
|
Account_Code_Data
|
Fully supported
|
Agent_Activity_Data
| Not supported
|
Call_Waiting_Data
| Not supported
|
Camp_For_Callback_Data
| Not supported
|
Class_Of_Service_Data
| Not supported
|
Do_Not_Disturb_Data
| Not supported
|
Forward_Data
| Not supported
|
Mute_Data
| Not supported
|
Speaker_Data
| Not supported
|
Switch_Specific_Data
| Not supported
|
Note: An account code is sent when an agent requests the account code
feature and enters a special code on the telephone.
A call can then be charged to an account by assigning the
account code to the call.
The account code can be assigned to both incoming and
outgoing calls while the telephone is ringing, during the
conversation, or just before a party physically hangs up
a telephone.
This event message always contains the dialed account code
and the number of the party that dialed it.
For more details, consult your ROLM feature documentation.
The Network_Reached call-progress event message tells a
program that the ROLM 9751 CBX (Release 9005) has progressed in its processing of an
outgoing host computer-initiated telephone call
(Make_Call) to the point where it is dialing the called
party. The ROLM 9751 CBX (Release 9005) does not send a
Network_Reached message when local calls are being
established, that is, when both the calling and called parties are
internal extensions to the ROLM 9751 CBX (Release 9005).
If the outgoing call is on an analog trunk, where
call-progress signals are not coming from the network, the
Network_Reached message may be the last call-progress event that can
be received for the telephone call.
The following table shows the ROLM 9751 CBX (Release 9005) support for Network_Reached:
| Fields
| Notes
|
version_number
| Fully supported
|
switch_ID
| Fully supported
|
timestamp
| STRUCTURE (Time_And_Date);
|
| calling_party_info
| STRUCTURE (Party_Structure);
|
| called_party_info
| STRUCTURE (Party_Structure);
|
| track_call_party_length
| Value is 0 to 32
|
| track_call_party
| Used when
track_call_party_length > 0
|
The Party_Status reply message provides information to the program
on the current status of a specified party.
Server/2
sends Party_Status to a program only as a result of the
program issuing an earlier Query_Party_Status program call.
The following table shows the ROLM 9751 CBX (Release 9005) support for Party_Status:
| Fields
| Notes
|
| version_number
| Fully supported
|
| switch_ID
| Fully supported
|
| timestamp
| STRUCTURE (Time_And_Date);
|
| party_length
| Value is 1 to 32
|
| party
| Fully supported
|
| status_count
| Value is 0 to 7
|
| status_list
| LIST OF (Status_Structure);
this information is collected by
CallPath SwitchServer/2 or CallPath Server/2
|
Note: The status_list field uses the Status_Structure,
which is fully supported by the ROLM 9751 CBX (Release 9005).
See Status_Structure
in CallPath Services Programmer's Reference.
The Response message is a response from the ROLM 9751 CBX (Release 9005) to an
earlier request from the program.
It tells the program whether the earlier request was accepted
or rejected by the ROLM 9751 CBX (Release 9005).
If Response is positive, indicating that the request was
accepted, the program must request one or more subsequent
call-progress event messages if it wishes to determine whether
the request was ultimately successful.
The following table shows the ROLM 9751 CBX (Release 9005) support for Response:
| Fields
| Notes
|
| version_number
| Fully supported
|
| switch_ID
| Fully supported
|
| timestamp
| STRUCTURE (Time_And_Date);
|
| request_tag
| Fully supported
|
| reserved
| Does not contain a value
|
| response_type_indicator
| Fully supported
|
| sense_code
|
|
| STL_UNASSIGNED_CONNECTION_ID
| Supported
|
| STL_INVALID_BILLED_PARTY
| Not supported
|
| STL_INVALID_DIRECTORY_NUMBER
| Supported
|
| STL_DEV_INCOMPATIBLE_WITH_RQ
| Supported
|
| STL_STATE_INCOMPATIBLE_WITH_RQ
| Supported
|
| STL_CONF_TRANSFER_INVALID
| Supported
|
| STL_PARTIES_UNKNOWN_TO_SWITCH
| Not supported
|
| STL_RQ_NOT_SUPPORTED_BY_SWITCH
| Supported
|
| STL_RETURN_CONTROL_STATE_ERROR
| Not supported
|
| STL_REQUEST_AND_COS_MISMATCH
| Not supported
|
| STL_AUTO_ANSWER_PARTY_UNKNOWN
| Not supported
|
| STL_SWITCH_SPECIFIC_ERROR
| Supported
|
| STL_RESOURCES_NOT_AVAILABLE
| Not supported
|
| STL_INVALID_AGENT_ASSIGNMENT
| Not supported
|
| STL_INVALID_POOL
| Not supported
|
| STL_REDUNDANT_POOL_ASSIGNMENT
| Not supported
|
| STL_TRACKING_INCONSISTENCY
| Not supported
|
| STL_SYSTEM_ERROR
| Supported
|
| STL_TRGR_REDUNDANCY
| Not supported
|
| STL_TRGR_BY_ANOTHER_PROGRAM
| Not supported
|
| STL_TRGR_BY_SAME_PROGRAM
| Not supported
|
| STL_RES_OWNERSHIP_INCOMPATIBLE
| Not supported
|
| STL_PGM_NOT_AUTHORIZED_FOR_RES
| Not supported
|
| Fields
| Notes
|
| STL_RESOURCE_AND_TYPE_MISMATCH
| Not supported
|
| STL_INVALID_AGENT_ID
| Not supported
|
| STL_CONNECTION_ID_MISMATCH
| Supported
|
| sense_code_qualifier_length
| Value is 0 to 32
|
| sense_code_qualifier
| Used when
sense_code_qualifier_length > 0;
|
The Party_Structure is a data structure composed
of several fields.
Most messages contain information about at least one party
associated with a telephone call.
The ROLM 9751 CBX (Release 9005) provides as much information about the party as
is available to it.
The information is extensive.
It can include the party's telephone number, the connection ID
associated with the party's connection in the telephone call,
the calling party's telephone number, and other data if it is
available.
The Party_Structure is referenced by the
individual messages.
The following table shows the ROLM 9751 CBX (Release 9005) support for
Party_Structure:
| Fields
| Notes
|
common_information
| STRUCTURE
|
| connection_ID_present
|
|
| STL_PRESENT
| Supported
|
| STL_NOT_PRESENT
| Not supported
|
| connection_ID
| Value is 8
|
| party_numbering_plan
|
|
| STL_UNKNOWN_PLAN
| Supported
|
| STL_TELEPHONY_PLAN
| Not supported
|
| STL_DATA_PLAN
| Not supported
|
| party_number_length
| Value is 0 to 32
|
| party_number
| Used when party_number_length > 0
|
| party_address_length
| Value is 0 to 32
|
| party_address
| Used when party_address_length > 0
|
| party_type
|
|
| STL_UNKNOWN_PARTY_TYPE
| Supported
|
| STL_EXTENSION_PARTY_TYPE
| Supported
|
| STL_ANI_PARTY_TYPE
| Supported
|
| STL_PILOT_PARTY_TYPE
| Supported
|
| STL_AGENT_ID_PARTY_TYPE
| Not supported
|
called_party_info
| STRUCTURE
|
| party_group_length
| Value is 0 to 32
|
| party_group
| Used when party_group_length > 0
|
| original_group_length
| Value is 0 to 32
|
| original_group
| Used when original_group_length > 0
|
| dialed_number_length
| Value is 0 to 32
|
| dialed_number
| Used when dialed_number_length > 0
|
| DNIS_length
| Value is 0 to 32
|
| DNIS
| Used when DNIS_length > 0;
the first two characters of DNIS are a table number.
|
| trunk_number_length
| Value is 0 to 32
|
| trunk_number
| Used when trunk_number_length > 0
|
Note: The following applies to the party_number field.
When all of the following are true:
- party_type is STL_UNKNOWN_PARTY_TYPE
- The party is not involved in a request (Make_Call)
- party_number_length is > 0
the following is the structure of the party_number field:
- The first two characters in the field are the
switch party_type value:
- 00 is extension
- 01 is trunk
- 02 is attendant console
- 03 is PhoneMail pilot
- The rest of the field is the party_number
associated with that switch party_type.
For example, in 010025, 01 is a trunk and 0025 is the trunk number.
The reason for this structure is that this party_number
field is a party/resource from another switch in the telephony
network.
This field can then be used to coordinate the activity
between different switches.
The Time_And_Date structure is referenced by the
individual messages.
The following table shows the ROLM 9751 CBX (Release 9005) support for
Time_And_Date:
| Fields
| Notes
|
|
time_and_date_field
| Fully supported (exception: the first x digit of
the timestamp field contains a value from 0 to 9; the
remaining xx digits are always 0)
|
| reserved
| Does not contain a value
|
This chapter describes the level of support the ROLM 9751 CBX (Release 9005)
provides for the feature_data parameter of
the Invoke_Feature program call.
The data is feature specific and its contents and format
vary, depending on the value of feature_code.
Refer to
CallPath Services Programmer's Reference for complete information on feature
formats and codes.
The following table shows the ROLM 9751 CBX (Release 9005) support for the
feature_data parameter of Invoke_Feature:
| Feature Data
| Notes
|
| Account_Code_Data
| STRUCTURE;
not supported
|
| Agent_Activity_Data
| STRUCTURE
|
| party_length
| Value is 1 to 22
|
| party
| Fully supported
|
| activity
|
|
| STL_AGENT_LOGON
| Not supported
|
| STL_AGENT_LOGOFF
| Not supported
|
| STL_AGENT_READY
| Supported
|
| STL_AGENT_READY_EXPLICITLY
| Not supported
|
| STL_AGENT_READY_IMPLICITLY
| Not supported
|
| STL_AGENT_BUSY
| Not supported
|
| STL_AGENT_BUSY_WITH_CALL
| Not supported
|
| STL_AGENT_BUSY_WITH_FOLLOWUP
| Not supported
|
| STL_AGENT_NOT_READY
| Supported
|
| agent_ID_length
| Value is 0
|
| agent_ID
| Not supported
|
| pool_length
| Value is 0
|
| pool
| Not supported
|
| Call_Waiting
| STRUCTURE;
not supported
|
| Camp_For_Callback_Data
| STRUCTURE;
not supported
|
| Class_of_Service
| STRUCTURE;
not supported
|
| Do_Not_Disturb_Data
| STRUCTURE;
|
| party_length
| Value is 1 to 22
|
| party
| Fully supported
|
| mode
| Fully supported
|
| Forward_Data
| STRUCTURE;
|
| party_length
| Value is 1 to 22
|
| party
| Fully supported
|
| forward_to_party_length
| Value is 1 to 22
|
| forward_to_party
| Fully supported
|
| mode
| Fully supported
|
| forward_type
|
|
| STL_BUSY_FORWARD
| Not supported
|
| STL_RING_NO_ANSWER_FORWARD
| Not supported
|
| STL_UNCONDITIONAL_FORWARD
| Supported
|
| Mute_Data
| STRUCTURE;
not supported
|
| Speaker_Data
| STRUCTURE;
not supported
|
| Switch_Specific
| STRUCTURE;
not
supported
|
Feature Formats and Codes
This chapter describes the types of problem determination data
available and how to obtain them.
If an error is reported by CallPath SwitchServer/2
or CallPath Server/2
(collectively called "Server/2" hereafter), consult
Using CallPath SwitchServer/2 or
the CallPath Server Planning, Installation,
and Problem Determination Guide as appropriate.
Note: Except where there is a need to differentiate between CallPath SwitchServer/2
and CallPath Server/2, the term Server/2 will be used in place of
the phrases "CallPath SwitchServer/2 and CallPath Server/2".
For more detailed troubleshooting procedures when using CallPath SwitchServer/2,
use the Editor to read the READ.ME file
in the CallPath SwitchServer/2 C:\GATEWAY directory.
For more detailed troubleshooting procedures when using CallPath Server/2,
see the CallPath Server Planning, Installation, and
Problem Determination Guide.
The ROLM 9751 CBX (Release 9005) fully supports return codes.
See
CallPath Services Programmer's Reference
for information about return codes.
When the ROLM 9751 CBX (Release 9005) or Server/2 detects
an error in a request, the
program is informed of the error by receipt of a negative
Response message.
(This assumes that the program has set return_response
to STL_RESPONSE_RETURNED or
STL_NEGATIVE_RESPONSE_RETURNED.) The negative
Response message contains a sense_code value and, if
applicable, a sense_code_qualifier value.
A sense code reflects the associated error.
A sense code qualifier provides additional information
regarding the error detected in the request with which the
Response is associated.
Information in sense_code_qualifier
is dependent upon the value of sense_code.
For details on sense codes and sense code qualifiers, see
"Response".
The following sense code qualifiers grouped by sense codes
are used by
Server/2
when connected to the ROLM 9751 CBX (Release 9005):
Sense code qualifier: X'nn...nn'
Description: nn...nn is an invalid directory number.
A request was issued with an invalid directory number.
Action: Reissue the request with a valid directory number.
Sense Code Qualifiers
Sense code qualifier: X'nn...nn'
Description: nn...nn is an invalid connection ID.
A request was issued with an invalid connection ID.
Action: Reissue the request with a valid connection ID.
Sense Code Qualifiers
Sense code qualifier: X'00000002'
Description: The maximum number of Connect ID control blocks has been reached.
This condition should be temporary.
Action: Retry the request.
If the problem persists, collect the trace data, then ask your
IBM service representative to review the results.
Sense code qualifier: X'00000003'
Description: A request was issued specifying a connection ID which has no
associated directory number.
This request cannot be completed and should not be retried.
Action: Correct the host connection ID
for the calling or called party and reissue the request.
If the problem persists, collect the trace data, then ask
your IBM service representative to review the results.
Sense code qualifier: X'00000004'
Description: The maximum number of Monitor requests allowed for the ROLM 9751 CBX (Release 9005)
has been reached.
Action: Issue stop Monitor requests and retry the request.
It may be necessary to deactivate and reactivate the CallPath Server/2 or CallPath SwitchServer/2.
If the problem persists, collect the trace data, then ask your
IBM service representative to review the results.
Sense code qualifier: X'00000008'
Description: A request failed because the outbound
portion of CallBridge Link Manager was not configured.
Action: Configure the outbound portion of CallBridge Link Manager and retry the
request.
If the problem persists, collect the trace data,
then ask your IBM service representative to review the results.
Sense code qualifier: X'0000000C'
Description: The maximum number of outstanding requests supported by the
ROLM 9751 CBX (Release 9005) has been reached.
Action: Deactivate and activate the ROLM 9751 CBX (Release 9005) before reissuing
the request.
If the problem persists, collect the trace data,
then ask your IBM service representative to review the results.
Sense code qualifier: X'0000000D'
Description: A Disconnect request was issued specifying a connection
ID for a party that was found to be in an invalid state.
Action: Check that the connection ID is in a non-Idle state
and reissue the request.
If the problem persists, collect the trace data,
then ask your IBM service representative to review the results.
Sense code qualifier: X'0000000E'
Description: A request was issued specifying program_data.
program_data is supported, however, the length specified
exceeds that supported by the ROLM 9751 CBX (Release 9005).
Action: Re-issue the request specifying a supported
program_data_length.
If the problem persists, collect the trace data,
then ask your IBM service representative to review the results.
Sense code qualifier: X'00020E23F0'
Description: The acknowledge code value in the Response message, sent by the
ROLM 9751 CBX (Release 9005) for the request, is invalid.
Action: Deactivate and activate the ROLM 9751 CBX (Release 9005) before reissuing the
request.
If the problem persists, collect the trace data, then ask
your IBM service representative to review the results.
Sense code qualifier: X'00020E23F1'
Description: The subscriber number field in the Response message, sent by the
ROLM 9751 CBX (Release 9005) for the Make_Call request, is invalid.
Action: Deactivate and activate the ROLM 9751 CBX (Release 9005) before reissuing the request.
If the problem persists, collect the trace data,
then ask your IBM service representative to review the results.
Sense code qualifier: X'00020E23F2'
Description: The called party field in the Response message, sent by the
ROLM 9751 CBX (Release 9005) for the Make_Call request, is invalid.
Action: Deactivate and activate the ROLM 9751 CBX (Release 9005) before reissuing the request.
If the problem persists, collect the trace data,
then ask your IBM service representative to review the results.
Sense code qualifier: X'00020E23F3'
Description: The local set field in the Response message, sent by the
ROLM 9751 CBX (Release 9005) for the Make_Call request, is invalid.
Action: Deactivate and activate the ROLM 9751 CBX (Release 9005) before reissuing the request.
If the problem persists, collect the trace data,
then ask your IBM service representative to review the results.
Sense code qualifier: X'00020E23F4'
Description: The calling party field in the Response message, sent by the
ROLM 9751 CBX (Release 9005) for the Make_Call request, is invalid.
Action: Deactivate and activate the ROLM 9751 CBX (Release 9005) before reissuing the request.
If the problem persists, collect the trace data,
then ask your IBM service representative to review the results.
Sense code qualifier: X'00020E23F5'
Description: The acknowledge code value in the Response message, sent by the
ROLM 9751 CBX (Release 9005) for the Make_Call request, is invalid.
Action: Deactivate and activate the ROLM 9751 CBX (Release 9005) before reissuing the request.
If the problem persists, collect the trace data, then ask
your IBM service representative to review the results.
Sense code qualifier: X'00020C14'
Description: The acknowledge code value in the Response message sent
by the ROLM 9751 CBX (Release 9005) indicates that the reference number for the
issued Make_Call is in use.
Action: Deactivate and activate
CallPath Server/2 or CallPath SwitchServer/2
before reissuing the Make_Call request.
If the problem persists, collect the trace data,
then ask your IBM service representative to review the results.
Sense code qualifier: X'00020C16'
Description: The acknowledge code value in the Response message indicates
that the ROLM 9751 CBX (Release 9005) encountered a system error while processing a
request.
Action: Deactivate and activate
CallPath Server/2 or CallPath SwitchServer/2
before reissuing the Make_Call
request.
If the problem persists, collect the trace data,
then ask your IBM service representative to review the results.
Sense code qualifier: X'00020C32'
Description: There was no available ODI to process a request.
Action: Retry the request. If the problem persists, collect
the trace data, then ask your IBM service representative
to review the results.
Sense code qualifier: X'00020Emm0Fnn'
Description: While processing a
request,
the ROLM 9751 CBX (Release 9005) encountered an error.
mm is one of the following error code values in
the Response message:
Name Value
unrecognized service 01
invalid class 02
missing mandatory field 03
illegal optional field 04
unrecognized field 05
syntax error 06
content error 07
nn is the byte position of the error.
The message is rejected.
Action: Check the
Server/2
switch-dependent code.
Deactivate and activate
Server/2
before reissuing the request.
If the problem persists, collect the trace data,
then ask your IBM service representative to review the results.
Sense Code Qualifiers
Sense code qualifier: X'00000001'
Description: The ROLM 9751 CBX (Release 9005) support could not decode the request.
Action: Deactivate and activate
Server/2
before reissuing the
request.
If the problem persists, collect the trace data, then ask your
IBM service representative to review the results.
Sense code qualifier: X'00000005'
Description: The internal
Server/2
switch-dependent function found the
current state to be invalid for one of the parties of a
positive Response for a request.
Action: Reissue the request.
If the problem persists, collect the trace data, then ask your IBM service representative to
review the results.
Sense code qualifier: X'00000008'
Description: A major error was encountered between the ROLM 9751 CBX (Release 9005) and
Server/2
while
processing a request.
Action: Check the system message data for the exact error that occurred.
If the problem persists, collect the trace data, then ask your IBM service representative to
review the results.
Sense Code Qualifiers
Sense code qualifier: X'81000000'
Description: Add_Party is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX" for valid
program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'81030000'
Description: Conference_Call is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX"
for valid program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'81040000DF2E'
Description: The disconnect_execution_option value
contained within the call profile specified by the
call_profile_ID parameter on the Disconnect
program call must be
STL_DSC_UNCONDITIONAL.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for this call
profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)"
and
CallPath Services Programmer's Reference for valid call profile characteristics.
Reissue the program call with valid information.
Sense code qualifier: X'81040000DF46'
Description: The remaining_parties_option value
contained within the call profile specified by the
call_profile_ID parameter on the Disconnect
program call must be
STL_REMAINING_CONDITIONAL.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for this call
profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)"
and
CallPath Services Programmer's Reference for valid call profile characteristics.
Reissue the program call with valid information.
Sense code qualifier: X'81050000DF20'
Description: The account_code parameter of the
Extend_Call program call is not supported by the ROLM 9751 CBX (Release 9005)
Action: See "STLXTND (Extend_Call)" for the supported
parameters and parameter values.
Reissue the program call with valid information.
Sense code qualifier: X'81050000DF26'
Description: The billed_party value contained within the
call profile specified by the call_profile_ID
parameter on the Extend_Call program call must be a null
value.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for this call
profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)"
and
CallPath Services Programmer's Reference for valid call profile characteristics.
Reissue the program call with valid information.
Sense code qualifier: X'81050000DF31'
Description: The extend_purpose value contained within the
call profile specified by the call_profile_ID
parameter on the Extend_Call program call is not supported
by the ROLM 9751 CBX (Release 9005).
Action: See "STLSEP (Set_Extend_Purpose)" for the supported parameter
values.
Reissue the program call with valid information.
Sense code qualifier: X'81050000DF39'
Description: The held_call_connection value contained
within the call profile specified by the
call_profile_ID parameter on the Extend_Call
program call must be
STL_CONNECT_TO_SWITCH_DEFAULT.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for this call
profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)"
and
CallPath Services Programmer's Reference for valid call profile characteristics.
Reissue the program call with valid information.
Sense code qualifier: X'81050000DF44'
Description: The held_call_recording value contained
within the call profile specified by the
call_profile_ID parameter on the Extend_Call
program call must be a null value.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for this call
profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)"
and
CallPath Services Programmer's Reference for valid call profile characteristics.
Reissue the program call with valid information.
Sense code qualifier: X'81050000DF8107'
Description: The called_party_alerting_time value
contained within the call profile specified by the
call_profile_ID parameter on the Extend_Call
program call must be 0.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for this call
profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)"
and
CallPath Services Programmer's Reference for valid call profile characteristics.
Reissue the program call with valid information.
Sense code qualifier: X'81060000'
Description: Hold_Call is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX" for valid
program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'81070000DF22'
Description: The activity value in the feature_data
parameter specified on the Invoke_Feature program call is
not supported by the ROLM 9751 CBX (Release 9005).
Action: See Chapter 8. "Feature Formats and Codes" for the valid activity
values in the feature_data parameter.
Reissue the program call with valid information.
Sense code qualifier: X'81070000DF33'
Description: The value in the feature_code parameter
specified on the Invoke_Feature program call is not
supported by the ROLM 9751 CBX (Release 9005).
Action: See "STLINVK (Invoke_Feature)" for the valid
feature_code parameter values.
Reissue the program call with valid information.
Sense code qualifier: X'81070000DF37'
Description: The forward_type value in the
feature_data parameter specified on the
Invoke_Feature program call is not supported by the ROLM 9751 CBX (Release 9005).
Action: See Chapter 8. "Feature Formats and Codes", for the valid
forward_type values in the feature_data
parameter.
Reissue the program call with valid information.
Sense code qualifier: X'81070000DF3D'
Description: The mode value in the feature_data
parameter specified on the Invoke_Feature program call is
not supported by the ROLM 9751 CBX (Release 9005).
Action: See Chapter 8. "Feature Formats and Codes", for the valid mode
values in the feature_data parameter.
Reissue the program call with valid information.
Sense code qualifier: X'81070000DF63'
Description: The agent_id value in the feature_data
parameter specified on the Invoke_Feature program call is
not supported by the ROLM 9751 CBX (Release 9005).
Action: See Chapter 8. "Feature Formats and Codes", for the valid agent_id
values in the feature_data parameter.
Reissue the program call with valid information.
Sense code qualifier: X'81070000DF64'
Description: The pool value in the feature_data
parameter specified on the Invoke_Feature program call is
not supported by the ROLM 9751 CBX (Release 9005).
Action: See Chapter 8. "Feature Formats and Codes", for the valid pool
values in the feature_data parameter.
Reissue the program call with valid information.
Sense code qualifier: X'81080000DF20'
Description: The account_code parameter of the Make_Call
program call is not supported by the ROLM 9751 CBX (Release 9005).
Action: See "STLMAKE (Make_Call)" for the supported parameters
and parameter values.
Reissue Make_Call with valid information.
Sense code qualifier: X'81080000DF25'
Description: The automatic_answer value contained within
the call profile specified by the call_profile_ID
parameter on the Make_Call program call must be
STL_NO_ANSWER.
The ROLM 9751 CBX (Release 9005) does not support the initialized value for this
call profile characteristic.
Action: See "STLSAA (Set_Automatic_Answer)".
See "STLINIT (Initialize_Call_Profile)"
and
CallPath Services Programmer's Reference for valid call profile characteristics.
Reissue the request with valid information.
Sense code qualifier: X'81080000DF26'
Description: The billed_party value contained within the
call profile specified by the call_profile_ID
parameter on the Make_Call program call must be a null value.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for this call
profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)"
and
CallPath Services Programmer's Reference for valid call profile characteristics.
Reissue the request with valid information.
Sense code qualifier: X'81080000DF29'
Description: The call_type value contained within the call profile
specified by the call_profile_ID parameter on the
Make_Call program call must be STL_VOICE.
The ROLM 9751 CBX (Release 9005) supports
only the initialized value for this call profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)"
and
CallPath Services Programmer's Reference for valid call
profile characteristics.
Reissue the request with valid information.
Sense code qualifier: X'81080000DF2C'
Description: The party_specification value contained within
the call profile specified by the call_profile_ID
parameter on the Make_Call program call must be
STL_DIRECTORY_NUMBER.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for this call
profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)"
and
CallPath Services Programmer's Reference
for valid call profile characteristics.
Reissue the request with valid information.
Sense code qualifier: X'81080000DF2F'
Description: The make_call_DND_override value contained within
the call profile specified by the call_profile_ID
parameter on the Make_Call program call must be
STL_NO_DND_OVERRIDE.
The ROLM 9751 CBX (Release 9005) does not support the initialized value for this
call profile characteristic.
Action: See "STLSMCD (Set_Make_Call_DND_Override)".
See "STLINIT (Initialize_Call_Profile)" and
CallPath Services Programmer's Reference for valid call profile
characteristics.
Reissue the request with valid information.
Sense code qualifier: X'81080000DF36'
Description: The make_call_forward_override value
contained within the call profile specified by the
call_profile_ID parameter on the Make_Call
program call must be
STL_NO_FORWARD_OVERRIDE.
The ROLM 9751 CBX (Release 9005) does not support the initialized value for this
call profile characteristic.
Action: See "STLSMCF (Set_Make_Call_Forward_Override)".
See "STLINIT (Initialize_Call_Profile)" and
CallPath Services Programmer's Reference for valid call profile
characteristics.
Reissue the request with valid information.
Sense code qualifier: X'81080000DF3C'
Description: The make_call_notification value contained
within the call profile specified by the
call_profile_ID parameter on the Make_Call
program call must be
STL_MC_NORMAL_CALL_PROGRESS.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for this call
profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)" and
CallPath Services Programmer's Reference for valid call profile characteristics.
Reissue the request with valid information.
Sense code qualifier: X'81080000DF8107'
Description: The called_party_alerting_time value
contained within the call profile specified by the
call_profile_ID parameter on the Make_Call
program call must be 0.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for this call
profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)" and
CallPath Services Programmer's Reference
for valid call profile characteristics.
Reissue the request with valid information.
Sense code qualifier: X'81080000DF8108'
Description: The make_call_party_order value
contained within the call profile specified by the
call_profile_ID parameter on the Make_Call
program call must be
STL_CONNECT_PARTY_ONE_FIRST.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for this call
profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)" and
CallPath Services Programmer's Reference
for valid call profile characteristics.
Reissue the request with valid information.
Sense code qualifier: X'810900000000'
Description: The ROLM 9751 CBX (Release 9005) does not support a parameter specified on Monitor.
No further information is known about the unsupported parameter
specification.
Action: See "STLMON (Monitor)" for valid parameters.
Reissue the request with valid information.
Sense code qualifier: X'81090000DF63'
Description: The monitor_resource_type value of
STL_MONITOR_AGENT_IDENTIFIER specified on
Monitor is not supported.
Action: See "STLMON (Monitor)" for valid
monitor_resource_type values.
Reissue Monitor with valid information.
Sense code qualifier: X'81090000DF7A'
Description: The monitor_resource_type value of
STL_MONITOR_GROUP is supported, but the
group definition ID value specified in the resource
parameter on Monitor is not supported.
Action: See the Monitor program call in
CallPath Services Programmer's Reference
for valid resource values.
Reissue Monitor with a valid resource value.
Sense code qualifier: X'81090000DF8106'
Description: The monitor_resource_type value of
STL_MONITOR_PILOT_NUMBER specified on
Monitor is not supported.
Action: See "STLMON (Monitor)" for valid
monitor_resource_type values.
Reissue Monitor with valid information.
Sense code qualifier: X'81090000FF5DFFEE23E0...0000'
Description: A Monitor was issued with an invalid event/rank combination
specified in the event_list and rank_list
parameters.
Bytes 7 through 32 of sense_code_qualifier
are a bit map that indicate what event/rank combinations are
supported by the switch.
Refer to the Monitor program call in
CallPath Services Programmer's Reference
for the table that defines the bit map.
Action: Reissue Monitor with a valid event/rank combination.
Sense code qualifier: X'810A0000'
Description: Redirect_Call is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX"
for valid program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'810B0000'
Description: Reject_Call is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX"
for valid program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'810C0000'
Description: Retrieve_Call is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX"
for valid program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'810D0000'
Description: Return_Control is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX"
for valid program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'810E0000DF20'
Description: The account_code parameter of the
Transfer_Call program call is not supported by the ROLM 9751 CBX (Release 9005).
Action: See "STLTRAN (Transfer_Call)" for the supported
parameters.
Reissue the program call with valid information.
Sense code qualifier: X'810E0000DF26'
Description: The billed_party value contained within the
call profile specified by the call_profile_ID
parameter of the Transfer_Call program call must be a
null value.
The ROLM 9751 CBX (Release 9005) supports only the initialized value for
this call profile characteristic.
Action: See "STLINIT (Initialize_Call_Profile)" and
CallPath Services Programmer's Reference for valid call profile characteristics.
Reissue the program call with valid information.
Sense code qualifier: X'810F0000'
Description: Trigger is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX"
for valid program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'86240000'
Description: Immediate_Transfer is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX" for valid
program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'8B3E0000'
Description: Park_Call is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX" for valid
program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'8B3F0000'
Description: Pick_Call is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX" for valid
program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'8B400000'
Description: Provide_Indicator is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX" for valid
program calls for the ROLM 9751 CBX (Release 9005).
Sense code qualifier: X'8B420000'
Description: Send_Device_Data is not supported by the ROLM 9751 CBX (Release 9005).
Action: See the table in "Program Calls Supported by the ROLM 9751 CBX" for valid
program calls for the ROLM 9751 CBX (Release 9005).
Server/2
records all system messages in a system messages buffer.
You can display the system messages directly on the screen or
log them to a file that you can browse, print, or delete.
Each system message requires one line on the screen.
For details on displaying the system messages, see
Using CallPath SwitchServer/2
or the CallPath Server Planning, Installation, and
Problem Determination Guide.
System messages include noncritical and critical program
error messages.
Noncritical program errors are primarily informational.
When a critical program error occurs,
Server/2
automatically reloads
its code and data from the disk and restarts the program
if configured for restart on failure.
All critical program errors are
also sent, as follows:
The following table shows the category and numerical range of
the system messages listed in this section:
| Category
| Range
|
| Program (noncritical)
| 5000-5899
|
| Overload (noncritical)
| 5900-5999
|
| Program (critical)
| 6000-6199
|
| Message error
| 6200-6399
|
| Switch connection
| 6400-6599
|
Note: To keep message explanations, causes, and user actions brief,
CallPath Server/2 and CallPath SwitchServer/2
are referred to as server
within the messages that follow.
Respond to the messages within the context of your
ROLM 9751 CBX (Release 9005) configuration
in use at the time of the message--ROLM 9751 CBX (Release 9005) communicating with
Server/2.
5000
ERR_NON_CRITICAL_PGM
Explanation: Noncritical program error
Module: SWITCH.EXE
Severity: WARNING
5001
ERR_PARTY_RSRC_OVERLOAD
Explanation: A resource overload has been encountered.
Cause: The switch is overloading
the switch dependent code with call information.
There is
the possibility of losing valid call information.
Action: This condition is automatically relieved by
the server through garbage collection procedures.
If the problem persists, contact your IBM Service Representative.
Module: CGEN
Severity: WARNING
5002
ERR_NO_CALLID_FOR_DN
Explanation: No call IDs exist for the specified directory number.
Cause: The Call State routines could not find any
calls associated with the specific directory number.
Action: No action is needed.
Module: CGEN
Severity: WARNING
5003
ERR_NO_CALLID_FOR_CID
Explanation: No call IDs exist for the specified connection ID.
Cause: The Call State routines could not find any
calls associated with the specific connection ID.
Action: No action is needed.
Module: CGEN
Severity: WARNING
5004
ERR_NO_CALLID_FOR_CALL
Explanation: No call IDs exist for the call.
Cause: The Call State routines could not find any
calls associated with the specific call ID.
Action: No action is needed.
Module: CGEN
Severity: WARNING
5005
ERR_INACT_STACK_EMPTY
Explanation: The inactive stack of call status blocks is empty.
Cause: The Call State routines detected that the
garbage collection stack is empty and no further
garbage collection is needed at this time.
Action: No action is needed.
Module: CGEN
Severity: WARNING
5006
ERR_INACT_STACK_FULL
Explanation: The inactive stack of call status blocks is full.
Cause: The Call State routines detected that the
garbage collection stack is full and
garbage collection is needed at this time.
Action: No action is needed.
This condition is
automatically relieved by the server through
garbage collection procedures.
Module: CGEN
Severity: WARNING
5007
ERR_MSB_NOT_FOUND
Explanation: No monitor status block was found for the specified party.
Cause: The Call State routines could not find any
monitor status blocks associated with the specific party.
Action: No action is needed.
Module: CGEN
Severity: WARNING
5008
ERR_RT_RSRC_UNAVAIL
Explanation: A depletion of request tags has been encountered.
Cause: The Call State routines detected a shortage of available
request tags in the database.
The sum of the number of telephone calls
being controlled and the number of resources being monitored exceeds
the maximum allowed by the switch-dependent code.
Action: Reduce the number of resources being monitored.
If the problem persists, contact your IBM Service Representative.
Module: CGEN
Severity: WARNING
5009
ERR_MON_RSRC_UNAVAIL
Explanation: A depletion of monitor status blocks has been encountered.
Cause: The Call State routines detected a shortage of
available monitor status blocks in the database.
There is the possibility of losing valid call information.
Action: This condition is automatically relieved
by the server through garbage collection procedures.
If the problem persists, contact your IBM Service Representative.
Module: CGEN
Severity: WARNING
5010
ERR_HOST_MON_RSRC_UNAVAIL
Explanation: A depletion of host computer monitor status blocks has been encountered.
Cause: The Call State routines detected a shortage of
available host computer monitor status blocks in the database.
Action: This condition is automatically
relieved by the host application programs sending
a series of stop Monitor requests.
Module: CGEN
Severity: WARNING
5011
ERR_CI_RSRC_UNAVAIL
Explanation: A depletion of call IDs has been encountered.
Cause: The Call State routines detected a shortage
of available call ID control blocks in the database.
There is the possibility of losing valid call information.
Action: This condition is automatically relieved
by the server through garbage collection procedures.
If the problem persists, contact your IBM Service Representative.
Module: CGEN
Severity: WARNING
5012
ERR_RT_INVALID
Explanation: An invalid request tag was received while processing a request.
Cause: The Call State routines were given a request tag
that is not in the database.
Action: If this problem persists, the switch
needs to be checked for possible errors.
Run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5013
ERR_CALL_LIST_OVERFLOW
Explanation: The specified directory number is participating in too many calls.
Cause: The Call State routines detected that a particular
directory number is involved in more calls than
can be handled at one time.
Action: The additional calls are lost or
not processed properly, thereby losing information or
presenting invalid information.
If the problem persists, contact your IBM Service Representative.
Module: CGEN
Severity: WARNING
5014
ERR_NO_PREV_DN_MONITOR
Explanation: The original directory number is not being monitored.
Cause: The Call State routines were requested to create a second
monitor status block for a particular directory number but
found that the first monitor status block did not exist.
Action: This system message is strictly informational.
The system automatically corrects the situation.
Module: CGEN
Severity: WARNING
5015
ERR_RT_NOT_INUSE
Explanation: The specified request tag is not presently in use.
Cause: The Call State routines were requested to process a
request tag that is not in use at this time.
Latent processing is
being done on a request tag that has already been or was never used.
Action: If the problem persists, the switch needs to be checked
for possible errors or there is a synchronization problem
between the switch and the server.
Module: CGEN
Severity: WARNING
5016
ERR_RT_QUEUE_OVERFLOW
Explanation: Too many request tags have been deleted.
Cause: The Call State routines detected that the server
is trying to free more request tags than are currently in use.
Request tags are being reused without going through
the Call State database.
Action: If this problem persists, the switch-dependent
part of the server needs to be checked.
Module: CGEN
Severity: WARNING
5017
ERR_GRT_QUEUE_OVERFLOW
Explanation: Too many gateway request tags have been deleted.
Cause: The Call State routines detected that the server
is trying to free more gateway requests than are currently in use.
Action: This condition indicates that gateway request tags
are being reused without going through the Call State database.
If this problem persists, the switch dependent part
of the server needs to be checked for possible errors.
Module: CGEN
Severity: WARNING
5018
ERR_GRT_NOT_INUSE
Explanation: The specified gateway request tag is not presently in use.
Cause: The Call State routines were requested to process
a gateway request tag that is not in use at this time.
Action: This condition indicates that somehow latent
processing is being done on a gateway request tag that
has already been or never was in use.
Module: CGEN
Severity: WARNING
5019
ERR_GRT_RSRC_UNAVAIL
Explanation: A depletion of gateway request tags has been encountered.
Cause: The Call State routines detected a shortage
of available gateway request tags in the database.
Action: Application is not responding to Request_Instruction
messages quickly enough. If this problem persists,
run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5020
ERR_CALL_ID_NOT_INUSE
Explanation: Local call ID not in use.
Cause: The Call State routines are trying to use an invalid call ID.
Action: Run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5021
ERR_CALLID_ASSOCIATED
Explanation: Local call ID is already associated with a switch call ID.
Cause: The Call State routines are trying to associate
a switch call ID with a local call ID that is already
associated with another switch call ID.
Action: Run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5022
ERR_NO_DN_IN_CALL
Explanation: The specified directory number is not in the call.
Cause: The switch-dependent part of the server
was not able to find a specified directory number
for a particular call ID.
Action: Run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5023
ERR_TRACK_LEN_EXCEEDED
Explanation: The length of a directory number that is being call tracked is invalid.
Cause: The Call State routines were requested to process a call with
an invalid directory number that was being call tracked by a party.
Latent processing is being done on a directory number that has an
invalid length.
This message never appears in the event log.
Action: If the problem persists, the switch-dependent part of
the server needs to be checked.
Module: CGEN
Severity: WARNING
5024
ERR_MAX_TRACK_EXCEEDED
Explanation: Too many directory numbers have been call tracked for the same call.
Cause: Too many directory numbers that are or once were
part of a call are being call tracked. This condition
indicates that the call is being tracked by more parties
than the Call State can presently handle.
Action: The switch-dependent part of the server
needs to be checked for possible errors.
Module: CGEN
Severity: WARNING
5025
ERR_CLEAR_OVERLOAD
Explanation: A switch request tag overload condition has been relieved.
Cause: The Call State routines detected that the overload
condition has been relieved.
Action: No action is needed.
Module: CGEN
Severity: WARNING
5026
ERR_GLO_PI_INVALID_TOKEN
Explanation: An invalid token was encountered while processing a message.
Cause: The interface to the switch-independent part of
the server rejected a request to process a message from
the switch-dependent part. An invalid token was given as input.
Action: Run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5027
ERR_TOO_MANY_MON
Explanation: The monitor status block is already associated with another call.
Cause: The Call State routines were requested to create
a second monitor status block for a particular directory number,
but found that a second monitor status block already existed
for the directory number.
Action: No action is required.
This is an informational
system message and the situation is automatically corrected.
Module: CGEN
Severity: WARNING
5030
ERR_ASN1_DECODE_INVAL_REQ
Explanation: The decoder encountered an invalid request.
Cause: The decoder encountered a request that is not supported.
Action: See the reference manual for valid requests and
reissue the request. If the problem persists, run the
server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5031
ERR_ASN1_DECODE_BUF_OVFLW
Explanation: The decoder encountered a request that is too large.
Cause: The decoder encountered a request that is too big to parse.
Action: Verify that the format and parameters for the
request are valid and reissue the request. If the problem
persists, run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5032
ERR_ASN1_DECODE_BAD_TAG
Explanation: The decoder encountered a request with an invalid tag.
Cause: The decoder encountered a request with an invalid tag.
Action: Verify that the tags are valid and reissue the request.
If you supply valid information and the problem persists,
run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5033
ERR_ASN1_DECODE_INVAL_LNG
Explanation: The decoder encountered a field containing an invalid length.
Cause: The decoder encountered a request with an invalid field length.
Action: Verify that the field lengths are valid and reissue the
request. If you supply valid information and the problem persists,
run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5034
ERR_ASN1_DECODE_NOT_SUPP
Explanation: During validation the decoder encountered an invalid field.
Cause: The decoder encountered a request with an invalid field.
Action: Verify that the request contains valid fields and
reissue the request. If the problem persists,
run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5035
ERR_ASN1_DECODE_LENGTH
Explanation: The decoded encountered a request that was missing required fields.
Cause: The decoder encountered a request that did not contain
all the required fields for that request.
Action: Verify that the request contains all the required fields
and reissue the request. If the problem persists,
run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5036
ERR_ASN1_DEC_ENC_ERROR
Explanation: The decoder encountered an error and could not encode the response.
Cause: The decoder encountered a request with
an error and could not encode the proper response.
Action: Verify that your request is complete and
accurate and reissue the request. If the problem persists,
run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5050
ERR_GLO_INVALID_GET_PTR
Explanation: An invalid get pointer was detected on get message request.
Cause: The interface to the switch-independent part of
the server rejected a request to receive a message
from the switch-dependent part.
An invalid pointer was given as input.
Action: If this problem persists, the switch-dependent
part of the server needs to be checked.
Module: CGEN
Severity: WARNING
5051
ERR_GLO_SWM_REPORT_REQUIRED
Explanation: Switch Manager Report required.
Cause: The interface to the switch-independent part of
the server rejected a request to receive a message from
the switch-dependent part.
The switch-dependent part of
the server is required to send a Switch Manager Report first.
Action: If this problem persists, the switch-dependent
part of the server needs to be checked.
Module: CGEN
Severity: WARNING
5053
ERR_GLO_BUFFER_TOO_SMALL
Explanation: Buffer too small for message.
Cause: The interface to the switch-independent part of
the server rejected a request to receive a message
from the switch-dependent part.
The buffer assigned to hold the message is too small.
Action: If this problem persists, the switch-dependent
part of the server needs to be checked.
Module: CGEN
Severity: WARNING
5054
ERR_GLO_INVAL_GET_SERV_RC
Explanation: An invalid return code from GetServicePrimitive was detected.
Cause: The interface to the switch-independent part of
the server passed an invalid return code to the
switch-dependent part as a result of a receive request.
Action: If this problem persists, the switch-dependent
part of the server needs to be checked.
Module: CGEN
Severity: WARNING
5055
ERR_GLO_INVALID_SEND_PTR
Explanation: An invalid send pointer was detected.
Cause: The interface to the switch-independent part of
the server rejected a request to send a message
from the switch-dependent part.
An invalid pointer was given as input.
Action: If this problem persists, the switch-dependent
part of the server needs to be checked.
Module: CGEN
Severity: WARNING
5056
ERR_GLO_INVAL_SEND_SERV_RC
Explanation: An invalid return code from SendServicePrimitive was detected.
Cause: The interface to the switch-independent part of
the server passed an invalid return code to the
switch-dependent part as a result of a send request.
Action: If this problem persists, the switch-dependent
part of the server needs to be checked.
Module: CGEN
Severity: WARNING
5058
ERR_GLO_OPERATION_FAILED
Explanation: Either the get or send operation failed.
Cause: The interface to the switch-independent part
of the server rejected a request from
the switch-dependent part.
While processing the request,
the switch-independent part encountered an operation failure.
Action: If this problem persists, the switch-dependent
part of the server needs to be checked.
Module: CGEN
Severity: WARNING
5059
ERR_GLO_INVALID_CSP
Explanation: An invalid CallPath service primitive was detected.
Cause: The interface to the switch-independent part of
the server rejected a request from the switch-dependent
part.
While decoding the message, the switch-independent part
encountered an error.
Action: If this problem persists, the switch-dependent
part of the server needs to be checked.
Module: CGEN
Severity: WARNING
5060
ERR_INVALID_PTR
Explanation: An invalid pointer was passed to a function.
Cause: A Call State routine was passed a bad pointer.
This is an error in the switch-dependent part of the server.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: WARNING
5100
ERR_ACL_ACK_SYS_ERR_MC_RSP
Explanation: While processing a request, a switch system error was encountered.
Cause: The response indicates that the ROLM 9751 CBX
encountered a system error.
Action: Ensure that the ROLM 9751 CBX and its
outbound links are still functioning and retry the request.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5102
ERR_INVALID_STATE
Explanation: The parties involved in a call were found to be in invalid states.
Cause: The information in the server
database is not synchronized with the outbound portion
of CallBridge Link Manager handling the requests.
Action: If the problem persists, collect
the system message and trace data, then
ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5103
ERR_INVALID_STATE_EVENT
Explanation: The parties involved in a call were found to be in invalid states.
Cause: The information in the server
database is not synchronized with the incoming event.
Action: If the problem persists, collect
the system message and trace data, then
ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5104
ERR_UNEXPECTED_RC
Explanation: Unexpected return code %s detected in %s.
Cause: This is an internal software condition.
Action: If the problem persists, collect
the system message and trace data, then
ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5105
ERR_EVENT_PROGRAM_DATA
Explanation: Copy of program data to a %s event failed because %s.
Cause: The program data associated with a call could
not be retrieved.
Action: If the problem persists, collect
the system message and trace data, then
ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5110
ERR_ALP_EVENT_MSG_UNKN_RES_CD
Explanation: The switch sent an invalid notify event.
Cause: A notify event was received containing an invalid type.
This error indicates a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5120
ERR_ACL_INV_REF_IE_RRS_IE
Explanation: Invalid field was found where request tag field should exist.
Cause: While parsing the response, an invalid field was found
where the request tag field should exist. The response will not
be processed. This error indicates a possible corruption
of the data and messages.
Action: Check the outbound ROLM 9751 CBX links for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5121
ERR_ACL_INV_REF_IE_RS_IE
Explanation: An invalid field was found where the request tag field should be.
Cause: While parsing a reject response, an invalid field was
found where the request tag field should exist. The reject
response will not be processed, thereby resulting in an invalid call.
This error indicates a possible corruption of the data and messages.
Action: Check the outbound ROLM 9751 CBX links for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5122
ERR_ACL_INV_CHS_IE_RSS_IE
Explanation: While parsing the response, an invalid field was encountered.
Cause: While parsing the response, an invalid field was
encountered. The response will not be processed. This error
indicates a possible corruption of the data and messages.
Action: Check the outbound ROLM 9751 CBX links for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5123
ERR_ACL_INV_ACS_IE_ACR_IE
Explanation: An invalid field was encountered in a response.
Cause: While parsing an activation or deactivation response,
an invalid field was encountered. The activation or
deactivation response was not processed, thereby resulting
in the failure to activate or deactivate the ROLM 9751 CBX interface.
This error indicates a possible corruption of the data and messages.
Action: Check the outbound ROLM 9751 CBX links for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5124
ERR_ACL_UNK_MSG_RS_IE
Explanation: An invalid field was encountered in a Reject response.
Cause: While parsing a reject response, an invalid message
field type was encountered. The reject response will not
be processed, thereby resulting in an invalid call. This
error indicates a possible corruption of the data and messages.
Action: Check the outbound ROLM 9751 CBX links for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5125
ERR_ACL_ERR_CDE_IE_RS_IE
Explanation: An invalid field was encountered in a Reject response.
Cause: While parsing a reject response, an invalid error
code field was encountered. The reject response will not be
processed, thereby resulting in an invalid call. This error
indicates a possible corruption of the data and messages.
Action: Check the outbound ROLM 9751 CBX links for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5126
ERR_ACL_UNK_MSG_TYPE
Explanation: An invalid message type field was encountered in a response.
Cause: While parsing a response, an invalid message type
field was encountered. The response message will not be
processed, thereby resulting in an invalid call. This error
indicates a possible corruption of the data and messages.
Action: Check the outbound ROLM 9751 CBX links for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5127
ERR_ALP_UNK_MSG_FNCT
Explanation: An unknown or invalid function type field was encountered.
Cause: While parsing an event, an unknown or invalid function
type field was encountered. The event message will not be
processed, thereby resulting in an invalid call. This error
indicates a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5128
ERR_ALP_UNK_MSG_SUBFNCT
Explanation: An unknown or invalid sub-function type field was encountered.
Cause: While parsing an event, an unknown or invalid sub-function
type field was encountered. The event message will not be
processed, thereby resulting in an invalid call. This error
indicates a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5129
ERR_ALP_INV_PARTY1_NUM
Explanation: The first party field in an event was found to be invalid.
Cause: While parsing an event, the first party field was
found to be invalid. The event message will not be processed,
thereby resulting in an invalid call. This error indicates
a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5130
ERR_ALP_INV_PARTY2_NUM
Explanation: The second party field in an event was found to be invalid.
Cause: While parsing an event, the second party field was
found to be invalid. The event message will not be processed,
thereby resulting in an invalid call. This error indicates
a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5131
ERR_ALP_INV_PARTY3_NUM
Explanation: The third party field in an event was found to be invalid.
Cause: While parsing an event, the third party field was
found to be invalid. The event message will not be processed,
thereby resulting in an invalid call. This error indicates
a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5132
ERR_ALP_INV_PARTY4_NUM
Explanation: The fourth party field in an event was found to be invalid.
Cause: While parsing an event, the fourth party field was
found to be invalid.
The event message will not be processed,
thereby resulting in an invalid call. This error indicates
a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5133
ERR_ALP_INV_DNIS_NUM
Explanation: An invalid DNIS field in an event was encountered.
Cause: While parsing an event, an invalid DNIS field was
encountered. The event message will not be processed,
thereby resulting in an invalid call. This error
indicates a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5134
ERR_ALP_INV_DEST_NUM
Explanation: An invalid destination field in an event was encountered.
Cause: While parsing an event, an invalid destination
field was encountered. The event message will not be
processed, thereby resulting in an invalid call. This error
indicates a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5135
ERR_ALP_INV_ANI_NUM
Explanation: While parsing an event, an invalid ANI field was encountered.
Cause: While parsing an event, an invalid ANI field was
encountered. The event message will not be processed,
thereby resulting in an invalid call. This error indicates
a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5136
ERR_ALP_INV_SATOPS_NUM
Explanation: While parsing an event, an invalid SATOPS field was encountered.
Cause: While parsing an event, an invalid SATOPS field was
encountered. The event message will not be processed,
thereby resulting in an invalid call. This error
indicates a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5137
ERR_ALP_INV_EVENT_CTN_LEN
Explanation: While parsing an event, an invalid CTN field was encountered.
Cause: While parsing an event, an invalid called target
number field was encountered. The event message will not
be processed, thereby resulting in an invalid call. This
error indicates a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5138
ERR_ALP_INV_PARTY_TYPE
Explanation: While parsing an event, an invalid party type field
was encountered.
Cause: While parsing an event, an invalid party type field
was encountered. The event message will not be processed,
thereby resulting in an invalid call. This error indicates
a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5139
ERR_ALP_INV_ACCTCODE_NUM
Explanation: An invalid account code field was encountered in an event.
Cause: While parsing an event, an invalid account code field
was encountered. The event message will not be processed,
thereby resulting in an invalid call. This error indicates
a possible corruption of the data and messages.
Action: Check the inbound ROLM 9751 CBX link for possible errors.
If the problem persists, collect the system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: WARNING
5150
ERR_BAD_RC_ON_MAKECALL
Explanation: An invalid return code was received from a Make_Call request.
Cause: While processing a Make_Call request,
CallBridge Link Manager returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5151
ERR_BAD_RC_ON_SIGN_ON
Explanation: An invalid return code was received from a SIGN_ON request.
Cause: While processing a SIGN_ON request,
CallBridge Link Manager returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5152
ERR_BAD_RC_ON_SIGN_OFF
Explanation: An invalid return code was received from a SIGN_OFF request.
Cause: While processing a SIGN_OFF request,
CallBridge Link Manager returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5153
ERR_BAD_RC_ON_EVENT_ON
Explanation: An invalid return code was received from an EVENT_ON request.
Cause: While processing an EVENT_ON request,
CallBridge Link Manager returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5154
ERR_BAD_RC_ON_LOOPBACK
Explanation: An invalid return code was received from a LOOPBACK request.
Cause: While processing a LOOPBACK request,
CallBridge Link Manager returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5155
ERR_BAD_RC_ON_RECMD
Explanation: While receiving messages, an invalid return code was received.
Cause: While receiving a message, CallBridge Link Manager
returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5156
ERR_BAD_RC_ON_CONNECT
Explanation: Invalid return code while connecting to CallBridge Link Manager.
Cause: While connecting with CallBridge Link Manager,
an invalid return code was received.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5157
ERR_BAD_RC_ON_DISCONNECT_CALL
Explanation: An invalid return code was received for a Disconnect request.
Cause: While processing a Disconnect request,
CallBridge Link Manager returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5158
ERR_BAD_RC_ON_ANSWER_CALL
Explanation: An invalid return code was received for an Answer_Call request.
Cause: While processing an Answer_Call request,
CallBridge Link Manager returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5159
ERR_BAD_RC_ON_TRANSFER_CALL
Explanation: An invalid return code was received for a Transfer_Call request.
Cause: While processing a Transfer_Call request,
CallBridge Link Manager returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5160
ERR_BAD_RC_ON_ALTERNATE_CALL
Explanation: An invalid return code was received for an Alternate_Call request.
Cause: While processing an Alternate_Call request,
CallBridge Link Manager returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5161
ERR_BAD_RC_ON_EXTEND_CALL
Explanation: An invalid return code was received for an Extend_Call request.
Cause: While processing an Extend_Call request,
CallBridge Link Manager returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5162
ERR_BAD_RC_ON_INVOKE_FEAT
Explanation: An invalid return code was received for an Invoke_Feature request.
Cause: While processing an Invoke_Feature request,
CallBridge Link Manager returned an invalid return code.
The various return code possibilities are available within
the critical system messages.
Action: Identify the associated critical system message:
6135, 6136, 6140-6145, 6150-6160.
Module: SWITCH.EXE
Severity: WARNING
5900
ERR_OVERLOAD_ON_REQ
Explanation: A depletion of request tags has been encountered.
Cause: The applications are overrunning the ROLM 9751 CBX,
or there are possible errors with the outbound links to it.
Action: Wait for the message indicating that the request
tag shortage has been relieved to appear in the log.
If the overload condition does not clear up,
reset the outbound links and flow control the applications.
Module: SWITCH.EXE
Severity: WARNING
5901
ERR_OVERLOAD_ON_RSP
Explanation: Switch congestion has been encountered.
Cause: The applications are overrunning the ROLM 9751 CBX,
or there are possible errors with the outbound links to it.
Action: Wait for the message indicating that the
switch congestion has been relieved to appear in the log.
If the overload condition does not clear up,
reset the outbound links and flow control the applications.
Module: SWITCH.EXE
Severity: WARNING
5902
ERR_OVERLOAD_OFF_REQ
Explanation: The switch request tag shortage has been relieved.
Cause: The ROLM 9751 CBX overload condition has been relieved.
Action: The applications can resume processing
with the ROLM 9751 CBX.
Module: SWITCH.EXE
Severity: WARNING
5903
ERR_OVERLOAD_OFF_RSP
Explanation: The switch congestion has been relieved.
Cause: The ROLM 9751 CBX switch congestion has been relieved.
Action: The applications can resume processing
with the ROLM 9751 CBX.
Module: SWITCH.EXE
Severity: WARNING
6000
ERR_CRITICAL_PGM
Explanation: Critical program error type.
Module: SWITCH.EXE
Severity: SEVERE
6001
ERR_EXCEEDED_MAX_RCT
Explanation: The number of request tags is too large at initialization.
Cause: The switch-dependent part of the server requested
that more request tags be allocated than the Call State
database can handle.
Action: Run the server trace facility, then ask
your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6002
ERR_BAD_LINKAGE
Explanation: The linkage between parties cannot be determined.
Cause: The Call State routines detected a linkage between
parties that could not possibly occur, thereby indicating
the corruption of the server data space.
Action: Collect the system message, trace, and dump data,
then ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6003
ERR_NO_CCB
Explanation: There are no communication control blocks left to allocate.
Cause: The switch-dependent part of the server has tried to
allocate a communication control block and none are available.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6004
ERR_NO_PCB
Explanation: There are no party control blocks left to allocate.
Cause: The switch-dependent part of the server has tried to
allocate a party control block and none are available.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6005
ERR_BAD_COMMBUF_TYPE
Explanation: An incorrect type of communication buffer was encountered.
Cause: The switch-dependent part of the server has tried
to allocate a communication control block of unknown type,
thereby indicating the corruption of the server data space.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6006
ERR_BAD_LIST_TYPE
Explanation: An incorrect list type was encountered.
Cause: A Call State routine has tried to process
an unknown type of list in the database.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6007
ERR_BAD_ALLOC_PARM
Explanation: An incorrect parameter was passed to allocate a segment.
Cause: An incorrect parameter was passed to the operating
system while trying to obtain a segment of storage.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6008
ERR_NO_INUSE_CSB
Explanation: There are no call status blocks left to deallocate.
Cause: The Call State routines were requested to deallocate
a party.
While trying to obtain the party in the "in use" list,
the list was found empty. The Call State routines are
mismanaging the database or the server data space is corrupted.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6009
ERR_UNKNOWN_EVT
Explanation: An unknown event was encountered.
Cause: The Call State routines were requested to process
a monitor function for an event type that is unknown
to the Call State. The server data space is corrupted.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6010
ERR_BAD_THREAD_CREATION
Explanation: An error was encountered creating a thread.
Cause: While trying to create a thread for the switch-dependent
part of the server, an error was encountered by the operating
system.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6011
ERR_PARTY_LINKED_2CALL
Explanation: Party already linked in the call.
Cause: The Call State routines were requested to add
a party to a call.
While checking the party, it was found
that the party was already attached to a valid call and
could not be attached to the new call.
The Call State
routines are mismanaging the database or the server
data space is corrupted.
Module: CGEN
Severity: SEVERE
6012
ERR_NOT_SUB_TB_TRACE
Explanation: An invalid trace parameter was passed to the tool box.
Cause: The Call State routines were requested to report trace
information to the log. While evaluating the parameters, it was
found that one of the parameters was invalid or unknown.
Action: Verify that the parameters for the request are valid and
reissue the request. If the problem persists, collect the system
message, trace, and dump data, then ask your IBM Service
Representative to review the results.
Module: CGEN
Severity: SEVERE
6013
ERR_NOT_SUB_TB_LEVEL
Explanation: An invalid trace level was passed to the tool box.
Cause: The Call State routines were requested to report trace
information to the log. While evaluating the trace level, it was
found to be invalid or unknown.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6014
ERR_WRONG_MEM_PARM
Explanation: An invalid trace level was passed to the tool box.
Cause: The Call State routines were requested to report trace
information to the log. While evaluating the trace level, it was
found to be invalid or unknown.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6015
ERR_INVALID_DN_LENGTH
Explanation: An invalid directory number length was encountered.
Cause: The Call State routines were requested to find a particular
number in the database. While evaluating the directory number,
it was found that the length was invalid.
Action: Supply the correct directory number length and reissue
the request. If the problem persists, collect the system message,
trace, and dump data, then ask your IBM Service Representative to
review the results.
Module: CGEN
Severity: SEVERE
6016
ERR_BAD_SETSUB_PARM
Explanation: An invalid parameter was passed to setsubmemory.
Cause: While trying to request the operating system to partition
storage into sub-units, an invalid parameter was passed to the
routine to partition the storage.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6017
ERR_INVALID_CID_PTR
Explanation: An invalid pointer was passed to the connection ID hash table.
Cause: The Call State routines were requested to find a particular
connection ID in the database. While processing, it was found that
the pointer to the connection ID field was invalid.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6018
ERR_INVALID_DN_PTR
Explanation: An invalid pointer was passed to the directory number hash table.
Cause: The Call State routines were requested to find a particular
directory number in the database. While processing, it was found
that the pointer to the directory number field was invalid.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6019
ERR_INVALID_CALLID_PTR
Explanation: An invalid pointer was passed to the call ID hash table.
Cause: The Call State routines were requested to find
a particular call ID in the database. While processing,
it was found that the pointer to the call ID field was invalid.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6020
ERR_NULL_PCB_PTR
Explanation: The system attempted to put a null pointer on the stack.
Cause: An attempt was made by the switch-dependent part
of the server to put an invalid communication buffer
(null pointer) back to the pool of communication buffers.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6021
ERR_UNK_REQUEST
Explanation: An invalid type of request was encountered by the Call State Routines.
Cause: The Call State routines were requested to process a request
that was determined to be invalid. The switch-dependent part of
the server is corrupted.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6022
ERR_BAD_LIST_LOCATION
Explanation: A control block was found in an incorrect location in a linked list.
Cause: The Call State routines were requested to insert
or delete a control block from a certain position in a list.
The position was found to be invalid. The switch-dependent
part of the server data space is corrupted.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6023
ERR_BAD_RESOURCE_TYPE
Explanation: An invalid resource type was encountered by the Call State Routines.
Cause: The Call State routines were requested to process a certain
type of resource control block. The type of resource was found to be
invalid. The switch-dependent part of the server data space is
corrupted.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6024
ERR_BAD_EVENT_TYPE
Explanation: An invalid type of event was encountered by the Call State routines.
Cause: The Call State routines were requested to process a given
event. This event was determined to be invalid. The
switch-dependent part of the server data space is corrupted.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6025
ERR_NO_GROUPID_MSB
Explanation: There is no monitor status block for the group identifier.
Cause: The Call State routines were requested to process
a given group identifier. There is no monitor status block
for the group identifier. The switch-dependent part
of the server data space is corrupted.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6026
ERR_PUT_TOO_MANY_PCB
Explanation: Too many party control blocks were returned to the queue.
Cause: The Call State routines were requested to put back a Party Control
Block that was either never taken off the party control block queue,
or was already put back to the party control block queue.
There is an error in the switch-dependent part of the server.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6027
ERR_PUT_TOO_MANY_CCB
Explanation: Too many party control blocks were returned to the queue.
Cause: The Call State routines were requested to put back a Party Control
Block that was either never taken off the party control block queue,
or was already put back to the party control block queue.
There is an error in the switch-dependent part of the server.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6028
ERR_BAD_CRITICAL_ERR_NUM
Explanation: A noncritical error was passed to the critical error processing routine.
Cause: A Call State routine that handles only critical errors
was passed a noncritical error.
This is an error in the
switch-dependent part of the server.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6052
ERR_GLO_NO_CSP
Explanation: No CallPathServices primitive available for receiving a message.
Cause: The interface to the switch-independent part of
the server rejected a request to receive a message
from the switch-dependent part.
There was no CallPathServices
primitive available for processing at the time.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6070
ERR_GLO_ASN1_ENCODE_INVAL_REQ
Explanation: The encoder detected an invalid event message.
Cause: The switch-dependent part of the server
passed an invalid event message to the encoder.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review
the results.
Module: CGEN
Severity: SEVERE
6071
ERR_GLO_ASN1_ENCODE_BUF_OFLW
Explanation: The encoder detected a buffer overflow.
Cause: The switch-dependent part of the server
passed an output buffer with an invalid size to the encoder.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6072
ERR_GLO_ASN1_ENCODE_INVAL_FLD
Explanation: The encoder detected an invalid field.
Cause: While trying to encode an event, the encoder
detected an invalid field in the table.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6073
ERR_GLO_ASN1_ENCODE_INV_FLDLEN
Explanation: The encoder detected a field containing an invalid length.
Cause: While encoding an event message, the encoder detected
a field that was larger than the encoding table allows.
Action: Verify that all field lengths are valid and
reissue the request. If the problem persists,
collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6074
ERR_INVAL_ASN1_ENC_DEC_RC
Explanation: The encoder or decoder encountered an invalid return code.
Cause: The encoder or decoder passed an invalid return
code to the switch-dependent part of the server.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6075
ERR_INV_REP_FUNC_TYPE
Explanation: An invalid report type was encountered.
Cause: The switch-dependent part of the server
passed an invalid report type to the Report function.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6076
ERR_OS2_SEM_CREATE
Explanation: A semaphore was not created.
Cause: The operating system returned an error when a request
to create a semaphore was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review
the results.
Module: CGEN
Severity: SEVERE
6077
ERR_OS2_QUE_CREATE
Explanation: A queue was not created.
Cause: The operating system returned an error when a request
to create a queue was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6078
ERR_OS2_SUSPEND_SLEEP
Explanation: A bad suspend was encountered with DosSleep.
Cause: The operating system returned an error when a request
to suspend the current thread for an amount of time was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6079
ERR_OS2_SUSPEND_WAIT
Explanation: A bad suspend was encountered with DosWait.
Cause: The operating system returned an error when a request
to suspend the current thread based on a semaphore was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6080
ERR_OS2_LOCK
Explanation: The semaphore was not locked.
Cause: The operating system returned an error when a request
to lock a semaphore was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6081
ERR_OS2_UNLOCK
Explanation: The semaphore was not unlocked.
Cause: The operating system returned an error when a request
to unlock a semaphore was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6082
ERR_OS2_HUGE_SHIFT
Explanation: The huge section of memory was not shifted.
Cause: The operating system returned an error when a request
to provide the shift for a huge section of storage was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6083
ERR_OS2_HUGE_ALLOC
Explanation: The huge section of memory was not allocated.
Cause: The operating system returned an error when a request
to allocate a huge section of storage was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6084
ERR_OS2_NORM_ALLOC
Explanation: The section of storage was not allocated.
Cause: The operating system returned an error when a request
to allocate a section of storage was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6085
ERR_OS2_DEALLOC
Explanation: The section of storage was not deallocated.
Cause: The operating system returned an error when a request
to deallocate a section of storage was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6086
ERR_OS2_START_TIMER
Explanation: The Start Timer operation was unsuccessful.
Cause: The operating system returned an error when a request
to start a timer was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6087
ERR_OS2_TERM_ROUTINE
Explanation: The termination routine was not initialized.
Cause: The operating system returned an error when a request
to initialize the proper termination routine was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6088
ERR_OS2_SUB_SET
Explanation: The storage was not partitioned.
Cause: The operating system returned an error when a request
to partition storage into sub-units was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6089
ERR_OS2_SUB_ALLOC
Explanation: The storage was not suballocated.
Cause: The operating system returned an error when a request
to suballocate a section of storage was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6090
ERR_OS2_ENTER_CRIT_PATH
Explanation: The entering of critical path was unsuccessful.
Cause: The operating system returned an error when a request
to enter a critical section in the process was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6091
ERR_OS2_EXIT_CRIT_PATH
Explanation: The exiting of critical path was unsuccessful.
Cause: The operating system returned an error when a request
to exit a critical section in the process was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6092
ERR_OS2_CLOSE_Q
Explanation: The queue was not closed.
Cause: The operating system returned an error when a request
to close a queue was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6093
ERR_OS2_READ_Q
Explanation: The queue was not read.
Cause: The operating system returned an error when a request
to read from a queue was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6094
ERR_OS2_WRITE_Q
Explanation: The queue was not written to.
Cause: The operating system returned an error when a request
to write to a queue was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6095
ERR_OS2_QUERY_Q
Explanation: The queue was not queried.
Cause: The operating system returned an error when a request
to query a queue was received.
The return code from the request is in the OS/2 system message.
Action: Collect the system message, trace, and dump data, then
ask your IBM Service Representative to review the results.
Module: CGEN
Severity: SEVERE
6100
ERR_INI_INV_NUM_SUCCESSES
Explanation: Initialization detected an error in the configuration file.
Cause: While reading the configuration file,
invalid data was encountered.
Action: Collect the system message data and the configuration file,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6101
ERR_INI_UNABLE_OPEN_CONF_FILE
Explanation: Initialization was unable to open the configuration file.
Action: Ensure that the configuration file (KB9751.CFG)
is in the C:\CPSS2\DATA directory. If it does not exist,
reinstall the software. If reinstallations does not
resolve the problem, collect the system message data
and the configuration file, then ask your IBM service
representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6102
ERR_INI_READING_LINE_CONFIG
Explanation: The reading of the configuration file failed.
Cause: Initialization detected an error while reading a
record from the configuration file.
Action: Collect the system message data and the configuration
file, then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6103
ERR_COM_INV_SENDACLR_MSG_TYPE
Explanation: An invalid message was sent to the outbound
CallBridge Link Manager.
Cause: An invalid message type was passed to the routine which
sends messages to the outbound portion of CallBridge Link Manager.
This error only occurs if the routine is NOT used
properly or the thread's stack space is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6104
ERR_COM_INV_SENDALP_MSG_TYPE
Explanation: An invalid message was sent to the inbound CallBridge Link Manager.
Cause: An invalid message type was passed to the routine which
sends messages to the inbound portion of CallBridge Link Manager.
This error only occurs if the routine is NOT used
properly or the thread's stack space is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6105
ERR_COM_INV_ENCACLR_MSG_TYPE
Explanation: An invalid message was sent to the outbound
CallBridge Link Manager.
Cause: An invalid message type was passed to the routine which
builds messages for the outbound portion of CallBridge Link Manager.
This error only occurs if the routine is NOT used
properly or the thread's stack space is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6106
ERR_COM_INV_ENCALP_MSG_TYPE
Explanation: An invalid message was sent to the inbound CallBridge Link Manager.
Cause: An invalid message type was passed to the routine which
builds messages for the inbound portion of CallBridge Link Manager.
This error only occurs if the routine is NOT used
properly or the thread's stack space is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6116
ERR_DSC_BAD_HCI_DISC
Explanation: For a disconnect event, an invalid event type was passed.
Cause: While processing a disconnect event from
the ROLM 9751 CBX, a non-supported disconnect switch
event type was encountered. This error
only occurs if the communication buffer is corrupted
or the ROLM 9751 CBX communication link is inactive.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6117
ERR_REJ_BAD_CID_STATE
Explanation: For a rejected event, the parties were in invalid states.
Cause: While processing a rejected event from the
ROLM 9751 CBX, a non-supported state was encountered
for one of the parties in the call. This error only occurs
if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6118
ERR_BAD_ALT_STATE
Explanation: For an alerting event, the parties were in invalid states.
Cause: While processing an alert event from the
ROLM 9751 CBX, a non-supported state was encountered
for one of the parties in the call. This error
only occurs if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6119
ERR_BAD_HELD_STATE
Explanation: For a held event, the parties were in invalid states.
Cause: While processing a held event from the
ROLM 9751 CBX, a non-supported state was encountered
for one of the parties in the call. This error
only occurs if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6120
ERR_BAD_CNCT_STATE
Explanation: For a connected event, the parties were in invalid states.
Cause: While processing a connected event from the
ROLM 9751 CBX, a non-supported state was encountered
for one of the parties in the call. This error
only occurs if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6121
ERR_BAD_PARK_STATE
Explanation: For a parked event, the parties were in invalid states.
Cause: While processing a parked event from the
ROLM 9751 CBX, a non-supported state was encountered
for one of the parties in the call. This error
only occurs if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6122
ERR_BAD_PICK_STATE
Explanation: For a picked event, the parties were in invalid states.
Cause: While processing a picked event from the
ROLM 9751 CBX, a non-supported state was encountered
for one of the parties in the call. This error
only occurs if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6124
ERR_BAD_XFER_STATE
Explanation: For a transferred event, the parties were in invalid states.
Cause: While processing a transferred event from the
ROLM 9751 CBX, a non-supported state was encountered
for one of the parties in the call. This error only
occurs if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6125
ERR_CONF_TRANSITION
Explanation: Invalid relationship between parties in a conference event.
Cause: While processing a conference event from the
ROLM 9751 CBX, an invalid relationship between the
parties was encountered. This error only occurs
if the given thread's stack space is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6126
ERR_BAD_REDIR_STATE
Explanation: For a routed event, the parties were in invalid states.
Cause: While processing a routed event from the
ROLM 9751 CBX, a non-supported state was encountered
for one of the parties in the call. This error
only occurs if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6127
ERR_BAD_FOUND_FLAG
Explanation: Invalid relationship between the parties in a routed event.
Cause: While processing a routed event from the
ROLM 9751 CBX, an invalid relationship between the
parties was encountered. This error only occurs
if the given thread's stack space is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6128
ERR_RPCCC_INVALID_STATE
Explanation: While trying to remove a party from a call, the party was found
to be in an invalid state.
Cause: While attempting to remove a party for the call, a
non-supported state was encountered for the party. This error
only occurs if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6129
ERR_QPS_INVALID_STATE
Explanation: The party in a Query_Party_Status request is in an invalid state.
Cause: While processing a Query_Party_Status request,
a non-supported state was encountered for the party.
This error only occurs if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data, then
ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6130
ERR_CNFH_STATE
Explanation: The parties in the held call of a conference call
are in invalid states.
Cause: While processing a held event for a conferenced event, a
non-supported state was encountered for one of the parties in the call.
This error only occurs if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data, then
ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6131
ERR_XFER_TRANSITION
Explanation: The parties in a transferred event were in an invalid state.
Cause: While processing a transferred event from the ROLM 9751 CBX,
an invalid relationship between the parties was encountered.
This error only occurs if the given thread's stack space is corrupted.
Action: Collect the system message, trace, and dump data, then
ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6132
ERR_INVALID_RELATIONSHIP
Explanation: The parties in a call are in an invalid state.
Cause: While processing an agent from the ROLM 9751 CBX, an invalid
relationship between the parties was encountered. This error
only occurs if the Call State database is corrupted.
Action: Collect the system message, trace, and dump data, then
ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6135
ERR_ACL_INV_RC
Explanation: Invalid return code from outbound CallBridge Link Manager.
Cause: While processing a message, the outbound portion of
CallBridge Link Manager returned an invalid return code.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6136
ERR_ALP_INV_RC
Explanation: Invalid return code from inbound CallBridge Link Manager.
Cause: While processing a message, the inbound portion
of CallBridge Link Manager returned an invalid return code.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6140
ERR_ACL_INVALID_HANDLE
Explanation: Invalid handle from outbound CallBridge Link Manager on API call.
Cause: The outbound portion of CallBridge Link Manager detected
that an invalid handle was passed on an API call.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6141
ERR_ACL_NO_DATA_RECEIVED
Explanation: Data buffer space was unavailable for processing the API call.
Cause: The outbound portion of CallBridge Link Manager detected
that the data buffer space was unavailable for processing
the API call.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6142
ERR_ACL_MSG_TOO_BIG
Explanation: Message too large for the data buffer space.
Cause: The outbound portion of CallBridge Link Manager
detected that a message was received that will not fit
into the data buffer space supplied by the API call.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6143
ERR_ACL_SYSTEM_IPC_FAILED
Explanation: Communication failure detected by CallBridge Link Manager.
Cause: While processing an API call, the outbound portion
of CallBridge Link Manager encountered an inter-process
communication failure. Check the CallBridge Link Manager.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6144
ERR_ACL_START_ROLM_FAILED
Explanation: Error while loading or initializing CallBridge Link Manager.
Cause: While loading and initializing CallBridge Link Manager,
the outbound portion of CallBridge Link Manager encountered
an error. Check CallBridge Link Manager.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6145
ERR_ACL_START_ACC_FAILED
Explanation: Error from CallBridge Link Manager during outbound communication.
Cause: While starting outbound communication with
the ROLM 9751 CBX, the outbound portion of CallBridge Link Manager
encountered an error. Check CallBridge Link Manager.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6150
ERR_ALP_PI_ERROR
Explanation: Indeterminate error from inbound CallBridge Link Manager.
Cause: While processing an API call, the inbound portion
of CallBridge Link Manager detected an indeterminable error.
Check CallBridge Link Manager.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6151
ERR_ALP_PI_LINK_DOWN
Explanation: Inactive communication link to inbound CallBridge Link Manager.
Cause: While processing an API call, the inbound portion
of CallBridge Link Manager detected that the communication
link was inactive.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6152
ERR_ALP_PI_RESOURCE_BUSY
Explanation: Resource busy condition from inbound CallBridge Link Manager.
Cause: While processing an API call, the inbound portion
of CallBridge Link Manager encountered a permanent
resource busy condition.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6153
ERR_ALP_PI_RESOURCE_FATAL
Explanation: Invalid resource condition from inbound CallBridge Link Manager.
Cause: While processing an API call, the inbound portion of
CallBridge Link Manager encountered an invalid resource condition.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6154
ERR_ALP_PI_REQ_FAILED
Explanation: Internal error from inbound CallBridge Link Manager.
Cause: While processing an API call, the inbound portion
of CallBridge Link Manager encountered an internal error.
Check CallBridge Link Manager.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6155
ERR_ALP_PI_BAD_PARM
Explanation: Invalid parameter from inbound CallBridge Link Manager.
Cause: While processing an API call, the inbound portion
of CallBridge Link Manager detected that an invalid
parameter was passed.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6156
ERR_ALP_PI_CNFG_FILE
Explanation: Inbound CallBridge Link Manager found no configuration file.
Cause: The inbound portion of CallBridge Link Manager
detected that the configuration file does not exist.
Action: Ensure that the configuration file (KB9751.CFG) is
in the C:\CPSS2\DATA directory. If it does not exist;
reinstall the server.
Module: SWITCH.EXE
Severity: SEVERE
6157
ERR_ALP_PI_BAD_CNFG
Explanation: The configuration file contains invalid values.
Cause: The inbound portion of CallBridge Link Manager
detected invalid values while reading the configuration file.
Action: Collect the system message data, CallBridge Link Manager
system message data, and the configuration file,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6158
ERR_ALP_PI_PORT_CLOSED
Explanation: Inbound port (link) is closed.
Cause: While trying to execute a request from the switch-dependent
part of the server, the CallBridge Link Manager
discovered that the inbound port (link) is closed.
Action: Collect the system message, trace and dump data,
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6159
ERR_ALP_PI_PORT_UNCNFG
Explanation: Inbound port (link) is not configured.
Cause: The CallBridge Link Manager was requested to perform
some type of action. While evaluating the port's value, it was
found that it is no longer configured.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6160
ERR_ALP_PI_PORT_OPEN
Explanation: Inbound port (link) was already opened.
Cause: The CallBridge Link Manager was requested
to perform some type of action. While evaluating
the port's status, it was found that it is already active.
Action: Collect the system message, trace, and dump data
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
6161
ERR_UNABLE_TO_RESTART_LINKS
Explanation: The ROLM 9751 CBX links could not be reactivated.
Cause: The ROLM 9751 CBX links are not active.
Check the ROLM 9751 CBX CallBridge Link Manager.
Action: Collect the system message, trace, and dump data,
and the CallBridge Link Manager system message and trace data,
then ask your IBM service representative to review the results.
Module: SWITCH.EXE
Severity: SEVERE
In the following messages, the percent sign (%) indicates
variable data, which can range from 1 to 20 characters in length.
6268
ERR_ROLM_2100
Explanation: System Log Manager version %s installed.
Cause: The System Log Manager is installed.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: INFORMATIONAL
6269
ERR_ROLM_2169
Explanation: Number of RICs installed less than configured.
Cause: The number of the RICs is less than that configured.
Action: Correct the configuration file to reflect what
is actually installed and restart the system. If the problem
persists, call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: INFORMATIONAL
6272
ERR_ROLM_2104
Explanation: System Log Manager exiting.
Cause: The System Log Manager is exiting.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: INFORMATIONAL
6274
ERR_ROLM_2150
Explanation: System Control Task version %s installed.
Cause: System Control Task version %s is installed.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: INFORMATIONAL
6275
ERR_ROLM_2170
Explanation: System Control Task Exiting.
Cause: One of the processes is ending normally for shutdown.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: INFORMATIONAL
6276
ERR_ROLM_2171
Explanation: System Control Task Exiting - error %s.
Cause: There is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Service Center for assistance.
Module: SWITCH.EXE
Severity: INFORMATIONAL
6280
ERR_ROLM_5000
Explanation: ACL Filter version %s installed.
Cause: The application connectivity link filter is installed.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: INFORMATIONAL
6281
ERR_ROLM_5001
Explanation: ACL Filter program exiting.
Cause: The application connectivity link filter program is exiting.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: INFORMATIONAL
6295
ERR_ROLM_5070
Explanation: Dialer Manager version %s started RIC %s Port %s.
Cause: The Dialer Manager has started on RIC/Port %s successfully.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: INFORMATIONAL
6296
ERR_ROLM_5071
Explanation: Dialer Manager initialized on RIC %s Port %s.
Cause: The Dialer Manager has initialized
on RIC/Port %s successfully.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: INFORMATIONAL
6300
ERR_ROLM_5171
Explanation: Control link manager shut down. Code=%s.
Cause: This is the message that is logged
when the control link process ends.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: WARNING
6304
ERR_ROLM_5200
Explanation: Link Driver version %s installed RIC %s.
Cause: The Control Link Driver version %s
was successfully installed on RIC/Port %s.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: WARNING
6305
ERR_ROLM_5250
Explanation: Resource Manager version %s installed.
Cause: The Resource Manager is installed.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: WARNING
6306
ERR_ROLM_5253
Explanation: Resource Manager shut down.
Cause: The Resource Manager is now inactive.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: WARNING
6307
ERR_ROLM_5261
Explanation: Resource Manager successfully initialized.
Cause: The Resource Manager has initialized successfully.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: WARNING
6310
ERR_ROLM_5305
Explanation: All links active. %s active %s config.
Cause: All configured ports are active.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: WARNING
6311
ERR_ROLM_5306
Explanation: Control link active RIC %s Port %s.
Cause: The link that was inactive is now active.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: WARNING
6330
ERR_ROLM_4000
Explanation: ROLM Error 4000
Cause: The event link communication (sender or receiver)
task is now active.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: WARNING
6331
ERR_ROLM_4002
Explanation: Event link error handler is activated.
Cause: The event link error handler is activated.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: WARNING
6332
ERR_ROLM_4003
Explanation: Event link trace handler is activated.
Cause: The event link trace handler is activated.
Action: This system message is strictly informational.
Module: SWITCH.EXE
Severity: WARNING
6333
ERR_ROLM_4022
Explanation: Event link bad parameter.
Cause: This is an internal software error condition.
Action: Check previous messages. If the problem persists,
call the ROLM Customer Service Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6350
ERR_ROLM_SPARE
Explanation: ROLM message error number: %s.
Cause: This is an unknown error reported by CallBridge Link Manager.
Action: Check previous messages. If the problem persists,
call the ROLM Customer Service Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6400
ERR_SWITCH_ACTIVATION_FAILED
Explanation: Inoperable CallBridge Link Manager during SIGN_ON.
Cause: The switch-dependent part of the server
did not receive any responses to the SIGN_ON requests
within the allocated time period.
Action: Check CallBridge Link Manager and the communication
links (both inbound and outbound) and reactivate
the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6401
ERR_ACL_INV_ACKCODE_IE_SIGNON
Explanation: An invalid acknowledge code field was found in a SIGN_ON message.
Cause: CallBridge Link Manager was requested to perform
SIGN_ON requests. The switch-dependent part of
the server received a response from the outbound
portion of CallBridge Link Manager with an invalid field.
Action: Check CallBridge Link Manager and the outbound
communication link and reactivate the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6405
ERR_SWITCH_DEACTIVATION_FAILED
Explanation: Inoperable CallBridge Link Manager found during SIGN_OFF.
Cause: CallBridge Link Manager was requested to perform
SIGN_OFF requests. The switch-dependent part of the server
did not receive any responses
to the SIGN_OFF requests within the allotted time period.
Action: Check CallBridge Link Manager and the communication links
(both inbound and outbound) and reactivate the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6406
ERR_ACL_INV_ACKCODE_IE_SIGNOFF
Explanation: An invalid acknowledge code field was found in a SIGN_OFF message.
Cause: CallBridge Link Manager was requested to perform
SIGN_OFF requests. The switch-dependent part
of the server did not receive any responses
to the SIGN_OFF requests within the allotted time period.
Action: Check CallBridge Link Manager and the communication links
(both inbound and outbound) and reactivate the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6410
ERR_ALP_EVENT_MSG_LOST
Explanation: Error with one of the nodes. Resetting the node.
Cause: The ROLM 9751 CBX has reported that one
of its nodes has an error or it is resetting the node.
This system message could result in the loss of
messages to the attached host computer applications.
Action: If the problem persists, follow the problem
determination procedures in your ROLM documentation.
Module: SWITCH.EXE
Severity: WARNING
6411
ERR_ALP_SWBUFSPACE_OVRUN
Explanation: Transmit buffer has overrun its buffer space.
Cause: The ROLM 9751 CBX has reported that it has overrun
its transmit buffer space for sending messages
to the server. This system message could result
in the loss of events to the attached host computer applications.
Action: Check CallBridge Link Manager, inbound communication link,
and the switch-dependent part of the server for errors.
Module: SWITCH.EXE
Severity: WARNING
6412
ERR_ALP_MSG_STREAM_STOP
Explanation: The switch has stopped the event stream due to an internal error.
Cause: The ROLM 9751 CBX has reported that the event stream
has stopped due to an internal error.
Action: There is a problem with the ROLM 9751 CBX. Follow
the problem determination procedures in your ROLM documentation.
When this system message occurs, the switch-dependent part
of the server resets itself internally.
Module: SWITCH.EXE
Severity: WARNING
6416
ERR_ACL_INV_TESTDATA_IE_LPBK
Explanation: An invalid test data field was found in a LOOPBACK message.
Cause: CallBridge Link Manager was requested to perform
LOOPBACK requests. The switch-dependent part of
the server received a response from the outbound portion
of CallBridge Link Manager with an invalid test data field type.
Action: Check CallBridge Link Manager and the communication link
(outbound) and reactivate the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6417
ERR_ACL_INV_TESTDATA_RECD_LPBK
Explanation: Invalid test data was found in a LOOPBACK message.
Cause: CallBridge Link Manager was requested to perform
LOOPBACK requests. The switch-dependent part of
the server received a response from the outbound portion
of CallBridge Link Manager with an invalid test data field type.
Action: Check CallBridge Link Manager and the communication link
(outbound) and reactivate the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6420
ERR_LINK_DOWN
Explanation: Links to the switch are inactive.
Cause: CallBridge Link Manager was requested to perform
LOOPBACK requests. The switch-dependent part of
the server did not receive any responses to the
LOOPBACK requests within the allotted time period.
Action: Check CallBridge Link Manager and the communication links
(both inbound and outbound) and reactivate the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6421
ERR_ALP_SWITCH_INACTIVE
Explanation: The switch inbound link is now inactive.
Cause: The ROLM 9751 CBX has reported that
the inbound link is now inactive.
Action: Check the inbound communication link
and reactivate the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6422
ERR_RMA_NEGATIVE
Explanation: Negative response to outbound activation or deactivation request.
Cause: The outbound portion of CallBridge Link Manager was
requested to perform either an activation or deactivation
request. The switch-dependent part of the server
received a negative response to the request.
Action: Check the outbound communication link and
reactivate the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6423
ERR_RMA_SYSTEM_ERROR
Explanation: Switch encountered a system error.
Cause: The outbound portion of CallBridge Link Manager
was requested to perform either an activation or deactivation
request. The switch-dependent part of the server
received a negative response to the request indicating
that the ROLM 9751 CBX encountered a system error.
Action: Reactivate the outbound communication link.
Module: SWITCH.EXE
Severity: WARNING
6424
ERR_RMA_OTHER_COM_ALSO_ACTIVE
Explanation: Another command is already active.
Cause: The outbound portion of CallBridge Link Manager was
requested to perform either an activation or deactivation
request. The switch-dependent part of the server
received a negative response to the request indicating the
ROLM 9751 CBX link is already active.
Action: Deactivate the ROLM 9751 CBX link and reactivate it.
Module: SWITCH.EXE
Severity: WARNING
6425
ERR_RMA_EVENT_STREAM_DISABLED
Explanation: Event stream is disabled.
Cause: The outbound portion of CallBridge Link Manager was
requested to perform either an activation or deactivation
request. The switch-dependent part of the server
received a negative response to the request indicating that
the event stream is disabled.
Action: Deactivate the ROLM 9751 CBX link and reactivate it.
Module: SWITCH.EXE
Severity: WARNING
6426
ERR_RMA_SIGN_ON_NO_EVT_STREAM
Explanation: Event stream was not enabled, but activation was successful.
Cause: The outbound portion of CallBridge Link Manager was
requested to perform an activation request. The switch-dependent
part of the server received a negative response
to the request indicating that the
activation was successful but the event stream was not enabled.
Action: Deactivate the ROLM 9751 CBX link and reactivate it.
Module: SWITCH.EXE
Severity: WARNING
6427
ERR_RMA_INCOMPAT_ACL_VERSION
Explanation: Switch is incompatible with the server.
Cause: The version of the ROLM 9751 CBX
is incompatible with this version of the server.
Action: Check the ROLM 9751 CBX version of the software and the
outbound version specified in the configuration file
(C:\GATEWAY\DATA\KB9751.CFG). Check file for corruption.
Deactivate the ROLM 9751 CBX link and reactivate it.
Module: SWITCH.EXE
Severity: WARNING
6428
ERR_ALP_SIGNON_REJECTED
Explanation: A negative response was returned for the inbound SIGN_ON request.
Cause: The inbound portion of CallBridge Link Manager was
requested to perform a SIGN_ON request. The switch-dependent
part of the server received a negative response
to the request.
Action: Check the inbound communication link
and reactivate the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6430
ERR_ALP_SIGNON_MSG_STRM_STOPPED
Explanation: Event stream is not enabled.
Cause: SIGN_ON request resulted in a negative response
to the request indicating that the activation was successful
but the event stream was not enabled.
Action: Check the inbound communication link.
Deactivate the ROLM 9751 CBX link and reactivate it.
Module: SWITCH.EXE
Severity: WARNING
6431
ERR_ALP_SIGNON_VERSION_MISMATCH
Explanation: Version of switch is incompatible with the server.
Cause: Result of SIGN_ON request indicates incompatible
versions of ROLM 9751 CBX and the server.
Action: Check the ROLM 9751 CBX version of the software and the
inbound version specified in the configuration file
(C:\CPSS2\DATA\KB9751.CFG). Check the file for corruption.
Deactivate the ROLM 9751 CBX link and reactivate it.
Module: SWITCH.EXE
Severity: WARNING
6432
ERR_ALP_SIGNOFF_REJECTED
Explanation: A negative response was returned for the inbound SIGN_OFF request.
Cause: The inbound portion of CallBridge Link Manager was
requested to perform a SIGN_OFF request.
The switch-dependent part of the server
received a negative response to the request.
Action: Check the inbound communication link
and reactivate the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6433
ERR_ALP_EVENTON_REJECTED
Explanation: A negative response was returned for the inbound EVENT_ON request.
Cause: The inbound portion of CallBridge Link Manager
was requested to perform an EVENT_ON request.
The switch-dependent part of the server
received a negative response to the request.
Action: Check the inbound communication link
and reactivate the ROLM 9751 CBX link.
Module: SWITCH.EXE
Severity: WARNING
6435
ERR_ROLM_2151
Explanation: Could not read RIC Input Buffer.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6436
ERR_ROLM_2152
Explanation: Could not issue command to RIC
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6437
ERR_ROLM_2153
Explanation: RIC task not initialized.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6438
ERR_ROLM_2154
Explanation: Could not read primary status.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6439
ERR_ROLM_2155
Explanation: Could not set RIC semaphore.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6440
ERR_ROLM_2156
Explanation: Could not register RIC semaphore.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6441
ERR_ROLM_2157
Explanation: Could not create RIC semaphore.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6442
ERR_ROLM_2158
Explanation: Could not create SU-MSG-READER thread.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6443
ERR_ROLM_2159
Explanation: Could not allocate stack space.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6444
ERR_ROLM_2160
Explanation: Could not open device driver.
Cause: The device driver may not have been loaded.
Action: Check and make sure that CONFIG.SYS has
the statement DEVICE=C:\GATEWAY\SWITCH\ICARICIO.SYS.
Restart the system. If the problem persists, call
the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6445
ERR_ROLM_2161
Explanation: Could not load System Tasks on RIC.
Cause: One or more RIC executable files are missing.
Action: Reinstall the ROLM distribution diskette.
Restart the system. If the problem persists, call
the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6446
ERR_ROLM_2162
Explanation: No RIC cards configured.
Cause: No RIC card is configured.
Action: Correct the configuration and restart the system.
If the problem persists, call the ROLM
Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6447
ERR_ROLM_2163
Explanation: Could not read configuration file.
Cause: Either the configuration file is missing
or there is an internal software error.
Action: Make sure the configuration file exists
and restart the system. If the problem persists, call
the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6448
ERR_ROLM_2164
Explanation: Could not read mailbox information file.
Cause: Either the mailbox information file is missing
or there is an internal software error.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6449
ERR_ROLM_2165
Explanation: Could not allocate named memory segment.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6450
ERR_ROLM_2166
Explanation: Operating system error while setting semaphore.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6451
ERR_ROLM_2167
Explanation: Operating system error while creating semaphore.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6452
ERR_ROLM_2168
Explanation: Internal error - RIC index not found.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6453
ERR_ROLM_2175
Explanation: Error - System Tasks already exists.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6483
ERR_ROLM_5002
Explanation: Error opening System Mailbox: %s.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6484
ERR_ROLM_5003
Explanation: Error initializing mailboxes.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6485
ERR_ROLM_5004
Explanation: Error creating semaphore for mailbox.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6486
ERR_ROLM_5005
Explanation: Error creating semaphore for timer.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6487
ERR_ROLM_5006
Explanation: Error creating System Mailbox: %s.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6488
ERR_ROLM_5007
Explanation: Message received prior to CONNECT request.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6489
ERR_ROLM_5008
Explanation: Request contains an invalid handle.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6490
ERR_ROLM_5009
Explanation: Error: Invalid request.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6491
ERR_ROLM_5010
Explanation: Length of request invalid (too large).
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6492
ERR_ROLM_5011
Explanation: Bad code: %s, in message from Resource Manager.
Cause: This is an internal programming error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6493
ERR_ROLM_5013
Explanation: Bad return code: %s from MailBox Write.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6494
ERR_ROLM_5015
Explanation: Unexpected request prior to CONNECT.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6495
ERR_ROLM_5020
Explanation: Error %s from Mailbox Read function.
Cause: This is an internal software error condition.
Action: Check previous messages and restart the system.
If the problem persists, call the
ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6496
ERR_ROLM_5021
Explanation: Error %s while reading System Mailbox.
Cause: This is an internal software error condition.
Action: Check previous messages and restart the system.
If the problem persists, call the
ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6497
ERR_ROLM_5022
Explanation: Invalid request type = %s.
Cause: This is an internal software error condition.
Action: Check previous messages and restart the system.
If the problem persists, call the
ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6498
ERR_ROLM_5030
Explanation: Return code %s from OS/2.
Cause: This is an internal software error condition.
Action: Check previous messages and restart the system.
If the problem persists, call the
ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6499
ERR_ROLM_5031
Explanation: Internal error (CRITICAL): %s.
Cause: This is an internal software error condition.
Action: Check previous messages and restart the system.
If the problem persists, call the
ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6500
ERR_ROLM_5032
Explanation: Internal error (noncritical): %s.
Cause: This is an internal software error condition.
Action: Check previous messages and restart the system.
If the problem persists, call the
ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6501
ERR_ROLM_5073
Explanation: Failure RIC %s Port %s Code %s.
Cause: This is an internal software error condition.
Action: Follow the problem determination procedures
in your ROLM documentation. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6502
ERR_ROLM_5074
Explanation: Error RIC %s Port %s Code %s Data %s.
Cause: This is an internal software error condition.
Action: Follow the problem determination procedures
in your ROLM documentation. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6503
ERR_ROLM_5075
Explanation: RIC %s Port %s terminating abnormally.
Cause: This is an internal software error condition.
Action: Follow the problem determination procedures
in your ROLM documentation. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6506
ERR_ROLM_5201
Explanation: Wrong parameter number %s.
Cause: This is an internal software error condition.
Action: Check previous messages. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6507
ERR_ROLM_5202
Explanation: Cannot initialize RIC %s.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6508
ERR_ROLM_5203
Explanation: Cannot register mailbox. RIC %s.
Cause: This is an internal software error condition.
Action: Check previous messages. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6509
ERR_ROLM_5204
Explanation: Mailbox receive error. RIC %s.
Cause: This is an internal software error condition.
Action: Check previous messages. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6510
ERR_ROLM_5205
Explanation: Invalid message received. RIC %s.
Cause: This is an internal software error condition.
Action: Check previous messages. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6511
ERR_ROLM_5206
Explanation: Wrong card type. RIC %s Port %s.
Cause: The card and/or port number is not consistent
with the configuration data.
Action: Check the RIC configuration, all ports
on the RIC card should configure for RS-422 operation.
Module: SWITCH.EXE
Severity: WARNING
6512
ERR_ROLM_5207
Explanation: Cannot send a message. RIC %s.
Cause: This is an internal software error condition.
Action: Check previous messages. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6513
ERR_ROLM_5208
Explanation: Wrong interface board. RIC %s.
Cause: The RIC card has an incorrect interface option.
It requires the RS-422 interface board.
Action: Install the correct daughterboard on the RIC card.
Module: SWITCH.EXE
Severity: WARNING
6514
ERR_ROLM_5209
Explanation: Port allocation error. RIC %s, Port %s.
Cause: This is an internal software error condition.
Action: Restart the system. If the problem persists,
call the ROLM Customer Support Center for assistance.
Module: SWITCH.EXE
Severity: WARNING
6515