[IBM Books] Reference for Nortel DMS-100 CO Switch IBM CallPath Reference for Nortel DMS-100 CO Switch Version 2.1 S370-79 SC30-3548-04 5639-A14 Note: Before using this information and the product it supports, be sure to read the general information under Appendix C. "Notices". Fifth Edition (June 1997) This edition applies to Version 2.1 of the CallPath Server for OS/2 licensed program, Program Number 5622-959, Version 2.1 of the CallPath Server for AIX licensed program, Program Number 5765-636, Version 2.1 of the CallPath Server for Microsoft Windows NT licensed program, Program Number 5639-B49, Version 2.1 of CallPath SwitchServer/2, Program Number 5639-A14, and Version 2.1 of the CallPath Developers Toolkit licensed program, Program Number 5622-958, and to all subsequent releases and modifications until otherwise indicated in new editions, or technical newsletters. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. IBM welcomes your comments. A form for readers' comments appears at the back of this publication. If the form has been removed, you may send your comments to the following address: International Business Machines Corporation Department CGMD P.O. Box 12195 Research Triangle Park, NC 27709-9990 USA If you prefer to send comments electronically, use one of the following methods: * IBMLink: CIBMOFCF at RALVM13 * IBM Mail: USIB2HPD at IBMMAIL * Internet: USIB2HPD@vnet.ibm.com * Fax: 1-800-227-5088 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. --------------------------------------------------------------------------- Table of Contents Figures Tables About This Book * Who Should Use This Book * How to Use This Book * Where to Find More Information * What's New in This Book Chapter 1. Introduction * Purpose of This Book * Approval of Applications * Naming and Notational Conventions Chapter 2. Installing and Configuring CallPath SwitchServer/2 * DMS-100 Switch Configuration o DMS-100 Switch Hardware and Software Requirements o CallPath SwitchServer/2 Hardware and Software Requirements * Installation Considerations o Checking the CONFIG.SYS File o Updating the STARTUP.CMD File o Before You Begin * Summary of Installation Steps * Step 1: Installing OS/2 * Step 2: Installing and Configuring the Adapter for Host Communications * Step 3: Installing the X.25 Interface Co-Processor Adapter o Configuring the X.25 Interface Co-Processor Adapter * Step 4: Installing the CallPath SwitchServer/2 Program o Backing up the CallPath SwitchServer/2 Program * Step 5: Configuring X.25 Communication Link between the DMS-100 CO Switch and Host o Installing Communications Manager/2 o Setting Up a Communications Profile for CallPath SwitchServer/2 o Creating the X.25 Links o Creating the X.25 Directory Entries o Verifying the Profile * Step 6: Setting the DMS-100 CO Switch Logon Parameters o Multiple Logons Using the Same Service ID o Multiple Logons Using Different Service IDs Chapter 3. Installing and Configuring CallPath Server for OS/2 * DMS-100 Switch Configurations o DMS-100 Switch Hardware and Software Requirements o CallPath Server for OS/2 Hardware and Software Requirements o Before You Begin * Summary of Installation Steps * Step 1: Installing and Configuring OS/2 * Step 2: Installing and Configuring TCP/IP Hardware and Software o Installing and Configuring TCP/IP Hardware and Software for a Networked Server o Installing and Configuring TCP/IP Hardware and Software for a Stand-Alone Server * Step 3: Installing CallPath Server for OS/2 and Other CallPath Components * Step 4: Restarting the CallPath Server for OS/2 Computer * Step 5: Starting the CallPath Server Management Facility and Configuring CallPath Server for OS/2 o Starting the CallPath Server for OS/2 Management Facility o Configuring CallPath Server for OS/2 (Minimal Configuration) o Starting the CallPath Server for OS/2 Subsystem * Step 6: Installing and Configuring the X.25 Interface Co-Processor Adapter for Switch Communications o Installing One or More X.25 Interface Co-Processor Adapters o Configuring One or More X.25 Interface Co-Processor Adapters o Installing Communications Manager/2 o Creating the X.25 Links o Creating the X.25 Directory Entries o Verifying the Profile o Installing the DMS-100 CO Switch-Dependent Code Feature o Configuring the DMS-100 CO Switch Connection(s) * Step 7: Restarting the CallPath Server for OS/2 Computer * Step 8: Starting CallPath Server for OS/2 and the DMS-100 CO Switch Connection(s) o Starting the CallPath Server Management Facility o Starting the CallPath Server for OS/2 Subsystem o Starting the DMS-100 CO Switch Connection(s) o Multiple Logons Using the Same Service ID o Multiple Logons Using Different Service IDs Chapter 4. Installing and Configuring CallPath Server for AIX * DMS-100 Switch Configuration o DMS-100 Switch Hardware and Software Requirements o CallPath Server for AIX Hardware and Software Requirements o Before You Begin * Summary of Installation Steps * Step 1: Installing and Configuring AIX * Step 2: Installing and Configuring TCP/IP Hardware and Software o Installing and Configuring TCP/IP Hardware and Software for a Networked Server o Installing and Configuring TCP/IP Hardware and Software for a Stand-Alone Server * Step 3: Installing or Updating CallPath Server for AIX and Other CallPath Components o Installing or Updating CallPath Developers Toolkit for AIX * Step 4: Starting the CallPath Server Management Facility and Configuring CallPath Server for AIX o Starting the CallPath Server for AIX Management Facility o Configuring CallPath Server for AIX (Minimal Configuration) o Starting the CallPath Server for AIX Subsystem * Step 5: Installing and Configuring One or More X.25 Interface Co-Processor/2 Adapters for Switch Communications o Installing One or More X.25 Interface Co-Processor/2 Adapters o Installing DMS-100 CO Switch-Dependent Code Feature o Identifying the X.25 Interface Co-Processor/2 Adapter to AIX o Configuring the Device Driver for Each X.25 Interface Co-Processor/2 Adapter o Starting X.25 Communication Links between CallPath Server for AIX and the DMS-100 CO Switch o Configuring the DMS-100 CO Switch Connection(s) * Step 6: Starting CallPath Server for AIX and the DMS-100 CO Switch Connection o Starting the CallPath Server Management Facility o Starting CallPath Server for AIX o Starting the DMS-100 CO Switch Connection o Multiple Logons Using the Same Service ID o Multiple Logons Using Different Service IDs Chapter 5. Installing and Configuring CallPath Server for MS Windows NT * DMS-100 CO switch Configurations o DMS-100 CO switch Hardware and Software Requirements o CallPath Server for MS Windows NT Hardware and Software Requirements o Before You Begin * Summary of Installation Steps * Step 1: Installing and Configuring Microsoft Windows NT * Step 2: Installing and Configuring TCP/IP Hardware and Software * Step 3: Installing CallPath Server for MS Windows NT and Other CallPath Components o Viewing the Component Installation History o Displaying the "Readme" Information o Uninstalling CallPath Components * Step 4: Restarting the CallPath Server for MS Windows NT Computer * Step 5: Starting the CallPath Server Management Facility and Configuring CallPath Server for MS Windows NT o Starting the CallPath Server for MS Windows NT Management Facility o Configuring CallPath Server for MS Windows NT (Minimal Configuration) o Starting the CallPath Server for MS Windows NT Subsystem * Step 6: Installing and Configuring the X.25 Interface Co-Processor Adapter for Switch Communications o Installing and Configuring the X.25 Adapter Hardware o Installing the X.25 Adapter Software o Configuring the X.25 Directory Links o Installing the DMS-100 CO Switch-Dependent Code Feature o Configuring the DMS-100 CO Switch Connection(s) in CallPath Server for MS Windows NT * Step 7: Restarting the CallPath Server for MS Windows NT Computer * Step 8: Starting CallPath Server for MS Windows NT and the DMS-100 CO Switch Connection(s) o Starting the CallPath Server Management Facility o Starting the CallPath Server for MS Windows NT Subsystem o Starting the DMS-100 CO Switch Connection(s) Chapter 6. DMS-100 CO Switch Functions * Unsupported Program Calls, Parameters, and Characteristics * Program Calls Supported by the DMS-100 CO Switch * Set Program Calls Supported by the DMS-100 CO Switch * Messages Supported by the DMS-100 CO Switch * Special Considerations and Limitations Chapter 7. Partially Supported Program Calls * STLCONF (Conference_Call) * STLINIT (Initialize_Call_Profile) * STLINVK (Invoke_Feature) * STLMAKE (Make_Call) o Version 0 and Version 1 Supported Parameters o Additional Version 1 Supported Parameters * STLMON (Monitor) * STLQACD (Query_ACD_Information) * STLRCV (Receive) * STLRED (Redirect_Call) o Version 0 and Version 1 Supported Parameters o Additional Version 1 Supported Parameters * STLTRAN (Transfer_Call) * STLTRGR (Trigger) * STLXTND (Extend_Call) o Version 0 and Version 1 Supported Parameters o Additional Version 1 Supported Parameters Chapter 8. Partially Supported Set Program Calls * STLSDEO (Set_Disconnect_Execution_Option) * STLSEP (Set_Extend_Purpose) Chapter 9. Partially Supported Messages * ACD_Information * Call_Alerting o Version 0 and Version 1 Supported Fields o Additional Version 1 Supported Fields * Call_Connected o Version 0 and Version 1 Supported Fields o Additional Version 1 Supported Fields * Call_Held * Call_Picked * Call_Rejected * Call_Routed o Version 0 and Version 1 Supported Fields o Additional Version 1 Supported Fields * Call_Transferred o Version 0 and Version 1 Supported Fields o Additional Version 1 Supported Fields * Disconnected o Version 0 and Version 1 Supported Fields o Additional Version 1 Supported Fields * Feature_Invoked * Party_Status * Request_Instruction * Response * Party_Structure * Status_Structure * Time_And_Date Chapter 10. Problem Determination * Return Codes * Sense Code Qualifiers o STL_SWITCH_SPECIFIC_ERROR o STL_SYSTEM_ERROR o STL_RQ_NOT_SUPPORTED_BY_SWITCH * System Messages Data o Program Messages (Noncritical) o Program Messages (Critical) * NetView Alerts (for CallPath SwitchServer/2 Only) * SNMP Traps (for CallPath Server Only) * CallPath SwitchServer/2 Is Not Communicating with DMS-100 Central Office (CO) Switch * Trace Data o Field Descriptions o Function Key Descriptions * Dump Data Chapter 11. Example Program Call and Message Flows * Overview o Inbound Call o Inbound Call (Queued) o Inbound Call (Not Queued) o Inbound Call (Call Forwarded) o Inbound Call (Call Picked) o Inbound Call (Call Waited) o Blind Transfer o Screened Transfer o Screened Transfer/ACD to Directory Number o Trigger o Call Redirection/ACD to ACD/Inbound Call o Call Redirection/ACD to Directory Number/Inbound Call o Queue Overflow (A) o Queue Overflow (B) o Ring Threshold Overflow o Outbound Call o Outbound Call to Intra-Switch o Blind Transfer/Host Initiated o Blind Transfer/Directory Number to Directory Number o Screened Transfer/Directory Number to Directory Number o Consultation/Directory Number to Directory Number o Screened Transfer/Host Initiated o Consultation/Host Initiated o Conference/Host Initiated (A) o Conference/Host Initiated (B) * Program Flows for Version 1 Specific Features o Conference/Host Initiated (C) Appendix A. Restart of Switch Connection Following Link Failure * Automatic Restart of Switch Connection * Manual Restart of Switch Connection Appendix B. Installing and Configuring the X.25 Interface Adapter Using AIX Version 4.1 * Overview o Installing X.25 Interface Co-Processor/2 Adapters o Installing DMS-100 CO Switch-Dependent Code Feature o Identifying the X.25 Interface Co-Processor/2 Adapter o Configuring the Device Driver for Each X.25 Interface Co-Processor/2 Adapter o Starting X.25 Communication Links o Configuring the DMS-100 CO Switch Connection(s) Appendix C. Notices * Trademarks Appendix D. Glossary Index --------------------------------------------------------------------------- Figures 1. DMS-100 CO Switch Connection to CallPath SwitchServer/2 2. DMS-100 CO Switch Connection to CallPath Server for OS/2 3. Enter Switch Configuration Data Window 4. DMS-100 CO Switch Connection to CallPath Server for AIX 5. Enter Switch Configuration Data Window 6. DMS-100 CO switch Connection to CallPath Server for MS Windows NT 7. Enter Switch Configuration Data Window 8. Trace Message Example 9. Adding an X.25 Port Screen 10. Enter Switch Configuration Data Window --------------------------------------------------------------------------- Tables 1. DMS-100 CO Switch Workspace Parameter Worksheet for CallPath SwitchServer/2 2. DMS-100 CO Switch Workspace Parameter Worksheet for CallPath Server for OS/2 3. DMS-100 CO Switch Workspace Parameter Worksheet for CallPath Server for AIX 4. DMS-100 CO Switch Workspace Parameter Worksheet for CallPath Server for AIX 5. Data Elements Provided in the switch_ACD_data Buffer --------------------------------------------------------------------------- About This Book This book provides application program reference information for developing telephony applications using IBM CallPath(*) Services in connection with the Nortel DMS-100(**) Central Office (CO) Switch. In this book, the system is referred to as the DMS-100 CO switch. --------------------------------------------------------------------------- Who Should Use This Book The following individuals should read this book: * Telecommunications personnel responsible for installing and configuring the DMS-100 CO switch and connections to CallPath SwitchServer/2(*), CallPath Server for OS/2, CallPath Server for AIX, or CallPath Server for MS Windows NT * Application programmers who design or manage programs used with CallPath Services and the DMS-100 CO switch --------------------------------------------------------------------------- How to Use This Book This book provides switch-specific information and is designed to be read with the CallPath Developers Toolkit Programming Guide and 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. * Chapter 2. "Installing and Configuring CallPath SwitchServer/2", provides information for installing and configuring the DMS-100 CO switch and CallPath SwitchServer/2 hardware and software. Read it with the installation information in Using CallPath SwitchServer/2. * Chapter 3. "Installing and Configuring CallPath Server for OS/2", provides information for installing and configuring the DMS-100 CO switch and CallPath Server for OS/2 hardware and software. Read it with the installation information in the CallPath Server Planning, Installation, and Problem Determination Guide * Chapter 4. "Installing and Configuring CallPath Server for AIX", provides information for installing and configuring the DMS-100 CO switch and CallPath Server for AIX hardware and software. Read it with the installation information in CallPath Server Planning, Installation, and Problem Determination Guide * Chapter 5. "Installing and Configuring CallPath Server for MS Windows NT", provides information for installing and configuring the DMS-100 CO switch and CallPath Server for MS Windows NT hardware and software. Read it along with the installation information in CallPath Server Planning, Installation, and Problem Determination Guide * Chapter 6. "DMS-100 CO Switch Functions", provides quick-reference tables showing the DMS-100 CO switch support for CallPath program calls and messages. * Chapter 7. "Partially Supported Program Calls", describes the CallPath program calls that are partially supported by the DMS-100 CO switch. * Chapter 8. "Partially Supported Set Program Calls", describes the CallPath Set program calls that are partially supported by the DMS-100 CO switch. * Chapter 9. "Partially Supported Messages", describes the CallPath messages that are partially supported by the DMS-100 CO switch. * Chapter 10. "Problem Determination", provides problem determination information specific to the DMS-100 CO switch. * Chapter 11. "Example Program Call and Message Flows", provides examples that show sequences of information flow from the DMS-100 CO switch. * Appendix A. "Restart of Switch Connection Following Link Failure", describes how to manually or automatically restart the communication link. * Appendix B. "Installing and Configuring the X.25 Interface Adapter Using AIX Version 4.1", describes installing the X.25 Interface co-processor adapter using AIX Version 4.1. This book also includes a glossary of terms and abbreviations and an index. --------------------------------------------------------------------------- Where to Find More Information Use the following IBM CallPath publications with this book: * CallPath Developers Toolkit Programming Guide and Reference, GC31-6824 * Using CallPath SwitchServer/2, SC34-2406 Also, these IBM CallPath 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 * CallPath for OS/2 General Information, GC30-3616 * CallPath for OS/2 Planning, Installation, and Problem Determination Guide, SC30-3617 * CallPath Toolkit for OS/2 Application Programming Guide, SC30-3618 * CallPath Toolkit for OS/2 Programmer's Reference, SC30-3619 * 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 The following CallPath books may be useful when implementing the CallPath Services Architecture in a client/server environment: * IBM CallPath Server General Information, GC31-8529 * IBM CallPath Server Planning, Installation, and Problem Determination Guide, SC31-6242 * IBM CallPath Developers Toolkit Programming Guide and Reference, SC31-6243 Other IBM publications that may be useful to you include: * Documents that accompanied the OS/2 and AIX operating systems. * Operating System/2 2.1 Information and Planning Guide SC31-7007 * Communications Manager/2 User's Guide, SC31-6108 * Communications Manager/2 Configuration Guide, SC31-6171 * Operating System/2 Programming Tools and Information 64F0275 * X.25 Interface Co-Processor/2 Technical Reference, S1616F-1879 * X.25 Interface Co-Processor/2 Guide to Operations, 16F1864 In addition, you should consult: * The Nortel service documentation for your DMS-100 CO switch * CompuCall Interface Specification, NT NIS-Q218 * Nortel Feature Planning Guide 50004.1/01-92 or later --------------------------------------------------------------------------- What's New in This Book The following items are new or have changed since the last edition of this book: * Support is provided for the Server to run on a Microsoft Windows NT platform. See Chapter 5. "Installing and Configuring CallPath Server for MS Windows NT". --------------------------------------------------------------------------- Chapter 1. Introduction The Nortel DMS-100 CO Switch is a digital telecommunications system. In this book, the system is referred to as the DMS-100 CO switch. The DMS-100 CO switch interfaces with the following: * CallPath Services host computers through IBM CallPath SwitchServer/2 * CallPath Server for OS/2 computers using a direct (local) connection or the services of CallPath SwitchServer/2 * CallPath Server for AIX computers using a direct (local) connection or the services of CallPath SwitchServer/2 * CallPath Server for MS Windows NT computers using a direct (local) connection or the services of CallPath SwitchServer/2 CallPath is IBM's architecture for computer-telephone system communications. It defines an application program interface (API) systems--in this book, the DMS-100 CO switch. The CallPath API enables new or existing applications to provide advanced switching functions through the integration of voice and data processing capabilities. CallPath SwitchServer/2 Connections CallPath SwitchServer/2 connects the DMS-100 CO switch to one or more CallPath host computers. It performs protocol conversion between CallPath requests and messages and DMS-100 CO switch protocols. CallPath SwitchServer/2 isolates the CallPath host computer from the specific communications formats and protocols that are required to interface with the DMS-100 CO switch, while allowing the DMS-100 CO switch to interface concurrently with multiple CallPath host computers. CallPath Server for OS/2 Connections CallPath Server for OS/2 can connect directly to the DMS-100 CO switch or through the services of CallPath SwitchServer/2. When connected directly to the DMS-100 CO switch, CallPath Server for OS/2 performs protocol conversion between CallPath requests and messages and DMS-100 CO switch protocols in a client/server environment. Application programs running on the network are isolated from the specific communications formats and protocols that are required to interface with the DMS-100 CO switch, while allowing the DMS-100 CO switch to interface concurrently with multiple application programs running on a variety of client workstations. CallPath Server for AIX Connections CallPath Server for AIX can connect directly to the DMS-100 CO switch or through the services of CallPath SwitchServer/2. When connected directly to the DMS-100 CO switch, CallPath Server for AIX performs protocol conversion between CallPath requests and messages and DMS-100 CO switch protocols in a client/server environment. Application programs running on the network are isolated from the specific communications formats and protocols that are required to interface with the DMS-100 CO switch, while allowing the DMS-100 CO switch to interface concurrently with multiple application programs running on a variety of client workstations. CallPath Server for MS Windows NT Connections CallPath Server for MS Windows NT can connect directly to the DMS-100 CO switch or through the services of CallPath SwitchServer/2. When connected directly to the DMS-100 CO switch, CallPath Server for MS Windows NT performs protocol conversion between CallPath requests and messages and DMS-100 CO switch protocols in a client/server environment. Application programs running on the network are isolated from the specific communications formats and protocols that are required to interface with the DMS-100 CO switch, while allowing the DMS-100 CO switch to interface concurrently with multiple application programs running on a variety of client workstations. Note: Except where there is a need to differentiate between CallPath SwitchServer/2, CallPath Server for OS/2, CallPath Server for AIX, and CallPath Server for MS Windows NT, the term Server will be used in place of these names. --------------------------------------------------------------------------- Purpose of This Book This book provides switch-specific information for the DMS-100 CO switch. It describes the level of support provided by the DMS-100 CO switch for the program calls and messages that make up the CallPath 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 the CallPath Developers Toolkit Programming Guide and Reference. You should also refer to the CallPath programming guide for your host computer system, as this may define a different level of support for the architecture. This book also identifies any deviation from the procedures described in Using CallPath SwitchServer/2and the CallPath Server Planning, Installation, and Problem Determination Guide for installation, administration, or problem determination required when using CallPath in conjunction with the DMS-100 CO switch. --------------------------------------------------------------------------- Approval of Applications 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. Neither the DMS-100 CO switch, CallPath SwitchServer/2, CallPath Server for OS/2, CallPath Server for AIX, nor CallPath Server for MS Windows NT enforces these restrictions. The application developer must ensure that each application program complies with the restrictions by following these steps: 1. Contact the IBM Support Center to find out the regulations for the country or countries in which the application program is to be used. 2. Notify the switch vendor of the details of the operation of the application program that may be subject to constraint. 3. Request a confirmation from the switch vendor that the application program will comply with the restrictions. Once the confirmation is received, it is the switch vendor who is liable to the Telecommunications Authority as long as the application program does what was stated in the notification. --------------------------------------------------------------------------- Naming and Notational Conventions 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 STLRED is used by a program to change the destination of an incoming telephone call from one party to another. The pseudonym for STLRED is Redirect_Call. 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, the book's convention is to either say so explicitly or use "function" notation. For example, a party_specification of STL_DIRECTORY_NUMBER may also appear as party_specification (STL_DIRECTORY_NUMBER). 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 Developers Toolkit Programming Guide and 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 Server 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 with 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_Extend_Purpose program call to modify the call profile characteristic of extend_purpose to a value of STL_EXTEND_TRANSFER. * The real name of the program call, as known by the CallPath Server subsystem, for Set_Extend_Purpose is STLSEP (see "STLSEP (Set_Extend_Purpose)"). STLSEP has a parameter list of call_profile_ID, extend_purpose, and return_code. The CallPath Developers Toolkit Programming Guide and Reference contains a description of all the CallPath Services program calls, including the syntax and semantics of the variables used for each call. * The extend_purpose variable that goes into the call as a parameter is a 32-bit integer. The CallPath Developers Toolkit Programming Guide and Reference provides a complete description of all variables. * The value of STL_EXTEND_TRANSFER that is placed into the extend_purpose parameter on the call to STLSEP is defined as an integer value of 1. The CallPath Developers Toolkit Programming Guide and 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 return_code value is provided in CallPath Developers Toolkit Programming Guide and Reference. Note: Pseudonym value names are not actually passed to the CallPath Server 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_EXTEND_TRANSFER as meaning an integer value of 1. The actual program code would then read as described previously, that extend_purpose is replaced with STL_EXTEND_TRANSFER. The end result, however, is that an integer value of 1 is placed into the variable. The term Co-Processor/2 refers to an adapter designed for a PC with microchannel architecture. The term Co-Processor refers to an adapter designed for a PC with ISA architecture. Unless specified, the term co-processor specifies any adapter suitable for your machine architecture. --------------------------------------------------------------------------- Chapter 2. Installing and Configuring CallPath SwitchServer/2 This chapter provides installation and configuration information for the DMS-100 CO switch hardware and software that is used with the CallPath SwitchServer/2 program product. Note: If you want to install CallPath Server for OS/2 for a direct connection to the DMS-100 CO switch or as the CallPath SwitchServer/2 host, see Chapter 3. "Installing and Configuring CallPath Server for OS/2". If you want to install CallPath Server for AIX for a direct connection to the DMS-100 CO switch or as the CallPath SwitchServer/2 host, see Chapter 4. "Installing and Configuring CallPath Server for AIX". If you want to install CallPath Server for MS Windows NT for a direct connection to the DMS-100 CO switch or as the CallPath SwitchServer/2 host, see Chapter 5. "Installing and Configuring CallPath Server for MS Windows NT". Also included in this chapter are lists of the additional hardware and software that is required to connect CallPath SwitchServer/2 to the DMS-100 CO switch. Use these instructions with the installation instructions in Using CallPath SwitchServer/2. --------------------------------------------------------------------------- DMS-100 Switch Configuration The following figure shows the hardware configuration for the DMS-100 CO switch connection to CallPath SwitchServer/2. Figure 1. DMS-100 CO Switch Connection to CallPath SwitchServer/2 [Image] View figure. DMS-100 Switch Hardware and Software Requirements To use the DMS-100 CO switch with CallPath SwitchServer/2, the following hardware and software are required: Hardware Requirements A DMS-100 CO switch with the following: o ACD feature o CompuCall feature Refer to the Nortel Feature Planning Guide 50004.1/01-92 or later. Also contact your Nortel installation agent for installation, configuration, and upgrade changes to your DMS-100 CO switch hardware. Software Requirements Software requirements are installation specific: o Refer to the Nortel Feature Planning Guide 50004.1/01-92 or later for the BCS33 through BCS36 levels of the CompuCall feature. o Contact your Nortel installation agent for installation, configuration, and upgrade changes to your DMS-100 CO switch software. CallPath SwitchServer/2 Hardware and Software Requirements To use CallPath SwitchServer/2 with the DMS-100 CO switch, the following hardware and software are required: Hardware Requirements 1. 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 CO + 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 of the following: + An IBM X.25 Interface Co-Processor/2 for a PC with microchannel architecture, + An IBM X.25 Interface Co-Processor with memory for a PC with ISA architecture + One of the following: + IBM 5822-10 Data Service Unit (DSU) + IBM 7855-10 modem or equivalent for V.24 2. A connection from the PC to the DMS-100 CO switch using an IBM X.25 Interface co-processor cable option V.35 or cable option V.24 3. 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: o IBM Operating System/2(*) (*)) Version 2.1 or higher, (including OS/2 Warp* Version 3.0), and the latest Corrective Services Diskettes (CSDs) o Communications Manager/2* Version 1.1 or higher, and the latest CSDs o CallPath SwitchServer/2-to-host connectivity software; see Using CallPath SwitchServer/2 --------------------------------------------------------------------------- Installation Considerations It is recommended that a PS/2 be dedicated to running CallPath SwitchServer/2 and the programs listed in "CallPath SwitchServer/2 Hardware and Software Requirements". Checking the CONFIG.SYS File During the CallPath SwitchServer/2 installation process, the CONFIG.SYS file is automatically updated to include the following: PRIORITY=ABSOLUTE LIBPATH=C:\CPSS2 DPATH=C:\CPSS2;C:\CMLIB DEVICE=C:\CMLIB\ICARICIO.SYS PATH=C:\CPSS2 IOPL=YES No additional changes are needed for the CONFIG.SYS file. Updating the STARTUP.CMD File During CallPath SwitchServer/2 installation process, the STARTUP.CMD file can be updated to start CallPath SwitchServer/2 automatically. No additional changes need to be made to the STARTUP.CMD file. The original STARTUP.CMD file is saved as STARTUP.BAK. Before You Begin Contact your DMS-100 CO switch representative to have the DMS-100 CO switch hardware and software installed. You also need to contact your switch representative to obtain the following information: * CCITT compliance date (1980 or 1984) * Local DTE address * Remote DTE address * The following switch logon parameters: o Network Node ID o Service ID o Service Version (BCS level) o Business Group ID o Application ID o Password for the given Business Group ID The workspace in Table 1 provides space for you to record this information. Only one switch connection is supported. Space is provided in the table for a primary and three alternative connections. You will also need to know whether you are running on a point-to-point connection or a public packet network connection. If the first CallPath SwitchServer/2 installation diskette contains a README or a TIPS file, read them before installing CallPath SwitchServer/2. Table 1. DMS-100 CO Switch Workspace Parameter Worksheet for CallPath SwitchServer/2 Description Switch Connection Description Network Node ID Service ID Description Service Version (BCS level) Business Group ID Application ID Slot Number Local Address (KBPS2) Remote Address (DMS) Logon Password* Note: *May want to leave password blank, depending on security requirements. --------------------------------------------------------------------------- Summary of Installation Steps Following is an overview of the procedure for installing and configuring the DMS-100 CO switch for use with CallPath SwitchServer/2: Step 1: Installing OS/2 Step 2: Installing and configuring the adapter for host communications Step 3: Installing the X.25 Interface co-processor adapter Step 4: Installing the CallPath SwitchServer/2 program Step 5: Configuring X.25 communication link between the DMS-100 CO switch and host Step 6: Setting the DMS-100 CO switch logon parameters This procedure is described in detail in the following sections. --------------------------------------------------------------------------- Step 1: Installing OS/2 Make sure that OS/2 is installed and running before attempting to install CallPath SwitchServer/2. Note: Install the latest Corrective Services Diskettes (CSDs) for OS/2. --------------------------------------------------------------------------- Step 2: Installing and Configuring the Adapter for Host Communications Install and configure the adapter for CallPath SwitchServer/2-to-host communications. See the documentation that accompanied your hardware adapter for information on installing and configuring the host adapters supported by CallPath SwitchServer/2. --------------------------------------------------------------------------- Step 3: Installing the X.25 Interface Co-Processor Adapter Install and configure an X.25 Interface co-processor adapter for each CallPath SwitchServer/2-to-DMS-100 CO switch connection. An X.25 Interface co-processor adapter card provides the communications channel between the DMS-100 CO switch and CallPath SwitchServer/2. Install the X.25 co-processor adapter that is appropriate for your machine architecture, according to the instructions supplied with the co-processor adapter. Record the slot number in which you install the X.25 Interface co-processor adapter for use when configuring the X.25 link. Continue with "Configuring the X.25 Interface Co-Processor Adapter". Configuring the X.25 Interface Co-Processor Adapter Refer to the documentation that accompanied your machine for information about configuring the co-processor adapter. Continue with "Installing Communications Manager/2". --------------------------------------------------------------------------- Step 4: Installing the CallPath SwitchServer/2 Program To install CallPath SwitchServer/2, do the following: 1. Insert CallPath SwitchServer/2 program Diskette 1 in drive A. 2. Open an OS/2 full-screen session. 3. Enter a: to make drive A the current drive. 4. Enter install. A message informs you that the transfer utility program is running, and the version and modification levels of CallPath SwitchServer/2 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. 5. Select one of the following: o N to stop the installation o Y to continue with the installation The necessary directories are created and the files are copied to them. 6. Follow the instructions if you are prompted to insert additional diskettes. After the files are copied, a prompt asks if you want to update the CONFIG.SYS file. 7. Enter one of the following: o Y to update the CONFIG.SYS o N to continue without updating the file A prompt asks whether you want to update the STARTUP.CMD file. 8. Enter one of the following: o Y to update the STARTUP.CMD file o N to continue without updating A prompt asks whether you want CallPath SwitchServer/2 to start automatically when a critical error occurs. 9. Enter one of the following: o Y to restart on errors o N for the program to stop when an error occurs A prompt asks whether you want to view the README.TXT file. 10. Enter one of the following: o Y to display and view the README.TXT file o N to continue without displaying the README.TXT file The Installation Complete message is displayed. 11. Remove the program diskette from drive A. Continue with "Backing up the CallPath SwitchServer/2 Program". Backing up the CallPath SwitchServer/2 Program To back up the CallPath SwitchServer/2 program, do the following: 1. Obtain two blank, 3.5 inch, high-density diskettes that have been formatted to 1.44MB. 2. Open an OS/2 full-screen session. 3. Enter c: to make drive C the current drive. 4. Enter CD CPSS2 to change to the CallPath SwitchServer/2 directory. 5. Enter BACKSS2 to run the backup utility program. 6. Insert one of the blank diskettes into drive A. 7. Enter Y in response to the prompt to begin backing up. 8. 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. 9. Remove the backup diskette from the drive. 10. Label the backup diskette or diskettes. --------------------------------------------------------------------------- Step 5: Configuring X.25 Communication Link between the DMS-100 CO Switch and Host Following is an overview of the tasks required for installing and configuring X.25 communications between CallPath SwitchServer/2 and the DMS-100 CO switch: * Installing Communications Manager/2 * Setting up a communications profile for CallPath SwitchServer/2 * Creating the X.25 link for the X.25 Interface co-processor adapter * Creating the X.25 directory entries for the Interface co-processor adapter * Verifying the profile * Setting the DMS-100 switch logon Parameters These tasks are described in more detail in the following sections. Installing Communications Manager/2 Install Communications Manager/2 by following the instructions in the Communications Manager Version 1.1 Workstation Installation and Configuration Guide Default configuration files for host communications are provided with CallPath SwitchServer/2. To use one of these default files, do the following during Communications Manager/2 installation: 1. When the Open Configuration window is displayed, select C: under Directories. 2. Select the CPSS2 directory. 3. Under Configurations, select one of the following configuration files based on the host connection adapter type installed in the CallPath SwitchServer/2 PC: CPSS2TR Token ring configuration file. CPSS2SD Synchronous Data Link Control (SDLC) configuration file. CPSS2X2 X.25 configuration file. CPSS2EN Ethernet configuration file. 4. Continue with configuration until the Communications Manager Configuration Definition window is displayed. Continue with "Setting Up a Communications Profile for CallPath SwitchServer/2". Setting Up a Communications Profile for CallPath SwitchServer/2 To set up communications parameters for CallPath SwitchServer/2, do the following: 1. Open an OS/2 command window. 2. Insert the backup copy of the X.25 and Multiport/2 Option diskette in Drive A. 3. At the OS/2 command prompt, enter the following command: copy a:icaaim.com c:\cmlib 4. Return to the Communications Manager Configuration Definition window. 5. Select X.25 in the Workstation Connection Type list box. 6. Select X.25 APIs in the Feature or Application list box. 7. Click on Configure. The Communications Manager Profile List window is displayed. Continue with "Creating the X.25 Links". Creating the X.25 Links If you did not record the slot number in which you installed the X.25 Interface co-processor adapter, do so now before continuing. The slot number will be used to identify the X.25 link in the following procedure. (The numbers are listed on the back panel of the PC.) To create the X.25 links from the Communications Manager Profile List window, do the following: 1. Select X.25 Links. The X.25 Links window is displayed. 2. Select Configure.... 3. Select Create... to create a profile. The X.25 Link Parameters window is displayed. 4. Edit the profile, providing the following settings: Link name NTI Adapter type X.25 Slot number Number of the slot where the X.25 card is installed in your PC. (The numbers are listed on the back panel.) Network type 1 Local CCITT compliance Either 1980 or 1984. The entry must match DMS-100 table MPCLINK. Link setup mode Initiate from DTE. Local DTE address The address by which the switch recognizes CallPath SwitchServer/2. (The entry must match the address the DMS-100 has for CallPath SwitchServer/2.) Optional comment You supply the comment. 5. From the Additional parameters list, select Virtual Circuit Ranges, then select Change. 6. Edit the parameters, by providing the following settings: In-only SVCs Number of Virtual Circuits = 0 Lowest Logical Channel Number = not accessible Two-Way SVCs Number of Virtual Circuits = 1 Lowest Logical Channel Number = 1 Out-only SVCs Number of Virtual Circuits = 0 Lowest Logical Channel Number = not accessible 7. Select OK. 8. Select Frame values from the Additional parameters list, then select Change. The Frame Values window is displayed. 9. Edit the frame values, providing the following settings: Frame sequence modulo 8 Window size 7 T1 - Frame retransmission timeout In the range of 5000-15000. This value is in milliseconds. It provides adequate time before generating a clear request that causes the switch session to be terminated. Note: Check with your switch administrator for the retransmission timeout value set by the switch. The T1 value must not be less than that provided by the switch. To calculate the T1 value, multiply the switch retransmission timeout, in seconds, by 1000. For example, if the switch T1 timeout is set to 12 seconds, the T1 value on the SwitchServer/2 machine should be 12000 or more. N2 - Frame transmission attempt count 10 T4 - Inoperational timeout (seconds) Set to value that the DMS-100 CO switch uses. Typical value is 25 (for the United States) or 10 (for Canada). 10. Select OK. 11. Select SVC/PVC packet sizes from the Additional parameters list, then select Change. The SVC/PVC Packet Sizes window appears. 12. Edit the parameters, by providing the following settings: SVC maximum Incoming=128, Outgoing=128 SVC default Incoming=128, Outgoing=128 PVC default Incoming=128, Outgoing=128 13. Select OK. 14. Select SVC/PVC window sizes in the Additional parameters list, then select Change. The SVC/PVC Window Sizes window is displayed. Ask your switch administrator whether your connection is a point-to-point or a public packet network connection. 15. Do one of the following: o If this is a point-to-point connection, set all SVC sizes to 7. o If this is a public packet network connection, set all SVC sizes to 2. 16. Select OK. 17. Select Modem parameters from the Additional parameters list, then select Change. 18. Edit the parameters, by providing the following settings: Use Transpac VX32 modem Leave unselected Operation mode DTE Initial mode of links Connect 19. Select OK. 20. Select OK on the X.25 Link Parameters window. 21. Select Close on the X.25 Links window. Continue with "Creating the X.25 Directory Entries". Creating the X.25 Directory Entries To create the X.25 directory entries for the Communications Manager Profile List window, do the following: 1. Select X.25 Directory Entries, then select Configure. 2. Select Create in the X.25 Directory Entries window. 3. Edit the fields, providing the following settings: Directory entry name KBPS2 Directory entry LOCAL 4. Select OK. The X.25 Local Directories window is displayed. 5. Select Create. The Local Directory Entry window is displayed. 6. Edit the fields, providing the following settings: Link name NTI Local address The address by which the switch recognizes CallPath SwitchServer/2. (The entry must match the "REMDNA" field in the DMS-100 table SCAICOMS.) Local address extension Leave blank. 7. Select OK. 8. Enter a comment in the Optional comment field if you want. 9. Select OK. The X.25 Directory Entries window is displayed. 10. Select Create. The Create Directory Entry window is displayed. 11. Edit the fields, providing the following settings: Directory entry name DMS Directory entry Remote Remote type Non-SNA Virtual circuit type SVC 12. Select OK. The Non-SNA SVC Directory Entry Window is displayed. 13. Edit the fields, providing the following settings: Link name NTI Optional Remote DTE address The address by which the switch identifies itself. This value must match the DMS-100 table MPCLINK field EXINFO (SVCDNA). Remote DTE address extension Optional field--leave blank. Optional comment You supply the comment. 14. Select OK. The X.25 Directory Entries window is displayed. 15. Select Close. The Communications Manager Profile List window is displayed. 16. Select Close. The Communications Manager Configuration Profile List window is displayed. Continue with "Verifying the Profile". Verifying the Profile To verify the profile, do the following: 1. Select Close from the Communications Manager Profile List window. 2. Select Close from the Communications Manager Configuration Definition - X.25 window. The verification program will check the configuration file for inconsistencies. If the program detects any errors, a message will inform you that an error exists. You can view the Communications Manager/2 error log to help determine the cause of the error. You should check that you entered the correct values in each of the profiles and that the names match those provided in this installation procedure. 3. If you are prompted to install additional features or to change CONFIG.SYS, select OK. 4. Insert any additional diskettes that are needed by the new profiles. If the edited configuration is the active configuration, you are asked whether the changes are to be made dynamically (without stopping Communications Manager/2). 5. Select Yes to activate the changes. The Communications Manager Setup window is displayed. 6. Select Close. 7. To ensure that Communications Manager is started when the PC running CallPath SwitchServer/2 is restarted, add the following line to the STARTUP.CMD file: START CM 8. Remove any diskettes from the drive, shutdown, and restart the system. --------------------------------------------------------------------------- Step 6: Setting the DMS-100 CO Switch Logon Parameters Use the information recorded in Table 1 when performing the procedure that follows. To set DMS-100 CO switch log-on parameters, do the following: 1. Open the CallPath SwitchServer/2 application. If you did not configure CallPath SwitchServer/2 to automatically start when restarting the PC enter cpss2 to start CallPath SwitchServer/2. 2. Select Connections from the CallPath SwitchServer/2 window. 3. Select Configure from the action bar. 4. Select Supply additional switch parameters from the Configure pull-down menu. See Figure 3. 5. Complete the fields that need to be initialized or modified. See item 9 for a description of the fields. The following items are exceptions to those descriptions: o Local directory entry name is KBPS2 (see "Creating the X.25 Directory Entries", item 3) o Remote directory entry name is DMS (see "Creating the X.25 Directory Entries", item 11) o Password is limited to 4 characters using BCS level 36 6. Click on OK to save the entries or Cancel to ignore the entries changed. Note: For more information about the switch parameters, refer to CompuCall Interface Specification and check with your DMS-100 CO switch representative. When you have completed the logon parameter update, return to "Configuring CallPath SwitchServer/2" in Using CallPath SwitchServer/2 Multiple Logons Using the Same Service ID Multiple logons to a single business group using the same service ID cause unpredictable results and are not supported by this program. If multiple logons occur, the switch response to a request is sent to the next available server link instead of being sent to the server making the request. This causes the call state model to be out of synchronization and the server stops due to a critical error. To avoid such an error, log on to a business group using the same service ID for only one switch link at a time. This means that any switch session logon to a given business group using a given service ID must be stopped before a different logon to the same business group using the same service ID can be attempted. For example, switch session SWITCH01 and switch session SWITCH02 each have the same password and the same service ID and both are enabled to log on to the same business group. If switch session SWITCH01 is active, but you want to start an application that uses switch session SWITCH02, switch session SWITCH01 must be stopped first. This is true even if switch session SWITCH01 has no traffic. Switch links SWITCH01 and SWITCH02 cannot be simultaneously active. Note: This limitation is true for any combination of SwitchServer/2, CallPath Server/2, and CallPath Server/6000 link sessions that can log on to the same business group. It is recommended that switch sessions avoid overlapping. Multiple Logons Using Different Service IDs The switch can be configured to enable independent logons to a business group using different service IDs for each logon. The switch considers these to be independent sessions. :p The first session to execute an association (that is, monitoring) of a primary ACD-DN or Centrex DN has exclusive event messaging for that resource. All events concerning that resource remain within the link established during that session. If a session ends for any reason (such as the failure of an X.25 link) any remaining session can execute an association with the orphaned resource. The switch enables up to eight sessions for each business group. Each session requires a unique service ID. This process partitions a business group into unique and independent sub-business groups. The Server supports this independent, simultaneous, switch session environment. --------------------------------------------------------------------------- Chapter 3. Installing and Configuring CallPath Server for OS/2 This chapter provides installation and configuration information for the DMS-100 CO switch hardware and software that is used with the CallPath Server for OS/2 program product. Note: If you want to install CallPath SwitchServer/2 for a remote connection to the DMS-100 CO switch, see Chapter 2. "Installing and Configuring CallPath SwitchServer/2". If you want to install CallPath Server for AIX for a direct connection to the DMS-100 CO switch or as the CallPath SwitchServer/2 host, see Chapter 4. "Installing and Configuring CallPath Server for AIX". If you want to install CallPath Server for MS Windows NT for a direct connection to the DMS-100 CO switch or as the CallPath SwitchServer/2 host, see Chapter 5. "Installing and Configuring CallPath Server for MS Windows NT". Also included in this chapter are lists of the additional hardware and software that is required for the local (direct physical) connection of CallPath Server for OS/2 to the DMS-100 CO switch. Use these instructions with the installation instructions in the CallPath Server Planning, Installation, and Problem Determination Guide --------------------------------------------------------------------------- DMS-100 Switch Configurations The following figure shows the hardware configuration for the DMS-100 CO switch connection to CallPath Server for OS/2. Figure 2. DMS-100 CO Switch Connection to CallPath Server for OS/2 [Image] View figure. DMS-100 Switch Hardware and Software Requirements To use the DMS-100 CO switch with CallPath Server for OS/2, the following hardware and software are required: Hardware Requirements A DMS-100 CO switch with the following: o ACD feature o CompuCall feature Refer to the Nortel Feature Planning Guide 50004.1/01-92 or later. Also contact your Nortel installation agent for installation, configuration, and upgrade changes to your DMS-100 CO switch hardware. Software Requirements Software requirements are installation specific: o Refer to the Nortel Feature Planning Guide 50004.1/01-92 or later for the BCS33 through BCS36 levels of the CompuCall feature. o Contact your Nortel installation agent for installation, configuration, and upgrade changes to your DMS-100 CO switch software. CallPath Server for OS/2 Hardware and Software Requirements To use CallPath Server for OS/2 in a direct connection with the DMS-100 CO 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 One of the following sets of hardware is required for each active connection (up to 2 active connections are supported): Option 1 + IBM X.25 Interface Co-Processor/2 for a PC with microchannel architecture or an IBM X.25 Interface Co-Processor for a PC with ISA architecture + IBM 5822-10 Data Service Unit (DSU) or equivalent for V.35 Option 2 + IBM 7855-10 modem or equivalent for V.24 + A connection from the PC to the DMS-100 CO switch using an IBM X.25 Interface co-processor cable option V.35 or cable option V.24 Software Requirements The following additional software is required for implementing the local connection to CallPath Server for OS/2: o IBM Communications Manager/2 Version 1.1 o X.25 Interface Co-Processor/2 Technical Reference and the X.25 and Multiport/2 Option diskette Note: These requirements are for installing and configuring only the connection between CallPath Server for OS/2 and the DMS-100 CO switch. Additional hardware and software is required, based on the applications and the networking environment used by the CallPath Server for OS/2 client workstations. See the CallPath Server Planning, Installation, and Problem Determination Guide for more information. Before You Begin Contact your DMS-100 CO switch representative to have the DMS-100 CO switch hardware and software installed. You also need to contact your switch representative to obtain the following information for each switch connection: * CCITT compliance date (1980 or 1984) * Local DTE address * Remote DTE address * The following switch logon parameters: o Network Node ID o Service ID o Service Version (BCS level) o Business Group ID o Application ID o Logon password The workspace in Table 2 provides space for you to record this information. You will also need to know whether you are running on a point-to-point connection or a public packet network connection. If the first CallPath Server for OS/2 installation diskette contains a README or a TIPS file, read them before installing CallPath Server for OS/2. Table 2. DMS-100 CO Switch Workspace Parameter Worksheet for CallPath Server for OS/2 Description Switch Connection 1 Switch Connection 2 Description Network Node ID Service ID Description Service Version (BCS level) Business Group ID Application ID Slot Number Directory Entry Name (LOCAL) Local Address Directory Entry Name (REMOTE) Remote Address Logon Password* Note: *You may want to leave the password field blank, depending on security requirements. --------------------------------------------------------------------------- Summary of Installation Steps Following is an overview of the procedure for installing and configuring CallPath Server for OS/2 and communication links with the DMS-100 CO switch: Step 1: Installing and configuring OS/2 Step 2: Installing and configuring TCP/IP hardware and software Step 3: Installing CallPath Server for OS/2 and Other CallPath Components Step 4: Restarting the CallPath Server for OS/2 computer Step 5: Starting the CallPath Server Management Facility and configuring CallPath Server for OS/2 Step 6: Installing and configuring the X.25 Interface Co-Processor adapter(s) for switch communications Step 7: Restarting the CallPath Server for OS/2 computer Step 8: Starting CallPath Server for OS/2 and the DMS-100 CO switch connection(s) This procedure is described in detail in the following sections. --------------------------------------------------------------------------- Step 1: Installing and Configuring OS/2 Make sure that OS/2 is installed and running before attempting to install CallPath Server for OS/2. Note: Install the latest Corrective Services Diskettes (CSDs) for OS/2. --------------------------------------------------------------------------- Step 2: Installing and Configuring TCP/IP Hardware and Software Install and configure TCP/IP for the communications between CallPath Server for OS/2 and the client workstations. Different procedures are required for TCP/IP installation and configuration depending on your operating environment. * See "Installing and Configuring TCP/IP Hardware and Software for a Networked Server" for information about installing and configuring TCP/IP in a network environment. * See "Installing and Configuring TCP/IP Hardware and Software for a Stand-Alone Server" for information about installing and configuring TCP/IP in a stand-alone environment. Continue with "Installing and Configuring TCP/IP Hardware and Software for a Networked Server". Installing and Configuring TCP/IP Hardware and Software for a Networked Server After installing OS/2, install the networking hardware and install and configure TCP/IP for communications between the CallPath Server for OS/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. Continue with "Installing and Configuring TCP/IP Hardware and Software for a Stand-Alone Server". Installing and Configuring TCP/IP Hardware and Software for a Stand-Alone Server When installing TCP/IP, use the following procedure: 1. If given the option, do not select to install LAPS (or MPTS). 2. If given the option, do not select to Configure Network Connection. 3. Select to autostart the PortMapper from the TCP/IP configuration so that it will start whenever OS/2 is started. 4. 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 in the remaining steps. To select the loopback interface, do the following: 1. Change to the \bin directory. 2. 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 5. 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: 1. Change to the \etc directory. 2. 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. --------------------------------------------------------------------------- Step 3: Installing CallPath Server for OS/2 and Other CallPath Components The installation program copies selected CallPath Components 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 also backs up the CONFIG.SYS file. To install CallPath Server for OS/2 and other CallPath Components, do the following: 1. Follow the instructions provided on the information jacket that comes with the distribution media. It has instructions for accessing the CD-ROM and initializing the installation process. You will be prompted to install one or more of the following CallPath Components: o Server o CallPath Developers Toolkit 2. When the Installation Options window is displayed on your screen, only the CallPath Components you selected from the CD are listed. Click on OK to start installation of those components. 3. When prompted, enter the target directory, including the drive letter and path, where you want CallPath installed. The directory you select will be appended with a subdirectory called csasrvr for the Server and csatk for the CallPath Developers Toolkit. Notes: 1. If the selected disk has insufficient disk space, you will be prompted to select another. 2. If you are reinstalling CallPath Server Version 2.1 over an earlier version, but you want to retain the current switch level, you must first uninstall the previous CallPath Developers Toolkit and then uninstall CallPath Server for OS/2, in that order. This is necessary to accommodate the new directory structure of CallPath Server Version 2. You can also select the All Component option which uninstalls all components. If you do, be sure to backup your customized or modified configuration files. When the installation is complete, your Server folder will contain the following items: * The CallPath Server Management Facility * A README file * An install history file Note: If the installation program stops because it detected an error condition, and the error cannot be corrected, record the error message and exit the installation. Once you have corrected the error condition, re-install the component. Most errors will also be displayed by selecting the Display Install History option. --------------------------------------------------------------------------- Step 4: Restarting the CallPath Server for OS/2 Computer To activate the CallPath Server for OS/2 installation, restart the CallPath Server for OS/2 computer. --------------------------------------------------------------------------- Step 5: Starting the CallPath Server Management Facility and Configuring CallPath Server for OS/2 Following is an overview of the tasks required for starting the CallPath Server Management Facility and configuring CallPath Server for OS/2: * Starting the CallPath Server Management Facility * Configuring CallPath Server for OS/2 * Starting the CallPath Server for OS/2 subsystem to confirm that the CallPath Server for OS/2 configuration works These tasks are described in more detail in the following sections. Starting the CallPath Server for OS/2 Management Facility 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 icon on the OS/2 desktop and then double-click on the CallPath Server for OS/2 icon. Once CallPath Server for OS/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. Continue with "Configuring CallPath Server for OS/2 (Minimal Configuration)". Configuring CallPath Server for OS/2 (Minimal Configuration) CallPath Server for OS/2 requires the following operating parameters before it can communicate with client applications: * Maximum number of applications capable of connecting to the server at the same time * Maximum number of concurrent users of CallPath Server for OS/2 To configure CallPath Server for OS/2, do the following: 1. Display the Set Server Configuration window, in one of the following ways: o From the CallPath Server Management Facility menu bar: 1. Select the Configuration menu. 2. Select the Server menu option. o From the CallPath Server icon: 1. Select the CallPath Server icon using the mouse menu button. 2. Select Configuration. 2. Enter new maximum values for the following fields. (See the CallPath Server Planning, Installation, and Problem Determination Guide for information about tuning the CallPath Server for OS/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 from IBM. Contact your purchasing organization if you do not know this number. 3. Click on OK to accept the CallPath Server for OS/2 configuration values. The new configuration values take effect the next time CallPath Server for OS/2 is started. Starting the CallPath Server for OS/2 Subsystem After starting the CallPath Server Management Facility, start the CallPath Server for OS/2 subsystem in one of the following ways: * From the CallPath Server Management Facility window: 1. Select the Administration menu option from the menu bar. 2. Select the Server menu option. 3. Select Start. 4. Click on one of the following in response to the confirmation message: + Yes to start the CallPath Server subsystem + No to return to the CallPath Server Management Facility window without starting the CallPath Server subsystem 5. Select Yes from the confirmation message window. * From the CallPath Server icon: 1. Click on the CallPath Server icon. 2. Select Start. 3. Click on one of the following in response to the confirmation message: + Yes to start the CallPath Server subsystem + No to return to the CallPath Server Management Facility window without starting the CallPath Server subsystem --------------------------------------------------------------------------- Step 6: Installing and Configuring the X.25 Interface Co-Processor Adapter for Switch Communications Following is an overview of the tasks required for installing and configuring the X.25 Interface co-processor adapter(s) for communications between CallPath Server for OS/2 and the DMS-100 CO switch: * Installing one or more X.25 Interface co-processor adapters * Configuring one or more X.25 Interface co-processor adapters * Installing Communications Manager/2 * Creating the X.25 link for each co-processor adapter * Creating the X.25 directory entries for each co-processor adapter * Verifying the profile * Installing the DMS-100 switch-dependent code feature * Configuring the DMS-100 CO switch connection(s) in CallPath Server for OS/2 These tasks are described in more detail in the following sections. Installing One or More X.25 Interface Co-Processor Adapters X.25 Interface co-processor adapter cards provide the communication channel or channels between the DMS-100 CO switch and Server/2. Install the X.25 co-processor adapter that is appropriate for your machine architecture, according to the instructions supplied with the co-processor adapter. Record the slot number in which you install the X.25 Interface co-processor adapter for use when configuring the X.25 link. Continue with "Configuring One or More X.25 Interface Co-Processor Adapters". Configuring One or More X.25 Interface Co-Processor Adapters Refer to the documentation that accompanied your machine for information about configuring the co-processor adapter. Continue with "Installing Communications Manager/2". Installing Communications Manager/2 Install Communications Manager/2 by following the instructions in the Communications Manager Version 1.1 Workstation Installation and Configuration Guide Default configuration files are provided with CallPath Server for OS/2. To use one of these default files, do the following during Communications Manager/2 installation: 1. When the Open Configuration window is displayed, select C: under Directories. 2. Select the CSASRVR directory. 3. Under Configurations, select one of the following configuration files based on the network adapter installed in the CallPath Server for OS/2 PC: CPSVTRCM Token ring configuration file CPSVETCM Ethernet configuration file 4. Continue with configuration until the Communications Manager Configuration Definition window is displayed. 5. Open a new OS/2 command window. 6. Insert the backup copy of the X.25 and Multiport/2 Option diskette in Drive A. 7. At the OS/2 command prompt, enter the following command: copy a:icaaim.com c:\cmlib 8. Return to the Communications Manager Configuration Definition window. 9. Select X.25 in the Workstation Connection Type list box. 10. Select X.25 APIs in the Feature or Application list box. 11. Click on Configure. The Communications Manager Profile List window is displayed. Continue with "Creating the X.25 Links". Creating the X.25 Links If you did not record the slot numbers in which you installed the X.25 Interface co-processor adapters, do so now before continuing. The slot numbers will be used to identify each X.25 link in the following procedure. (The numbers are listed on the back panel.) To create the X.25 links from the Communications Manager Profile List window, do the following: 1. Select X.25 Links. The X.25 Links window is displayed. 2. Select Configure.... 3. Select Create... to create a profile. The X.25 Link Parameters window is displayed. 4. Edit the profile, providing the following settings: Link name NTIx, where x (which can be 1-8) is the slot number in which the X.25 Interface co-processor adapter was installed. Adapter type X.25 Slot number Number of the slot where the X.25 card is installed in your PC. (The numbers are listed on the back panel.) Network type 1 Local CCITT compliance Either 1980 or 1984. The entry must match DMS-100 table MPCLINK. Link setup mode Initiate from DTE. Local DTE address The address by which the switch recognizes CallPath Server/2. (The entry must match the address the DMS-100 has for CallPath Server for OS/2.) Optional comment You supply the comment. 5. From the Additional parameters list, select Virtual Circuit Ranges, then select Change. 6. Edit the parameters, providing the following settings: In-only SVCs Number of Virtual Circuits = 0 Lowest Logical Channel Number = not accessible Two-Way SVCs Number of Virtual Circuits = 1 Lowest Logical Channel Number = 1 Out-only SVCs Number of Virtual Circuits = 0 Lowest Logical Channel Number = not accessible 7. Select OK. 8. Select Frame values from the Additional parameters list, then select Change. The Frame Values window is displayed. 9. Edit the frame values, providing the following settings: Frame sequence modulo 8 Window size 7 T1 - Frame retransmission timeout In the range of 5000-15000. This value is in milliseconds. It provides adequate time before generating a clear request that causes the switch session to be terminated. Note: Check with your switch administrator for the retransmission timeout value set by the switch. The T1 value must not be less than that provided by the switch. To calculate the T1 value, multiply the switch retransmission timeout, in seconds, by 1000. For example, if the switch T1 timeout is set to 12 seconds, the T1 value on the CallPath Server/2 machine should be 12000 or more. N2 - Frame transmission attempt count 10 T4 - Inoperational timeout (seconds) Set to value that the DMS-100 CO switch uses. Typical value is 25 (for the United States) or 10 (for Canada). 10. Select OK. 11. Select SVC/PVC packet sizes from the Additional parameters list, then select Change. The SVC/PVC Packet Sizes window appears. 12. Edit the parameters, providing the following settings: SVC maximum Incoming=128, Outgoing=128 SVC default Incoming=128, Outgoing=128 PVC default Incoming=128, Outgoing=128 13. Select OK. 14. Select SVC/PVC window sizes in the Additional parameters list, then select Change. The SVC/PVC Window Sizes window is displayed. Ask your switch administrator whether your connection is a point-to-point or a public packet network connection. 15. Do one of the following: o If this is a point-to-point connection, set all SVC sizes to 7. o If this is a public packet network connection, set all SVC sizes to 2. 16. Select OK. 17. Select Modem parameters from the Additional parameters list, then select Change. 18. Edit the parameters, providing the following settings: Use Transpac VX32 modem Leave unselected Operation mode DTE Initial mode of links Connect 19. Select OK. 20. Select OK on the X.25 Link Parameters window. 21. Select Close on the X.25 Links window. Repeat this procedure for each X.25 Interface co-processor adapter installed in the CallPath Server for OS/2 computer. Continue with "Creating the X.25 Directory Entries". Creating the X.25 Directory Entries To create the X.25 directory entries for the Communications Manager Profile List window, do the following: 1. Select X.25 Directory Entries, then select Configure. 2. Select Create in the X.25 Directory Entries window. 3. Edit the fields, providing the following settings: Directory entry name SERVERx, where x is the slot in which the X.25 Interface co-processor adapter was installed. Directory entry LOCAL 4. Select OK. The X.25 Local Directories window is displayed. 5. Select Create. The Local Directory Entry window is displayed. 6. Edit the fields, providing the following settings: Link name NTIx, where x is the slot number in which the X.25 Interface co-processor adapter was installed. This value must be the same as the value entered in Step 4. Local address The address by which the switch recognizes CallPath Server for OS/2. (The entry must match the "REMDNA" field in the DMS-100 table SCAICOMS.) Local address extension Leave blank 7. Select OK. 8. Enter a comment in the Optional comment field if you want. 9. Select OK. The X.25 Directory Entries window is displayed. 10. Select Create. The Create Directory Entry window is displayed. 11. Edit the fields, providing the following settings: Directory entry name DMSx, where x is the slot number in which the X.25 Interface co-processor adapter was installed Directory entry Remote Remote type Non-SNA Virtual circuit type SVC 12. Select OK. The Non-SNA SVC Directory Entry Window is displayed. 13. Edit the fields, providing the following settings: Link name NTIx, where x is a value from 1-8 that matches the value for NTIx entered in Step 4. Remote DTE address The address by which the switch identifies itself. This value must match the DMS-100 table MPCLINK field EXINFO (SVCDNA). Optional remote DTE address extension Optional field--leave blank. Optional comment You supply the comment. 14. Select OK. The X.25 Directory Entries window is displayed. 15. Select Close. The Communications Manager Profile List window is displayed. 16. Select Close. The Communications Manager Configuration Profile List window is displayed. Repeat "Creating the X.25 Links" and "Creating the X.25 Directory Entries" for each X.25 Interface co-processor adapter installed. Continue with "Verifying the Profile". Verifying the Profile To verify the profile, do the following: 1. Select Close from the Communications Manager Profile List window. 2. Select Close from the Communications Manager Configuration Definition - X.25 window. The verification program will check the configuration file for inconsistencies. If the program detects any errors, a message will inform you that an error exists. You can view the Communications Manager/2 error log to help determine the cause of the error. You should check that you entered the correct values in each of the profiles and that the names match those provided in this installation procedure. 3. If you are prompted to install additional features or to change CONFIG.SYS, select OK. 4. Insert any additional diskettes that are needed by the new profiles. If the edited configuration is the active configuration, you are asked whether the changes are to be made dynamically (without stopping Communications Manager/2). 5. Select Yes to activate the changes. The Communications Manager Setup window appears. 6. Select Close. 7. To ensure that Communications Manager is started when the PC running CallPath Server for OS/2 is restarted, add the following line to the STARTUP.CMD file: START CM 8. Remove any diskettes from the drive, shutdown, and restart the system. Continue with "Installing the DMS-100 CO Switch-Dependent Code Feature". Installing the DMS-100 CO Switch-Dependent Code Feature Use the CallPath Server for OS/2 Installation Utility to install the DMS-100 CO switch-dependent code feature on the PC running CallPath Server for OS/2. To install the DMS-100 CO switch switch-dependent code feature, do the following: 1. (For diskette installation only) Insert CallPath Server for OS/2 product diskette 1 in the source disk drive. 2. At the OS/2 command prompt, enter :install, where is one of the following: o Drive letter of the diskette drive containing product diskette 1 o Drive letter and path where CallPath Server for OS/2 files were previously installed The Installation Options window is displayed that lets you select the CallPath Server for OS/2 installation options. 3. Select Switch Dependent to install the DMS-100 CO switch-dependent code feature. Notes: 1. CallPath Server for OS/2 must be installed before you install the DMS-100 CO switch-dependent code feature. 2. Click on OK to accept the selection. 3. Follow the prompts. Continue with "Configuring the DMS-100 CO Switch Connection(s)". Configuring the DMS-100 CO Switch Connection(s) Use the information recorded in Table 2 when performing the procedure that follows. Before CallPath Server for OS/2 can communicate with the DMS-100 CO switch, the switch connection must be configured in CallPath Server for OS/2: Switch description The name to be used in the CallPath Server Management Facility for the DMS-100 CO switch connection. Auto-start Whether CallPath Server for OS/2 should start communications with the DMS-100 CO switch automatically when the CallPath Server for OS/2 subsystem is started. Restart on failure Whether CallPath Server for OS/2 should restart communications with the DMS-100 CO switch automatically after a fatal error has terminated communications between CallPath Server for OS/2 and the switch. Switch parameters The following information is required: o Switch password for the given Business Group ID o Network Node ID o Service ID o Service Version (BCS level) o Business Group ID o Application ID o Local Directory Entry o Remote Directory Entry Obtain the first six switch logon parameters from your switch administrator. The last two values correspond to the directory entry name (local, see step 3) and directory entry name (remote, see step 11), respectively, as defined when installing and configuring the X.25 adapter. To configure the DMS-100 CO switch in CallPath Server for OS/2 for a local connection, do the following: 1. Start CallPath Server Management Facility. See "Starting the CallPath Server for OS/2 Management Facility" for instructions. 2. Display the CallPath Server Management Facility Set Switch Configuration window in one of the following ways: o From the CallPath Server Management Facility menu bar: 1. Select the Configuration menu. 2. Select the Switch Connection menu option. 3. Select On file. 4. Select the switch from the scrollable list box. o From the switch icon: 1. Click on the Switch icon using the mouse menu button. 2. Select the Configuration option. 3. Select On file. 4. Select DMS-100 from the scrollable list box. 3. Type the description for the switch in the Switch description field. 4. Select Auto-start if you want DMS-100 CO switch to start automatically when the CallPath Server for OS/2 subsystem starts. 5. Select Restart on failure if you want the DMS-100 CO switch to restart when there is a failure in communications between it and CallPath Server for OS/2. 6. Click on the Switch type field. 7. Click on DMS-100. 8. Click on one of the following: o OK to save the configuration information and return to the CallPath Server Management Facility after setting the DMS-100 CO switch logon parameters o Apply to save the configuration information and return to the Set Switch Configuration window after setting the DMS-100 CO switch logon parameters The Enter Switch Configuration Data window shown in Figure 3 is displayed. Figure 3. Enter Switch Configuration Data Window [Image] View figure. 9. Complete the following fields if they need to be modified: Network Node ID Identifies this DMS-100 CO switch. The range of values is 0 to 32767. Service ID Identifies the service profile for this DMS-100 CO switch. The range of values is 0 to 255. BCS Version (level) of service that the DMS-100 CO switch and CallPath Server for OS/2 are operating under. Acceptable values are in the range of 33-36. Notes: 1. If the switch load is more than two levels higher than the BCS level used in the logon parameters, the switch will not accept it. For example, if the switch is set at level 36 and the BCS logon parameter is set at level 33, the switch will reject the logon. 2. The Level 36 function, DV_SET_FEATURE (log on, log off, ready, and not ready), is supported. Further, the switch event messages indicating the status of the agent are flowed to the application. The BCS level must be set to 36 to implement this request. 3. Multiple-link capability using BCS level 35 and 36 is not supported. 4. The BCS level must be set to 35 or 36 to implement the Query_ACD_Information request. Business Group ID Identifies your switch within the public telephone network. Your switch administrator has the value assigned to you by the telephone company. Application ID Identifier for the host application program to be run. The range of values is 1 to 32,767. Slot number Not used for CallPath Server for OS/2. Local Directory Entry Name established when creating the X.25 directory entries for the local directory entry. This field must match the name used in Step 3 and is case sensitive. Remote Directory Entry Name established when creating the X.25 directory entries for the remote directory entry. This field must match the name used in Step 11 and is case sensitive. Enter Password The password assigned to the specified business group for this DMS-100 CO switch. Your switch administrator has the 1-to-8 character password. Use uppercase for all alphabetic characters in the password. Note: You do not have to change the DMS-100 CO switch password unless the switch administrator has changed it for the DMS-100 CO switch for the given business group or if the password has never been entered. Verify Password The current password again to confirm that you typed it correctly in the "Enter Password" field. Leave blank if "Enter Password" field was left blank. 10. Click on OK. Either the CallPath Server Management Facility or the Set Switch Configuration window is displayed, depending on your selection in Step 8. 11. Repeat this procedure for each switch connection starting with Step 2. --------------------------------------------------------------------------- Step 7: Restarting the CallPath Server for OS/2 Computer After configuring the X.25 communications and the switch, exit CallPath Server Management Facility, and restart your CallPath Server for OS/2 machine. --------------------------------------------------------------------------- Step 8: Starting CallPath Server for OS/2 and the DMS-100 CO Switch Connection(s) Following is an overview of the tasks required for starting the CallPath Server for OS/2 and the DMS-100 CO switch connection(s): * Start the CallPath Server Management Facility * Start the CallPath Server for OS/2 subsystem * Start the DMS-100 CO switch connection(s) 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. Starting the CallPath Server Management Facility 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 icon on the OS/2 desktop and then double-click on the CallPath Server for OS/2 icon. Once CallPath Server for OS/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. Continue with "Starting the CallPath Server for OS/2 Subsystem". Starting the CallPath Server for OS/2 Subsystem After starting the CallPath Server Management Facility, start the CallPath Server for OS/2 subsystem in one of the following ways: * From the CallPath Server Management Facility window: 1. Select the Administration menu from the menu bar. 2. Select the Server menu option. 3. Select Start. 4. Click on one of the following in response to the confirmation message: + Yes to start the CallPath Server for OS/2 subsystem + No to return to the CallPath Server Management Facility window without starting the CallPath Server for OS/2 subsystem 5. Select Yes from the confirmation message window. * From the CallPath Server icon: 1. Click on the CallPath Server icon. 2. Select Start. 3. Click on one of the following in response to the confirmation message: + Yes to start the CallPath Server for OS/2 subsystem + No to return to the CallPath Server Management Facility window without starting the CallPath Server for OS/2 subsystem Continue with "Starting the DMS-100 CO Switch Connection(s)". Starting the DMS-100 CO Switch Connection(s) After starting the CallPath Server for OS/2 subsystem, start your DMS-100 CO switch connection in one of the following ways: * From the CallPath Server Management Facility window menu bar: 1. Select the Administration menu. 2. Select the Switch Connection menu option. 3. Select Start. 4. Select the switch. 5. 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: 1. Click on the Switch icon. 2. Select Start. 3. 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 Repeat one of the above procedures for each switch connection you want to start. Multiple Logons Using the Same Service ID Multiple logons to a single business group using the same service ID cause unpredictable results and are not supported by this program. If multiple logons occur, the switch response to a request is sent to the next available server link instead of being sent to the server making the request. This causes the call state model to be out of synchronization and the server stops due to a critical error. To avoid such an error, log on to a business group using the same service ID for only one switch link at a time. This means that any switch session logon to a given business group using a given service ID must be stopped before a different logon to the same business group using the same service ID can be attempted. For example, switch session SWITCH01 and switch session SWITCH02 each have the same password and the same service ID and both are enabled to log on to the same business group. If switch session SWITCH01 is active, but you want to start an application that uses switch session SWITCH02, switch session SWITCH01 must be stopped first. This is true even if switch session SWITCH01 has no traffic. Switch links SWITCH01 and SWITCH02 cannot be simultaneously active. Note: This limitation is true for any combination of SwitchServer/2, CallPath Server/2, and CallPath Server/6000 link sessions that can log on to the same business group. It is recommended that switch sessions avoid overlapping. Multiple Logons Using Different Service IDs The switch can be configured to enable independent logons to a business group using different service IDs for each logon. The switch considers these to be independent sessions. :p The first session to execute an association (that is, monitoring) of a primary ACD-DN or Centrex DN has exclusive event messaging for that resource. All events concerning that resource remain within the link established during that session. If a session ends for any reason (such as the failure of an X.25 link) any remaining session can execute an association with the orphaned resource. The switch enables up to eight sessions for each business group. Each session requires a unique service ID. This process partitions a business group into unique and independent sub-business groups. The Server supports this independent, simultaneous, switch session environment. --------------------------------------------------------------------------- Chapter 4. Installing and Configuring CallPath Server for AIX This chapter provides installation and configuration information for the DMS-100 CO switch hardware and software that is used with the CallPath Server for AIX program product. Note: If you want to install CallPath SwitchServer/2 for a remote connection to the DMS-100 CO switch, see Chapter 2. "Installing and Configuring CallPath SwitchServer/2". If you want to install CallPath Server for OS/2 for either a direct connection to the DMS-100 CO switch or as a host, see Chapter 3. "Installing and Configuring CallPath Server for OS/2". If you want to install CallPath Server for MS Windows NT for either a direct connection to the DMS-100 CO switch or as a host, see Chapter 3. "Installing and Configuring CallPath Server for OS/2". Also included in this chapter are lists of the additional hardware and software that is required for the local (direct physical) connection of CallPath Server for AIX to the DMS-100 CO switch. Use these instructions with the installation instructions in the CallPath Server Planning, Installation, and Problem Determination Guide --------------------------------------------------------------------------- DMS-100 Switch Configuration The following figure shows the hardware configuration for the DMS-100 CO switch connection to CallPath Server for AIX. Figure 4. DMS-100 CO Switch Connection to CallPath Server for AIX [Image] View figure. DMS-100 Switch Hardware and Software Requirements To use the DMS-100 CO switch with CallPath Server for AIX, the following hardware and software are required: Hardware Requirements A DMS-100 CO switch with the following: o ACD feature o CompuCall feature Refer to the Nortel Feature Planning Guide 50004.1/01-92 or later. Also contact your Nortel installation agent for installation, configuration, and upgrade changes to your DMS-100 CO switch hardware. Software Requirements DMS-100 CO switch software requirements are installation specific: o Refer to the Nortel Feature Planning Guide 50004.1/01-92 or later for the BCS33 through BCS36 levels of the CompuCall feature. o Contact your Nortel installation agent for installation, configuration, and upgrade changes to your DMS-100 CO switch software. CallPath Server for AIX Hardware and Software Requirements To use CallPath Server for AIX in a local connection to the DMS-100 CO switch, the following hardware and software are required in addition to the base CallPath Server/6000 hardware and software requirements that are described in the Planning, Installation, and Problem Determination Guide Hardware Requirements Both of the following for each active connection (up to 3 active connections are supported): o IBM X.25 Interface Co-Processor/2 adapter (feature number 2960) o A connection from the CallPath Server for AIX to the DMS-100 CO switch using an IBM X.25 Interface Co-Processor/2 cable option V.35 or cable option V.24 Software Requirements The following software is required for implementing the CallPath Server for AIX and CallPath Developers Toolkit packages with DMS-100 CO switch: o AIX Version 3.2.5 (or higher) for RISC System/6000 Note: These requirements are for installing and configuring only the connection between CallPath Server for AIX and DMS-100 CO switch. Additional hardware and software are required, based on the applications and the networking environment used by the CallPath Server for AIX client workstations. See the CallPath Server Planning, Installation, and Problem Determination Guide for more information. Before You Begin Contact your DMS-100 CO switch representative to have the DMS-100 CO switch hardware and software installed. You also need to contact your switch representative to obtain the following information: * CCITT compliance date for the switch (1980 or 1984) * Local DTE address * Remote DTE address * The following switch log-on parameters: o Network Node ID o Service ID o Service Version (BCS level) o Business Group ID o Application ID o Logon password (for the given Business Group ID) The workspace in Table 3 provides space for you to record this information. You will also need to know whether you are running on a point-to-point connection or a public packet network connection. If the first CallPath Server for AIX installation diskette contains a README or a TIPS file, read them before installing CallPath Server for AIX. Table 3. DMS-100 CO Switch Workspace Parameter Worksheet for CallPath Server for AIX Switch Connection Switch Connection Switch Connection Description 1 2 3 Description X.25 Port (01-04) X.25s Number (0-3) Network Node ID Service ID Description Service Version (BCS level) Business Group ID Application ID Slot Number Local Address Remote Address Logon Password* Note: *You may want to leave the password field blank, depending on security requirements. --------------------------------------------------------------------------- Summary of Installation Steps Following is an overview of the procedure for installing and configuring CallPath Server for AIX and communication links with the DMS-100 CO switch: Step 1: Installing and Configuring AIX Step 2: Installing and configuring TCP/IP hardware and software Step 3: Installing or Updating CallPath Server for AIX and Other CallPath Components Step 4: Starting the CallPath Server Management Facility and configuring CallPath Server for AIX Step 5: Installing and configuring one or more X.25 Interface Co-Processor/2 adapters for switch communications Step 6: Starting CallPath Server for AIX and the DMS-100 CO switch connection This procedure is described in detail in the following sections. --------------------------------------------------------------------------- Step 1: Installing and Configuring AIX Make sure that AIX is installed and running before attempting to install CallPath Server for AIX. --------------------------------------------------------------------------- Step 2: Installing and Configuring TCP/IP Hardware and Software Install and configure TCP/IP for the communications between CallPath Server for AIX and the client workstations. Different procedures are required for TCP/IP installation and configuration depending on your operating environment. * See "Installing and Configuring TCP/IP Hardware and Software for a Networked Server" for information on installing and configuring TCP/IP in a network environment. * See "Installing and Configuring TCP/IP Hardware and Software for a Stand-Alone Server" for information on installing and configuring TCP/IP in a stand-alone environment. Continue with "Installing and Configuring TCP/IP Hardware and Software for a Networked Server". Installing and Configuring TCP/IP Hardware and Software for a Networked Server After installing AIX, install the networking hardware and configure TCP/IP for communications between the CallPath Server for AIX computer and the client workstations. Continue with "Installing and Configuring TCP/IP Hardware and Software for a Stand-Alone Server". Installing and Configuring TCP/IP Hardware and Software for a Stand-Alone Server The TCP/IP product is packaged with the AIX operating system. The system has the loopback address and alias host name preconfigured. The alias for the default loopback address 127.0.0.1 is the localhost. To configure your system to use the loopback address, do the following: 1. Log on to AIX as root. 2. Start SMIT 3. Select Communications Applications and Services. 4. Select TCP/IP. 5. Select Further Configuration 6. Select Hostname. 7. Enter localhost as the hostname. 8. Exit SMIT. --------------------------------------------------------------------------- Step 3: Installing or Updating CallPath Server for AIX and Other CallPath Components CallPath Server for AIX and the CallPath Developers Toolkit, are provided in installp format, the AIX-standard automatic installation format. Refer to AIX Version 4.1 Commands Reference for more information on installp. Only a person with root or administrator authority can install CallPath. To install or update CallPath Server for AIX, do the following: 1. Ensure that CallPath Server/6000 is not already running before installing it. If you attempt to install CallPath Server/6000 while it is already running, the installation will be aborted. You will be prompted with recovery instructions. 2. Follow the instructions provided on the information jacket that comes with the distribution media. It has instructions for accessing the CD-ROM and initializing the installation process. You will be prompted to specify where on your hard disk you want to store the CallPath Server installation image. After the image is stored on your hard disk, use SMIT to complete the installation or change to the subdirectory where you copied csasrvr.obj and use the following command to install it: installp -aXF -d./ csasrvr.obj 3. If CallPath Server for AIX is already installed, make sure it is committed by entering the following command: installp -c csasrvr.obj If this is the first installation, do the following: * Add the following to the user's .profile file: export CSA_DIR=/usr/lpp/csasrvr * Set up security * Add the following to the users' path variable: /usr/lpp/csasrvr/bin If you are reinstalling CallPath Server Version 2.1 over an earlier version, but you want to retain the current switch level, you must first uninstall the previous CallPath Developers Toolkit. This is necessary to accommodate the new directory structure of CallPath Server Version 2. Note: Uninstalling CallPath Server for AIX automatically uninstalls the Server, the Toolkit and the switch-dependent code. Installing or Updating CallPath Developers Toolkit for AIX To install or update CallPath Developers Toolkit for AIX, do the following: 1. Follow the instructions provided on the information jacket that comes with the distribution media. It has instructions for accessing the CD-ROM and initializing the installation process. You will be prompted to specify where on your hard disk you want to store the CallPath Developers Toolkit for AIX installation image. After the image is stored on your hard disk, use SMIT to complete the installation or change to the subdirectory where you copied csatk.obj and use the following command to install it: installp -aXF -d./ csatk.obj 2. If the CallPath Developers Toolkit for AIX is already installed, make sure it is committed by entering the following command: installp -c csatk.obj If this is the first installation, do the following: * Set up security * Add the following to the users' path variable: /usr/lpp/csatk/bin --------------------------------------------------------------------------- Step 4: Starting the CallPath Server Management Facility and Configuring CallPath Server for AIX Following is an overview of the tasks required for starting the CallPath Server Management Facility and configuring CallPath Server for AIX: * Starting the CallPath Server Management Facility * Configuring CallPath Server for AIX * Starting the CallPath Server for AIX subsystem to confirm that the CallPath Server for AIX configuration works These tasks are described in more detail in the following sections. Starting the CallPath Server for AIX Management Facility You can start the CallPath Server for AIX Management Facility in one of the following ways: * Starting the CallPath Server for AIX Management Facility from the system prompt: To start the CallPath Server for AIX Management Facility from the system prompt, do the following: 1. Log onto the system as root or as an authorized group. 2. Enter the following command: cd /usr/lpp/csasrvr/bin 3. Enter csasrvr. * Starting the CallPath Server for AIX Management Facility from SMIT: SMIT can be run in either MOTIF**asterisk. (using X-Windows** and a mouse) MOTIF CallPath Server Management Facility windows and screens. If you run CallPath Server for AIX on an Xstation and use MOTIF, but would like to use SMIT in character mode, enter smit -C csasrvr on the command line. This temporarily changes SMIT from MOTIF to character mode. See the CallPath Server Planning, Installation, and Problem Determination Guide for sample CallPath Server Management Facility screens in character mode. To start the CallPath Server for AIX Management Facility from SMIT, do the following: 1. Log onto the system as root or as an authorized group. 2. Enter smit at the system prompt. 3. Select Communications Applications and Services from the System Management menu. Note: SMIT provides fastpath commands that take you directly to a SMIT panel without making individual menu selections. 4. Select CallPath Server for AIX. Once CallPath Server for AIX is started, the CallPath Server Management Facility window and the Product Information window are displayed. Click on OK to clear the Product Information window. 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, do the following: 1. Type the password, then click on OK. Note: The default password, until you change it, is password. If you use SMIT, there is no Administrative Password window and hence, no password. 2. Click on OK in the CallPath Server Management Facility Product Information window to access the CallPath Server Management Facility window. Configuring CallPath Server for AIX (Minimal Configuration) CallPath Server for AIX requires the following operating parameters before it can communicate with client applications: * Maximum number of applications capable of connecting to the server at the same time * Maximum number of concurrent users allowed to access CallPath Server for AIX To configure CallPath Server for AIX, do the following: 1. Display the Set Server Configuration window in one of the following ways: o From the CallPath Server Management Facility menu bar: 1. Select the Configuration menu. 2. Select the Server menu option. o From the CallPath Server icon: 1. Select the CallPath Server icon using the mouse menu button. 2. Select Configuration. 2. 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 for AIX 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 from IBM. Contact your purchasing organization if you do not know this number. 3. Click on OK to accept the CallPath Server for AIX configuration values. The new configuration values take effect the next time CallPath Server for AIX is started. Starting the CallPath Server for AIX Subsystem After starting the CallPath Server Management Facility, start the CallPath Server for AIX subsystem in one of the following ways: * From the CallPath Server Management Facility window: 1. Select the Administration menu from the menu bar. 2. Select the Server menu option. 3. Select Start. 4. Click on one of the following in response to the confirmation message: + Yes to start the CallPath Server subsystem + No to return to the CallPath Server Management Facility window without starting the CallPath Server subsystem 5. Select Yes from the confirmation message window. * From the CallPath Server icon: 1. Click on the CallPath Server icon. 2. Select Start. 3. Click on one of the following in response to the confirmation message: + Yes to start the CallPath Server subsystem + No to return to the CallPath Server Management Facility window without starting the CallPath Server subsystem --------------------------------------------------------------------------- Step 5: Installing and Configuring One or More X.25 Interface Co-Processor/2 Adapters for Switch Communications Following is an overview of the tasks required for installing and configuring the X.25 Interface Co-Processor/2 adapter(s) for communications between CallPath Server for AIX and the DMS-100 CO switch when using AIX Version 3.2.5. If you are using AIX Version 4.1, see Appendix B. "Installing and Configuring the X.25 Interface Adapter Using AIX Version 4.1". * Installing one or more X.25 Interface Co-Processor/2 adapters * Installing the DMS-100 CO switch-dependent code feature * Identifying the X.25 Interface Co-Processor/2 adapter to AIX * Configuring the Device Driver for each X.25 Interface Co-Processor/2 adapter by doing the following: o Adding the X.25 Device Driver o Associating each X.25 Interface Co-Processor/2 adapter with its device name o Configuring the device driver o Configuring the X.25 packet parameters o Configuring the X.25 frame parameters * Starting X.25 communication links between CallPath Server for AIX and DMS-100 CO switch * Configuring the DMS-100 CO switch connection(s) in CallPath Server for AIX These tasks are described in more detail in the following sections. Installing One or More X.25 Interface Co-Processor/2 Adapters X.25 Interface Co-Processor/2 adapters provide the communication channel between the DMS-100 CO switch and CallPath Server for AIX. Install the X.25 Co-Processor/2 adapter according to the instructions supplied with the co-processor adapter. Continue with "Installing DMS-100 CO Switch-Dependent Code Feature". Installing DMS-100 CO Switch-Dependent Code Feature DMS-100 CO switch-dependent code feature is provided in installp AIX Version 3.2: Commands Reference for more information about installp.) To install the DMS-100 CO switch-dependent code feature, AIX CallPath Server/6000 must first be installed, then do the following: 1. Log on as root. 2. Enter the following command: installp -aXF all Note: If previously installed software has not been committed, you will be prompted to do so. To commit existing code at any time, enter the following: installp -c csadms.obj 3. Respond to the prompts for inserting the DMS-100 CO switch-dependent code feature installation diskettes. 4. Set up security (see the CallPath Server Planning, Installation, and Problem Determination Guide for additional information on setting up security). 5. Give write permission to the following: /usr/lpp/csasrvr/switchdm/dmslogon.* 6. Give read and execute permission to the following: /usr/lpp/csasrvr/switchdm/* Continue with "Identifying the X.25 Interface Co-Processor/2 Adapter to AIX". Identifying the X.25 Interface Co-Processor/2 Adapter to AIX To identify the installed X.25 Interface Co-Processor/2 adapter to the AIX operating system, do the following: 1. Start the AIX RISC System/6000. 2. Log on as root. 3. Enter the following command at a system prompt to verify that the X.25 Interface Co-Processor/2 adapter is installed and available to the RISC System/6000 server: lsdev -C -H º grep ampx Note: ampx is the physical location of the adapter prior to setting up the X.25 communications. If an adapter is not listed, it is not recognized by AIX. The adapter is either bad or installed incorrectly. 4. Back up the X.25 and Multiport/2 Option diskette. 5. Insert the X.25 disk (64F2076) into the diskette drive. 6. Enter the following command to install the X.25 microcode: adfutil -m icaaim.com -q 7. Verify that the microcode has been installed in the correct directory by entering the following command: ls -l /etc/microcode/icaaim.com If the command does not result in the following display, go to Step 8. Otherwise, go to Step 9. -rw -r--r-- 1 root system filesize date /etc/microcode/icaaim.com 8. Enter the following commands: cd /etc/microcode chown root icaaim.com chgrp system icaaim.com chmod 644 icaaim.com Continue with Step 9. 9. Start SMIT. 10. Select Devices. 11. Select Configure Devices Added After IPL. 12. Click on Done. Continue with "Configuring the Device Driver for Each X.25 Interface Co-Processor/2 Adapter". Configuring the Device Driver for Each X.25 Interface Co-Processor/2 Adapter Repeat the following tasks for each X.25 Interface Co-Processor/2 adapter installed in the CallPath Server for AIX computer: * Adding the X.25 device driver * Associating each X.25 Interface Co-Processor/2 adapter with its device name * Configuring the device driver * Configuring the X.25 packet parameters * Configuring the X.25 frame parameters These procedures are described next. Adding the X.25 Device Driver To add the X.25 card device driver, do the following after starting SMIT: 1. Select Devices. 2. Select Communication. 3. Select X.25 Co-Processor/2 or Multiport Adapter. 4. Select Adapter. 5. Select Manage Device Drivers for X.25 Co-Processor/2 or Multiport/2 Adapters. 6. Select Manage X.25 Co-Processor/2 Device Driver. 7. Select Add a Device Driver. 8. If more than one device driver is displayed, select the one you want from the list box. 9. Select Network User Address. 10. Type in the server address in the "Network User Address" field. (The other fields should contain their default values and should not be changed.) This is the server's local address that will be recognized by the DMS-100 CO switch. 11. Select Do. 12. Select Done. 13. Select Cancel. Continue with "Associating Each X.25 Interface Co-Processor/2 Adapter with its Device Name". Associating Each X.25 Interface Co-Processor/2 Adapter with its Device Name You need to know the device name assigned to the X.25 Interface Co-Processor/2 adapter's physical address as you continue with the installation process. To determine the X.25 Interface Co-Processor/2 adapter's device name, open another window and enter the following command at a system prompt: lsdev -C -H -t x25s This command displays all the installed X.25 devices, their physical addresses, their device names, and their status. Write down the physical address and corresponding device name for each X.25 device. You will need this information later. It is suggested that the X.25 cable(s) be labeled with the Business Group ID or name for future reference. Continue with "Configuring the Device Driver". Configuring the Device Driver After adding the device driver for a card, do the following to configure the device driver: 1. Display the Manage X.25 Co-Processor/2 Device Drivers menu. If you exited SMIT before beginning this procedure, repeat Steps 1 through 6 in "Adding the X.25 Device Driver" or enter the following SMIT fastpath command to display the Manage X.25 Co-Processor/2 Device Drivers menu: smit x25a_dd 2. Select Change / Show Characteristics of a Device Driver from the Manage X.25 Co-Processor/2 Device Drivers menu. 3. Select Change / Show Network Parameters. Note: If more than one connection and board have been installed, a list box shows device drivers by device name (x25s#) and physical location from 00 to 0n where n is 1 to 4. Select the one you want to configure. 4. Change the contents of the displayed fields to reflect the values shown next: Device Name x25s# (# may be 0-9) Do not change this value. Network User Address (Value used when adding the Device Driver) Do not change this value. Lowest logical channel number for an incoming SVC 1 Number of logical channels for incoming SVCs 0 Lowest logical channel number for a two-way SVC 1 Number of logical channels for two-ways SVCs 1 Lowest logical channel number for an outgoing SVC 1 Number of logical channels for outgoing SVCs 0 Lowest logical channel number for a PVC 1 Number of PVCs 0 Auto-Call unit none 5. Select Do. 6. Select Done. 7. Select Cancel. Continue with "Configuring the X.25 Packet Parameters". Configuring the X.25 Packet Parameters After configuring the device driver for a card, do the following to configure the packet parameters: 1. Display the Manage X.25 Co-Processor/2 Device Drivers menu. If you exited SMIT before starting this procedure, repeat Steps 1 through 6 in "Adding the X.25 Device Driver" or enter the following SMIT fastpath command to display the Manage X.25 Co-Processor/2 Device Drivers menu: smit x25a_dd 2. Select Change / Show Packet Parameters from the Manage X.25 Co-Processor/2 Device Drivers menu. If more than one device driver has been installed, select the one you want from the list box that is displayed. 3. Change the contents of the displayed fields to reflect the values shown in the following list (which includes only the fields that need to be changed): CCITT Must be consistent with CCITT level of the switch, either 1980 or 1984 Packet modulo 8 Type of line DTE Default receive packet size 128 Default transmit packet size 128 Default receive packet window 7 Default transmit packet window 7 Maximum receive packet size 128 Maximum transmit packet size 128 Maximum receive packet window One of the following: 7 for point-to-point 2 for public packet network Note: Value must agree with DMS-100 CO administered value. Maximum transmit packet window One of the following: 7 for point-to-point 2 for public packet network Note: Value must agree with DMS-100 CO administered value. T21 timer 200 T22 timer 180 T23 timer 180 T24 timer 0 T25 timer 0 T26 timer 180 4. Select Do. 5. Select Done. 6. Select Cancel. Continue with "Configuring the X.25 Frame Parameters". Configuring the X.25 Frame Parameters After configuring the packet parameters for a card, do the following to configure the frame parameters: 1. Display the Manage X.25 Co-Processor/2 Device Drivers menu. To do this, repeat Steps 1 through 6 in "Adding the X.25 Device Driver" or enter the following SMIT fastpath command: smit x25a_dd 2. Select Change / Show Frame Parameters from the Manage X.25 Co-Processor/2 Device Drivers menu. If more than one device driver has been installed, select the one you want from the list box that is displayed. 3. Change the contents of the displayed fields to reflect the values shown in the following list (which includes only the fields that need to be changed): Frame window size 7 T1 timer In the range of 100-255. Each increment is a 50 millisecond block. This provides adequate time before generating a clear request that causes the switch session to be terminated. Note: Check with your switch administrator for the retransmission timeout value set by the switch. The T1 value must not be less than that provided by the switch. To calculate the T1 value, multiply the switch retransmission timeout, in seconds, by 20. For example, if the switch T1 timeout is set to 12 seconds, set the T1 value on the RISC System/6000 to 240 or more. The maximum T1 value is 255 or 12.75 seconds. T4 - Inoperational timeout (seconds) Set to value that the DMS-100 CO switch uses. Typical value is 25 (for the United States) or 10 (for Canada). N2 counter 10 4. Select Do. 5. Select Done. 6. Select Cancel. If you have more than one X.25 Interface Co-Processor/2 adapter to install, return to "Configuring the Device Driver for Each X.25 Interface Co-Processor/2 Adapter". Otherwise, continue with "Starting X.25 Communication Links between CallPath Server for AIX and the DMS-100 CO Switch"< /A>. Starting X.25 Communication Links between CallPath Server for AIX and the DMS-100 CO Switch Before a session with the switch can be started, the AIX operating system must connect the link to the switch using xmanage. The link you want to start must correspond to the switch session to be run. Starting the X.25 Communication Links After installing, adding and configuring the X.25 Co-Processor/2 Adapter card, enter the following command to start the communication links: cnctx25s. # where # is a digit from 0-9 and corresponds to device name x25s #. Note: The root session may be terminated without affecting the link status. When the AIX RISC System/6000 restarts, the cncntx25s. # command will be executed automatically (execution of cnctx25s. # is normally not required after restarting the AIX RISC/6000 system). A link may be started by root user without restarting the system if the link has not been started. To start the link without restarting the system, do the following: 1. Change to the /usr/lpp/csasrvr/switchdm directory. 2. Execute the cnctx25s. # command. The results of the link connect attempt will be displayed on the terminal screen and in a log file, x25s # lnk.log. Do not call the cnctx25s. # command more than once. If you do, you run the risk of having too many Switch Virtual Circuits (SVCs) opened, restart the RISC System/6000 system. Viewing the Communication Link Status If there any connect errors, the cause and resolution of the error will be suggested in the message. To view the current link status, enter the following command: xmanage -s If the link status is disconnected, you may restart the system or, log on as root and enter the following command: cnctx25s. # where # is a digit from 0-9. Note: Any link connection started from xmanage requires that the root session remain active. Configuring the DMS-100 CO Switch Connection(s) Before CallPath Server for AIX can communicate with the DMS-100 CO switch, the switch connection(s) must be configured by recording the following information in CallPath Server for AIX: Switch description The name to be used in the CallPath Server Management Facility for the DMS-100 CO switch. Auto-start Whether CallPath Server for AIX should start communications with the DMS-100 CO switch automatically when the CallPath Server for AIX subsystem is started. Restart on failure Whether CallPath Server for AIX should restart communications with the DMS-100 CO switch automatically after a fatal error has terminated communications between CallPath Server for AIX and the switch. Switch parameters The following information is required from Table 3: o Switch password for the given Business Group ID o Network Node ID o Service ID o Service Version (BCS level) o Business Group ID o Application ID o Local Address o Remote Address o Slot Address You can get the first six switch log-on parameters from your switch administrator. The last three values correspond to the device name (slot number), local card address (network user address, or NUA), administrator) as defined when installing and configuring the X.25 adapter. Separate procedures follow for configuring the DMS-100 CO switch connection using the CallPath Server Management Facility and using SMIT. Configuring the DMS-100 CO Connecting in CallPath Server for AIX To configure the DMS-100 CO switch in CallPath Server for AIX for a local connection, do the following: 1. Start the CallPath Server Management Facility. 2. Display the CallPath Server Management Facility Set Switch Configuration window in one of the following ways: o From the CallPath Server Management Facility menu bar: 1. Select the Configuration menu. 2. Select the Switch Connection menu option. 3. Select On file. 4. Select the switch from the scrollable list box. o From the switch icon: 1. Click on the Switch icon using the mouse menu button. 2. Select the Configuration option. 3. Select On file. 4. Select DMS-100 from the scrollable list box. 3. Type the description for the switch in the "Switch description" field. 4. Select Auto-start if you want DMS-100 CO switch to start automatically when CallPath Server for AIX starts. 5. Select Restart on failure if you want DMS-100 CO switch to restart when there is a failure in communications between it and CallPath Server for AIX. 6. Click on the Switch type field. 7. Click on DMS-100. 8. Click on one of the following: o OK to save the configuration information and return to the CallPath Server Management Facility after setting the DMS-100 CO switch logon parameters o Apply to save the configuration information and return to the Set Switch Configuration window after setting the DMS-100 CO switch logon parameters The Enter Switch Configuration Data window shown in Figure 5 is displayed. Note: If you are using SMIT instead of the CallPath Server Management Facility, the Enter Switch Configuration window is not available. See "Configuring the DMS-100 CO Switch Connection in SMIT" for additional CallPath Server for AIX-to-DMS-100 CO switch connection instructions. Figure 5. Enter Switch Configuration Data Window [Image] View figure. 9. Complete the following fields: Network Node ID Identifies this DMS-100 CO switch. The range of values is 0 to 32767. Service ID Identifies the service profile for this DMS-100 CO switch. The range of values is 0 to 255. BCS Version (level) of service in which the DMS-100 CO switch and CallPath Server for AIX are operating. Acceptable values are in the range of 33-36. Notes: 1. If the switch load is more than two levels higher than the BCS level used in the logon parameters, the switch will not accept it. For example, if the switch is set at level 36 and the BCS logon parameter is set at level 33, the switch will reject the logon. 2. The Level 36 function, DV_SET_FEATURE (log on, log off, ready, and not ready), is supported. Further, the switch event messages indicating the status of the agent are flowed to the application. The BCS level must be set to 36 to implement this request. 3. Multiple-link capability using BCS level 35 and 36 is not supported. 4. The BCS level must be set to 35 or 36 to implement the Query_ACD_Information request. Business Group ID Identifies your switch within the public telephone network. Your switch administrator has the value assigned to you by the telephone company. Application ID Identifier for the host application program to be run. The range of values is 1 to 32,767. Local Address Link address for the RISC System/6000 as registered with the DMS-100 CO switch. Your switch administrator has the value assigned to CallPath Server for AIX. Remote Address The address by which the DMS-100 CO switch identifies itself. Your switch administrator has this value. Slot number Device name assigned to the X.25 slot used. Acceptable values are x25s0, x25s1, x25s2, and x25s3. Some larger servers may allow slot numbers through x25s17. Enter Password The password assigned to the specified business group for this DMS-100 CO switch. Your switch administrator has the 1-to-8 character password. Use uppercase for all alphabetic characters in the password. Note: Once you enter the DMS-100 CO switch password, there is no need to change it unless the switch administrator has changed it for the DMS-100 CO switch or if the password has never been entered. Verify password The current password again to confirm that you typed it correctly in the "Enter Password" field. Leave blank if "Enter Password" field is blank. 10. Click on OK. Either the CallPath Server Management Facility or the Set Switch Configuration window is displayed, depending on your selection in Step 8. 11. Repeat this procedure for each switch connection starting with Step 2. Configuring the DMS-100 CO Switch Connection in SMIT To configure the DMS-100 CO switch in SMIT for a local connection, do the following: 1. Start SMIT. 2. Select Communications Applications and Services 3. Select CallPath Server/6000 4. Select CallPath Server/6000 Configuration 5. Select Set Switch Connection Configuration 6. Select Set Switch Connection Configuration 7. Select the switch connection (SWITCHnn, where nn is a valid 2-digit switch connection) and type (DMS) to configure. 8. Type the description for the switch in the "Switch description" field. 9. Select Auto-start if you want DMS-100 CO switch to start automatically when CallPath Server for AIX starts. 10. Select Restart on failure if you want DMS-100 CO switch to restart when there is a failure in communications between it and CallPath Server for AIX. 11. Complete the following fields: Network Node ID Identifies this DMS-100 CO switch. The range of values is 0 to 32767. Service ID Identifies the service profile for this DMS-100 CO switch. The range of values is 0 to 255. BCS Version (level) of service that the DMS-100 CO switch and CallPath Server for AIX are operating under. Acceptable values are in the range of 33-36. Business Group ID Identifies your switch within the public telephone network. Your switch administrator has the value assigned to you by the telephone company. Application ID Identifier for the host application program to be run. The range of values is 1 to 32,767. Local Address Link address for the RISC System/6000 as registered with the DMS-100 CO switch. Your switch administrator has the value assigned to CallPath Server for AIX. Remote Address The address by which the DMS-100 CO switch identifies itself. Your switch administrator has this value. Slot number Device name assigned to the X.25 slot used. Acceptable values are x25s0, x25s1, x25s2, x25s3, x25s4, x25s5, x25s6, and x25s7. Password The password assigned to the specified business group for this DMS-100 CO switch. Your switch administrator has the 1-to-8 character password. Use uppercase for all alphabetic characters in the password. Verify password Retype the password for verification. 12. Select Do. Note: If you need to do more configuration using SMIT, you must restart SMIT for CallPath Server for AIX. --------------------------------------------------------------------------- Step 6: Starting CallPath Server for AIX and the DMS-100 CO Switch Connection Following is an overview of the tasks required for starting CallPath Server for AIX and the DMS-100 CO switch connection: * Starting the CallPath Server Management Facility * Starting the CallPath Server for AIX subsystem * Starting the DMS-100 CO 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 Starting the CallPath Server Management Facility You can start CallPath Server Management Facility in one of the following ways: * Starting the CallPath Server for AIX Management Facility from the system prompt: To start the CallPath Server for AIX Management Facility from the system prompt, do the following: 1. Log onto the system as root or as an authorized group. 2. Enter the following command: cd /usr/lpp/csasrvr/bin 3. Enter csasrvr. * Starting the CallPath Server for AIX Management Facility from SMIT: SMIT can be run in either MOTIF (using X-Windows and a mouse) MOTIF CallPath Server Management Facility windows and screens. If you run CallPath Server for AIX on an Xstation and use MOTIF, but would like to use SMIT in character mode, enter smit -C csasrvr on the command line. This temporarily changes SMIT from MOTIF to character mode. See the CallPath Server Planning, Installation, and Problem Determination Guide for sample CallPath Server Management Facility screens in character mode. To start the CallPath Server for AIX Management Facility from SMIT, do the following: 1. Log onto the system as root or as an authorized group. 2. Enter smit at the system prompt. 3. Select Communications Applications and Services from the System Management menu. Note: SMIT provides fastpath commands that take you directly to a SMIT panel without making individual menu selections. 4. Select CallPath Server for AIX. Once CallPath Server for AIX 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. If you use SMIT, there is no Administrative Password window and hence, no password. Continue with "Starting CallPath Server for AIX". Starting CallPath Server for AIX After starting the CallPath Server Management Facility, start CallPath Server for AIX in one of the following ways: * From the CallPath Server Management Facility window: 1. Select the Administration menu from the menu bar. 2. Select the Server menu option. 3. Select Start. 4. Click on one of the following in response to the confirmation message: + Yes to start CallPath Server for AIX + No to return to the CallPath Server Management Facility window without starting CallPath Server for AIX 5. Select Yes from the confirmation message window. * From the CallPath Server icon: 1. Click on the CallPath Server icon. 2. Select Start. 3. Click on one of the following in response to the confirmation message: + Yes to start CallPath Server for AIX + No to return to the CallPath Server Management Facility window without starting CallPath Server for AIX Continue with "Starting the DMS-100 CO Switch Connection". Starting the DMS-100 CO Switch Connection Start your DMS-100 CO switch switch connection in one of the following ways: * From the CallPath Server Management Facility window menu bar: 1. Select the Administration menu. 2. Select the Switch Connection menu option. 3. Select Start. 4. Select the switch. 5. 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: 1. Click on the Switch icon. 2. Select Start. 3. 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 Multiple Logons Using the Same Service ID Multiple logons to a single business group using the same service ID cause unpredictable results and are not supported by this program. If multiple logons occur, the switch response to a request is sent to the next available server link instead of being sent to the server making the request. This causes the call state model to be out of synchronization and the server stops due to a critical error. To avoid such an error, log on to a business group using the same service ID for only one switch link at a time. This means that any switch session logon to a given business group using a given service ID must be stopped before a different logon to the same business group using the same service ID can be attempted. For example, switch session SWITCH01 and switch session SWITCH02 each have the same password and the same service ID and both are enabled to log on to the same business group. If switch session SWITCH01 is active, but you want to start an application that uses switch session SWITCH02, switch session SWITCH01 must be stopped first. This is true even if switch session SWITCH01 has no traffic. Switch links SWITCH01 and SWITCH02 cannot be simultaneously active. Note: This limitation is true for any combination of SwitchServer/2, CallPath Server/2, and CallPath Server/6000 link sessions that can log on to the same business group. It is recommended that switch sessions avoid overlapping. Multiple Logons Using Different Service IDs The switch can be configured to enable independent logons to a business group using different service IDs for each logon. The switch considers these to be independent sessions. The first session to execute an association (that is, monitoring) of a primary ACD-DN or Centrex DN has exclusive event messaging for that resource. All events concerning that resource remain within the link established during that session. If a session ends for any reason (such as the failure of an X.25 link) any remaining session can execute an association with the orphaned resource. The switch enables up to eight sessions for each business group. Each session requires a unique service ID. This process partitions a business group into unique and independent sub-business groups. The Server supports this independent, simultaneous, switch session environment. --------------------------------------------------------------------------- Chapter 5. Installing and Configuring CallPath Server for MS Windows NT This chapter provides installation and configuration information for the DMS-100 CO switch hardware and software that is used with the CallPath Server for MS Windows NT program product. Note: If you want to install CallPath SwitchServer/2 for a remote connection to the DMS-100 CO switch, see Chapter 2. "Installing and Configuring CallPath SwitchServer/2". If you want to install CallPath Server for OS/2 for a direct connection to the DMS-100 CO switch or as the CallPath SwitchServer/2 host, see Chapter 3. "Installing and Configuring CallPath Server for OS/2". If you want to install CallPath Server for AIX for a direct connection to the DMS-100 CO switch or as the CallPath SwitchServer/2 host, see Chapter 4. "Installing and Configuring CallPath Server for AIX". Also included in this chapter are lists of the additional hardware and software that is required for the local (direct physical) connection of CallPath Server for MS Windows NT to the DMS-100 CO switch. Use these instructions with the installation instructions in the CallPath Server Planning, Installation, and Problem Determination Guide --------------------------------------------------------------------------- DMS-100 CO switch Configurations The following figure shows the hardware configuration for the DMS-100 CO switch connection to CallPath Server for MS Windows NT. Figure 6. DMS-100 CO switch Connection to CallPath Server for MS Windows NT [Image] View figure. DMS-100 CO switch Hardware and Software Requirements To use the DMS-100 CO switch with CallPath Server for MS Windows NT, the following hardware and software are required: Hardware Requirements A DMS-100 CO switch with the following: o ACD feature o CompuCall feature Refer to the Nortel Feature Planning Guide 50004.1/01-92 or later. Also contact your Nortel installation agent for installation, configuration, and upgrade changes to your DMS-100 CO switch hardware. Software Requirements Software requirements are installation specific: o Refer to the Nortel Feature Planning Guide 50004.1/01-92 or later for the BCS33 through BCS36 levels of the CompuCall feature. o Contact your Nortel installation agent for installation, configuration, and upgrade changes to your DMS-100 CO switch software. CallPath Server for MS Windows NT Hardware and Software Requirements To use CallPath Server for MS Windows NT in a direct connection with the DMS-100 CO 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 The following hardware is required for each active connection. Up to 2 active connections are supported: o IBM X.25 Interface Co-Processor/2 or Co-Processor adapter that is appropriate for the architecture of your machine: MCA Micro-channel Architecture ISA Industry Standard Architecture PCI Peripheral Component Interconnect o IBM 7855-10 modem or equivalent for V.24 o A connection from the PC to the DMS-100 CO switch using an IBM X.25 Interface co-processor cable, option V.35 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 The following additional software is required to implement the local connection to CallPath Server for MS Windows NT: o X.25 Co-Processor/2 or X.25 software driver (See the README file provided on the CallPath distribution media.) o X.25 API which includes the X.25 configuration utility Necessary Documentation It is strongly suggested that you read the following source documentation before installing or configuring the X.25 adapter: o The CallPath Server Planning, Installation, and Problem Determination Guide describes additional hardware and software that may be required, depending on the applications and networking environment used by the client workstations. o The X.25 Interface Co-Processor/2 Technical Reference provides details about the X.25 adapter. o The X.25 Interface Co-Processor/2 Guide to Operations provides details about the X.25 adapter connections. o The documentation that comes with the X.25 adapter describes special settings for the adapter you have chosen. These settings are unique for each of the three types of architecture. o The README file that is shipped on the CallPath distribution media provides last minute updates to the hardware and software installation instructions in this book. It is imperative that you read this file before starting the hardware or software installation. Before You Begin Contact your DMS-100 CO switch representative to have the DMS-100 CO switch hardware and software installed. You also need to contact your switch representative to obtain the following information for each switch connection: * CCITT compliance date (1980 or 1984) * Local DTE address * Remote DTE address * The following switch logon parameters: o Network Node ID o Service ID o Service Version (BCS level) o Business Group ID o Application ID o Logon password (for the given Business Group ID) The workspace in Table 4 provides space for you to record this information. You will also need to know whether you are running on a point-to-point connection or a public packet network connection. If the CallPath Server for MS Windows NT installation media contains a README or a TIPS file, read it before installing CallPath Server for MS Windows NT. Table 4. DMS-100 CO Switch Workspace Parameter Worksheet for CallPath Server for AIX Switch Connection Switch Connection Switch Connection Description 1 2 3 Description X.25 Port (01-04) X.25s Number (0-3) Network Node ID Service ID Description Service Version (BCS level) Business Group ID Application ID Local Address Remote Address Logon Password* Note: *You may want to leave the password field blank, depending on security requirements. --------------------------------------------------------------------------- Summary of Installation Steps Following is an overview of the procedure for installing and configuring CallPath Server for MS Windows NT and communication links with the DMS-100 CO switch: Step 1: Installing and configuring Microsoft Windows NT Step 2: Installing and configuring TCP/IP hardware and software Step 3: Installing CallPath Server for MS Windows NT and other CallPath components Step 4: Restarting the CallPath Server for MS Windows NT computer Step 5: Starting the CallPath Server Management Facility and configuring CallPath Server for MS Windows NT Step 6: Installing and configuring the X.25 Interface co-processor adapter for switch communications Step 7: Restarting the CallPath Server for MS Windows NT computer Step 8: Starting CallPath Server for MS Windows NT and the DMS-100 CO switch connection(s) These tasks are described in detail in the following sections. --------------------------------------------------------------------------- Step 1: Installing and Configuring Microsoft Windows NT Make sure that Microsoft Windows NT is installed and running before attempting to install CallPath Server for MS Windows NT. Install the latest Corrective Services Diskettes (CSDs) for Microsoft Windows NT. --------------------------------------------------------------------------- Step 2: Installing and Configuring TCP/IP Hardware and Software After installing Microsoft Windows NT, install the networking hardware. Then install and configure TCP/IP to enable communications between the CallPath Server for MS Windows NT computer and the clients. --------------------------------------------------------------------------- Step 3: Installing CallPath Server for MS Windows NT and Other CallPath Components The installation program copies CallPath system files to the directory path you specify, updates the NT registry, and adds a CallPath folder to the desktop. Note: If CallPath Server for MS Windows NT or other components were previously installed, they will be reinstalled in the same path. Configuration files will not be overwritten, because the install process simply copies the CallPath system files to the specified path. To install CallPath Server for MS Windows NT and other CallPath Components, such as the CallPath Developers Toolkit or the switch-dependent code, do the following: 1. Follow the instructions provided on the information jacket that comes with the distribution media. It has instructions for accessing the CD-ROM and initializing the installation process. You will be prompted to install one or more of the following CallPath Components: o Server o CallPath Developers Toolkit o switch-dependent code 2. When the Installation Options window is displayed on your screen, only the CallPath Components you selected from the CD are listed. Click on OK to start installation of those components. 3. When prompted, you can change the suggested target path, including the drive letter, where you want CallPath installed. The directory you select is appended with a subdirectory called csasrvr for the Server and csatk for the CallPath Developers Toolkit. Notes: 1. If the selected disk has insufficient disk space, you will be prompted to select another. 2. If you are reinstalling Server over a previous installation, you must install to the same location. If you want to change the path, you must uninstall the previous version. Uninstalling the previous version deletes all folders, files, and subdirectories. Be sure to back up your customized or modified configuration files. When the installation is complete, your Server folder will contain the following: * CallPath Server Management Facility program item * Server readme program item * Install History program item * Uninstall program item * Switch-dependent code readme program item for each installed switch The CallPath Developers Toolkit folder will contain the following: * API Test Utility program item * CallPath Developers Toolkit readme program item * Uninstall program item Note: If the installation program stops because it detected an error condition, and the error cannot be corrected, record the error message and exit the installation. Once you have corrected the error condition, re-install the component. Most errors will also be displayed by selecting the Install History program item. Viewing the Component Installation History To display the installation processing performed to date, do the following: 1. Open the CallPath Server or the CallPath Developers Toolkit folder. 2. Open the Install History program item. The Install History window is displayed. 3. Use the scroll bars to view the contents of the Install History window. 4. After viewing the installation history, exit the editor or press F3 to close the file and return to the folder. Displaying the "Readme" Information To view the readme file for the server or any other components, such as the CallPath Developers Toolkit or the switch-dependent code, do the following: 1. Open one of the CallPath folders. 2. From that folder, open the readme program item. The selected file is displayed. 3. Use the scroll bars to view the contents of the file. 4. After viewing the file, exit the editor or press F3 close the file and return to the folder. Uninstalling CallPath Components To uninstall the CallPath Server or the switch-dependent code, do the following: 1. Click on the Uninstall icon in the CallPath Server folder. The folder displays a list from which you can select the CallPath Server and switch-dependent code for all installed switches. o If you select CallPath Server, all folders, subdirectories, files, environment variables, path updates, and registry updates will be erased or deleted. o If you select switch-dependent code for one or more switches, only the switch-dependent code will be deleted. The CallPath Server is not affected. 2. When prompted, confirm your selection. To uninstall the CallPath Developers Toolkit, click on the uninstall icon in the CallPath Developers Toolkit folder. When prompted, confirm your selection. --------------------------------------------------------------------------- Step 4: Restarting the CallPath Server for MS Windows NT Computer To activate the CallPath Server for MS Windows NT installation, restart the CallPath Server for MS Windows NT computer. --------------------------------------------------------------------------- Step 5: Starting the CallPath Server Management Facility and Configuring CallPath Server for MS Windows NT Following is an overview of the tasks required for starting the CallPath Server Management Facility and configuring CallPath Server for MS Windows NT: * Starting the CallPath Server Management Facility * Configuring CallPath Server for MS Windows NT * Starting the CallPath Server for MS Windows NT subsystem to confirm that the CallPath Server for MS Windows NT configuration works These tasks are described in more detail in the following sections. Starting the CallPath Server for MS Windows NT Management Facility To start the CallPath Server Management Facility, do one of the following: * Enter csasrvr at the DOS command prompt. * Double-click on the CallPath icon on the desktop and then double-click on the CallPath Server for MS Windows NT icon. Once CallPath Server for MS Windows NT 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. Continue with "Configuring CallPath Server for MS Windows NT (Minimal Configuration)". Configuring CallPath Server for MS Windows NT (Minimal Configuration) CallPath Server for MS Windows NT requires the following operating parameters before it can communicate with client applications: * Maximum number of applications capable of connecting to the server at the same time * Maximum number of concurrent users of CallPath Server for MS Windows NT To configure CallPath Server for MS Windows NT, do the following: 1. Display the Set Server Configuration window, in one of the following ways: o From the CallPath Server Management Facility menu bar: 1. Select the Configuration menu. 2. Select the Server menu option. o From the CallPath Server icon: 1. Select the CallPath Server icon using the mouse menu button. 2. Select Configuration. 2. Enter new maximum values for the following fields. (See the CallPath Server Planning, Installation, and Problem Determination Guide for information about tuning the CallPath Server for MS Windows NT 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 from IBM. Contact your purchasing organization if you do not know this number. 3. Click on OK to accept the CallPath Server for MS Windows NT configuration values. The new configuration values take effect the next time CallPath Server for MS Windows NT is started. Starting the CallPath Server for MS Windows NT Subsystem After starting the CallPath Server Management Facility, start the CallPath Server for MS Windows NT subsystem in one of the following ways: * From the CallPath Server Management Facility window: 1. Select the Administration menu option from the menu bar. 2. Select the Server menu option. 3. Select Start. 4. Click on one of the following in response to the confirmation message: + Yes to start the CallPath Server subsystem + No to return to the CallPath Server Management Facility window without starting the CallPath Server subsystem 5. Select Yes from the confirmation message window. * From the CallPath Server icon: 1. Click on the CallPath Server icon. 2. Select Start. 3. Click on one of the following in response to the confirmation message: + Yes to start the CallPath Server subsystem + No to return to the CallPath Server Management Facility window without starting the CallPath Server subsystem --------------------------------------------------------------------------- Step 6: Installing and Configuring the X.25 Interface Co-Processor Adapter for Switch Communications Following is an overview of the tasks required for installing and configuring the X.25 Interface co-processor adapter(s) for communications between CallPath Server for MS Windows NT and the DMS-100 CO switch: * Installing one or more X.25 Interface co-processor adapters * Installing the X.25 device driver * Installing the X.25 configuration software * Configuring the X.25 directory links * Installing the DMS-100 CO switch-dependent code feature * Configuring the DMS-100 CO switch connection(s) in CallPath Server for MS Windows NT These tasks are described in more detail in the following sections. Installing and Configuring the X.25 Adapter Hardware The X.25 Interface co-processor/2 adapter card provides the communication channel between the DMS-100 CO switch and the Server. Carefully complete the following steps to ensure a successful adapter installation: 1. View the README file included on the distribution media before installing the X.25 adapter. Last minute updates to the procedure and the settings are specified there. 2. For the X.25 adapter for ISA architecture, set the option switches on the adapter for the IRQ and card address by closely following the information in the README file and the documentation that accompanies the adapter. 3. For any variety of X.25 adapter, record the IRQ and card address settings for use in configuring the software. 4. Install the X.25 adapter in an available slot. 5. Record the slot number where you install the X.25 Interface co-processor adapter for use in configuring the software. 6. Connect the adapter to a modem using an appropriate cable. 7. Reboot the CallPath Server for MS Windows NT computer. Installing the X.25 Adapter Software To install the X.25 software, do the following: 1. Access the CallPath website or bulletin board (BBS): Website http://wwprodsoln.bocaraton.ibm.com/artic/ 2. Navigate from this home page until you reach the file repository list. Locate "Complete File List", and download the two packages that are needed: o Package one, the device drivers and microcode, contains ARTIC support for the Microsoft Windows NT Miniport or the Microsoft Windows NT Co-Processor adapter. View the readme file in the package for instructions about how to retrieve and install the driver code. o Package two, ARTIC support for X.25, contains the X.25 call library (API). As of this writing, the API support is only a beta version. It can only be obtained by an email request. View the readme file about how to retrieve and install the API. Be sure to view the readme file included on the CallPath CD-ROM for any updated instructions. Configuring the X.25 Directory Links To configure the X.25 directory links, complete the following steps: 1. At the DOS prompt, change to the directory containing the file X25CONF.EXE. 2. Start the X25CONF.EXE configuration program by entering X25CONF at the DOS prompt. 3. At the main menu, highlight Set/View X.25 Link Profiles, and press Enter. 4. On the X.25 Link Profile panel, complete the Link profile name field by entering NTInn, where nn is a 2-digit number in the range 01-99, or press F4 to display a list of available link profile names that were previously configured. If you have a previously configured link name, select and load it by pressing F10. 5. For the remainder of this panel, use the cursor keys to move from field to field. As you do so, a popup list of available options is displayed for each field. Press F5 to highlight a selection from the popup list, then press F10 to insert the selection in the field. 6. Press F8 to go to the Link Profile Frame Parameters panel, then complete the fields as follows: Window size 7 or 2, depending on the window Frame sequence modulus 8 Retry timeout 50 micro-second units Retry count 10 Response timeout 25 seconds (10 in Canada) Operational timeout 180 seconds 7. Press F8 to go to theLink Profile Packet Parameters panel, then complete the fields as follows: Number of PVCs 0 Lowest PVC channel number 1 Number of incoming only SVCs 0 Lowest SVC incoming only number 1 Number of bothway SVCs 1 Lowest bothway SVC number 1 Number of outgoing only SVCs 0 Lowest SVC outgoing only number 1 Packet sequence number modulus 8 8. Press F8 to go to theLink Profile Packet Timeouts panel,then complete the fields as follows: Restart request timeout 180 seconds Call request timeout 200 seconds Reset request timeout 180 seconds Clear request timeout 180 seconds Acknowledgement timeout 0 seconds Data packet timeout 0 seconds Interrupt packet timeout 0 seconds Reset request retry count 5 seconds Clear request retry count 5 seconds 9. Press F8 to go to panel 5 of 6, Link Profile SVC Parameters, then complete the fields as follows: Default incoming packet size 128 bytes Maximum incoming packet size 128 bytes Default outgoing packet size 128 bytes Maximum outgoing packet size 128 bytes Default incoming window size 7 packets. Use 2 as an alternative. Check with the system administrator. Maximum incoming window size 7 packets. Use 2 as an alternative. Check with the system administrator. Default outgoing window size 7 packets. Use 2 as an alternative. Check with the system administrator. Maximum outgoing window size 7 packets. Use 2 as an alternative. Check with the system administrator. Maximum throughput class 19200 bps. Use 48000 as an alternative. Check with the system administrator. 10. Ignore the Link Profile PVC Parameters panel, then return to the X.25 Link Profile panel by pressing F7 as many times as necessary. 11. Press F10 to save the new profile parameters. 12. Press F7 to return to the main menu. 13. Highlight Set/View Call Nicknames and press Enter. 14. On the Call Nicknames panel, complete the fields as follows: (Ref #1.)Call nickname Enter a unique new nickname, or press F4 to display a list of available call nicknames. For each switch connection, you need a nickname for the switch address and another for the CallPath address. Description User defined. Link profile name This is the same as the name entered in Step 4. Address Required. Obtain this address from switch administrator. Address extension Leave blank. Request reverse charging No. 15. Reboot the CallPath Server for MS Windows NT computer. Installing the DMS-100 CO Switch-Dependent Code Feature Use the CallPath Server for MS Windows NT Installation Utility to install the DMS-100 CO switch-dependent code feature on the PC running CallPath Server for MS Windows NT. To install the DMS-100 CO switch-dependent code feature, do the following: 1. Insert CallPath Server for MS Windows NT product distribution media in the source drive. 2. At the DOS command prompt, enter :install, where is the letter of the drive containing the source distribution media. The Installation Options window is displayed, which enables you to select the CallPath Server for MS Windows NT components for installation. 3. Select Switch Dependent to install the DMS-100 CO switch-dependent code feature. Note: CallPath Server for MS Windows NT must be installed before you install the DMS-100 CO switch-dependent code feature. 4. Click on OK to accept the selection. 5. Follow the prompts. Continue with "Configuring the DMS-100 CO Switch Connection(s) in CallPath Server for MS Windows NT". Configuring the DMS-100 CO Switch Connection(s) in CallPath Server for MS Windows NT Use the information recorded in Table 4 when performing the procedure that follows. Before CallPath Server for MS Windows NT can communicate with the DMS-100 CO switch, the switch connection must be configured in CallPath Server for MS Windows NT: Switch description The name to be used in the CallPath Server Management Facility for the DMS-100 CO switch connection. Auto-start Whether CallPath Server for MS Windows NT should start communications with the DMS-100 CO switch automatically when the CallPath Server for MS Windows NT subsystem is started. Restart on failure Whether CallPath Server for MS Windows NT should restart communications with the DMS-100 CO switch automatically after a fatal error has terminated communications between CallPath Server for MS Windows NT and the switch. Switch parameters The following information is required: o Switch password for the given Business Group ID o Network Node ID o Service ID o Service Version (BCS level) o Business Group ID o Application ID o Local Directory Entry o Remote Directory Entry To configure the DMS-100 CO switch in CallPath Server for MS Windows NT for a local connection, do the following: 1. Start CallPath Server Management Facility. See "Starting the CallPath Server for MS Windows NT Management Facility" for instructions. 2. Display the CallPath Server Management Facility Set Switch Configuration window in one of the following ways: o From the CallPath Server Management Facility menu bar: 1. Select the Configuration menu. 2. Select the Switch Connection menu option. 3. Select On file. 4. Select the switch from the scrollable list box. o From the switch icon: 1. Click on the Switch icon using the mouse menu button. 2. Select the Configuration option. 3. Type the description for the switch in the Switch description field. 4. Select Auto-start if you want DMS-100 CO switch to start automatically when the CallPath Server for MS Windows NT subsystem starts. 5. Select Restart on failure if you want the DMS-100 CO switch to restart when there is a failure in communications between it and CallPath Server for MS Windows NT. 6. Click on the Switch type field. 7. Click on SL1. The Enter Switch Configuration Data window shown in Figure 7 is displayed. Figure 7. Enter Switch Configuration Data Window [Image] View figure. 8. Complete the following fields if they need to be modified: Network Node ID Identifies this DMS-100 CO switch. The range of values is 0 to 32767. Service ID Identifies the service profile for this DMS-100 CO switch. The range of values is 0 to 255. BCS Version (level) of service that the DMS-100 CO switch and CallPath Server for OS/2 are operating under. Acceptable values are in the range of 33-36. Notes: 1. If the switch load is more than two levels higher than the BCS level used in the logon parameters, the switch will not accept it. For example, if the switch is set at level 36 and the BCS logon parameter is set at level 33, the switch will reject the logon. 2. The Level 36 function, DV_SET_FEATURE (log on, log off, ready, and not ready), is supported. Further, the switch event messages indicating the status of the agent are flowed to the application. The BCS level must be set to 36 to implement this request. 3. Multiple-link capability using BCS level 35 and 36 is not supported. 4. The BCS level must be set to 35 or 36 to implement the Query_ACD_Information request. Business Group ID Identifies your switch within the public telephone network. Your switch administrator has the value assigned to you by the telephone company. Application ID Identifier for the host application program to be run. The range of values is 1 to 32,767. Slot Number Not used for CallPath Server for MS Windows NT. Local Directory Entry Name established when creating the X.25 directory entries for the local directory entry. This field must match the name used in Step 3 and is case sensitive. Remote Directory Entry Name established when creating the X.25 directory entries for the remote directory entry. This field must match the name used in Step 11 and is case sensitive. Enter Password The password assigned to the specified business group for this DMS-100 CO switch. Your switch administrator has the 1-to-8 character password. Use uppercase for all alphabetic characters in the password. Note: You do not have to change the DMS-100 CO switch password unless the switch administrator has changed it for the DMS-100 CO switch for the given business group or if the password has never been entered. Verify Password The current password again to confirm that you typed it correctly in the "Enter Password" field. Leave blank if "Enter Password" field was left blank. 9. Click on OK. Either the CallPath Server Management Facility or the Set Switch Configuration window is displayed, depending on your selection in Step 10. 10. Click on one of the following: o OK to save the configuration information and return to the CallPath Server Management Facility after setting the DMS-100 CO switch logon parameters o Apply to save the configuration information and return to the Set Switch Configuration window after setting the DMS-100 CO switch logon parameters 11. Repeat this procedure for each switch connection starting with Step 2. --------------------------------------------------------------------------- Step 7: Restarting the CallPath Server for MS Windows NT Computer After configuring the X.25 communications and the switch, exit CallPath Server Management Facility, and restart your CallPath Server for MS Windows NT machine. --------------------------------------------------------------------------- Step 8: Starting CallPath Server for MS Windows NT and the DMS-100 CO Switch Connection(s) Following is an overview of the tasks required for starting the CallPath Server for MS Windows NT and the DMS-100 CO switch connection(s): * Start the CallPath Server Management Facility * Start the CallPath Server for MS Windows NT subsystem * Start the DMS-100 CO switch connection(s) 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. Starting the CallPath Server Management Facility 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 icon on the OS/2 desktop and then double-click on the CallPath Server for OS/2 icon. Once CallPath Server for OS/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. Continue with "Starting the CallPath Server for MS Windows NT Subsystem". Starting the CallPath Server for MS Windows NT Subsystem After starting the CallPath Server Management Facility, start the CallPath Server for MS Windows NT subsystem in one of the following ways: * From the CallPath Server Management Facility window: 1. Select the Administration menu from the menu bar. 2. Select the Server menu option. 3. Select Start. 4. Click on one of the following in response to the confirmation message: + Yes to start the CallPath Server for MS Windows NT subsystem + No to return to the CallPath Server Management Facility window without starting the CallPath Server for MS Windows NT subsystem 5. Select Yes from the confirmation message window. * From the CallPath Server icon: 1. Click on the CallPath Server icon. 2. Select Start. 3. Click on one of the following in response to the confirmation message: + Yes to start the CallPath Server for MS Windows NT subsystem + No to return to the CallPath Server Management Facility window without starting the CallPath Server for MS Windows NT subsystem Continue with "Starting the DMS-100 CO Switch Connection(s)". Starting the DMS-100 CO Switch Connection(s) After starting the CallPath Server for MS Windows NT subsystem, start your DMS-100 CO switch connection in one of the following ways: * From the CallPath Server Management Facility window menu bar: 1. Select the Administration menu. 2. Select the Switch Connection menu option. 3. Select Start. 4. Select the switch. 5. 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: 1. Click on the Switch icon. 2. Select Start. 3. 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 Repeat one of the above procedures for each switch connection you want to start. --------------------------------------------------------------------------- Chapter 6. DMS-100 CO Switch Functions This chapter lists all program calls and messages in quick-reference tables to provide an overall picture of the level of support provided by the DMS-100 CO switch. Not all values defined by the architecture are supported by the DMS-100 CO switch. This chapter also lists special considerations and limitations for using the CallPath API with the DMS-100 CO switch. The tables that follow show the program calls and messages that are fully supported, partially supported, or not supported by the DMS-100 CO switch. * 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. Refer to CallPath Developers Toolkit Programming Guide and 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 supports both Version 0 and Version 1 features of the CallPath Services Architecture while CallPath SwitchServer only supports Version 0 features. Refer to the programming guide for your CallPath host software for details. --------------------------------------------------------------------------- Unsupported Program Calls, Parameters, and Characteristics If a program issues a program call that is not supported by the DMS-100 CO switch or that contains a parameter value that is not supported by the DMS-100 CO switch, an error occurs. Similarly, 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 DMS-100 CO switch, an error occurs. 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 DMS-100 CO switch, 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 DMS-100 CO switch; 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 described previously. --------------------------------------------------------------------------- Program Calls Supported by the DMS-100 CO Switch The following table shows the DMS-100 CO switch level of support for the CallPath program calls. See Chapter 7. "Partially Supported Program Calls", for a detailed description of each partially supported program call. Fully Partially Not Program Calls Supported Supported Supported Page Add_Party &check. Alternate_Call &check. Answer_Call &check. Conference_Call &check. "STLCONF (Conference_Call)" Create_Program_Name (1) &check. Delete_Call_Profile (1) &check. Disconnect &check. Extend_Call &check. "STLXTND (Extend_Call)" Identify_Program_Name &check. (1) Identify_Program_Version &check. Immediate_Transfer &check. Initialize_Call_Profile &check. "STLINIT (1,2) (Initialize_Call_Profile)" Invoke_Feature &check. "STLINVK (Invoke_Feature)" Make_Call &check. "STLMAKE (Make_Call)" Monitor &check. "STLMON (Monitor)" Monitor_System_Messages &check. (1) Park_Call &check. Pick_Call &check. Query_ACD_Information &check. "STLQACD (Query_ACD_Information)" Query_Call_Parties &check. Query_Hardware_Status &check. Query_Party_Status (3) &check. Receive (1) &check. "STLRCV (Receive)" Redirect_Call &check. "STLRED (Redirect_Call)" Register_Ownership (1,4) &check. Reject_Call &check. Release_Program_Name (1) &check. Retrieve_Call (5) &check. Return_Control &check. Send_Device_Data &check. Transfer_Call &check. "STLTRAN (Transfer_Call)" Trigger &check. "STLTRGR (Trigger)" Notes: 1. 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. 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 DMS-100 CO switch does not support that overall function. For details, see "STLINIT (Initialize_Call_Profile)". 3. Query_Party_Status is processed by Server. No request flows to the DMS-100 CO switch as a result of this program call. When the program issues a Query_Party_Status program call, Server creates a Party_Status message in reply. If Server is already aware of connections involving this party, it returns the already-existing connection ID or IDs associated with that party. Server reports the status of the party in question as found in an internal state model. The DMS-100 CO switch does not support a Query_Party_Status request. If any party in a call is NOT monitored, then the status may not reflect the current state of the parties in the call. 4. Server provides no support for Register_Ownership. Host computers may provide a partial implementation of the function. Consult your host documentation to determine any limited support that may be supplied from the host computer. 5. If there has been an Extend_Call and the consulted party manually disconnects, a Retrieve_Call request is rejected by the switch (incompatible state). --------------------------------------------------------------------------- Set Program Calls Supported by the DMS-100 CO Switch The following table shows the DMS-100 CO switch level of support for the CallPath Services Set program calls. See Chapter 8. "Partially Supported Set Program Calls", for a detailed description of the partially supported Set program calls. Fully Partially Not Set Program Calls Supported Supported Supported Page Set_Add_Party_Direction &check. Set_Automatic_Answer &check. Set_Billed_Party(1) &check. Set_Call_Type(1) &check. Set_Called_Party_Alerting_Time(1) &check. Set_Disconnect_Execution_Option(2) &check. "STLSDEO (Set_Disconnect_Execution_Option)" Set_Extend_Purpose &check. "STLSEP (Set_Extend_Purpose)" Set_Held_Call_Connection(1) &check. Set_Held_Call_Recording(1) &check. Set_Holding_Party_Callback &check. Set_Holding_Party_Calling &check. Set_Make_Call_DND_Override(1) &check. Set_Make_Call_Forward_Override(1) &check. Set_Make_Call_Notification(1) &check. Set_Make_Call_Party_Order(1) &check. Set_Monitor_Tracking &check. Set_Parking_Party_Calling &check. Set_Party_Specification(1) &check. Set_Remaining_Parties_Option(1) &check. Set_Return_Response &check. Note: 1. Only the initialized value of the related characteristic for this Set program call is supported by the DMS-100 CO switch. 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. 2. This Set program call must be issued to modify the initialized setting of a call profile characteristic before any program call that references that characteristic can be issued. --------------------------------------------------------------------------- Messages Supported by the DMS-100 CO Switch The following table shows the DMS-100 CO switch level of support for the CallPath messages. See Chapter 9. "Partially Supported Messages", for a detailed description of each partially supported message. Fully Partially Not Messages Supported Supported Supported Page ACD_Information &check. "ACD_Information" Call_Alerting &check. "Call_Alerting" Call_Alternated &check. Call_Conferenced &check. Call_Connected &check. "Call_Connected" Call_Held (1) &check. "Call_Held" Call_Parked &check. Call_Parties &check. Call_Picked &check. "Call_Picked" Call_Rejected (2) &check. "Call_Rejected" Call_Routed &check. "Call_Routed" Call_Transferred &check. "Call_Transferred" Data_Collected &check. Disconnected &check. "Disconnected" Feature_Invoked &check. "Feature_Invoked" Hardware_Status &check. Indicator_Provided &check. Network_Reached &check. Party_Status &check. "Party_Status" Request_Instruction &check. "Request_Instruction" Resource_Deleted &check. Response &check. "Response" Status_Structure &check. Switch_Status &check. Notes: 1. A Call_Held message is generated when the switch notifies Server of a pending transfer, a positive Response to an Extend_Call request or a party being put on hold to answer another incoming call. 2. A Call_Rejected message is generated only when a Make_Call request fails because the ACD (automatic call distribution) agent did not pick up the telephone to answer the call. --------------------------------------------------------------------------- Special Considerations and Limitations The following are special considerations and limitations for using the CallPath API with the DMS-100 CO switch: * The DMS-100 CO switch CompuCall(**) feature only works in conjunction with its ACD (automatic call distribution) (**) Digital Centrex (MDC) features. MDC directory numbers and agent position ID's. * The DMS-100 CO switch sends event messages for a monitored resource when a call arrives at that resource. If A calls B and B is not monitored, no event messages are sent. We recommend that you monitor all telephone numbers involved in CallPath applications. For example, for calls that originate from a monitored agent, the only event message that will be generated is a one party Call_Connected message, unless the called party is also monitored. Refer to "STLMON (Monitor)" for more information on the Monitor program call. * If the same telephone call is manipulated by both CallPath program calls and by manual telephone activity, DMS-100 CO switch requests may be unsuccessful and DMS-100 CO switch messages may be unavailable or contain inaccurate information. * DMS-100 CO switch messages flow from the switch only when the primary ACD pilot number or MDC directory number is monitored. We therefore recommend that you monitor all ACD pilot numbers and MDC directory numbers involved in CallPath Services application programs. * 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 Server. * MDC telephones cannot be manipulated with CallPath Services program calls. Functions such as transferring a call must be done from the phone pad. However, the Disconnect program call may be used to remove an MDC telephone from a Conference_Call if the MDC telephone was the target of an Extend_Call. * A maximum of three parties can participate in a call. If a manual telephone operation is used to extend to a fourth party, unpredictable event messages will result. * The DMS-100 CO switch must be configured to send Call_Alerting event messages. * The DMS-100 CO switch does not support the Call_Conferenced event message. Server cannot confirm to CallPath application programs whether a Conference_Call request is successful. ACD agents must determine success or failure through progress tones on their phones. If you find that a conference attempt failed, you may issue a Retrieve_Call request to the switch to re-establish the original call. In this case, you should not send a Disconnect request. * As noted earlier in note 3, the call state of a given directory number or agent ID may be incorrect. This is caused by incomplete telephony information regarding this resource. The most common situation is that the DMS-100 CO switch does not send all Disconnected event messages and an agent ID is shown to be in one or more active calls that no longer exist. Stopping the monitor and restarting the monitor may not purge the invalid information. * For further information on Query_Party_Status refer to note 3. For further information on Extend_Call and on Retrieve_Call refer to note 5. --------------------------------------------------------------------------- Chapter 7. Partially Supported Program Calls This chapter describes the program calls provided by CallPath Services that are partially supported by the DMS-100 CO switch. (The Set program calls are described in Chapter 8. "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 Developers Toolkit Programming Guide and Reference for complete information on all program calls. You should also refer to the CallPath programming reference for your host computer system. See Chapter 11. "Example Program Call and Message Flows", for examples of program calls. --------------------------------------------------------------------------- STLCONF (Conference_Call) A program uses the Conference_Call (STLCONF) program call to retrieve a party in a held telephone call and to join the party in the retrieved telephone call with the parties in a second, active telephone call. The Conference_Call program call must be preceded by an Extend_Call program call. Note: The requesting party must be an ACD agent to implement a Conference_Call request, and this agent must have initiated the earlier Extend_Call request. The following tables show the DMS-100 CO switch support for Conference_Call: Related Calls Notes Set_Billed_Party Partially supported, see Note 1 Set_Return_Response Fully supported Parameters Notes requesting_party_ID_1 Fully supported requesting_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 --------------------------------------------------------------------------- STLINIT (Initialize_Call_Profile) A program uses the Initialize_Call_Profile (STLINIT) program call to initialize values for various program call 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 Developers Toolkit Programming Guide and Reference. Certain call profile characteristic values set by Initialize_Call_Profile are not valid for the DMS-100 CO switch. The appropriate Set program call must be issued after each Initialize_Call_Profile to set an acceptable value, as follows: * The characteristic disconnect_execution_option must be set to STL_DSC_IF_CONNECTED_NOT_QUEUE (see page "STLSDEO (Set_Disconnect_Execution_Option)"). 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) * held_call_connection (initialized value is STL_CONNECT_TO_SWITCH_DEFAULT) * held_call_recording (initialized value is null) * make_call_DND_override (STL_PARTY_ONE_DND_OVERRIDE) * make_call_forward_override (STL_PARTY_ONE_FORWARD_OVERRIDE) * 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_UNCONDITIONAL) For the following call profile characteristic, the initialized value and at least one other value is supported: * extend_purpose can be set to STL_EXTEND_UNSPECIFIED (initialized value) or STL_EXTEND_TRANSFER or STL_EXTEND_CONFERENCE. The following call profile characteristics are not supported: * add_party_direction * automatic_answer * 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 Developers Toolkit Programming Guide and Reference. --------------------------------------------------------------------------- STLINVK (Invoke_Feature) A program uses the Invoke_Feature (STLINVK) program call to invoke a switch feature for the telephone associated with the specified party, primarily to request the switch to change the status of a position ID. The possible status requests are Login, Logout, Ready, and Not Ready. The switch acknowledges the request. A positive response indicates that the switch will execute the request. A negative response indicates an error condition. After the status has been changed, the new status is sent as an event message, provided that the pilot ACD has been monitored. If the affected agent has been monitored, the event will be sent to the application as a Feature_Invoked event. As an agent's status changes, the event is published. This is done when the status is changed by an Invoke_Feature program call, when the agent depresses a status change key, or when the switch forces the position into a logged-off state. The switch is comprised of two entities: 1. A position ID that is a unique physical location of the telephone handset or headset 2. An agent ID (login ID) of the operator who can move from one position ID to another The following tables show the DMS-100 CO switch support for Invoke_Feature: Related Calls Notes Set_Return_Response Fully supported Parameters Notes call_profile_ID Fully supported feature_code STL_ADVANCED_AGENT_ACTIVITY Fully supported ALL OTHER VALUES Not supported feature_data_length 148 feature_data party_length Value 1 to 4 party Fully supported activity Partially supported STL_AGENT_LOGON Fully supported STL_AGENT_LOGOFF Fully supported STL_AGENT_READY Fully supported STL_AGENT_NOT_READY Fully supported ALL OTHER ACTIVITIES Not supported agent_id_length Value 1 to 4 agent_id Fully supported pool_length Value 0 pool Not supported work_group_ID_length Partially supported Value 1 to 3 work_group_ID Partially supported (Used for walk-away reason only) password_length Partially supported Value 1 to 4 password Partially supported (Agent password used for logon only) request_tag Fully supported return_code Fully supported Notes: 1. The BCS level must be set to 36. 2. The switch requires the position ID for all four status changes. 3. The Agent ID is required for login. 4. If the switch data table is set to accept a password upon login, then a valid password must be sent in the request. If a password is sent but the data table is not set to accept a password, the switch will send a negative response to a login request. 5. Login passwords are associated with agents, not position IDs. This association is established in the switch data tables. 6. If the switch data table requires a walk-away reason when Not Ready is invoked, then a walk-away reason must accompany the request. The validity of the walk-away reason is not checked. If a walk-away reason is sent and the data table is not set to receive a walk-away reason, the switch will send a negative response. 7. An agent ID may not log in at multiple positions at any one time. --------------------------------------------------------------------------- STLMAKE (Make_Call) A program uses the Make_Call (STLMAKE) program call to establish a two-party telephone call. The DMS-100 CO switch establishes a connection to party one first. If that connection is successful, a connection to the second party is attempted. Party one must be a valid DMS-100 CO switch agent position ID. The following tables show the DMS-100 CO switch support for Make_Call: Related Calls Notes Set_Automatic_Answer Not supported Set_Billed_Party Partially supported, see Note 1 Set_Call_Type Partially supported, see Note 1 Set_Called_Party_Alerting_Time Partially supported, see Note 1 Set_Make_Call_DND_Override Partially supported, see Note 1 Set_Make_Call_Forward_Override Partially supported, see Note 1 Set_Make_Call_Notification Partially supported, see Note 1 Set_Make_Call_Party_Order Partially supported, see Note 1 Set_Party_Specification Partially supported, see Note 1 Set_Return_Response Fully supported Version 0 and Version 1 Supported Parameters Parameters Notes party_one_length Value is 1 to 4 party_one Fully supported party_two_length Value is 1 to 21 party_two Fully supported call_profile_ID Fully supported account_code_length Value is 0 to 14 account_code Fully supported party_one_ID Fully supported party_two_ID Fully supported request_tag Fully supported return_code Fully supported Additional Version 1 Supported Parameters Parameters Notes program_data_length Value is 0 to 512 program_data Fully Supported --------------------------------------------------------------------------- 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 switch only sends event messages for the agents associated with an ACD group when the primary ACD pilot number for that ACD group is also monitored. To receive event messages for an agent position ID, both the agent position ID and the primary ACD pilot number must be monitored. We recommend that all ACD pilot numbers involved in all CallPath application programs be monitored. When issuing Monitor for a: * Primary ACD pilot number, specify monitor_resource_type to be STL_MONITOR_PILOT_NUMBER and a resource_length value of 10. * Supplementary ACD pilot number or an MDC directory number, specify monitor_resource_type to be STL_MONITOR_DIRECTORY_NUMBER and a resource_length value of 10. * ACD agent's position ID, specify monitor_resource_type to be STL_MONITOR_AGENT_IDENTIFIER and a resource_length value of 4. Notes: 1. A ten digit number must be used for monitor_resource_type STL_MONITOR_PILOT_NUMBER and STL_MONITOR_DIRECTORY_NUMBER. In North America the monitored number is a ten digit North American Numbering Plan directory number for pilot and directory number resource. An ACD agent position ID is represented by a four digit directory number. 2. Server uses monitor_resource_type STL_MONITOR_DIRECTORY_NUMBER for both ACD supplementary directory numbers and MDC directory numbers. If the switch returns an error for an unrecognized directory number, it may be that the directory number is invalid or that the user wants to monitor for a supplementary directory number. Server cannot distinguish in this case, and will return a positive Response. 3. If monitor_tracking is set to STL_TRACK_CALL you only get the events within the ACD group. For more information, please refer to CompuCall Interface Specification The following tables show the DMS-100 CO switch support for Monitor: Related Calls Notes Set_Monitor_Tracking Fully supported Set_Return_Response Fully supported Parameters Notes resource_length Value is 1 to 21 resource Fully supported monitor_resource_type Supported STL_MONITOR_AGENT_IDENTIFIER Supported STL_MONITOR_DIRECTORY_NUMBER Supported STL_MONITOR_GROUP Not supported list_size Fully supported event_list STL_CALL_ALERTING_EVENT Supported STL_CALL_ALTERNATED_EVENT Not supported STL_CALL_CONFERENCED_EVENT Not supported STL_CALL_CONNECTED_EVENT Supported STL_CALL_HELD_EVENT Supported (generated by CallPath and not by the DMS-100 CO switch) STL_CALL_PARKED_EVENT Not supported STL_CALL_PICKED_EVENT Supported STL_CALL_REJECTED_EVENT Supported (generated by CallPath and not by the DMS-100 CO switch) 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_NETWORKED_REACHED_EVENT Not 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 --------------------------------------------------------------------------- STLQACD (Query_ACD_Information) A program uses the Query_ACD_Information (STLQACD) program call to solicit information from a switch concerning automatic call distribution (ACD) processing. This information can be ACD status, the primary ACD-DN, the queue status identified by priority, and the agent status. An example of the type of information that can be requested is the number of telephone calls currently queued at an ACD pilot number. This information is returned in the Query_ACD_Information message. The resource queried is the primary ACD-DN or one of four supplementary ACD-DNs. See the Nortel CompuCall Interface Specification about DV-Resource_Query requests for more information. The following tables show the DMS-100 CO switch support for Query_ACD_Information: Related Calls Notes Set_Return_Response Fully supported Parameters Notes ACD_query_type STL_QUERY_PILOT_QUEUED_CALLS Not supported STL_QUERY_PILOT_AGENTS_SUMMARY Not supported STL_QUERY_PILOT_AGENTS_DETAIL Not supported STL_QUERY_SWITCH_SPECIFIC_ACD Fully supported resource_length Value is 10 resource Fully supported call_profile_ID Fully supported request_tag Fully supported return_code Fully supported Notes: 1. The BCS level must be set to 35 or 36. 2. The Query_ACD_Information program call queries the primary or supplementary ACD-DN. 3. The ACD_Information message resource field echoes the 10-digit ACD-DN number. --------------------------------------------------------------------------- STLRCV (Receive) A program uses the Receive (STLRCV) program call to receive a message sent to the program. The following table shows the DMS-100 CO switch 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 Supported STL_CALL_ALERTING_MSG Supported STL_CALL_ALTERNATED_MSG Not supported STL_CALL_CONFERENCED_MSG Not supported STL_CALL_CONNECTED_MSG Supported STL_CALL_HELD_MSG Supported STL_CALL_PARKED_MSG Not 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 Not supported STL_PARTY_STATUS_MSG Supported STL_REQUEST_INSTRUCTION_MSG 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 --------------------------------------------------------------------------- STLRED (Redirect_Call) A program uses the Redirect_Call (STLRED) program call to change the destination of an incoming call from one party to another. Notes: 1. The new party cannot be an agent position ID. 2. Redirects to a busy regular DN or a busy external party are not supported. The following tables show the DMS-100 CO switch support for Redirect_Call: Related Calls Notes Set_Called_Party_Alerting_Time Partially supported, see Note 1 Set_Return_Response Fully supported Version 0 and Version 1 Supported Parameters Parameters Notes party_ID Fully supported new_party_length Value is 1 to 21 new_party Fully supported call_profile_ID Fully supported new_party_ID Fully supported request_tag Fully supported return_code Fully supported Additional Version 1 Supported Parameters Parameters Notes program_data_length Value is 0 to 512 program_data 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. The transferring party must have established a telephone call with the new party before requesting the transfer. The transferring party is removed from both telephone calls upon completion of the Transfer_Call request. The following tables show the DMS-100 CO switch support for Transfer_Call: Related Calls Notes Set_Billed_Party Partially supported, see Note 1 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 --------------------------------------------------------------------------- STLTRGR (Trigger) A program uses the Trigger (STLTRGR) program call to trigger an action in the DMS-100 CO switch when a specified event is encountered. That is, the switch is requested to perform a specified action upon encountering a specified event. The program may request that the switch send a Request_Instruction message to the program when the switch encounters a specified event. This allows the program to guide the switch in its processing of the telephone call with which the event is associated. Without the Trigger and Request_Instruction combination, the switch would continue its normal processing of the call and any attempt by the program to influence the processing might not reach the switch in time to be successful. Notes: 1. The DMS-100 CO switch must have the ACD group defined with the Call_Redirection feature. 2. Use the 10-digit number for the ACD primary pilot number when issuing Trigger. Refer to CompuCall Interface Specification for details on the Call_Redirection feature and the ACD pilot number. The following tables show the DMS-100 CO switch support for Trigger: Related Calls Notes Set_Return_Response Fully supported Parameters Notes resource_length Value is 1 to 21 resource Fully supported trigger_resource_type STL_TRIGGER_AGENT_IDENTIFIER Not supported STL_TRIGGER_DIRECTORY_NUMBER Supported STL_TRIGGER_GROUP Not supported STL_TRIGGER_PILOT_NUMBER Supported trigger_event STL_TRIGGER_ON_CALL_ROUTED Supported STL_TRIGGER_ON_SETUP Not supported mode Fully supported action_code STL_SEND_REQUEST_INSTRUCTION Supported STL_SEND_MAKE_CALL Not supported action_data_length Value is 0 action_data Not supported Parameters Notes call_profile_ID Fully supported request_tag Fully supported return_code Fully supported --------------------------------------------------------------------------- STLXTND (Extend_Call) A program uses the Extend_Call (STLXTND) program call to extend an existing telephone call. To successfully extend a call, the connections of the two parties in the existing telephone call must be in the Connected state. The connection of the new party must be in the Idle state. (For a full description of connections and connection states, see CallPath Developers Toolkit Programming Guide and Reference.) Following a successful execution of this request, the requesting party is connected to the new party and the party previously connected to the requesting party is placed on hold. Extend_Call can be used by itself or be followed by a Transfer_Call program call. Note: The party on whose behalf the Extend_Call program call is issued (that is, the party whose connection ID is specified in requesting_party_ID_1) must be an agent position ID. The following tables show the DMS-100 CO switch support for Extend_Call: Related Calls Notes Set_Billed_Party Partially supported, see Note 1 Set_Called_Party_Alerting_Time Partially supported, see Note 1 Set_Extend_Purpose Partially supported, see page "STLSEP (Set_Extend_Purpose)" Set_Held_Call_Connection Partially supported, see Note 1 Set_Held_Call_Recording Partially supported, see Note 1 Set_Return_Response Fully supported Version 0 and Version 1 Supported Parameters Parameters Notes requesting_party_ID_1 Fully supported new_party_length Value is 1 to 21 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 Additional Version 1 Supported Parameters Parameters Notes program_data_length Value is 0 to 512 program_data Fully Supported --------------------------------------------------------------------------- Chapter 8. Partially Supported Set Program Calls This chapter describes the Set program calls provided by CallPath Services that are partially supported by the DMS-100 CO switch, except those where only the initialized value of the call profile characteristic is supported. These Set program calls are identified in the table on page "Set Program Calls Supported by the DMS-100 CO Switch". 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 Set_Disconnect_Execution_Option program call must be issued after each Initialize_Call_Profile to override the initialized call profile characteristic value that is not valid for the DMS-100 CO switch. Refer to CallPath Developers Toolkit Programming Guide and Reference for complete information on all Set program calls. You should also refer to the CallPath Services programming reference for your host computer system. --------------------------------------------------------------------------- STLSDEO (Set_Disconnect_Execution_Option) Set_Disconnect_Execution_Option (STLSDEO) is used by a program to set the disconnect_execution_option characteristic for a given call profile. The disconnect_execution_option characteristic specifies under what conditions a subsequent Disconnect program call, and its resulting request to the target switch, is to be executed. Set_Disconnect_Execution_Option overrides the value that was assigned by the Initialize_Call_Profile program call. Note: A program is allowed to change the disconnect_execution_option at any time. The following table shows the DMS-100 CO switch support for Set_Disconnect_Execution_Option: Parameters Notes call_profile_ID Fully supported disconnect_execution_option STL_DSC_UNCONDITIONAL Not supported (initialized value) STL_DSC_IF_CONNECTED Not supported STL_DSC_IF_CONNECTED_NOT_QUEUE Supported STL_DSC_IF_CONNECTED_QUEUE Not supported STL_DSC_IF_ROUTING Not supported STL_DSC_IF_ROUTING_OR_ALERTING Not supported return_code Fully supported --------------------------------------------------------------------------- STLSEP (Set_Extend_Purpose) Set_Extend_Purpose (STLSEP) is used by a program to modify 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. The following table shows the DMS-100 CO switch support for Set_Extend_Purpose: Parameters Notes call_profile_ID Fully supported extend_purpose STL_EXTEND_UNSPECIFIED Supported STL_EXTEND_TRANSFER Supported STL_EXTEND_ALTERNATE Not supported STL_EXTEND_CONFERENCE Supported return_code Fully supported --------------------------------------------------------------------------- Chapter 9. Partially Supported Messages This chapter describes the messages provided by CallPath Services that are partially supported by the DMS-100 CO switch. 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 Developers Toolkit Programming Guide and Reference for complete information on the four types messages, and system messages. You should also refer to the CallPath 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 page "Time_And_Date". The level of support for Party_Structure, which is used by many fields of the messages, is described on page "Party_Structure". The status_list field, which is found in the Party_Status message, uses the Status_Structure structure, which is described on page "Status_Structure". --------------------------------------------------------------------------- ACD_Information The ACD_Information reply message provides information to the program regarding an automatic call distribution (ACD) group. It is sent in response to the Query_ACD_Information program call. The following table shows the DMS-100 CO switch support for ACD_Information: Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" resource_length Value is 10 resource Fully supported (This is the resource that was queried.) ACD_query_type STL_QUERY_PILOT_QUEUED_CALLS Not supported STL_QUERY_PILOT_AGENTS_SUMMARY Not supported STL_QUERY_PILOT_AGENTS_DETAIL Not supported STL_QUERY_SWITCH_SPECIFIC_ACD Fully supported reserved Does not contain a value ACD_data_length Value is 2060 ACD_data pilot_queued_calls_data Not supported pilot_agents_summary_data Not supported pilot_agents_detail_data Not supported switch_specific_ACD_data Partially supported Notes: 1. The BCS level must be set to 35 or 36. 2. The resource parameter is the resource that was queried. It echoes the ACD-DN that was queried in the STLQACD program call. It can be the primary or supplementary ACD-DN. 3. The timestamp is the Server timestamp. The switch includes a timestamp in its message, but it is ignored. 4. The switch_specific_ACD_data field contains contains four fields, as follows: o version_number o data_format_code o switch_ACD_data_length o switch_ACD_data The first three fields are of type INTEGER and the fourth field is a buffer of type UCHAR. This buffer contains data elements in ASCII string form as shown in Table 5. If a data element is missing in the switch message, the string is -1. Each string ends with a string termination character, \0. 5. If the STLQACD program call is made with an ACD_query_type other than STL_QUERY_SWITCH_SPECIFIC_ACD, a negative response is returned with a sense code qualifier of X'8C610000DF8125' and sense code equal to STL_RQ_NOT_SUPPORTED_BY_SWITCH. The maximum Group Primary ACD-DN string size is 31 characters (one byte per character), not including the string termination character (that is, a maximum of 32 bytes including the string termination character). All other data elements have a maximum string size of 7 characters per data element (that is, a maximum of 8 bytes including the string termination character). Following is a list of data elements provided in the switch_ACD_data buffer and the corresponding fixed offsets in the buffer: Table 5. Data Elements Provided in the switch_ACD_data Buffer Data Element Offset Group Primary ACD-DN 0 Group Status 32 Maximum Incoming Call Queue Size 40 Maximum Call Transfer Queue Size 48 Priority of Queried ACD-DN 56 Size of the Incoming Call Queue 64 Size of the Call Transfer Queue 72 Size of Overflow Out Queue 80 First Priority 88 1st Priority Incoming Call Queue Size 96 Second Priority 104 2nd Priority Incoming Call Queue Size 112 Third Priority 120 3rd Priority Incoming Call Queue Size 128 Fourth Priority 136 4th Priority Incoming Call Queue Size 144 Number of Agents Logged In 152 Number of Agents Active on a Call 160 Number of Agents Available 168 Number of Agents in a Not Ready State 176 Number of Agents with Transferred Calls Waiting in Queue 184 --------------------------------------------------------------------------- Call_Alerting 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 DMS-100 CO switch support for Call_Alerting: Version 0 and Version 1 Supported Fields Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" calling_party_info STRUCTURE (Party_Structure); partially supported, see page "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 Supported STL_CALL_EXTENSION Supported STL_NO_CALL_EXTENSION Supported STL_CALL_EXTENSION_TO_TRANSFER Not supported track_call_party_length Value is 1 to 21 track_call_party Fully supported alerting_party_count Value is 1 alerting_party_list List of (Party_Structure); partially supported, see page "Party_Structure" Additional Version 1 Supported Fields Fields Notes program_data_length Value is 0 to 512 program_data Fully supported billing_change Not supported related_call_party_count Not supported related_call_party_list Not supported alert_reason STL_ALERT_NOT_SPECIFIED Supported STL_CALL_BACK Not supported STL_ALERT_REMAINS_QUEUED Not supported --------------------------------------------------------------------------- Call_Connected The Call_Connected call-progress event message tells a program that a party has become an active participant in a telephone call. The following tables show the DMS-100 CO switch support for Call_Connected: Version 0 and Version 1 Supported Fields Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" connecting_party_info STRUCTURE (Party_Structure); partially supported, see page "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 Supported STL_CALL_EXTENSION Supported STL_NO_CALL_EXTENSION Supported STL_CALL_EXTENSION_TO_TRANSFER Not supported track_call_party_length Value is 1 to 21 track_call_party Fully supported existing_party_count Value is 0 to 1 existing_party_list List of (Party_Structure); partially supported, see page "Party_Structure" Additional Version 1 Supported Fields Fields Notes program_data_length Value is 0 to 512 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 --------------------------------------------------------------------------- Call_Held 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. This event message is generated by Server when it receives switch event messages that indicate a pending transfer, a positive Response to an Extend_Call request or that a party has been placed on hold to answer another incoming call. The following table shows the DMS-100 CO switch support for Call_Held: Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" holding_party_info STRUCTURE (Party_Structure); partially supported, see page "Party_Structure" holding_info; holding_party_calling STL_CALLS_NOT_PERMITTED Not supported STL_CALLS_PERMITTED Supported STL_SWITCH_DEFAULT_CALLING Not supported holding_party_ID_2 Supported holding_party_callback STL_NO_CALLBACK Not supported STL_CALLBACK Not supported STL_SWITCH_DEFAULT_CALLBACK Supported track_call_party_length Value is 1 to 21 track_call_party Fully supported held_party_count Value is 1 held_party_list List of (Party_Structure); partially supported, see page "Party_Structure" --------------------------------------------------------------------------- Call_Picked The Call_Picked call-progress event message tells a program that a telephone call has been picked; that is, 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. The DMS-100 CO switch will not send a Call_Picked event message when a Call_Held is picked. The following table shows the DMS-100 CO switch support for Call_Picked: Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" connecting_party_info STRUCTURE (Party_Structure); partially supported, see page "Party_Structure" picked_from_party_info STRUCTURE (Party_Structure); partially supported, see page "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 1 to 21 track_call_party Fully supported existing_party_count Value is 1 existing_party_list List of (Party_Structure); used when existing_party_count > 0; partially supported, see page "Party_Structure" --------------------------------------------------------------------------- Call_Rejected The Call_Rejected call-progress event message tells a program that a telephone call could not be completed. Information on the rejection of the telephone call is contained in the message. Call_Rejected only occurs as a result of a host-initiated request. This event message is generated by Server only when the ACD specified in the Make_Call request does not answer. The following table shows the DMS-100 CO switch support for Call_Rejected: Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" called_party_info STRUCTURE (Party_Structure); partially supported, see page "Party_Structure" calling_party_info STRUCTURE (Party_Structure); partially supported, see page "Party_Structure" reject_reason STL_REASON_UNKNOWN Not supported STL_REASON_BUSY Not supported STL_REASON_INVALID_DIR_NUM Not supported STL_REASON_DEV_OUT_OF_SERVICE Not supported STL_REASON_DO_NOT_DISTURB_SET Not supported STL_REASON_RING_NO_ANSWER Supported 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 STL_REASON_CIRCUIT_DETECT_UNAVAIL Not supported STL_REASON_TEMPORARY_CONGESTION Not supported STL_REASON_TRUNKS_UNAVAILABLE Not supported STL_REASON_CIRCUIT_DTCT_TMP_CONGEST Not supported STL_REASON_TRUNKS_TEMP_CONGEST Not supported error_indication STL_ERROR_IN_CALLING_PARTY Supported STL_ERROR_IN_CALLED_PARTY Not supported track_call_party_length Value is 1 to 21 track_call_party Fully supported --------------------------------------------------------------------------- Call_Routed The Call_Routed call-progress event message tells a program that an incoming telephone call has been routed to the called party. The following tables show the DMS-100 CO switch support for Call_Routed: Version 0 and Version 1 Supported Fields Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" calling_party_info STRUCTURE (Party_Structure); partially supported, see page "Party_Structure" routed_from_party_info STRUCTURE (Party_Structure); partially supported, see page "Party_Structure" 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 Not supported STL_DND_FORWARD_ROUTE Not supported STL_BUSY_FORWARD_ROUTE Not 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 Supported STL_CALL_EXTENSION Supported STL_NO_CALL_EXTENSION Supported STL_CALL_EXTENSION_TO_TRANSFER Not supported track_call_party_length Value is 1 to 21 track_call_party Fully supported routed_to_party_count Value is 1 routed_to_party_list List of (Party_Structure); partially supported, see page "Party_Structure" Additional Version 1 Supported Fields Fields Notes program_data_length Value is 0 to 512 program_data Fully supported related_call_party_count Not supported rrelated_call_party_list Not supported billing_change Not supported --------------------------------------------------------------------------- Call_Transferred 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 DMS-100 CO switch support for Call_Transferred: Version 0 and Version 1 Supported Fields Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" transferring_party_1_info STRUCTURE (Party_Structure); partially supported, see page "Party_Structure" transferring_party_2_info STRUCTURE (Party_Structure); partially supported, see page "Party_Structure" billed_party_length Value is 0 billed_party Not supported track_call_party_length Value is 1 to 21 track_call_party Fully supported Additional Version 1 Supported Fields Fields Notes remaining_party_count Value is 1 to 8 remaining_party_list List of (Party_Structure) --------------------------------------------------------------------------- Disconnected The Disconnected call-progress event message tells a program that a party's connection within a telephone call has transitioned to the Idle state. (For a full description of connections and connection states, see the CallPath Developers Toolkit Programming Guide and Reference.) The DMS-100 CO switch sends this message, for example, when a party physically hangs up a telephone to end a call. The following tables show the DMS-100 CO switch support for Disconnected: Version 0 and Version 1 Supported Fields Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" disconnecting_party_info STRUCTURE (Party_Structure); partially supported, see page "Party_Structure" track_call_party_length Value is 1 to 21 track_call_party Fully supported other_disconnected_party_count Value is 1 to 2 other_disconnected_party_list List of (Party_Structure); partially supported, see page "Party_Structure" Additional Version 1 Supported Fields Fields Notes remaining_party_count Value is 1 to 8 remaining_party_list List of (Party_Structure); partially supported, see page "Party_Structure" program_data_length Value is 0 to 512 program_data Fully supported disconnect_reason STL_DISCONNECT_NOT_SPECIFIED Supported STL_ABANDON Not supported --------------------------------------------------------------------------- Feature_Invoked The Feature_Invoked call-progress event message indicates to the 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, or when a program issues the Invoke_Feature program call to invoke a feature on behalf of a party. The following tables show the DMS-100 CO switch support for Feature_Invoked: Fields Notes version_number Fully Supported switch_ID Fully Supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" feature_code Partially supported (only supports STL_ADVANCED_AGENT_ACTIVITY.) feature_data party_length Value is 4 party Fully supported activity Partially supported STL_AGENT_LOGON Fully supported STL_AGENT_LOGOFF Fully supported STL_AGENT_READY Fully supported STL_AGENT_NOT_READY Fully supported ALL OTHER ACTIVITIES Not supported agent_id_length Value is 4 (only appears for STL_AGENT_LOGON) agent_id Partially supported (only appears for STL_AGENT_LOGON) pool_length Value is 10 pool Fully supported (contains the ACD-DN controlling this Position_ID) work_group_ID_length Value is 3 (only supported for STL_AGENT_NOT_READY) work_group_ID Partially supported (contains walk-away reason for Not Ready status) password_length Value is 0 password Not supported Notes: 1. The BCS level must be set to 36. 2. At least one of the applications must monitor the Primary ACD-DN for any valid event/rank combination. 3. In order to receive the Feature_Invoked message for a specific Position_ID, the following conditions must be satisfied: o Primary ACD_DN must be monitored o Position_ID must be monitored o Event_list for that Position_ID must include the STL_FEATURE_INVOKED_EVENT --------------------------------------------------------------------------- Party_Status The Party_Status reply message provides the current status of a particular party to the program. The switch sends the Party_Status message to a program only as a result of the program issuing an earlier Query_Party_Status program call. The following table shows the DMS-100 CO switch support for Party_Status: Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" party_length Value is 1 to 21 party Fully supported status_count Value is 0 to 8 status_list STRUCTURE (Status_Structure); used when status_count > 0; partially supported, see page "Status_Structure" --------------------------------------------------------------------------- Request_Instruction The Request_Instruction reply message solicits information from the program concerning how to proceed with a telephone call. The program, upon receiving the Request_Instruction message, may issue either a Redirect_Call or Return_Control program call. The following table shows the DMS-100 CO switch support for Request_Instruction: Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "Time_And_Date" timer_value Value is 0 trigger_event STL_TRIGGER_ON_CALL_ROUTED Supported STL_TRIGGER_ON_SETUP Not supported trigger_event_data Fully supported re_request Value is 0 reserved Not supported Note: The timer_value field is set to zero to indicate that the amount of time allowed for a program to reply to the Request_Instruction message is switch dependent and is not carried in the messages received from the DMS-100 CO switch. To determine the actual time configured for your DMS-100 CO switch, consult your switch administrator. The amount of time configured for your DMS-100 CO switch is the period that the switch will wait until it routes the call without any instructions from the application program. --------------------------------------------------------------------------- Response The Response message is a response from the DMS-100 CO switch to an earlier request from the program. It tells the program whether the earlier request was accepted or rejected by the DMS-100 CO switch. 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 DMS-100 CO switch support for Response: Fields Notes version_number Fully supported switch_ID Fully supported timestamp STRUCTURE (Time_And_Date); partially supported, see page "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 Not supported STL_STATE_INCOMPATIBLE_WITH_RQ Supported STL_CONF_TRANSFER_INVALID Not 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 Supported STL_AUTO_ANSWER_PARTY_UNKNOWN Not supported STL_SWITCH_SPECIFIC_ERROR Supported STL_RESOURCES_NOT_AVAILABLE Supported STL_INVALID_AGENT_ASSIGNMENT Not supported STL_INVALID_POOL Not supported STL_REDUNDANT_POOL_ASSIGNMENT Not supported STL_TRACKING_INCONSISTENCY Supported STL_SYSTEM_ERROR Supported STL_TRGR_REDUNDANCY Supported STL_TRGR_BY_ANOTHER_PROGRAM Supported STL_TRGR_BY_SAME_PROGRAM Supported STL_RES_OWNERSHIP_INCOMPATIBLE Not supported STL_PGM_NOT_AUTHORIZED_FOR_RES Not supported STL_RESOURCE_AND_TYPE_MISMATCH Not supported STL_INVALID_AGENT_ID Supported STL_CONNECTION_ID_MISMATCH Not supported sense_code_qualifier_length Value is 0 to 32 sense_code_qualifier Used when sense_code_qualifier_length > 0; see page "Sense Code Qualifiers" --------------------------------------------------------------------------- Party_Structure 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 DMS-100 CO switch provides as much information about the party as is available to it. The information is extensive and 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 DMS-100 CO switch support for Party_Structure: (*) Fields Notes Common_Information STRUCTURE connection_ID_present Fully supported connection_ID Fully supported party_numbering_plan Fully supported party_number_length Value is 0 to 21 party_number Fully supported party_address_length Value is 0 to 10 party_address Field contains the switch's local Call ID* party_type Fully supported Called_Party_Information STRUCTURE party_group_length Value is 0 to 21 party_group Fully supported original_group_length Value is 0 to 21 original_group Fully supported dialed_number_length Value is 0 to 21 dialed_number Fully supported DNIS_length Value is 0 DNIS Not supported trunk_number_length Value is 0 trunk_number Not supported --------------------------------------------------------------------------- Status_Structure The Status_Structure contains information about a party's connection within a telephone call. The Status_Structure is referenced by other structures and messages, such as the Party_Status message and the Call_Party_Structure. The following table shows the DMS-100 CO switch support for Status_Structure: Fields Notes party_ID Fully supported connection_state STL_STATE_UNKNOWN Fully supported STL_STATE_PENDING Fully supported STL_STATE_ROUTING Fully supported STL_STATE_ALERTING Fully supported STL_STATE_CONNECTED Fully supported STL_STATE_CONNECTED_ACTIVE Not supported STL_STATE_CONNECTED_HOLDING Not supported --------------------------------------------------------------------------- Time_And_Date The Time_And_Date structure is referenced by the individual messages. The following table shows the DMS-100 CO switch 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 --------------------------------------------------------------------------- Chapter 10. Problem Determination This chapter describes the types of problem determination data available and how you obtain them. If an error is reported by CallPath SwitchServer/2, CallPath Server for OS/2, or CallPath Server for AIX (collectively called "Server" hereafter) consult Using CallPath SwitchServer/2 or the CallPath Server Planning, Installation, and Problem Determination Guide as appropriate. For more detailed troubleshooting procedures when using CallPath SwitchServer/2, use an editor to view the READ.ME file in the CallPath SwitchServer/2 C:\GATEWAY directory. For more detailed troubleshooting procedures when using the Server on other platforms, see the CallPath Server Planning, Installation, and Problem Determination Guide. Note: Except where there is a need to differentiate between CallPath SwitchServer/2, CallPath Server for OS/2, CallPath Server for AIX, and CallPath Server for MS Windows NT, the term Server will be used in place of these names. --------------------------------------------------------------------------- Return Codes The DMS-100 CO switch fully supports return codes. For information about return codes, see CallPath Developers Toolkit Programming Guide and Reference and the CallPath programming reference for your host computer system. --------------------------------------------------------------------------- Sense Code Qualifiers When the DMS-100 CO switch or Server 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 on 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 when connected to the DMS-100 CO switch. STL_SWITCH_SPECIFIC_ERROR 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 DMS-100 CO switch. 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'000801' Description: A Make_Call request failed because the agent was not logged on to the ACD group. Action: Ensure that the agent is set up properly and reissue the request. Sense code qualifier: X'000802' Description: A Monitor request failed because the specified resource given is already being used in another switch session. Action: Consult your switch coordinator for more information. STL_SYSTEM_ERROR Sense code qualifier: X'00000007' Description: A request was rejected because the switch detected a protocol error. Action: Contact your IBM Service Representative. Sense code qualifier: X'00000009' Description: The switch-defined NetworkCallID inserted into the program's request by CallPath Server or CallPath SwitchServer/2 when it forwards the request to the switch is invalid. Action: Consult your IBM Service Representative. Sense code qualifier: X'0000000A' Description: The directory number provided by CallPath SwitchServer/2 is incorrect. In this case, the application did not provide a directory number in its request. CallPath Server or CallPath SwitchServer/2 supplied the number when it forwarded the request to the switch. Action: Consult your IBM Service Representative. STL_RQ_NOT_SUPPORTED_BY_SWITCH Sense code qualifier: X'810300000000' Description: A parameter specification on a Conference_Call is not supported by the switch. No further information is known about this parameter specification. Action: Refer to "STLCONF (Conference_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. If a current call profile characteristic value is not supported, issue the appropriate Set program call to change the value to one that is supported. Reissue the request with valid information. Sense code qualifier: X'81030000DF20' Description: The account_code value associated with Conference_Call is not supported. Action: Refer to "STLCONF (Conference_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request with valid information. Sense code qualifier: X'81030000DF26' Description: The billed_party value contained within the call profile specified by the call_profile_ID parameter on the Conference_Call program call is not supported. Issue the Set_Billed_Party program call to change the billed_party value to the supported value. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLCONF (Conference_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request with valid information. Sense code qualifier: X'810400000000' Description: A parameter specification on a Disconnect_Call is not supported by the switch. No further information is known about this parameter specification. Action: If a current call profile characteristic value is not supported, issue the appropriate Set program call to change the value to one that is supported. Reissue the request with valid information. 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 is not supported. Issue the Set_Disconnect_Execution_Option program call to change the disconnect_execution_option value to the supported val ue. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Reissue the request 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 is not supported. Action: Reissue the request with valid information. Sense code qualifier: X'810500000000' Description: A parameter specification on an Extend_Call is not supported by the switch. No further information is known about this parameter specification. Action: Refer to "STLXTND (Extend_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. If a current call profile characteristic value is not supported, issue the appropriate Set program call to change the value to one that is supported. Reissue the request with valid information. Sense code qualifier: X'81050000DF20' Description: The account_code value associated with Extend_Call is not supported. Action: Refer to "STLXTND (Extend_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request 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 is not supported. Issue the Set_Billed_Party program call to change the billed_party value to the supported value. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLXTND (Extend_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request 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. Action: Refer to "STLXTND (Extend_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request 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 is not supported. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLXTND (Extend_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request 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 is not supported. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLXTND (Extend_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request 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 is not supported. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLXTND (Extend_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request with valid information. Sense code qualifier: X'81070000DF33' Description: The activity or feature_code value contained in the STLINVK program call is not supported. The activity values supported are: STL_AGENT_LOGON, STL_AGENT_LOGOFF, STL_AGENT_READY and STL_AGENT_NOT_READY. The supported feature_code value is STL_ADVANCED_AGENT_ACTIVITY. Action: Reissue Invoke_Feature with the correct activity and feature_code values. Sense code qualifier: X'810800000000' Description: A parameter specification on a Make_Call is not supported by the switch. No further information is known about this parameter specification. Action: Refer to "STLMAKE (Make_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. If a current call profile characteristic value is not supported, issue the appropriate Set program call to change the value to one that is supported. Reissue the request with valid information. Sense code qualifier: X'81080000DF20' Description: The account_code value associated with Make_Call is not supported. Action: Refer to "STLMAKE (Make_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. 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 is not supported. Issue the Set_Billed_Party program call to change the billed_party value to the supported value. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLMAKE (Make_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. 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 is not supported. Issue the Set_Call_Type program call to change the call_type value to the supported value. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLMAKE (Make_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. 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 is not supported. Issue the Set_Make_Call_DND_Override program call to change the make_call_DND_override value to the supported value. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLMAKE (Make_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. 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 is not supported. Issue the Set_Make_Call_Forward_Override program call to change the make_call_forward_override value to the supported value. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLMAKE (Make_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. 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 is not supported. Issue the Set_Make_Call_Notification program call to change the make_call_notification value to the supported value. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLMAKE (Make_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. 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 is not supported. Issue the Set_Called_Party_Alerting_Time program call to change the called_party_alerting_time value to the supported value. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLMAKE (Make_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. 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 is not supported. Issue the Set_Make_Call_Party_Order program call to change the make_call_party_order value to the supported value. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLMAKE (Make_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request with valid information. Sense code qualifier: X'810900000000' Description: A parameter specification on a Monitor request is not supported by the switch. No further information is known about this parameter specification. Action: Refer to "STLMON (Monitor)" for valid parameter values for the Monitor program call. Reissue the request with valid information. Sense code qualifier: X'81090000DF3D' Description: The mode value associated with Monitor is not supported. Action: Refer to "STLMON (Monitor)" for valid parameter values for the Monitor program call. Reissue the request with valid information. Sense code qualifier: X'81090000DF7A' Description: The monitor_resource_type value of STL_MONITOR_GROUP on the Monitor program call is not supported by the DMS-100 CO switch. Action: Refer to "STLMON (Monitor)" for valid parameter values for the Monitor program call. Reissue the request with valid information. Sense code qualifier: X'81090000FF5DFFEC00...0' 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 indicates what event/rank combinations are supported by the switch. Refer to the Response message in the CallPath Developers Toolkit Programming Guide and Reference for the table that defines the bit map. Action: Reissue Monitor with a valid event/rank combination. Sense code qualifier: X'81090000FF5DFFEE00C00...0' 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 indicates what event/rank combinations are supported by the switch. Refer to the Response message in the CallPath Developers Toolkit Programming Guide and Reference for the table that defines the bit map. This sense code qualifier differs from the preceding sense code qualifier because of the support of the Feature_Invoked event with primary rank. Action: Reissue Monitor with a valid event/rank combination. Sense code qualifier: X'810A0000DF8107' Description: The called_party_alerting_time value contained within the call profile specified by the call_profile_ID parameter on the Redirect_Call program call is not supported. Issue the Set_Called_Party_Alerting_Time program call to change the called_party_alerting_time value to the supported value. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLRED (Redirect_Call)" Reissue the request with valid information. Sense code qualifier: X'810E00000000' Description: A parameter specification on a Transfer_Call is not supported by the switch. No further information is known about this parameter specification. Action: Refer to "STLTRAN (Transfer_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. If a current call profile characteristic value is not supported, issue the appropriate Set program call to change the value to one that is supported. Reissue the request with valid information. Sense code qualifier: X'810E0000DF20' Description: The account_code value associated with a Transfer_Call is not supported. Action: Refer to "STLTRAN (Transfer_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request 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 on a Transfer_Call program call is not supported. Issue the Set_Billed_Party program call to change the billed_party value to the supported value. The DMS-100 CO switch supports only the initialized value for this call profile characteristic. Action: Refer to "STLTRAN (Transfer_Call)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request with valid information. Sense code qualifier: X'810F00000000' Description: A parameter specification on a Trigger request is not supported by the switch. No further information is known about this parameter specification. Action: Refer to "STLTRGR (Trigger)" for the supported parameters, call profile characteristics, and parameter and characteristic values. If a current call profile characteristic value is not supported, issue the appropriate Set program call to change the value to one that is supported. Reissue the request with valid information. Sense code qualifier: X'810F0000DF3D' Description: The mode associated with Trigger is not supported. Action: Refer to "STLTRGR (Trigger)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request with valid information. Sense code qualifier: X'810F0000DF50' Description: The action_code associated with Trigger is not supported. Action: Refer to "STLTRGR (Trigger)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request with valid information. Sense code qualifier: X'810F0000DF51' Description: The trigger_event associated with Trigger is not supported. Action: Refer to "STLTRGR (Trigger)" for the supported parameters, call profile characteristics, and parameter and characteristic values. Reissue the request with valid information. Sense code qualifier: X'8C610000DF8125' Description: The ACD_Query_type value on an ACD_Information request is not supported. Action: Set the ACD_query_type to STL_QUERY_SWITCH_SPECIFIC_ACD. --------------------------------------------------------------------------- System Messages Data CallPath SwitchServer/2, CallPath Server for OS/2, and CallPath Server for AIX (hereafter collectively called server) record all system messages in a system messages buffer. You can display the system messages data directly on the screen, print them to a file, 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 the CallPath Server Planning, Installation, and Problem Determination Guide or Using CallPath SwitchServer/2. System messages include noncritical and critical program error messages. Noncritical program errors are primarily informational. When critical program errors occur, Server automatically reloads its code and data from the disk and restarts the program if it is configured for restart on failure. All critical program errors are also sent: * As alerts to IBM NetView*, a program product that displays message contents to the network administrator and provides network status information based on the alerts. For details on the alerts, see "NetView Alerts (for CallPath SwitchServer/2 Only)". * To the Simple Network Management Protocol (SNMP) focal point. The following table shows the category and numerical range of the system messages listed in this section: Category Range Program (noncritical) 5000-5999 Program (critical) 6000-6399, 6500-6699 Switch connection (critical--local connection 6400-6499 only) Note: When you receive severe error 6028 ERR_BAD_CRITICAL_ERR_NUM, another message number in the range 6000-6699 is displayed as well. Look up the second message number for problem determination and resolution. Overload messages, another category of messages, are not generated by CallPath SwitchServer/2 with the DMS-100 CO switch feature. When the link fails, such as when the plug becomes loose or the modem fails, several comment lines and a time stamp are appended to the file linkdbg.log in the switchdm subdirectory of the csasrvr directory (or in the CPSS2 directory for CallPath SwitchServer/2). Diagnostic and cause codes are provided by the X.25 API as they become available and are collected in a flat ASCII text file. If link failures are excessive, the contents of this file may be helpful in analyzing the X.25 API or line problems. The user is responsible for monitoring the size of this file and periodically removing old entries. Note: Except where there is a need to differentiate between CallPath SwitchServer/2, CallPath Server for OS/2, and CallPath Server for AIX, the term Server will be used in place of the phrases "CallPath SwitchServer/2, CallPath Server for OS/2, and CallPath Server for AIX". Program Messages (Noncritical) 5000 ERR_NON_CRITICAL_PGM Explanation: Non-critical 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_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 5018 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 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 Module: CGEN Severity: WARNING 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. 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_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 5029 ERR_INVAL_CALLID_SIZE Explanation: Invalid number of call IDs specified during Call State initialization. Cause: The switch-dependent part of the server requested that more call IDs 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: 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 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 5037 ERR_ASN1_DECODE_BAD_FIELD Explanation: The decoder encountered a bad field. Cause: The decoder encountered a bad field and could not decode the request. 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 5038 ERR_TOO_MANY_PARTIES Explanation: An attempt was made to add too many parties to a call. Cause: The switch-dependent part of the server requested that more than 20 parties be associated with a call. Action: The additional parties are lost or not processed properly, thereby losing information or presenting invalid information. Module: CGEN Severity: WARNING 5039 ERR_STILL_IN_OVERLOAD Explanation: A switch request tag overload condition still exists. Cause: A request was issued during an overload condition. Action: The application should wait until the overload condition is cleared before reissuing the request. Module: CGEN Severity: WARNING 5040 ERR_MAP_INVALID_REQUEST Explanation: The mapping routine encountered an unknown request. Cause: The switch-dependent part of the server encountered a internal error while processing a request. Action: If this problem persists, the switch-dependent part of the server needs to be checked. Run the server trace facility, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5041 ERR_MAP_INVALID_EVENT Explanation: The mapping routine encountered an unknown event. Cause: The switch-dependent part of the server tried to send an event that is not supported. Action: If this problem persists, the switch-dependent part of the server needs to be checked. Run the server trace facility, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5042 ERR_PI_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 5043 ERR_PI_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 5044 ERR_PI_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 5045 ERR_PI_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 5046 ERR_PI_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 5047 ERR_PI_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 5049 ERR_PI_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 5050 ERR_PI_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 5051 ERR_DN_LEN_ZERO Explanation: A directory number length of zero was detected. Cause: The Call State routines were passed a directory number that had a length of zero. Action: Verify that the request that has been issued has valid directory numbers and reissue the request. If this problem persists, the switch-dependent part of the server needs to be checked. Module: CGEN Severity: WARNING 5052 ERR_INVAL_GRT_NUMBER Explanation: The number of GRTs exceeds the maximum allowed at initialization. Cause: The switch-dependent part of the server requested that more gateway 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: WARNING 5053 ERR_INVAL_INACTIVE_PERCENT Explanation: The inactive percentage is too large at initialization. Cause: The switch-dependent part of the server requested during initialization of the Call State routines that the percentage of calls to be marked as inactive for cleanup is too large. Action: Run the server trace facility, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5054 ERR_INVAL_OVERLOAD_PERCENT Explanation: The overload percentage is invalid at initialization. Cause: The switch-dependent part of the server requested an invalid value for the percentage of requests that need to be cleaned up to exit the overload condition. Action: Run the server trace facility, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5055 ERR_INVAL_FIRST_RCT Explanation: The value of the first request tag is invalid at initialization. Cause: The switch-dependent part of the server requested an invalid value for the first request tag during initialization of the Call State routines Action: Run the server trace facility, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5056 ERR_INVAL_CRASH_PTR Explanation: The pointer to Crash routine is NULL at initialization. Cause: The switch-dependent part of the server passed an invalid pointer to a Crash routine during initialization of the Call State routines Action: Run the server trace facility, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5057 ERR_INVAL_NUM_STATES Explanation: The number of states exceeds the maximum allowed at initialization. Cause: The switch-dependent part of the server passed an invalid number of call states during initialization of the Call State routines Action: Run the server trace facility, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5058 ERR_ASN1_DEC_FIELD_MISSING Explanation: A required field is missing. Cause: The decoder encountered a request that does not have all the required fields. Action: If the problem persists, collect the trace data at both the server, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5059 ERR_ASN1_DECODE_PARTIAL Explanation: Only part of the request could be decoded. Cause: The decoder encountered a request that has additional fields that could not be decoded. Action: Verify that the CallPath platform product is not at a higher level of the CallPath Services Architecture than the server. Module: CGEN Severity: WARNING 5060 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: WARNING 5061 ERR_PROGDATA_NOT_SAVED Explanation: The program data associated with a call was not saved. Cause: The switch-dependent part of the server was not able to save the program data associated with the call. Action: Collect the system message, trace, and dump data, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5062 ERR_PROGDATA_BFR_REQUEST Explanation: The Call State routines could not get a buffer for program data. Cause: The switch-dependent part of the server was not able to save the program data associated with the call. The rc was %s. Action: Collect the system message, trace, and dump data, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5063 ERR_PROGDATA_BFR_CREATE Explanation: The Call State routines create a buffer pool for program data. Cause: The switch-dependent part of the server was not able to create the program data pool. Program data for calls will not be saved. The rc was %s. Action: Collect the system message, trace, and dump data, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5064 ERR_PROGDATA_BFR_RELEASE Explanation: The Call State routines had a failure releasing a program data buffer. Cause: The switch-dependent part of the server was not able to release a program data buffer. The rc was %s. Action: Collect the system message, trace, and dump data, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5065 ERR_ASN1_ENCODE_ERROR Explanation: The encoder could not encode an event message. Cause: The switch-dependent part of the server passed an event message to the encoder that could not be encoded. The rc was %s and the message type was %s. Action: Collect the system message, trace, and dump data, then ask your IBM Service Representative to review the results. Module: CGEN Severity: WARNING 5400 ERR_CNT_CONT_TEST_NO_RESPONSE Explanation: No response to DV-APPL-CONTINUITY-TEST message. Cause: The switch did not respond to a periodic continuity test. Action: Verify that the switch and the X.25 link are operating properly and if the problem persists, collect the server trace data and review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5401 ERR_SMS_LOGON_UNSUCCESSFUL Explanation: The attempt to logon to the switch was unsuccessful. Cause: The switch did not respond to the logon attempt. Action: Review the X.25 message which accompanies this message to find further information. Module: SWITCH.EXE Severity: WARNING 5402 ERR_SMS_LINK_UNSUCCESSFUL Explanation: Unable to initialize X.25 link. Cause: The attempt to initialize the X.25 link was unsuccessful. Action: Collect the Communications Manager log and ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: WARNING 5403 ERR_ALT_BAD_ROUTE_TO Explanation: Found no call to transfer to, or overflow from, during Call_Alerting. Cause: The server received a Call Offered message from the switch with a call type of transfer or overflow. The server has disregarded a call type and created a new call with the two parties specified in the switch message. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. Module: SWITCH.EXE Severity: WARNING 5404 ERR_ALT_CALLID_ASSOCIATE Explanation: Unable to associate call IDs for Call_Alerting. Cause: The switch has sent a Call Offered message which is a continuation of activity in an existing call. The server had no record of the existing call. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. Module: SWITCH.EXE Severity: WARNING 5405 ERR_CNFRR_SWITCH_RT_NOT_INUSE Explanation: Unable to locate the request tag for a Conference_Call request. Cause: The switch has sent a positive Response to a Conference_Call request that contains a request tag. The server had no record of the request tag being active. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. Module: SWITCH.EXE Severity: WARNING 5406 ERR_DSC_MULTIPLE_EXTEND Explanation: An attempt to extend a call to a fourth party is not permitted. Cause: The switch attempted to extend a three-party call and the server does not permit this. Action: The Extend_Call was ignored by the server. Module: SWITCH.EXE Severity: WARNING 5408 ERR_DSC_BAD_SWITCHRT Explanation: Disconnect processing could not find the switch request tag. Cause: Switch sent a request tag in the release message which could not be found. Action: None required. Module: SWITCH.EXE Severity: WARNING 5409 ERR_ERS_BAD_EVENT_TYPE Explanation: An unsupported message was received from the switch. Cause: The switch sent a message which the server does not recognize. Action: If you know what the message was and it is supported, collect the server trace data and review the results with your IBM service representative. If it is not supported, review the results with your switch vendor. Module: SWITCH.EXE Severity: WARNING 5410 ERR_ERS_BADRTN_DECODER Explanation: A message sent from the switch could not be decoded. Cause: The switch sent a message which may or may not be supported. All supported messages are listed in this book. Action: If you know what the message was and it is supported, collect the server trace data and review the results with your IBM service representative. If it is not supported, review the results with your switch vendor. Module: SWITCH.EXE Severity: WARNING 5411 ERR_ERS_ZERO_LENGTH_FIELD Explanation: A required field within a message was missing. Cause: The switch sent a message that omitted a field which the server requires to be filled in. Action: Check the configuration on your switch to insure all required fields are being filled properly. If they are, collect the server trace data and review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5412 ERR_ERT_BAD_EVENT_TYPE Explanation: An unknown event message was received from the switch. Cause: The switch sent a message which the server does not recognize. Action: If you know what the message was and it is supported, collect the server trace data and review the results with your IBM service representative. If it is not supported, review the results with your switch vendor. Module: SWITCH.EXE Severity: WARNING 5413 ERR_ERT_BAD_REASON_TYPE Explanation: An unknown call type was received from the switch. Cause: The switch sent a message which specified a call type which the server did not recognize. Action: Attempt to determine if the call type is supported or not. If it is not, review these results with your switch vendor. If it is, collect the server trace data and review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5414 ERR_ERR_BAD_MSG_TYPE Explanation: An unknown negative Response message was sent by the switch. Cause: The switch sent a negative Response message to a previous request that the server does not recognize. Action: Collect the server trace data and review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5415 ERR_ERR_BAD_SWITCHRT Explanation: The DMS-100 switch sent an invalid request tag. Cause: The switch sent a message containing a switch request tag that the server does not recognize. Action: Attempt to determine if the tag is valid or not. If it is not, contact your switch vendor. If it is, contact your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5417 ERR_DSC_COPY_CALLID_NOT_INUSE Explanation: Unable to locate an extended call ID for Disconnected processing. Cause: The switch sent a Call Release message to disconnect the two original parties in a call which was extended to another party, but could not find the call ID of the party who was extended to. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. Module: SWITCH.EXE Severity: WARNING 5418 ERR_DSC_NO_AGENT Explanation: No agent was found in a call during Disconnected processing. Cause: The switch sent a Call Release message which specified an agent to be deleted from a call. The server could not find the agent in that call. The call and any extension to it was deleted from the server tables. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. Module: SWITCH.EXE Severity: WARNING 5420 ERR_DSC_NO_DN_2CL_CALL Explanation: The disconnecting party could not be found in either call. Cause: The switch sent a Call Release message which specified a party to disconnect from a call which had one party on hold and two others active. The server could not find that party in the call and deleted the call. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. Module: SWITCH.EXE Severity: WARNING 5421 ERR_DSC_NO_DN_IN_AB_CALL Explanation: Unable to locate the disconnecting party in the abandoned call. Cause: The switch sent a Call Release message which specified a party to disconnect from a call. The server could not find the party in the call and deleted the call. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. Module: SWITCH.EXE Severity: WARNING 5423 ERR_DSC_NO_DN_IN_XFERTO_CALL Explanation: Unable to locate all parties in an extended call during transfer. Cause: The switch sent a Call Release message with a call type transfer, attempting to connect the party on hold with the party extended to. The server could not find all the active parties in the extended call. The message was ignored. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. Module: SWITCH.EXE Severity: WARNING 5424 ERR_DSC_NULL_RELEASE Explanation: A DV_CALL_RELEASE was ignored since no calls exist. Cause: The switch sent a Call Release message with a call ID which the server did not recognize. Action: None required unless other errors are occurring. There are occasions when the switch will send a release for calls already released. Nothing has to be done for these situations. Module: SWITCH.EXE Severity: WARNING 5425 ERR_DSC_TWO_RELEASED Explanation: The caller cannot abandon if there are two calls in existence. Cause: The switch sent a Call Release message which said that the caller abandoned the call. The server has an original call and an extended call in existence and an abandon cannot occur in this situation. The server has disconnected both calls. Action: No action required. Module: SWITCH.EXE Severity: WARNING 5426 ERR_DSC_XFER_ONE_CALL Explanation: The switch sent a transfer message when only one call exists. Cause: The switch sent a Call Release message with call type transfer when the server only has a record of two parties in one call. The server has sent a transfer message to the host with a blank transfer to a party and then deleted the call. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. Module: SWITCH.EXE Severity: WARNING 5427 ERR_HLD_NO_CALLID_FOR_CALL Explanation: No call ID found for this call during Call_Held processing. Cause: While attempting to put a call on hold, the server could not find a call ID of the parties which were being put on hold. The server ignored the message. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. Module: SWITCH.EXE Severity: WARNING 5428 ERR_HLD_NO_AGENT Explanation: No agent found in call during Call_Held processing. Cause: While attempting to put two parties in a call on hold, the server could not find an agent in the call. Since an agent is the only party type that can put another party on hold, the server did not put the parties in the call on hold. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. Module: SWITCH.EXE Severity: WARNING 5430 ERR_RTE_NO_AGENT Explanation: No agent found in call during Call_Routed processing. Cause: The server expected to see an agent in an extended call and did not. Processing for the message being handled could not continue. Action: Collect the server trace data and review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5432 ERR_RTE_NOT_XFER Explanation: A non-transfer Call_Routed message was found after a Call_Held. Cause: The server expected to see a call type of transfer on the message it was processing since a Call_Held was just issued which only occurs while extending a call. Action: Collect the server trace data and review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5434 ERR_RTE_OFLW_CALLID_NOT_INUSE Explanation: The call ID for this Overflow was not found for a Call_Routed. Cause: The server could not find a call ID for the message it was processing. Processing could not continue for the message. Action: Collect the server trace data and review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5435 ERR_RTE_ONE_CALLID_NOT_INUSE Explanation: Unable to find out how many calls exist for Call_Routed. Cause: The server could not access internal control data for the call it was processing. Processing for that call could not continue. Action: Collect the server trace data and review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5438 ERR_RTE_XFER_NO_CALLID Explanation: The call ID for this Transfer was not found for Call_Routed. Cause: The server could not find a call ID for this message sent by the switch. Action: Verify that you are properly monitoring the ACD groups that contain the parties involved in this call. If you are, then collect the server trace data and review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5439 ERR_ALT_MULTIPLE_EXTEND Explanation: A Call_Alerting message to a fourth party in a call was attempted. Cause: An extension to a fourth party in a call was attempted via a manual telephone. The server does not support four parties. Action: No action required. Module: SWITCH.EXE Severity: WARNING 5440 ERR_CON_IGNORE_MSG Explanation: An answered message was received from the switch with an unknown party. Cause: The switch sent an answered message with a party not recognized by the server. Action: Check with your switch representative regarding messages sent for non-associated parties. If the problem persists, collect the trace data, then review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5441 ERR_RTE_MULTIPLE_EXTEND Explanation: A queued message to a fourth party in a call was attempted. Cause: The switch sent a queued message for a fourth party in a call. This is not permitted. The Call State Model was corrupted and less than four parties were involved with a call. Action: Collect the trace data, then review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5442 ERR_ALT_ROUTE_REASON Explanation: A call was offered to a party with an incorrect route reason. Cause: The switch has sent a route reason not recognized by the server. Action: Review the trace data for the route reason value contained in the message. Confirm with your switch vendor that the route reason is not valid. Module: SWITCH.EXE Severity: WARNING 5443 ERR_ALT_NEVER_HAPPEN Explanation: A call was offered to a party but the call type was invalid. Cause: The switch has sent a call type not recognized by the server. Action: Review the trace data for the call type value contained in the message. Check the call type validity with your switch vendor. Module: SWITCH.EXE Severity: WARNING 5444 ERR_DSC_NO_ABCL_PARTY Explanation: The party the switch disconnected was not found. Cause: The Call State routine of the server is corrupted or the switch sent a message for a party not associated with the server. Action: Confirm with your switch representative that the switch only sends messages about parties who have been associated. Module: SWITCH.EXE Severity: WARNING 5445 ERR_DSC_NO_CF_PARTY Explanation: The forwarded party was not found in the Call State Model. Cause: The Call State routine of the server is corrupted. The error occurred while processing a call forward call-progress event message. Action: Collect the system message, trace, and dump data, then review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5446 ERR_DSC_NO_CP_PARTY Explanation: The picked party was not found in the Call State Model. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Picked call-progress event message. Action: Collect the system message, trace, and dump data, then review the results with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5447 ERR_RTE_ROUTE_REASON Explanation: A call was queued but there was an incorrect route reason. Cause: The switch has sent a route reason not recognized by the server. Action: Review the trace data for the route reason value contained in the message. Check with your switch vendor as to the route reason validity. Collect trace data and review with your IBM service representative. Module: SWITCH.EXE Severity: WARNING 5450 ERR_XFRRR_NO_CALL_ID_FOUND Explanation: The Call State Model did not find the call ID for extended call. Cause: The Call State Model has been corrupted or events are handled out of sequence. Action: None required. Module: SWITCH.EXE Severity: WARNING 5451 ERR_NO_PRIOR_CALL_ID_FOUND Explanation: Could not find the Call ID for the Held Call while processing transfer. Cause: The Call State Model has been corrupted or events are handled out of sequence. Action: None required. Module: SWITCH.EXE Severity: WARNING 5452 ERR_NO_PARTIES_FOUND Explanation: The Call State Model did not find any parties associated with the call. Cause: The Call State Model has been corrupted or events are handled out of sequence. Action: None required. Module: SWITCH.EXE Severity: WARNING 5453 ERR_CONTROLLING_PARTY_NOT_FOUND Explanation: The Call State Model could not find a controlling party to transfer. Cause: The Call State Model has been corrupted or events are handled out of sequence. Action: None required. Module: SWITCH.EXE Severity: WARNING Program Messages (Critical) 6000 ERR_CRITICAL_PGM Explanation: Critical program error type Module: SWITCH.EXE Severity: SEVERE 6001 ERR_CSM_NOT_STARTED Explanation: An error occurred while trying to start the Call State routines. Cause: The switch-dependent part of the server was not able to start the routines for the Call State. Action: Collect the system message, trace, and dump data, 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_REQUEST_COMMBFR Explanation: An error occurred when requesting a %s control block. Cause: The switch-dependent part of the server had an error requesting a control block. The request type was %s. The rc was %s. 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_FREE_COMMBFR Explanation: An error occurred when freeing a %s control block. Cause: The switch-dependent part of the server has an error freeing a control block. The request type was %s. The rc was %s. 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 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 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 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_CID_XCHK_ERROR Explanation: The CID field in Call State data block was corrupted. Cause: The switch-dependent part of CallPath SwitchServer/2 modified the CID field in one of the Call State data blocks. The Call State Data base 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 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_CREATE_COMMBFR Explanation: An error occurred while creating or attaching to communication buffers. Cause: The Call State routines attempted to %s the communication buffers and had an error. The rc was %s. 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 6029 ERR_BAD_PARM_PASSED Explanation: A bad parameter was passed to a function. Cause: A Call State routine was passed a bad parameter. 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 6030 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: SEVERE 6040 ERR_SEND_CSM_CMD Explanation: An error occurred while trying to send a command to the Cause: The error ID was %s. The rc was %s. The Group was %s and the function was %s. 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 6041 ERR_ATTACH_CSM Explanation: An error occurred while trying to attach to the Call State routines. Cause: The error ID was %s. The rc was %s. 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 6042 ERR_CREATE_CSM Explanation: An error occurred while trying to create to the Call State routines. Cause: The error ID was %s. The rc was %s. 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 6043 ERR_PARMS_LOCK Explanation: An error occurred while locking the Call State routine's parameters. Cause: The error ID was %s. The rc was %s. 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 6044 ERR_CSM_INIT Explanation: An error occurred while creating the Call State semaphore. Cause: The rc was %s. 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 6045 ERR_CSM_LOCK Explanation: An error occurred while trying to lock the Call State routines. Cause: The rc was %s. 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 6046 ERR_CSM_INIT_MSB Explanation: An error occurred while trying to initialize the Call State Routines. Cause: 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 6047 ERR_CSM_INIT_HCE Explanation: An error occurred while trying to initialize the Call State Routines. Cause: 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_PI_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_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_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 6073 ERR_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 6084 ERR_ALLOC_BUCKETS Explanation: An error occurred in the Call State routines allocating memory. Cause: The switch-dependent part of the server was unable to allocate memory required to cleanup old data. Action: Collect the system message, trace, and dump data, then ask your IBM Service Representative to review the results. Module: CGEN Severity: SEVERE 6097 ERR_ASN1_ENCODE_INV_CHOICE Explanation: The encoder detected an invalid choice. Cause: While encoding an event message, the encoder detected a choice field that 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 6098 ERR_ASN1_ENCODE_MISSING_FLD Explanation: The encoder detected a required field was missing. Cause: While encoding an event message, the encoder detected a missing required field. Action: Collect the system message, trace, and dump data, then ask your IBM Service Representative to review the results. Module: CGEN Severity: SEVERE 6101 ERR_MEM_INIT_TK Explanation: Toolkit failed to initialize Cause: The system is out of memory or the operating system has failed. Action: Restart the computer. If failure reoccurs, reinstall the CallPath product. If failure persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6102 ERR_X25_INACTIVE Explanation: X.25 feature is inactive. Cause: Communications Manager X.25 support is not initialized. Action: Restart the OS/2 system, and ensure that the Communications Manager X.25 feature is started properly. Module: SWITCH.EXE Severity: SEVERE 6105 ERR_X25_TERMINATING Explanation: X.25 feature is terminating. Cause: The X.25 feature is in the process of terminating. Action: Stop and restart OS/2 Communications Manager. Module: SWITCH.EXE Severity: SEVERE 6111 ERR_X25_DEVICE_DRIVER_ERROR Explanation: X.25 device driver error. Cause: The X.25 feature terminated when an error was returned by the X.25 device driver. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6113 ERR_X25_ADAPTER_ACCESS_ERROR Explanation: X.25 adapter access error. Cause: The X.25 Interface Co-Processor/2 adapter for this link is not installed or cannot be accessed. Action: Ensure that the Interface Co-Processor/2 adapter is installed and that the adapter, link, and directory feature profiles are defined correctly. Module: SWITCH.EXE Severity: SEVERE 6114 ERR_X25_ADAPTER_ERROR Explanation: X.25 adapter error. Cause: An error occurred on the adapter. Error data is stored in the Communications Manager log. Action: To use the adapter, you must stop and restart OS/2 Communications Manager. Module: SWITCH.EXE Severity: SEVERE 6115 ERR_X25_INVALID_LINK_NAME Explanation: Invalid X.25 link profile name. Cause: The X.25 link profile name has the wrong format or is not configured. Action: The problem may be with the adapter, link, or directory feature profiles. Provide a valid link name. Module: SWITCH.EXE Severity: SEVERE 6116 ERR_X25_NO_LINK_NAME Explanation: No X.25 link name. Cause: The directory entry does not contain a link name. Action: Refer to the reference manual for information on the local and remote directory profiles and provide a valid link name. Module: SWITCH.EXE Severity: SEVERE 6125 ERR_X25_APP_LIMIT_EXCEEDED Explanation: X.25 maximum applications limit exceeded. Cause: Too many X.25 application programs were started. 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_X25_APP_INACTIVE Explanation: X.25 application program has not initialized its use of the API. Cause: The X.25 application program has not initialized its use of the API. 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_X25_APP_TERMINATING Explanation: Application program requested X.25 application termination. Cause: The server has terminated the X.25 link to the switch. 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_X25_APP_Q_ERROR_TERMINATE Explanation: X.25 queue no longer exists. Cause: An X.25 queue used by the server no longer exists. 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_X25_NO_Q_SPACE_TERMINATE Explanation: No X.25 queue available. Cause: The X.25 feature does not have enough resources to process a request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6133 ERR_X25_NO_SEMAPHORES_CLEARED Explanation: No X.25 semaphore cleared. Cause: X.25 did not clear its semaphore due to an invalid request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6134 ERR_X25_APP_REQ_CLEAR_SEM Explanation: X.25 request completed because the application program requested X25SemClear. Cause: An invalid X25SemClear request was generated by the server. 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_X25_DIS_APP_REQ_CLEAR_SEM Explanation: X.25 data was not sent because the application program requested X25SemClear. Cause: An invalid X25SemClear request was generated by the server. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6136 ERR_X25_INVALID_RTE_NAMES Explanation: X.25 routing table entry is not valid. Cause: The X.25 routing table name specified during system configuration is invalid. Action: Collect the system message, trace and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6139 ERR_X25_INVALID_PVC_NAME Explanation: The X.25 application program is using an invalid PVC name. Cause: The PVC name specified by the application program is invalid (has the wrong format or is not configured). Action: Contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6140 ERR_X25_PVC_IN_USE Explanation: The X.25 application program named PVC is already in use. Cause: The PVC that the application program has specified is already allocated to a program. Action: Contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6141 ERR_X25_BUFFER_TOO_SHORT Explanation: X.25 buffer too short. Cause: The data buffer is too short for all data returned by the X.25 feature. The data is truncated. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6142 ERR_X25_INVALID_BUFFER_POINTER Explanation: X.25 invalid buffer pointer. Cause: The X.25 feature cannot access a data buffer. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6143 ERR_X25_INVALID_Q_NAME Explanation: X.25 unable to access queue. Cause: The X.25 feature cannot access one of the queue names specified by the server. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6144 ERR_X25_INVALID_SEMAPHORE_NAME Explanation: X.25 unable to access semaphore specified by application program. Cause: The X.25 feature cannot access one of the semaphore names specified by the server. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6145 ERR_X25_INVALID_NAME_REQ Explanation: Application program has specified an invalid X.25 directory name. Cause: The X.25 feature cannot access a directory name specified by the server. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6146 ERR_X25_NO_DIRECTORY_MATCH Explanation: X.25 no directory match. Cause: No directory entries match the fields supplied by the X.25 application program. Action: The problem may be with the adapter, link, or directory feature profiles. Refer to the reference manual for information on the X.25 feature profiles and provide a valid directory entry. Module: SWITCH.EXE Severity: SEVERE 6147 ERR_X25_INVALID_CONNECTION_ID Explanation: Invalid X.25 link connection ID. Cause: The specified X.25 link connection ID has not been assigned. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6148 ERR_X25_CALL_ALREADY_ACCEPTED Explanation: X.25 SVC call has already been accepted. Cause: An X.25 SVC call is already established between the server and the switch. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6149 ERR_X25_CALL_NOT_YET_ACCEPTED Explanation: X.25 cannot proceed until call has been accepted. Cause: The X.25 SVC call between the server and the switch has not been established. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6150 ERR_X25_PVC_FREED Explanation: The X.25 application program named PVC link was freed. Cause: The PVC has been freed; no more data can be sent or received using the connection ID that the application program has specified. Action: Contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6155 ERR_X25_CALLED_ADDR_LEN_ERR Explanation: X.25 called address length invalid. Cause: The server is using an X.25 called address length greater than 15 bytes. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6156 ERR_X25_CALLING_ADDR_LEN_ERR Explanation: X.25 calling address length invalid. Cause: The server is using an X.25 calling address length greater than 15 bytes. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6157 ERR_X25_CALLED_ADDR_NAME_ERR Explanation: X.25 called address name error. Cause: The server is using an invalid X.25 called address name. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6158 ERR_X25_CALLING_ADDR_NAME_ERR Explanation: X.25 calling address name error. Cause: The server is using an invalid X.25 calling address name. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6160 ERR_X25_FACILITIES_LEN_ERROR Explanation: X.25 facilities field is invalid. Cause: The server is using an invalid X.25 facilities value. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6161 ERR_X25_FACILITIES_ERROR Explanation: X.25 detected a format error while scanning the facilities field. Cause: The server is using an invalid X.25 facilities value. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6162 ERR_X25_USER_DATA_LEN_ERROR Explanation: X.25 user data field invalid. Cause: The server is using an invalid X.25 user data field length. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6163 ERR_X25_INVALID_CAUSE_CODE Explanation: X.25 clearing cause is invalid. Cause: The server is using an invalid X.25 clearing cause code. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6165 ERR_X25_NO_DATA_TO_ACK Explanation: An X.25 confirmation is outstanding. Cause: There is no outstanding request to acknowledge on the X.25 link to the switch. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6166 ERR_X25_ADAPTER_ACK_SELECTED Explanation: X.25 performing automatic confirmation for SVC. Cause: An invalid X.25 X25Ack request was attempted. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6167 ERR_X25_INTERRUPT_IN_PROGRESS Explanation: X.25 already processing X25Interrupt. Cause: An invalid X.25 X25Interrupt request was attempted. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6168 ERR_X25_BUFF_SHORTER_THAN_PKT Explanation: X.25 data buffer is shorter than maximum packet size. Cause: The server is using a data buffer smaller than the incoming X.25 packet size. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6170 ERR_X25_Q_BIT_INDICATOR_ERROR Explanation: X.25 verb contains an invalid Q-bit. Cause: The setting of the Q-bit in the X.25 Verb Request Block (XVRB) is invalid. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6171 ERR_X25_NO_RESET_TO_CONFIRM Explanation: X.25 SVC is not waiting for X25Reset confirm. Cause: An invalid X.25 X25ResetConfirm request was attempted. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6175 ERR_X25_QUEUE_LIMIT_EXCEEDED Explanation: X.25 application program has specified too many queues. Cause: The server is using too many X.25 queues. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6176 ERR_X25_ENTRY_LIMIT_EXCEEDED Explanation: X.25 maximum verb entries exceeded. Cause: The maximum number of entries for an X.25 verb has been exceeded. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6177 ERR_X25_INTERPT_DATA_LEN_ERR Explanation: X.25 interrupt user data length invalid. Cause: The length of the X.25 interrupt user data field is invalid. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6178 ERR_X25_D_BIT_INDICATOR_ERROR Explanation: X.25 verb contains an invalid D-bit. Cause: The setting of the D-bit in the X.25 verb request block (XVRB) is invalid. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6179 ERR_X25_LINK_CONN_INCOMING Explanation: X.25 cannot process outgoing calls. Cause: Outgoing calls cannot be made on the X.25 link to the switch. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6180 ERR_X25_UNKNOWN Explanation: X.25 unknown error. Module: SWITCH.EXE Severity: SEVERE 6181 ERR_X25_UNADDRESSABLE_CNTRL_BLK Explanation: The segment identified by the pointer to the XVRB cannot be addressed. Cause: The segment identified by the pointer to the X.25 Verb Request Block (XVRB) cannot be addressed by the X.25 feature. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6182 ERR_X25_CONTROL_BLOCK_TOO_SHORT Explanation: The XVRB that the application has provided is too short. Cause: The X.25 Verb Request Block (XVRB) that the application has provided is too short. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6183 ERR_X25_INVALID_VERSION_ID Explanation: The version identifier field in the XVRB is not set to x'00'. Cause: The version identifier field in the X.25 Verb Request Block (XVRB) is not set to x.00. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6184 ERR_X25_INVALID_VERB_ID Explanation: The verb identifier in the XVRB is not a valid X.25 verb identifier. Cause: The verb identifier in the X.25 Verb Request Block (XVRB) is not a valid X.25 verb identifier. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6185 ERR_X25_INVALID_Q_NUMBER Explanation: X.25 invalid queue name. Cause: The server specified an invalid X.25 queue name. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6187 ERR_X25_STACK_TOO_SMALL Explanation: The stack space provided by the X.25 application is too small. Cause: The stack space provided by the X.25 application is too small. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6188 ERR_X25_UNEXPECTED_OS2_ERROR Explanation: The X.25 feature received an unexpected OS/2 error. Cause: The X.25 feature received an unexpected OS/2 error. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6189 ERR_X25_ABEND Explanation: The X.25 feature has ended abnormally. Cause: The X.25 feature has ended abnormally. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6190 ERR_XIN_ALLOC_RCV Explanation: Unable to allocate memory for X.25 receive buffers. Cause: No memory is available for X.25 receive buffers. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6191 ERR_XIN_ALLOC_XMT Explanation: Unable to allocate memory for X.25 transmit buffers. Cause: No memory is available for X.25 transmit buffers. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6192 ERR_XIN_INIT_RCV Explanation: Unable to initialize memory for X.25 receive buffers. Cause: Memory cannot be initialized for X.25 receive buffers. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6193 ERR_XIN_INIT_XMT Explanation: Unable to initialize memory for X.25 transmit buffers. Cause: Memory cannot be initialized for X.25 transmit buffers. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6194 ERR_XIN_SUBALLOC_RCV Explanation: Unable to suballocate memory for X.25 receive buffers. Cause: Memory cannot be suballocated for X.25 receive buffers. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6195 ERR_XIN_SUBALLOC_XMT Explanation: Unable to suballocate memory for X.25 transmit buffers. Cause: Memory cannot be suballocated for X.25 transmit buffers. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6196 ERR_X25_INVALID_STATE Explanation: Invalid processing state detected by OS/2 Communications Manager. Cause: During processing, an invalid state was detected by the OS/2 Communications Manager. Action: Stop and restart OS/2 Communications Manager. Module: SWITCH.EXE Severity: SEVERE 6197 ERR_X25_COMMS_SERVICES_ERROR Explanation: Unable to access common communication service subroutines. Cause: While accessing common communication service subroutines, an unexpected error was encountered. Action: Stop and restart OS/2 Communications Manager. Module: SWITCH.EXE Severity: SEVERE 6198 ERR_XIN_XMT_INIT_IMMED Explanation: X25AppInit API interface failure. Cause: The server cannot initialize the application's use of the API. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6199 ERR_XIN_XMT_INIT_FAIL Explanation: X25AppInit I/O completion error. Cause: The server is unable to complete I/O to the API. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6200 ERR_CXS_INIT_FAILURE Explanation: X25 unknown error. Cause: The X.25 feature returned an unknown error code. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6201 ERR_CNFRR_NO_CALLID Explanation: Call ID associated with Conference_Call request is invalid. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Conference_Call request. Action: Collect the system message, trace, and dump data, then review the results with your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6202 ERR_MONRR_DEL_CALL_ID_NOT_INUSE Explanation: Unable to find a temporary call created for a Monitor request. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Monitor request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6203 ERR_CNF_CALL_ID_NOT_INUSE Explanation: Unable to locate the call ID for a Conference_Call request. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Conference_Call request. Action: Collect the system message, trace, and dump data, then review the results with your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6204 ERR_MON_CALL_ID_NOT_INUSE Explanation: Unable to locate a call ID while processing a Monitor request. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Monitor request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6205 ERR_MON_CREATECALL_UNAVAIL Explanation: Unable to create control blocks for a new call for a Monitor request. Cause: The switch-dependent part of the server internal control blocks could not be allocated while processing a Monitor request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6206 ERR_RDRRE_CALL_ID_NOT_INUSE Explanation: Unable to locate data for an internal call ID in a Redirect_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a negative Response to a Redirect_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6207 ERR_RDRRE_NO_CALLID_FOR_CALL Explanation: Unable to locate a call ID to remove party for a Redirect_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a negative Response to a Redirect_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6208 ERR_RDRRE_NUM_PARTY_IN_CALL Explanation: Incorrect number of parties found for a Redirect_Call request. Cause: The Call State routine of the server is corrupted. The error occurred while processing a negative Response to a Redirect_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6209 ERR_RDRRR_CALL_ID_NOT_INUSE Explanation: Unable to locate data for an internal call ID for a Redirect_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Redirect_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6210 ERR_RDRRR_NO_CALLID_FOR_CALL Explanation: Unable to locate a call ID to remove party for a Redirect_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Redirect_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6211 ERR_RDRRR_NUM_PARTY_IN_CALL Explanation: Incorrect number of parties found for a Redirect_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Redirect_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6212 ERR_CNFRR_ORIG_CALLID_NOT_INUSE Explanation: Unable to locate first call ID for a Conference_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Conference_Call request. The call ID of the first call cannot be located. Action: Collect the system message, trace, and dump data, then review the results with your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6213 ERR_RDR_ADDPARTY_C_UNAVAIL Explanation: Unable to add a party while processing a Redirect_Call request. Cause: The switch-dependent part of the server internal control blocks could not be allocated while processing a Redirect_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6214 ERR_RDR_CALL_ID_NOT_INUSE Explanation: Unable to locate a call ID for a Redirect_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Redirect_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6215 ERR_RDR_CREATEPARTY_C_UNAVAIL Explanation: Unable to create control blocks to produce a call for a Redirect_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Redirect_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6216 ERR_RQR_REQ_NO_SUPPRT_BY_SWITCH Explanation: The host sent a request not supported by the DMS-100 CO switch. Cause: The switch-dependent part of the server received an unknown request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6217 ERR_RTVRR_CALL_ID_NOT_INUSE Explanation: Unable to delete a call for a Retrieve_Call request. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Retrieve_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6218 ERR_RTVRR_CALL_LIST_OVERFLOW Explanation: Found a party in too many calls for a Retrieve_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Retrieve_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6219 ERR_RTVRR_NO_CALLID_FOR_DN Explanation: Unable to locate a call ID for a redirected party for a Retrieve_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Retrieve_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6220 ERR_RTVRR_NO_CALLID_FOR_EX_CALL Explanation: Unable to locate an extended call ID for a Retrieve_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Retrieve_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6221 ERR_RTVRR_NO_CALLID_FOR_OR_CALL Explanation: Unable to locate an original call ID for a Retrieve_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Retrieve_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6222 ERR_RTVRR_NUM_PARTY_IN_EX_CALL Explanation: Incorrect number of parties found in an extended call for a Retrieve_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Retrieve_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6223 ERR_RTVRR_NUM_PARTY_IN_RT_CALL Explanation: Incorrect number of parties found in an original call for a Retrieve_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Retrieve_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6224 ERR_RTVRR_RT_INVALID Explanation: Switch sent an invalid request_tag for a Retrieve_Call. Cause: The switch-dependent part of the server received a positive Response from the switch with an invalid invoke tag. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6225 ERR_RTV_CALL_ID_NOT_INUSE Explanation: Unable to save data in an internal call ID for a Retrieve_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Retrieve_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6226 ERR_RTV_CALL_LIST_OVERFLOW Explanation: Party found in incorrect number of calls for a Retrieve_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Retrieve_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6227 ERR_RTV_NO_CALLID_FOR_DN Explanation: Unable to locate a call ID for party for a Retrieve_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Retrieve_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6228 ERR_XFRRR_NO_CALLID_FOR_CALL Explanation: Unable to locate an original call ID for a Transfer_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Transfer_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6229 ERR_XFRRR_NUM_PARTY_IN_CALL Explanation: Incorrect number of parties found in original call for a Transfer_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Transfer_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6230 ERR_XFRRR_RT_INVALID Explanation: Switch sent invalid request_tag for a Transfer_Call. Cause: A positive Response was received from the switch with an invalid invoke tag. The error occurred while processing a positive Response to a Transfer_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6231 ERR_XFR_CALL_ID_NOT_INUSE Explanation: Unable to save data in an internal call ID for Transfer_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Transfer_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6232 ERR_ALT_CALL_ID_NOT_INUSE Explanation: Unable to locate data related to an internal call ID for Call_Alerting. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6233 ERR_ALT_XFER_CI_RSRC_UNAVAIL Explanation: Unable to save transfer call information for Call_Alerting. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6234 ERR_ALT_CG_AGENT_RSRC_OVERLOAD Explanation: Unable to hold a calling agent's information for a transfer Call_Alerting. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6235 ERR_ALT_CG_AG_CALL_ID_NOT_INUSE Explanation: Unable to locate a calling agent's call ID for a transfer Call_Alerting. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6236 ERR_ALT_CD_AGENT_RSRC_OVERLOAD Explanation: Unable to save a called agent's information for a transfer Call_Alerting. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6237 ERR_ALT_CD_AG_CALL_ID_NOT_INUSE Explanation: Unable to locate the called agent's call ID for a transfer Call_Alerting. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6238 ERR_ALT_CI_RSRC_UNAVAIL Explanation: Unable to save the new call information for Call_Alerting. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6239 ERR_ALT_CG_PARTY_RSRC_OVERLOAD Explanation: Unable to save the calling agent's information for Call_Alerting. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6240 ERR_CNFRR_2ND_CALLID_NOT_FOUND Explanation: Unable to locate the second call ID for a Conference_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Conference_Call request. The call ID of the second call cannot be located. Action: Collect the system message, trace, and dump data, then review the results with your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6241 ERR_ALT_NO_PILOT_EXT_CALL Explanation: Unable to locate a PILOT party after Call_Held processing. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6242 ERR_EMG_ERR_BAD_ENCODE Explanation: Unable to encode a return error message for the DMS-100 CO switch. Cause: The switch-dependent part of the server could not encode a DV-RETURN-ERROR to send to the DMS-100 CO switch. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6243 ERR_EMG_RSLT_BAD_ENCODE Explanation: Unable to encode a return result message for the DMS-100 CO switch. Cause: The switch-dependent part of the server could not encode a DV-RETURN-RESULT to send to the DMS-100 CO switch. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6244 ERR_ALT_NO_PILOT_ORIG_CALL Explanation: Unable to locate a PILOT party in an original call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6245 ERR_RTE_NO_PILOT_PARTY Explanation: Unable to locate a PILOT party in an extended call after Call_Held. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6246 ERR_CNFRR_DN_MISMATCHED Explanation: Directory numbers were mismatched for a Conference_Call. Cause: The Call State routine of the server is corrupted. While processing a positive Response to the Conference_Call request, the directory numbers of the held call and the active call did not match up. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6247 ERR_HLD_CI_RSRC_UNAVAIL Explanation: Unable to create an extended call for Call_Held message. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Held message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6248 ERR_RQI_CI_RSRC_UNAVAIL Explanation: Unable to save information for a new call for Request_Instruction. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6249 ERR_RTE_CALLID_ASSOCIATE Explanation: Unable to associate a switch call ID with an internal call ID. Cause: The switch-dependent part of the server could not find a switch NetworkCallID in its Call State routine. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6250 ERR_DSCREQ_CALLID_NOT_INUSE Explanation: The call ID associated with a Disconnect request was not in use. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnect request. The call ID associated with the Disconnect request is not active. Action: Collect the system message, trace, and dump data, then review the results with your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6251 ERR_RTE_NO_CALLID_FOR_CALL Explanation: Unable to locate an extended call ID for a Call_Routed message. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6252 ERR_CNF_ORIG_CALL_ID_NOT_INUSE Explanation: The original call ID is not in use for a Conference_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Conference_Call request. The original call ID associated with the Conference Call request is not active. Action: Collect the system message, trace, and dump data, then review the results with your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6255 ERR_RTE_CI_RSRC_UNAVAIL Explanation: Unable to save information for a new call for a Call_Routed message. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6256 ERR_RTE_CG_PARTY_RSRC_UNAVAIL Explanation: Unable to create control blocks for a calling party in a new call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6257 ERR_RTE_RT_PARTY_RSRC_UNAVAIL Explanation: Unable to create control blocks for a called party in a new call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6258 ERR_RTE_CG_CALL_ID_NOT_INUSE Explanation: Unable to add a calling party to a new call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6259 ERR_RTE_RT_CALL_ID_NOT_INUSE Explanation: Unable to add a called party to a new call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6260 ERR_ALT_CG_CALL_ID_NOT_INUSE Explanation: Unable to add a calling party to a new call for Call_Alerting. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6261 ERR_ALT_CD_PARTY_RSRC_OVERLOAD Explanation: Unable to create control blocks for a called agent in a new call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6262 ERR_ALT_NO_CALLID_FOR_ORIG_CALL Explanation: Unable to find an original call ID for a transfer Call_Alerting. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6263 ERR_NO_REQ_TAGS_REMAIN Explanation: All request tags are in use. Request_Instruction messages are ignored. Cause: The server does not have any free switch invoke tags left. This occurs when there are more than 1024 Request_Instruction messages pending. Action: Verify that your application answers all Request_Instruction messages with either a Redirect_Call or a Return_Control program call. Module: SWITCH.EXE Severity: SEVERE 6264 ERR_ALT_NO_ORIG_PARTY Explanation: Neither an agent nor PILOT party was found for Call_Alerting. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6265 ERR_ALT_NO_CALLID_FOR_EXT_CALL Explanation: Unable to locate an extended call after the Call_Held message. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6266 ERR_ALT_TOO_MANY_CALLS Explanation: More than two calls were found for Call_Alerting. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6267 ERR_ALT_ACD_CALL_ID_NOT_INUSE Explanation: Unable to locate a PILOT party and remove it from a call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6268 ERR_ALT_CR_CD_AG_RSRC_OVERLOAD Explanation: Unable to create control blocks for a called agent. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6269 ERR_ALT_CR_AG_CALLID_NOT_INUSE Explanation: Unable to add a called agent to a call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6270 ERR_RQI_CG_PARTY_RSRC_OVERLOAD Explanation: No resource for the calling party for a Request_Instruction message. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6271 ERR_RQI_RT_PARTY_RSRC_OVERLOAD Explanation: No resource for a called party in a Request_Instruction message. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6272 ERR_RQI_CALLID_ASSOCIATE Explanation: Unable to associate the call IDs for a Request_Instruction message. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6273 ERR_HLD_PARTY1_RSRC_OVERLOAD Explanation: No resource for a PILOT party in an extended call for Call_Held. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6274 ERR_HLD_PARTY2_RSRC_OVERLOAD Explanation: No resource for a called party in an extended call for Call_Held. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Held message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6275 ERR_ALT_CD_CALL_IO_NOT_INUSE Explanation: Unable to add a called agent to a new call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6276 ERR_QPS_INVALID_STATE Explanation: Found directory number with invalid Call State for Query_Party_Status. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Query_Party_Status request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6277 ERR_ALT_NO_CH_CALLID Explanation: Unable to locate the call ID of a Held_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Held message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6278 ERR_ALT_NO_OVFL_PARTY Explanation: Unable to locate an agent or PILOT party for an overflow Call_Alerting. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6279 ERR_DSCREQ_NO_CALLID Explanation: Unable to locate a call ID while processing a Disconnect request. Module: SWITCH.EXE Severity: SEVERE 6280 ERR_ALT_NO_TRACK_CALLID Explanation: No call ID containing the list of tracked parties for a new call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6281 ERR_ALT_NO_TRACK_ONECALL Explanation: No call ID with a list of tracked parties for an original call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6282 ERR_ALT_NO_TRACK_TWOALT Explanation: No call ID with a list of tracked parties for an extended call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6283 ERR_ALT_NO_TRACK_TWORTE Explanation: No call tracking array for a Call_Alerting message. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6284 ERR_DSC_BAD_REASON Explanation: Unknown route reason code while processing a Disconnected message. Cause: An unknown DV-CALL-RELEASE reason code was received from the DMS-100 CO switch. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6285 ERR_DSC_CALLID_ASSOCIATE_2CL Explanation: Unable to associate an extended call to a switch call ID. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6286 ERR_DSC_MON_A1_CALLID Explanation: No call ID with a tracked call party for an abandoned call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6287 ERR_DSC_MON_C1_CALLID Explanation: No call ID with a tracked call party for a single cleared call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6288 ERR_DSC_MON_C21_CALLID Explanation: No call ID with a tracked call party for an extended cleared call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6289 ERR_DSC_MON_C22_CALLID Explanation: No call ID with a tracked call party for an original cleared call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6290 ERR_DSC_MON_OVFL_CALLID Explanation: No call ID with a tracked call party for an overflow call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6291 ERR_DSC_MON_XFR_CALLID Explanation: No call ID with a tracked call party for a transfer. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6292 ERR_DSC_NO_CALLID_FOR_1CL_CALL Explanation: No call ID of an original call to remove parties from hold. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6293 ERR_DSC_NO_CALLID_FOR_2CL_CALL Explanation: No extended call ID for a disconnecting party for a cleared call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6294 ERR_DSC_NO_CALLID_FOR_AB_CALL Explanation: No original call ID for the disconnecting party for an abandoned call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6295 ERR_DSC_NO_CALLID_FOR_CALL Explanation: Unable to locate a call ID for a cleared call for Disconnected. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6296 ERR_DSC_NO_DN_1CL_CALL Explanation: Unable to locate parties in an original call being cleared. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6297 ERR_DSC_NO_XFERTO_CALLID Explanation: Unable to locate an extended call ID to transfer to. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6298 ERR_ERR_CALL_ID_NOT_INUSE Explanation: Unable to determine which error type the DMS-100 CO switch sent. Cause: The Call State routine of the server is corrupted. The error occurred while processing a switch DV-RETURN-ERROR message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6299 ERR_HLD_MON_CALLID Explanation: Unable to locate a call ID containing tracked party for Call_Held while processing a Call_Held message. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Held message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6300 ERR_MKCRR_MON_CALLID Explanation: No call ID containing tracked call party for Make_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6301 ERR_MONRE_CIB_CALL_ID_NOT_INUSE Explanation: Unable to get data for an internal call ID for Monitor. Cause: The Call State routine of the server is corrupted. The error occurred while processing a negative Response to a Monitor request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6302 ERR_RQI_MON_CALLID Explanation: No call ID containing a tracked call party for Request_Instruction. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6303 ERR_RTE_MON_CALLID Explanation: No call ID with tracked party data for a new call ID for Call_Routed. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6304 ERR_RTE_MON_ONE_CALLID Explanation: No call ID with tracked party data for an original call ID. Unable to locate an ID while processing a Call_Routed message. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6305 ERR_RTE_MON_HELD_CALLID Explanation: No call ID with tracked party data after Call_Held. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6306 ERR_RTE_MON_OVFL_CALLID Explanation: No call ID with tracked party data for an overflow Call_Routed. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6307 ERR_RTE_MON_XFER_CALLID Explanation: No call ID for Call_Routed if monitored. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6308 ERR_ALT_NO_CALLID_FOR_OVFL_CALL Explanation: No original call ID for an overflow Call_Alerting message. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6309 ERR_ALT_NO_PILOT_OVFL_CALL Explanation: No PILOT party in an original call for an overflow Call_Alerting. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6312 ERR_ALT_XFER_CALL_ID_NOT_INUSE Explanation: No data from an internal call ID for Call_Alerting. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6313 ERR_DSC_AP_CALLID_NOT_INUSE Explanation: No original call ID to move transfer to party into for Disconnected. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6314 ERR_DSC_CALLID_NOT_INUSE Explanation: No data for an internal original call ID for Disconnected. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6315 ERR_DSC_NO_AGENT_CALL Explanation: No original call ID to transfer party connected to a transferring agent. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6316 ERR_DSC_NO_OVFL_CALLID Explanation: No original call ID for an overflow Disconnected message. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6317 ERR_DSC_NO_OVFL_CGACD Explanation: No parties in original call for an overflow Disconnected message. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6318 ERR_DSC_NO_RF_CALL Explanation: No original call ID to remove a party for an overflow Disconnected. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6319 ERR_DSC_RP_CALLID_NOT_INUSE Explanation: No extended call ID to remove a party for transfer Disconnected. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6320 ERR_HLD_CALLID_NOT_INUSE Explanation: No data to determine if Call_Held is necessary. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Held message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6321 ERR_HLD_CALL_ID2_NOT_INUSE Explanation: No data from an internal extended call ID for Call_Held. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Held message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6322 ERR_HLD_CALL_ID_NOT_INUSE Explanation: No data from an internal original call ID for Call_Held. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Held message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6323 ERR_HLD_NO_AGACD Explanation: Unable to locate all parties in an original call ID for Call_Held. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Held message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6324 ERR_HLD_NO_CALLID_AGACD Explanation: Unable to locate original call ID for Call_Held. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Held message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6325 ERR_RTVRR_NO_2ND_CALLID Explanation: Unable to get data from an extended call ID for Retrieve_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Retrieve_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6326 ERR_RQI_CALL_ID_NOT_INUSE Explanation: Unable to put data into an internal call ID for Request_Instruction. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6327 ERR_RTE_NO_EXT_PILOT_PARTY Explanation: Unable to locate a PILOT party in an extended call for Call_Routed. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6328 ERR_RTE_NO_REM_AGENT_CALL Explanation: No agent to remove from an original call for Call_Routed. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6329 ERR_RTE_NO_RT_OVFL_AGENT Explanation: Unable to create control blocks for a second PILOT party. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6330 ERR_RTE_NO_RT_OVFL_PARTY Explanation: Unable to create control blocks for a PILOT party. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6331 ERR_RTE_NO_XFER_CALLID Explanation: Unable to locate a call ID for an original call for Call_Routed. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6332 ERR_RTE_NO_XFER_CALL_RSRC Explanation: Unable to create control blocks for an extended call for Call_Routed. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6333 ERR_RQI_ACD_NO_CALLID Explanation: No existing call ID to find parties for Request_Instruction. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6334 ERR_RQI_NO_ACD Explanation: No parties in an existing call for Request_Instruction. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6335 ERR_RQI_RT_PARTY_XFOF_OVERLOAD Explanation: No resources for a routed from party for Request_Instruction. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6336 ERR_RQI_REM_PARTY_NO_CALLID Explanation: No existing call ID to remove an original PILOT party. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6339 ERR_RQI_AGENT_NO_CALLID Explanation: No extended call ID to find parties for Request_Instruction. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6340 ERR_RQI_NO_AGENT Explanation: Unable to locate parties in an extended call for Request_Instruction. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6343 ERR_RQI_BAD_PARSER_CR Explanation: Unable to parse the Call_Routed message to send to the host. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Request_Instruction message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6344 ERR_RQI_GET_CALLID_NOT_INUSE Explanation: Unable to get data for an internal call ID. Cause: The Call State routine 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: SWITCH.EXE Severity: SEVERE 6345 ERR_ALT_NO_RT_AGENT_CALL2 Explanation: Unable to remove a previously called agent from an extended call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6346 ERR_ALT_RF_PILOT2_RSRC_OVERLOAD Explanation: Unable to create control blocks for a called agent in an extended call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6347 ERR_ALT_NO_OVFL_PARTY2 Explanation: Neither an agent nor a PILOT party was found in an extended call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Alerting message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6348 ERR_DSC_NO_OVFL_CALLID2 Explanation: Unable to locate an extended call ID for Disconnected. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6349 ERR_DSC_NO_OVFL2_CGACD Explanation: Unable to locate the parties in an extended call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6350 ERR_DSC_MON_OVFL_CALLID2 Explanation: No call ID containing the tracked party information. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6351 ERR_DSC_NO_RF_CALL2 Explanation: No extended call ID to remove the routed from party. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6353 ERR_DSC_RPAG_CALLID_NOT_INUSE Explanation: No original call ID to remove transferring agent. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6354 ERR_ERT_BAD_SWITCHRT Explanation: The DMS-100 CO switch sent a bad request tag. Cause: The switch-dependent part of the server received a Response message with an invalid request_tag. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6355 ERR_ERT_CALL_ID_NOT_INUSE Explanation: Unable to locate a call ID associated with a valid request. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Disconnected message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6356 ERR_ERT_BAD_MSG_TYPE Explanation: The DMS-100 switch sent an unsupported message. Cause: The switch-dependent part of the server received an unknown message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6357 ERR_DRQ_BAD_DMSENCODE Explanation: Unable to encode a message to be sent to the DMS-100 switch. Cause: The switch-dependent part of the server was unable to process a request to the DMS-100 CO switch. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6358 ERR_RDRRR_CALLID_NOT_INUSE Explanation: Unable to check pointer to an extended call for Redirect_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Redirect_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6359 ERR_RDRRE_CALLID_NOT_INUSE Explanation: Unable to check pointer to an extended call for Redirect_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a negative Response to a Redirect_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6360 ERR_EXTRE_CALLID_NOT_INUSE Explanation: No data for an original internal call ID for Extend_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a negative Response to an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6361 ERR_EXTRE_CALLID2_NOT_INUSE Explanation: No data for an extended internal call ID Extend_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a negative Response to an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6362 ERR_MONRR_BAD_EVENT_TYPE Explanation: An invalid message type was found for Monitor. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Monitor request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6363 ERR_RTE_NO_RT_OVFL_PARTY2 Explanation: Unable to create control blocks for a PILOT party in an extended call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6364 ERR_RTE_RT_CALL_ID2_NOT_INUSE Explanation: Unable to add a PILOT party to an extended call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a ring threshold Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6365 ERR_RTE_NO_REM_AGENT_CALL2 Explanation: Unable to remove the agent from an extended call. Cause: The Call State routine of the server is corrupted. The error occurred while processing an overflow Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6366 ERR_RTE_NO_RT_OVFL_AGENT2 Explanation: Unable to create control blocks for a PILOT party in an extended call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a ring threshold Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6367 ERR_RTE_RT_CALL_IDA2_NOT_INUSE Explanation: Unable to add a PILOT party to an extended call. Cause: The Call State routine of the server is corrupted. The error occurred while processing an overflow Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6368 ERR_RTE_BAD_PARTY2 Explanation: Unable to locate either an agent or a PILOT party in an extended call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6369 ERR_RTE_MON_OVFL_CALLID2 Explanation: Unable to locate an extended call ID containing tracked party data. Cause: The Call State routine of the server is corrupted. The error occurred while processing an overflow Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6370 ERR_RTE_BAD_ROUTE Explanation: No message was sent by the switch when two calls exist. Cause: The Call State routine of the server is corrupted. The switch should have sent either a transfer or an overflow message. The error occurred while processing a Call_Routed message. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6371 ERR_EXTRE_CALL_ID_NOT_INUSE Explanation: No call ID for an Extend_Call request. Cause: The Call State routine of the server is corrupted. The error occurred while processing a negative Response to an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6372 ERR_EXTRR_CALL_LIST_OVERFLOW Explanation: Extending party found in too many calls. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6373 ERR_EXTRR_NO_CALLID_FOR_DN Explanation: Unable to locate a call ID for an extending party. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6374 ERR_EXTRR_NO_CALLID_FOR_EX_CALL Explanation: Unable to locate an extended call ID. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6375 ERR_EXTRR_NO_CALLID_FOR_OR_CALL Explanation: Unable to locate an original call ID for Extend_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6376 ERR_EXTRR_NUM_PARTY_IN_EX_CALL Explanation: Incorrect number of parties found in an extended call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6377 ERR_EXTRR_NUM_PARTY_IN_OR_CALL Explanation: Incorrect number of parties found in an original call for Extend_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6378 ERR_EXTRR_RT_INVALID Explanation: The switch sent an invalid request tag for Extend_Call. Cause: The switch-dependent part of the server received a message with an invalid invoke tag while processing a positive Response to an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6379 ERR_EXT_ADDPARTY_A2_UNAVAIL Explanation: Unable to add a calling party to a new call for Extend_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6380 ERR_EXT_ADDPARTY_C_UNAVAIL Explanation: Unable to add a called party to a new call during Extend_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6381 ERR_EXT_CREATECALL_UNAVAIL Explanation: Unable to create control blocks for a new call during Extend_Call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6382 ERR_EXT_CREATEPARTY_A2_UNAVAIL Explanation: Unable to create control blocks for a calling party in a new call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6383 ERR_EXT_CREATEPARTY_C_UNAVAIL Explanation: Unable to create control blocks for a called party in a new call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6384 ERR_EXT_EXT_CALL_ID_NOT_INUSE Explanation: Unable to locate an extended call ID. Cause: The Call State routine of the server is corrupted. The error occurred while processing an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6385 ERR_EXT_ORIG_CALL_ID_NOT_INUSE Explanation: Unable to locate an original call ID during Extend_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing an Extend_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6386 ERR_MKCRE_CALL_ID_NOT_INUSE Explanation: Unable to locate a call ID during Make_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a negative Response to a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6387 ERR_MKCRR_CALLID_ASSOCIATED Explanation: Unable to associate a switch call ID twice during Make_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6388 ERR_MKCRR_CALL_ID_NOT_INUSE Explanation: No internal call ID for switch call ID during Make_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6389 ERR_MKCRR_NO_CALLID_FOR_CALL Explanation: No internal call ID for parties during Make_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6390 ERR_MKCRR_NUM_PARTY_IN_CALL Explanation: Incorrect number of parties found in a call during Make_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a positive Response to a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6391 ERR_MKCRR_RT_INVALID Explanation: The switch sent an invalid request_tag for Make_Call. Cause: The switch-dependent part of the server received a message with an invalid invoke tag while processing a positive Response to a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6392 ERR_MKC_ADDPARTY_A_UNAVAIL Explanation: Unable to add a calling party to a call during Make_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6393 ERR_MKC_ADDPARTY_B_UNAVAIL Explanation: Unable to add a called party to a call during Make_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6394 ERR_MKC_CALL_ID_NOT_INUSE Explanation: Unable to locate a call ID while processing a Make_Call request. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6395 ERR_MKC_CREATECALL_UNAVAIL Explanation: Unable to create control blocks for a call during Make_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6396 ERR_MKC_CREATEPARTY_A_UNAVAIL Explanation: Unable to create control blocks for a calling party during Make_Call. Cause: The Call State routine of the server is corrupted. The error occurred while processing a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6397 ERR_MKC_CREATEPARTY_B_UNAVAIL Explanation: Unable to create control blocks for a called party during Make_Call. Cause: The switch-dependent part of the server could not allocate internal control blocks while processing a Make_Call request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6398 ERR_MONRE_CALL_ID_NOT_INUSE Explanation: Unable to locate a call ID during a Monitor request. Cause: The Call State routine of the server is corrupted. The error occurred while processing a negative Response to a Monitor request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6399 ERR_MONRE_FLAG_NOT_SET Explanation: The Monitor flags were not properly set. Cause: The Call State routine of the server is corrupted. The error occurred while processing a negative Response to a Monitor request. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6400 ERR_X25_DATA_RCV_CLEAR Explanation: X.25 link disconnected. Cause: The X.25 cable has been disconnected, the X.25 communication has stopped, or the Communications Manager session has been stopped. Action: Fix the X.25 communication problem. From the server connection screen, inactivate the DMS-100 CO switch, then reactivate it. Module: SWITCH.EXE Severity: SEVERE 6404 ERR_CXS_X25_LINK_ERROR_LEVEL_1 Explanation: CXS X.25 link error level 1 Cause: The X.25 cable has been disconnected, the X.25 communication has stopped, or the Communications Manager session has been stopped. Action: Fix the X.25 communication problem. From the server connection screen, inactivate the DMS-100 CO switch, then reactivate it. Module: SWITCH.EXE Severity: SEVERE 6405 ERR_CXS_X25_LINK_ERROR_LEVEL_2 Explanation: CXS X.25 link error level 2 Cause: The X.25 cable has been disconnected, the X.25 communication has stopped, or the Communications Manager session has been stopped. Action: Fix the X.25 communications problem. From the server connection screen, inactivate the DMS-100 CO switch, then reactivate it. Module: SWITCH.EXE Severity: SEVERE 6408 ERR_X25_INSUFFICIENT_RESOURCE Explanation: X.25 feature has insufficient resources to process the request. Cause: The X.25 feature cannot process a request due to insufficient resources. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6421 ERR_X25_LINK_CLOSED Explanation: X.25 link disconnected. Cause: The X.25 link is in disconnect mode. Action: Reactivate the DMS-100 CO switch connection on the server. Module: SWITCH.EXE Severity: SEVERE 6422 ERR_X25_LINK_ERROR_LEVEL_1 Explanation: X.25 link error at physical level. Cause: There is a hardware error on the X.25 link. Action: If directly connected to the DMS-100 CO switch, check connectors and cables. If connected to a public network, contact the telephone company carrier. Module: SWITCH.EXE Severity: SEVERE 6423 ERR_X25_LINK_ERROR_LEVEL_2 Explanation: X.25 link error at link level. Cause: There is an error on the X.25 link at the link level. Action: Reactivate the DMS-100 CO switch connection on the server. Module: SWITCH.EXE Severity: SEVERE 6426 ERR_X25_APP_ACTIVE Explanation: X.25 application program initialized its use of the API. Cause: The server attempted to reinitialize the X.25 feature. Action: Reactivate the DMS-100 CO switch connection on the server. Module: SWITCH.EXE Severity: SEVERE 6429 ERR_X25_VC_FREED Explanation: X.25 SVC link was freed. Cause: The X.25 link to the switch was cleared. Action: Reactivate the DMS-100 CO switch connection on the server. Module: SWITCH.EXE Severity: SEVERE 6437 ERR_X25_NO_CONN_AVAILABLE Explanation: X.25 SVC limit has been reached. Cause: The total number of two way SVCs in use has reached the maximum number of SVCs configured. Action: Increase the configurable number of SVCs (be sure and have the switch translation tables modified accordingly). Module: SWITCH.EXE Severity: SEVERE 6438 ERR_X25_NO_VC_AVAILABLE Explanation: No X.25 SVC available. Cause: The total number of two way SVCs in use have reached the maximum number of SVCs available from X.25 API. Action: None. There are too many SVCs configured for switch connections. Cannot exceed the limit set by the X.25 API. Module: SWITCH.EXE Severity: SEVERE 6451 ERR_X25_CALL_CLEARED Explanation: X.25 call cleared. Cause: The X.25 call has been cleared. No more data can be exchanged. Action: Reactivate the DMS-100 CO switch connection on the server. Module: SWITCH.EXE Severity: SEVERE 6452 ERR_X25_CLEAR_COLLISION Explanation: X.25 received a Clear indication while processing X25CallClear. Cause: X.25 call is being cleared. Action: No action required. Module: SWITCH.EXE Severity: SEVERE 6453 ERR_X25_RESET_COLLISION Explanation: X.25 received a reset indication while processing X25Reset. Cause: The X.25 virtual circuit is being reset; there can be no further data exchange until the reset is complete. Action: No action required. Module: SWITCH.EXE Severity: SEVERE 6454 ERR_X25_VC_RESETTING Explanation: X.25 virtual circuit resetting. Cause: The X.25 virtual circuit is being reset; there can be no further data exchange until the reset is complete. Action: No action required. Module: SWITCH.EXE Severity: SEVERE 6464 ERR_X25_NO_DATA Explanation: X.25 transmission with no data. Cause: No data given to send. Action: This is an informational message. If the problem persists, collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6472 ERR_X25_RESET_IN_PROGRESS Explanation: X.25 Reset already in progress. Cause: The X.25 virtual circuit is being reset; there can be no further data exchange until the reset is complete. Action: No action required. Module: SWITCH.EXE Severity: SEVERE 6473 ERR_X25_M_BIT_INDICATOR_ERR Explanation: X.25 verb contains an invalid M-bit. Cause: The X.25 request contains an invalid M-bit value. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6499 ERR_X25_RCV_UNKNOWN Explanation: Unknown X.25 receive error. Cause: The X.25 receive function has returned an unknown error code. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6500 ERR_CNC_CALLID_RSRC_UNAVAIL Explanation: Unable to create a new call control block. Cause: The Call State routine of the server is corrupted. The error occurred while creating a new call. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6501 ERR_CNC_CD_CALLID_NOT_INUSE Explanation: Unable to create or add a new party to a call. Cause: The switch-dependent routine of the server was unable to allocate internal control blocks while adding a new party to an existing call. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6502 ERR_DCU_NO_CALLID Explanation: Unable to locate an existing call control block. Cause: The Call State routine of the server is corrupted. The error occurred while searching for information about an existing call. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6503 ERR_REP_PARTY_RSRC_OVERLOAD Explanation: Unable to create a new party. Cause: The switch-dependent routine of the server was unable to allocate internal control blocks while adding a new party to an existing call. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6504 ERR_REP_CALLID_NOT_INUSE Explanation: No existing call control block to add a new party to. Cause: The Call State routine of the server is corrupted. The error occurred while searching for information about an existing call. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6505 ERR_FP_NO_PARTY Explanation: Unable to locate both parties in a call. Cause: The Call State routine of the server is corrupted. The error occurred while processing information about an existing call. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6506 ERR_DSC_NO_CS_PARTY Explanation: Unable to locate an existing party in the Call State Model. Cause: The Call State routine of the server is corrupted. The error occurred while searching for information about an existing party. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6507 ERR_RTE_BAD_PARSER_CR Explanation: Unable to generate a Request_Instruction message. Cause: The Call State routine of the server is corrupted. The error occurred while attempting to send a Request_Instruction message to the host. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6508 ERR_CS_NO_PARTY Explanation: Unable to locate the party with the expected connection ID state. Cause: The Call State routine of the server is corrupted. The error occurred while searching for a party in an existing call that has a specific connection ID state. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6509 ERR_ACD_NO_PARTY Explanation: Unable to locate a PILOT party. Cause: The Call State routine of the server is corrupted. The error occurred while searching for a party in an existing call that has a specific party type. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6510 ERR_FPT_NO_PARTY Explanation: Unable to locate a party with the expected party type. Cause: The Call State routine of the server is corrupted. The error occurred while searching for a party in an existing call that has a specific party type. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6511 ERR_CON_NO_TRACK_CALLID Explanation: Unable to locate the call control block for the track call party. Cause: The Call State routine of the server is corrupted. The error occurred while searching for an internal control block that contains information about the track call party. Action: Collect the system message, trace, and dump data, then ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6512 ERR_MEM_SEM_CREATE Explanation: Memory error creating semaphore. Cause: Insufficient system resources. Action: Shutdown and reboot. If symptoms persist, ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6513 ERR_MEM_SHMEM_CREATE Explanation: Memory error creating shared semaphore. Cause: Insufficient system resources. Action: Shutdown and reboot. If symptoms persist, ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6514 ERR_MEM_SHMEM_ATTACH Explanation: Memory error attaching shared semaphore. Cause: Insufficient system resources. Action: Shutdown and reboot. If symptoms persist, ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6515 ERR_MEM_SEM_OPEN Explanation: Memory error opening semaphore. Cause: Insufficient system resources. Action: Shutdown and reboot. If symptoms persist, ask your IBM service representative to review the results. Module: SWITCH.EXE Severity: SEVERE 6516 ERR_UPDATING_CONFIG_FILE Explanation: Configuration file was not updated. Errors in configuration remain. Cause: Unable to update configuration file. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. Module: SWITCH.EXE Severity: SEVERE 6517 ERR_OPEN_CONFIG_FILE Explanation: Configuration file could not be opened to cure errors. Cause: The file containing logon parameters could not be opened. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. Module: SWITCH.EXE Severity: SEVERE 6518 ERR_READING_CONFIG_FILE Explanation: Configuration file could not be read to cure configuration errors. Cause: The file containing configuration parameters could not be read. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. Module: SWITCH.EXE Severity: SEVERE 6519 ERR_WRITING_TO_CONFIG_FILE Explanation: Configuration file could not be written to update configuration. Cause: The server could not write the configuration file to the disk. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. Module: SWITCH.EXE Severity: SEVERE 6520 ERR_CLOSING_CONFIG_FILE Explanation: Unable to close configuration file after attempting to correct errors. Cause: The configuration file could not be closed after writing to it. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. Module: SWITCH.EXE Severity: SEVERE 6521 ERR_ENCODE_LOGON Explanation: Error in encoding logon message to be sent to switch. Cause: Logon message to the switch could not be encoded. Action: Need a working copy of DMSLOG.PNL in the the server directory. Update DMS100.CFG or dmslogon.00N (where N is the particular switch connection number). before trying to log on to the switch. To update, choose "Change switch parameters" in the "Connections" section. Module: SWITCH.EXE Severity: SEVERE 6522 ERR_DECODE_LOGON Explanation: Error in decoding message in response to logon attempt. Cause: The return message from the switch to a logon attempt could not be decoded. Action: If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6523 ERR_COMM_SEND_LOGON Explanation: Attempt to send logon message failed. Cause: Could not send logon request to the switch. Action: If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6524 ERR_COMM_RCV_LOGON Explanation: Failed to receive any return to logon request. Cause: Received no response to logon request. Action: Try to make the switch connection active again. Contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6525 ERR_INVOKE_ID_LOGON_RTN Explanation: Invoke ID in the logon return message from switch is invalid. Cause: Response to logon request had an invalid Invoke Identification number. Action: If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6526 ERR_LOGON_MISSING_PARM Explanation: One or more parameters are missing from logon request. Module: SWITCH.EXE Severity: SEVERE 6527 ERR_LOGON_MISSING_NETNODEID Explanation: Switch returned error to logon request: missing network node ID. Cause: Logon request was missing the network node ID. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6528 ERR_LOGON_MISSING_SVC_ID Explanation: Switch return error to logon request: missing service ID. Cause: Logon request was missing the service ID. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6529 ERR_LOGON_MISSING_SVCVSN Explanation: Switch return error to logon request: missing service version. Cause: Logon request was missing the BCS level (service version). Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6530 ERR_LOGON_MISSING_BUSGRPID Explanation: Switch return error to logon request: missing Business Group ID. Cause: Logon request was missing the Business Group ID. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6531 ERR_LOGON_MISSING_APPL_ID Explanation: Switch return error to logon request: missing Application ID. Cause: Logon request was missing the Application ID. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6532 ERR_LOGON_MISSING_PASSWORD Explanation: Switch return error to logon request: missing password. Cause: Logon request was missing the Password. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6533 ERR_OPENING_DISPLAY_PANELS Explanation: Configuration display panel could not be opened. Cause: In an attempt to update switch logon parameters, the display panel could not be opened. Action: Need a working copy of DMSLOG.PNL in the server directory. Update DMS100.CFG before trying to log on to the switch. To update, choose to change switch parameters in the connections section. Module: SWITCH.EXE Severity: SEVERE 6534 ERR_READING_DISPLAY_PANELS Explanation: Configuration display panel could not be read. Cause: In an attempt to update configuration parameter, the display panel could not be read. Action: Need a working copy of DMSLOG.PNL in the the server directory. Update DMS100.CFG before trying to log on to the switch. To update, choose to change switch parameters in the connections section. Module: SWITCH.EXE Severity: SEVERE 6536 ERR_LOGON_INVALID_PARM Explanation: Switch return error to logon request: invalid parameter. Cause: Logon request contained an invalid parameter. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6537 ERR_LOGON_INVALID_NETNODEID Explanation: Switch return error to logon request: invalid network node ID. Cause: Logon request contained an invalid network node ID. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6538 ERR_LOGON_INVALID_SVC_ID Explanation: Switch return error to logon request: invalid service ID. Cause: Logon request contained an invalid service ID. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6539 ERR_LOGON_INVALID_SVCVSN Explanation: Switch return error to logon request: invalid service version. Cause: Logon request contained an invalid BCS level (service version). Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6540 ERR_LOGON_INVALID_BUSGRPID Explanation: Switch return error to logon request: invalid Business Group ID. Cause: Logon request contained an invalid Business Group ID. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6541 ERR_LOGON_INVALID_APPL_ID Explanation: Switch return error to logon request: invalid Application ID. Cause: Logon request contained an invalid Application ID. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6542 ERR_LOGON_INVALID_PASSWORD Explanation: Switch return error to logon request: invalid password. Cause: Logon request contained an invalid password. Action: For SwitchServer/2, start CPSS2 from the CPSS2 directory, then go to the connections panel. Choose "Switch" then choose "Change Switch Parameters". The file DMSLOG.PNL must be in the CPSS2 directory. For CallPath Server/2 and CallPath Server/6000, configure the switch parameters. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6543 ERR_LOGON_NO_RETURN_RSLT_RCVD Explanation: Message from switch was not a return result message. Cause: No return result message received from switch. Action: If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6544 ERR_NOT_LOGON_RTN_RSLT Explanation: Message from switch was not a logon return result message. Cause: Response to logon request by the switch was not a logon return result message. Action: If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6545 ERR_LOGON_RTN_ERR_INVALID Explanation: Switch logon return error cause is not recognized. Cause: Response to logon request by the switch was an unrecognized return error. Action: If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6546 ERR_NO_LOGON_RESRCES_AVAILABLE Explanation: Resources are not available for a logon request. Cause: The switch has insufficient resources to execute a new logon. Action: In the connections panel, opt for the switch menu. In the switch panel, opt for change in switch connection. Indicate that the switch is to be inactive. Press Enter. After a brief pause, retrace steps to get to the same panel. Attempt to activate switch. Module: SWITCH.EXE Severity: SEVERE 6547 ERR_X25AUTH Explanation: X.25 authorization error. Cause: User does not have systems permission to control the status of the link. Action: Program must be run by the root user ID. Module: SWITCH.EXE Severity: SEVERE 6548 ERR_X25BADID Explanation: The connection identifier or listen identifier is bad. Cause: The X.25 connection identifier or listen identifier is bad. Action: Check that your local and remote network addresses are consistent with the addresses used by the switch administrator. Module: SWITCH.EXE Severity: SEVERE 6549 ERR_X25CALLED Explanation: The called address is invalid. Cause: The address that the switch uses to identify itself is different than the switch address (remote address) that was provided in the dmslogon parameter file or by the directory entry name for the remote DTE. Action: Correct the remote address in dmslogon.00N or in the Communications Manager configuration. Module: SWITCH.EXE Severity: SEVERE 6550 ERR_X25CALLING Explanation: X.25 calling address is incorrect. Cause: The network user address provided in the dms logon parameter file or the directory entry name contains the wrong local address. Action: Check with the switch administrator for the address that the switch has for the server. Make changes as required. Module: SWITCH.EXE Severity: SEVERE 6551 ERR_X25CAUSE Explanation: X.25 API has caused an error in communications. Cause: The X25 API is corrupted. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6552 ERR_X25CTRUSE Explanation: X.25 counter use. Cause: The receive buffer counter is corrupted. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6553 ERR_X25INIT Explanation: X.25 initialization has already taken place. Cause: Some other application has already initialized the x25 link. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6554 ERR_X25INVFAC Explanation: An optional facility request is invalid. Cause: A request for an optional facility is rejected by the X25 API. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6555 ERR_X25INVMON Explanation: Monitor mode is invalid. Cause: Monitor call to X25 API is invalid. Action: This error should not be received. Contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6556 ERR_X25LINKUSE Explanation: X.25 link in use. Cause: The X25 API shows the virtual circuit to be in use. Action: Confirm that the link is not active in another program. If not active in another program, log on as root and enter xmanage -s. Execute a disconnect of the link in question. If the link will not disconnect, shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6557 ERR_X25LONG Explanation: X.25 long indicates that a parameter is too long. Cause: A parameter, such as local address, exceeds maximum length (in this case 15 characters). Action: Limit size of parameters to maximum allowed. Module: SWITCH.EXE Severity: SEVERE 6558 ERR_X25NAMEUSED Explanation: X.25 port name used. Cause: The slot number (x25s0 ... x25s3) is in use. Action: Resolve the conflict of slot name to use for the different switch sessions. Look in dmslogon.00N SLOT_NUMBER line for redundant use of same slot number. Module: SWITCH.EXE Severity: SEVERE 6559 ERR_X25NOACK Explanation: X.25 no acknowledgment required. Cause: Acknowledgment received and not required. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6560 ERR_X25NOCARD Explanation: X.25 card is not responding. Cause: X25 card is not responding. Action: Install a new card. If problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6561 ERR_X25NOCTR Explanation: X.25 counter unavailable. Cause: No x25 counter is available (resource limitation). Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6562 ERR_X25NODATA Explanation: No X.25 data in the receive buffer. Cause: No X25 data has been received. Action: The X25 API is corrupted. Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6563 ERR_X25NODEVICE Explanation: X.25 device driver not functioning. Cause: The X25 device driver is not functioning. Action: Install the device driver, icaaim.com in directory /etc/microcode. Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6564 ERR_X25NOIPC Explanation: X.25 no IPC. Cause: Initial program call not made. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6565 ERR_X25NOLINK Explanation: X.25 not linked. Cause: Link has not been connected or is disconnected. Action: Use xmanage to attempt to connect the link. Make sure that the data terminal or modem is in place. Ask your switch representative if the link is available from the switch. Use AIX/V3 X.25 Communications Cookbook to help determine the problem. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6566 ERR_X25NONAME Explanation: X.25 no name. Cause: The name used is not in the routing list. Action: Check your dmslogon.00N configuration files and the smit communications adapter configurations for consistent names. Module: SWITCH.EXE Severity: SEVERE 6567 ERR_X25NOROUTER Explanation: X.25 no router. Cause: Name router does not exist. Action: Check your name server for accuracy. Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6568 ERR_X25NOTPVC Explanation: X.25 not PVC. Cause: The link is not defined as a permanent virtual circuit. Action: Check smit configurations. Module: SWITCH.EXE Severity: SEVERE 6569 ERR_X25PGRP Explanation: X.25 PGRP. Cause: PVC Group may not defined. Action: Check smit configurations. Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6570 ERR_X25PROTOCOL Explanation: X.25 protocol. Cause: Message does not conform to X25 protocol. Action: If the error occurred during a receive message cycle, notify your switch representative. If the error occurred during a send, shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6571 ERR_X25PVCUSED Explanation: X.25 PVC used. Cause: Permanent virtual circuit is already in use. Action: Check smit for configurations. Do not use any PVCs. Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6572 ERR_X25RECEIVERINIT Explanation: X.25 receiver initialization not done. Cause: Receive process has not been initialized. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6573 ERR_X25RESETCLEAR Explanation: X.25 reset clear was received to a send message. Cause: The x25 link has been cleared by the switch. Action: Restart the session. If the problem persists, check with your switch administrator for switch error logs on the link. Module: SWITCH.EXE Severity: SEVERE 6574 ERR_X25ROUTERINIT Explanation: X.25 router initialization not done. Cause: Router initialization not done. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6575 ERR_X25TABLE Explanation: X.25 table not updated. Cause: Router table is in use. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6576 ERR_X25TIMEOUT Explanation: X.25 time out. Cause: A timeout problem occurred. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6577 ERR_X25TRUNC Explanation: X.25 packet truncated. Cause: Data packet was too large and had to be truncated. Action: Check the smit configurations for packet size. Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6578 ERR_X25TOOBIG Explanation: X.25 too big. Cause: The buffer to be transmitted is too big. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6579 ERR_X25TOOMANYVCS Explanation: X.25 has too many virtual circuits. Cause: Too many virtual circuits opened. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6598 ERR_X25AUTHCTR Explanation: X.25 authorization counter. Cause: Authorization counter exceeded. Action: Shutdown and reboot. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6599 ERR_X25AUTHLISTEN Explanation: X.25 authorization to listen not present. Cause: A listening process is not authorized. Action: Make sure all the executable code is owned by the same user ID. Module: SWITCH.EXE Severity: SEVERE 6600 ERR_X25BADCONNID Explanation: X.25 bad connection ID. Cause: The connection identifier is invalid. Action: Shutdown and reboot. If the condition persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6601 ERR_X25BADDEVICE Explanation: X.25 bad device. Cause: The port name is invalid. Action: Check the port names (slot number) in the configuration file. Make sure that the name matches the x25sN name used in smit configuration. Module: SWITCH.EXE Severity: SEVERE 6602 ERR_X25BADLISTENID Explanation: X.25 bad listen ID. Cause: The listen identifier is invalid. Action: Shutdown and reboot. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6603 ERR_X25INVCTR Explanation: X.25 invalid counter. Cause: A counter passed to the X25 API does not exist. Action: Shutdown and reboot. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6604 ERR_X25LINKUP Explanation: X.25 link is up. Cause: In an attempt to connect the link, the X25 API has returned a link already up status. Action: Retry. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6605 ERR_X25LONGCUD Explanation: X.25 long customer user data. Cause: User data exceeds the user data size. Action: Shutdown and reboot. If the symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6606 ERR_X25MAXDEVICE Explanation: X.25 max devices available have been exceeded. Cause: An attempt to connect more than the maximum number of devices available to X25 has been made. Action: Check X25 configurations in smit to see if all the devices requested are available. Shutdown and reboot. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6607 ERR_X25MONITOR Explanation: X.25 monitor is already on. Cause: Another application is monitoring X25 transactions. Action: Stop the other application that is monitoring X25. Module: SWITCH.EXE Severity: SEVERE 6608 ERR_X25NOACKREQ Explanation: X.25 no acknowledgment required. Cause: Acknowledgment sent when none required. Action: Shutdown and reboot. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6609 ERR_X25NOSUCHLINK Explanation: X.25 no such link. Cause: The X25 port does not exist. Action: Check your smit configurations and your dmslogon file(s) for correct port names. Shutdown and reboot. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6610 ERR_X25NOTINIT Explanation: X.25 not initialized. Cause: Initialization of X25 has not occurred. Action: Retry. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6611 ERR_X25TRUNCRX Explanation: X.25 message truncated. Cause: The message from the switch exceeds the receive buffer size and was truncated. Action: Check with switch vendor for any exception or error logs generated around the time in question. Check that the frame and packet parameter configuration files in smit are correct. Shutdown and reboot. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6612 ERR_X25TRUNCTX Explanation: X.25 message truncated. Cause: The message to be sent to the switch exceeds buffer size and was not sent. Action: Check the frame and packet parameter configuration files in smit. Make sure they conform to the values stated in the X25 configuration chapter in this book. Shutdown and reboot. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6613 ERR_X25BADSTATUS Explanation: X.25 bad status. Cause: Link status is not connected. Action: Check link status with xmanage. Try and re-establish link. Ask switch representative if there are link problems with the switch. Shutdown and reboot. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6614 ERR_X25SYSERR Explanation: System error. Cause: Operating system returned an error and may include a bad address pointer, signal interrupt, an I/O error, lack of resources or invalid authorization. Action: Shutdown and reboot. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6615 ERR_X25UNKNOWN Explanation: X.25 unknown error. Cause: An error number outside of the set of error numbers listed by X25 API was returned. Action: Shutdown and reboot. If symptoms persist, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6616 ERR_GETTING_NETNODE_ID Explanation: Error getting network node ID. Cause: NETNODE_ID is missing in the dmslogon.00N file (N is the switch connection number). Action: Reconfigure switch0N. There must be a line in the dmslogon.00N file with the parameter name NETNODE_ID aligned with the left-most column, and a value, such as 1, to its right on the same line. Module: SWITCH.EXE Severity: SEVERE 6617 ERR_GETTING_SERVICE_ID Explanation: Error getting service ID. Cause: SERVICE_ID is missing in the dmslogon.00N file (where N is the switch connection number). Action: Re-configure switch0N. There must be a line in the dmslogon.00N file with the parameter name SERVICE_ID aligned with the left-most column, and a value, such as 1, to its right on the same line. Module: SWITCH.EXE Severity: SEVERE 6618 ERR_GETTING_SERVICE_VERSION Explanation: Error getting service version. Cause: SERVICE_VERSION is missing in the dmslogon.00N file (where N is the switch connection number). Action: Re-configure switch0N. There must be a line in the dmslogon.00N file with the parameter name SERVICE_VERSION aligned with the left-most column, and a value to its right on the same line. Module: SWITCH.EXE Severity: SEVERE 6619 ERR_GETTING_BUSINESS_GROUP Explanation: Error getting business group. Cause: BUSINESS_GROUP_ID is missing in the dmslogon.00N file (where N is the switch connection number). Action: Re-configure switch0N. There must be a line in the dmslogon.00N file with the parameter name BUSINESS_GROUP_ID aligned in the left-most column, and a value, such as 1, to its right on the same line. Module: SWITCH.EXE Severity: SEVERE 6620 ERR_GETTING_APPL_ID Explanation: Error getting application ID. Cause: Application ID is missing in the dmslogon.00N file (where N is switch connection number). Action: Re-configure switch0N. There must be a line in the dmslogon.00N file with the parameter name APPLICATION_ID aligned in the left-most column, and a value, such as 1, to its right on the same line. Module: SWITCH.EXE Severity: SEVERE 6621 ERR_GETTING_PASSWORD Explanation: Unable to get the password. Cause: Password file, dmslogon.pwN (where N is 1, 2, ..., up to the maximum switch connections allowed), could not be read. Action: Recreate the password file by executing makepwd.exe. For example, to create dmslogon.pw3 with a password of PASS3, enter the command, makepwd.exe -3 PASS3. Alternatively, configure the switch from the graphical user interface. Module: SWITCH.EXE Severity: SEVERE 6622 ERR_GETTING_SLOT_NUMBER Explanation: Unable to get slot number (x25s0 or x25s1, or x25s2, or x25s3). Cause: Slot number was not found in dmslogon.00N file (where N is the switch connection number). Action: Slot number must be entered in the dmslogon.00N file used (even if in OS/2 server). The file must contain a line with the parameter SLOT_NUMBER aligned on the left edge of the text file, and a value, such as x25s0, on the same line. Module: SWITCH.EXE Severity: SEVERE 6623 ERR_GETTING_LOCAL_ADDR Explanation: Local address was not available. Cause: Unable to get local address or the directory entry name for the server. This input should have been in the dmslogon.00N (N is the switch session number). Action: Check that the file contains a line with the parameter LOCAL_CARD_ADDRESS_ENTRY aligned on the left edge of the text file, and that a value, such as 12345678 or SERVER06, is on the same line. Module: SWITCH.EXE Severity: SEVERE 6624 ERR_GETTING_SWITCH_ADDR Explanation: Remote address (that is, switch address) not available. Cause: Unable to get switch address or the directory entry name for the switch. This input should have been in the dmslogon.00N (N is the switch session number). Action: Check that the file contains a line with the parameter SWITCH_ADDRESS_ENTRY aligned on the left edge of the text file, and a value, such as 87654321 or DMS06 on the same line. Module: SWITCH.EXE Severity: SEVERE 6625 ERR_GLOBAL_PTR_NULL Explanation: NULL pointer for globals while trying to do getSwParms. Cause: There was an internal processing error. Action: Shutdown and restart. If the error is returned again, your code is corrupted. Get a replacement copy of the DMS100 code. Module: SWITCH.EXE Severity: SEVERE 6626 ERR_INSUF_SHELL_RESOURCES Explanation: Attempt to open a file returned NULL for a tmp file or a system call resulted in a bad return. Cause: System error. Action: Shutdown and restart. If the problem persists, contact your IBM service representative. Module: SWITCH.EXE Severity: SEVERE 6627 ERR_READ_PASSWORD Explanation: Password_read failed. Cause: Unable to read the encrypted password in file dmslogon.pwN (where N is 1, 2, ..., up to maximum switch connections allowed). Action: Make a password at a command prompt within the switchdm directory by entering makepwd.exe -N YOURPASSWORD, where N is the switch session and YOURPASSWORD is the password required by the switch for a good logon. Module: SWITCH.EXE Severity: SEVERE 6628 ERR_WRITE_PASSWORD Explanation: Password_write failed. Cause: Password_write to the encrypted binary password file dmslogon.pwN (where N is the switch session number) failed. Action: Write to password file, dmslogon.00N, offline by entering makepwd.exe -N YOURPASSWORD, where N is the switch session and YOURPASSWORD is the password that the switch requires for a good logon. Module: SWITCH.EXE Severity: SEVERE 6629 ERR_INCORRECT_PASSWORD Explanation: Password is incorrect. Cause: The password created and saved in dmslogon.pwN (where N is the switch session number) is incorrect. Action: Check with your switch administrator for the correct password. Re-make the dmslogon.pwN file by entering makepwd.exe -N GOODPASSWORD or by using the configure switch utility in the graphical user interface. Module: SWITCH.EXE Severity: SEVERE 6630 ERR_NONALPHA_PASSWORD Explanation: Password characters are out of readable range. Cause: Password characters are out of readable range of hex 0x20 (blank) to hex 0x7E (tilde or '~'). Action: Check with your switch administrator for the correct password. Re-make the dmslogon.pwN file by using makepwd.exe -N GOODPASSWORD or by using the configure switch utility in the graphical user interface. Module: SWITCH.EXE Severity: SEVERE 6631 ERR_GET_MSG_FAILED_MAX_COUNT Explanation: The server's request processor was unable to read a valid message from the server's message queue. Cause: All of a prior session's message queues have not been cleaned up. Action: Stop server and restart. If symptom persists, shutdown and restart. Module: SWITCH.EXE Severity: SEVERE 6632 ERR_HBT_CONT_TEST_NO_RESPONSE Explanation: No response to DV-APPL-CONTINUITY-TEST message. Cause: The switch did not respond to a periodic continuity test. Action: Verify that the switch and the X.25 link are operating properly. If the problem persists, collect the server trace data and review the results with your IBM service representative. Module: SWITCH.EXE Severity: SEVERE --------------------------------------------------------------------------- NetView Alerts (for CallPath SwitchServer/2 Only) This section deals specifically with the DMS-100 CO switch portion of CallPath SwitchServer/2. For more information about errors common to CallPath SwitchServer/2, see Using CallPath SwitchServer/2. Critical errors encountered by the DMS-100 CO switch portion of CallPath SwitchServer/2 cause an alert to be sent to NetView. When the DMS-100 CO switch portion of CallPath SwitchServer/2 encounters a critical error, one of the following types of NetView alerts is generated: * Resource alert--caused by a lack of resources in the CallPath SwitchServer/2 product * Software alert--caused by a software error in the DMS-100 CO switch portion of the CallPath SwitchServer/2 product Critical errors for CallPath SwitchServer/2 are logged in the system messages log. All critical errors specific to the DMS-100 CO switch portion of CallPath SwitchServer/2 are numbered in the 6000 to 6399, 6500 to 6599 range. To get the specifics of the error, check the system messages log on the CallPath SwitchServer/2 machine. Critical errors that cause resource alerts are: 6001 6234 6255 6271 6335 6501 6003 6236 6256 6273 6346 6503 6004 6238 6257 6274 6395 6190 6239 6261 6329 6396 6191 6247 6268 6330 6397 6233 6248 6270 6332 6500 All other critical errors cause software alerts. --------------------------------------------------------------------------- SNMP Traps (for CallPath Server Only) CallPath Server for OS/2 and CallPath Server for AIX can send severe messages to the specified SNMP focal point. See the CallPath Server Planning, Installation, and Problem Determination Guide for more information on SNMP. --------------------------------------------------------------------------- CallPath SwitchServer/2 Is Not Communicating with DMS-100 Central Office (CO) Switch CallPath SwitchServer/2 Is Not Communicating with DMS-100 Central Office (CO) Switch If the DMS-100 CO switch is not receiving messages, the switch connection is not in the Active state. When the switch connection remains in the Starting state for over one minute, follow these steps: 1. Check CallPath SwitchServer/2 system messages for possible error conditions. 2. Deactivate, then reactivate the switch connection using the instructions in Using CallPath SwitchServer/2. The connection status on CallPath SwitchServer/2 should go to the Active state within one minute of reactivating the switch connection. If this does not occur, proceed to step 3. 3. Power off CallPath SwitchServer/2, wait five seconds, then restart CallPath SwitchServer/2. If the DMS-100 CO switch connection still does not go to the Active state, contact your IBM service representative. --------------------------------------------------------------------------- Trace Data Server has the capability to trace and record all incoming and outgoing message activity. Trace data is available for the PC-to-host link and from the PC-to-DMS-100 CO switch link, and you can turn it on and off as desired. You can display trace data directly on the screen or log it to a file that you can browse, print, or delete. For details on displaying trace data, see Using CallPath SwitchServer/2 and the Callpath Server Planning, Installation, and Problem Determination Guide The trace file provides a translation of the encoded messages to and from the DMS-100 CO switch. Each message is displayed separately and may be on one or more screens. The following is an example of a Trace message for a Make_Call request to the switch: Figure 8. Trace Message Example +--------------------------------------------------------------------------------+ º 03-31-93 11:15:15 To Switch REQ11 º º DV_Make_Call º º Invoke ID = 15 º º MakeCallArgument CMP 25 Contents Follow º º Context field CTX 4 See next line º º OrigAddress CHC Choice follows º º PositionID NUM 2 4099 º º Context field CTX 12 See next line º º DestAddress CHC Choice follows º º DialedDigits STR 10 8004567890 º º ApplicationData CMP 3 Contents Follow º º MakeCallType NUM 1 0 º º Translation done...Hex dump is º º A1 21 02 01 0F 02 01 09 30 19 A0 04 80 02 10 03 A1 0C 81 0A º º 38 30 30 34 35 36 37 38 39 30 A2 03 80 01 00 º +--------------------------------------------------------------------------------+ Field Descriptions Header information, date (03-31-93), time (11:15:15), direction, and source or target of the message, as well as the link name (REQ11), are presented at the top of the screen. Under the date is the message name. Invoke ID follows. Refer to CompuCall Interface Specification for a description of the fields in the Trace messages. If the translation program encounters an error in the trace routine, three question marks (???) will appear in the left-most column under the date. As much of the message that can be traced will be shown, as well as some form of exception message. A hexadecimal dump of the encoded message will also be provided. Beneath the Invoke ID are all the fields in a predefined sequential order unique to that message (subfields are indented). Type of data contents (indicated by three capital letters) are: CMP Complex (the parameter is comprised of one or more parameters that follow in one or more lines) CTX Contextual (the parameter is contextually numbered to avoid ambiguity, actual parameter follows on next line) CHC Choice (the parameter is selected from alternate choices, actual choice is shown on following line) HEX Hexadecimal (the parameter is in hexadecimal) MIX Mixed data (the parameter is a mix of hexadecimal and ASCII) NUM Number (the parameter is an integer) STR String (the parameter is the ASCII string representation) Just to the right of the type of data contents is the number of bytes used for the data. If there are no contents or if the contents type is CHC (choice), the number of bytes field is blank. Data contents are to the right of the number of bytes. Function Key Descriptions In the Trace File screen, function key assignments are: * F1 - shows help screens * F5 - displays the prior message * F6 - displays the next message * F7 - displays the prior screen within the message * F8 - displays the next screen within the message * F12 - exits the display --------------------------------------------------------------------------- Dump Data CallPath SwitchServer/2 records the contents of virtual storage. Dump data is used by IBM service personnel in analyzing problems. --------------------------------------------------------------------------- Chapter 11. Example Program Call and Message Flows This chapter provides examples that show sequences of information flow from the DMS-100 CO switch. The examples include telephone calls initiated by CallPath Services program calls and telephone calls initiated manually using telephones. --------------------------------------------------------------------------- Overview To improve readability, only significant parameters and fields are listed in the examples. The following conditions apply to all examples, unless noted otherwise: * An Initialize_Call_Profile program call has been issued at some point before the start of the example. * A Set_Return_Response program call has been issued to set the value of return_response to STL_RESPONSE_RETURNED. * The Receive program call has been omitted from the examples. * Each program call made by the application program returns with a return_code of STL_OK. * A Monitor program call has been issued that specifies a mode of STL_START and that requests call track monitoring of the ACD primary pilot numbers. * If the program uses STLIPGV to identify itself as STL_VERSION_1, then the following program calls will have version fields set to Version 1 for CallPath Server for OS/2 and CallPath Server for AIX: o Call_Routed o Call_Alerting o Call_Canceled o Call_Disconnected o Call_Transfer The direction (Dir) column in each table indicates whether the information flow is from the host application program to the switch (SH). The parentheses around a parameter indicate that the parameter is returned to the application program, but not specified by the application program. Except where there is a need to differentiate between CallPath SwitchServer/2, CallPath Server for OS/2, and CallPath Server for AIX, the term "Server" will be used in place of the phrases "CallPath SwitchServer/2, CallPath Server/2, or CallPath Server for AIX" and "CallPath SwitchServer/2, CallPath Server for OS/2, and CallPath Server for AIX." Inbound Call Caller X dials B. Call is offered to B, then answered by B. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * B is the party number of Party B. * b1 is the connection ID of Party B. Activity Dir CallPath Services Program Call or Messages Call is S>H Call_Alerting calling_party_info (party_number=X, routed connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) to B. call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B B S>H Call_Connected connecting_party_info (party_number=B, answers connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) the call_type=STL_VOICE call. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B Call S>H Disconnected disconnecting_party_info (party_number=B, clears. connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B Inbound Call (Queued) Caller X dials SA. Call is put on queue of ACD Group SA, then is assigned to Agent AA. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of ACD Group SA. * sa1 is the connection ID of ACD Group SA. * AA is the party number of Agent AA. * aa1 is the connection ID of Agent AA. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Routed calling_party_info (party_number=X, queued connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) for ACD route_reason=STL_TO_QUEUE_ROUTE Group. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call is S>H Call_Routed calling_party_info (party_number=X, routed connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) to Agent route_reason=STL_FROM_PILOT_ROUTE AA. call_extension_indicator=STL_NO_CALL_EXTENSION routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_NO_CALL_EXTENSION alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA Agent AA S>H Call_Connected connecting_party_info (party_number=AA, answers connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, the original_group=SA, party_group=SA) call. call_extension_indicator=STL_NO_CALL_EXTENSION existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Call S>H Disconnected disconnecting_party_info (party_number=AA, clears. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Inbound Call (Not Queued) Caller X dials SA. Call is immediately assigned to Agent AA. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of ACD Group SA. * sa1 is the connection of ACD Group SA. * AA is the party number of Agent AA. * aa1 is the connection ID of Agent AA. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Routed calling_party_info (party_number=X, routed connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) to route_reason=STL_DIRECT_ROUTE agent. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Routed calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA Agent AA S>H Call_Connected connecting_party_info (party_number=AA, answers connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, the original_group=SA, party_group=SA) call. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Call S>H Disconnected disconnecting_party_info (party_number=AA, clears. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Inbound Call (Call Forwarded) Caller X dials Agent B. Call is offered to B, then is forwarded to C. C then answers the call. Note: B has the "CallForwardDon'tAnswer" call forwarding feature active. If B uses the "CallForwardUniversal" or "CallForwardBusy" features, no event messages are sent when a call is forwarded from B to C. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * B is the party number of Party B. * b1 is the connection ID of Party B. * C is the party number of Party C. * c1 is the connection ID of Party C. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Alerting calling_party_info (party_number=X, routed to connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) B. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B Call is forwarded. Call is S>H Call_Routed calling_party_info (party_number=X, offered to connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) C. routed_from_party_info (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE route_reason=STL_FORWARD_ROUTE routed_to_party_list (party_number=C, connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE dialed_number=B) track_call_party=B,C S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_NO_CALL_EXTENSION alerting_party_list (party_number=C, connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE, dialed_number=B) track_call_party=C C answers S>H Call_Connected connecting_party_info (party_number=C, the call. connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE, dialed_number=B) call_type=STL_VOICE call_extension_indicator=STL_NO_CALL_EXTENSION existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=C Call S>H Disconnected disconnecting_party_info (party_number=C, clears. connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE, dialed_number=B) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=C Inbound Call (Call Picked) Caller X dials Agent B. Call is routed to B. C picks up the call. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * B is the party number of Party B. * b1 is the connection ID of Party B. * C is the party number of Party C. * c1 is the connection ID of Party C. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Alerting calling_party_info (party_number=X, routed connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) to B. call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B Call is picked. C picks S>H Call_Picked connecting_party_info (party_number=C, up the connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE, call. dialed_number=B) picked_from_party_info (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B Call S>H Disconnected disconnecting_party_info (party_number=C, clears. connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE, dialed_number=B) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=C Inbound Call (Call Waited) Caller X dials B. Call is offered to B, then answered by B. While X and B talk, Y calls B. B puts X on hold, answers Y. B then drops Y and returns to X. Following is the legend for this example: * X is the party number of caller X. * x1 is the connection ID of caller X. * Y is the party number of Party Y. * y1 is the connection ID of Party Y. * B is the party number of Party B. * b1 is the connection ID of Party B. * b2 is the connection ID of Party B. Activity Dir CallPath Services Program Call or Message X calls S>H Call_Alerting calling_party_info (party_number=X, B. connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B B S>H Call_Connected connecting_party_info (party_number=B, answers connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) the call_type=STL_VOICE call. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B Y calls S>H Call_Alerting calling_party_info (party_number=Y, B. connection_ID=y1, party_type=STL_UNKNOWN_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=B, connection_ID=b2, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B B puts X S>H Call_Held holding_party_info (party_number=B, on hold, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) answers holding_party_calling=STL_CALLS_PERMITTED Y. holding_party_ID_2=b2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B S>H Call_Connected connecting_party_info (party_number=B, connection_ID=b2, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=Y, connection_ID=y1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B B drops S>H Disconnected disconnecting_party_info (party_number=B, Y and connection_ID=b2, party_type=STL_EXTENSION_PARTY_TYPE, returns dialed_number=B) other_disconnected_party_list to X. (party_number=Y, connection_ID=y1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B S>H Call_Connected connecting_party_info (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B Call S>H Disconnected disconnecting_party_info (party_number=B, clears. connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B Blind Transfer X dials SA. Call is queued for ACD Group SA, then is assigned to Agent AA. Agent AA then blind transfers the call to ACD Group SB via the telephone. Call is queued, then assigned to Agent BB. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number for ACD Group SA. * sa1 is the connection ID of ACD Group SA. * AA is the party number of Agent AA. * aa1 is the connection ID of Agent AA. * aa2 is the connection ID of Agent AA. * SB is the party number of ACD Group SB. * sb1 is the connection ID of ACD Group SB. * BB is the party number of Agent BB. * bb1 is the connection ID of Agent BB. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Routed calling_party_info (party_number=X, queued for connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) ACD Group. route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) Call is S>H Call_Routed calling_party_info (party_number=X, routed to connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) Agent AA. route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA Agent AA S>H Call_Connected connecting_party_info (party_number=AA, answers. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Agent AA S>H Call_Held holding_party_info (party_number=AA, calls Group connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, SB to start original_group=SA, party_group=SA) transfer. holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=aa2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA S>H Call_Routed calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) Agent AA S>H Call_Transferred transferring_party_ID_1 transfers. (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) transferring_party_ID_2 (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) Call is S>H Call_Routed calling_party_info (party_number=X, routed to connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) Agent BB. route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_NO_CALL_EXTENSION routed_from_party_info (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SB, party_group=SB) routed_to_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_NO_CALL_EXTENSION alerting_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Agent BB S>H Call_Connected connecting_party_info (party_number=BB, answers. connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) call_extension_indicator=STL_NO_CALL_EXTENSION existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA,SB Call S>H Disconnected disconnecting_party_info (party_number=BB, clears. connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA,SB Screened Transfer X dials SA. Call is queued for ACD Group SA, then is assigned to Agent AA. Agent AA then initiates transfers to ACD Group SB via the telephone. Call is queued, then assigned to Agent BB. Agents AA and BB talk, then AA transfers the original call to BB. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number for ACD Group SA. * sa1 is the connection ID of ACD Group SA. * AA is the party number of Agent AA. * aa1 is the connection ID of Agent AA. * aa2 is the connection ID of Agent AA. * SB is the party number of ACD Group SB. * sb1 is the connection ID of ACD Group SB. * BB is the party number of Agent BB. * bb1 is the connection ID of Agent BB. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Routed calling_party_info (party_number=X, queued for connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) ACD Group route_reason=STL_TO_QUEUE_ROUTE SA. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call is S>H Call_Routed calling_party_info (party_number=X, routed to connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) Agent AA. route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA Agent AA S>H Call_Connected connecting_party_info (party_number=AA, answers. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, party_group=SA, original_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Agent AA S>H Call_Held holding_party_info (party_number=AA, calls Group connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, SB to start original_group=SA, party_group=SA) transfer. holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=aa2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA S>H Call_Routed calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SB, party_group=SB) Call is S>H Call_Routed calling_party_info (party_number=AA, routed to connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, Agent BB. original_group=SA, party_group=SA) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION routed_from_party_info (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SB, party_group=SB) routed_to_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Call_Alerting calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION alerting_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Agent BB S>H Call_Connected connecting_party_info (party_number=BB, answers. connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA,SB Agent AA S>H Call_Transferred transferring_party_ID_1 transfers. (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) transferring_party_ID_2 (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA,SB Call S>H Disconnected disconnecting_party_info (party_number=BB, clears. connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA,SB Screened Transfer/ACD to Directory Number X dials SA. Call is queued for ACD Group SA, then is assigned to Agent AA. Agent AA then initiates transfer to C via the telephone. Agents AA and C talk, then AA transfers the original call to C. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of ACD Group SA. * sa1 is the connection ID of ACD Group SA. * AA. is the party number of Agent AA. * aa1 is the connection ID of Agent AA. * aa2 is the connection ID of Agent AA. * C is the party number of Party C. * c1 is the connection ID of Party C. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Routed calling_party_info (party_number=X, queued for connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) ACD Group route_reason=STL_TO_QUEUE_ROUTE SA. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call is S>H Call_Routed calling_party_info (party_number=X, routed to connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) Agent AA. route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA Agent AA S>H Call_Connected connecting_party_info (party_number=AA, answers. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, party_group=SA, original_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Agent AA S>H Call_Held holding_party_info (party_number=AA, calls Group connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, C to start original_group=SA, party_group=SA) transfer. holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=aa2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION alerting_party_list (party_number=C, connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=SA,C Agent C S>H Call_Connected connecting_party_info (party_number=C, answers. connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA,C Agent AA S>H Call_Transferred transferring_party_ID_1 transfers. (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) transferring_party_ID_2 (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA,C Call S>H Disconnected disconnecting_party_info (party_number=C, clears. connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA,C Trigger The DMS-100 CO switch-dependent code will not pass a Trigger request to the switch. It will send back a positive Response message. Redirection requests (via DV-CALL-RECEIVED-C) will be mapped to Request_Instruction and passed on to the switch-independent part of Server. Activity DirCallPath Services Program Call or Message Trigger is sent SHResponse request_tag=1 switch-dependent response_type_indicator=STL_POSITIVE_RESPONSE part of Server acknowledges. Call Redirection/ACD to ACD/Inbound Call Groups SA and SB have the Call Redirection feature set. The call from X is redirected from SA to SB. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of ACD Group SA. * sa1 is the connection ID of ACD Group SA. * SB is the party number of ACD Group SB. * BB is the party number of Agent BB. * bb1 is the connection ID of Agent BB. Activity Dir CallPath Services Program Call or Message Host sets up SH Response request_tag=1 acknowledges. response_type_indicator=STL_POSITIVE_RESPONSE Host sets up SH Response request_tag=2 acknowledges. response_type_indicator=STL_POSITIVE_RESPONSE DMS-100 CO S>H Call_Routed calling_party_info (party_number=X, switch asks connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) for route_reason=STL_DIRECT_ROUTE instructions call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN on new call to routed_to_party_list (party_number=SA, Group SA. connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Request_Instruction trigger_event=STL_TRIGGER_ON_CALL_ROUTED trigger_event_data calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_DIRECT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) Host redirects SH Response request_tag=3 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. DMS-100 CO switch provides closure. DMS-100 CO S>H Call_Routed calling_party_info (party_number=X, switch asks connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) for route_reason=STL_FORWARD_ROUTE instructions call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN on redirected routed_from_party_info (party_number=SA, call. connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB S>H Request_Instruction trigger_event=STL_TRIGGER_ON_CALL_ROUTED trigger_event_data= calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) party_type=STL_VOICE route_reason=STL_FORWARD_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) No SH Response request_tag=4 request. response_type_indicator=STL_POSITIVE_RESPONSE Call is routed S>H Call_Routed calling_party_info (party_number=X, to Agent BB. connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) routed_to_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) Agent BB S>H Call_Connected connecting_party_info (party_number=BB, answers. connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA,SB Call clears. S>H Disconnected disconnecting_party_info (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA,SB Call Redirection/ACD to Directory Number/Inbound Call Group SA has the Call Redirection feature set. The call from X is redirected from SA to B. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of ACD Group SA. * sa1 is the connection ID of ACD Group SA. * B is the party number of Party B. * b1 is the connection ID of Party B. Activity Dir CallPath Services Program Call or Message Host sets up SH Response request_tag=1 acknowledges. response_type_indicator=STL_POSITIVE_RESPONSE DMS-100 CO S>H Call_Routed calling_party_info (party_number=X, switch asks connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) for route_reason=STL_DIRECT_ROUTE instructions call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN on new call. routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Request_Instruction trigger_event=STL_TRIGGER_ON_CALL_ROUTED trigger_event_data calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_DIRECT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) Host redirects SH Response request_tag=2 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. DMS-100 CO switch provides closure. Call is routed S>H Call_Routed calling_party_info (party_number=X, to Agent B. connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_FORWARD_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=SA,B S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=SA,B Agent B S>H Call_Connected connecting_party_info (party_number=B, answers. connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA,B Call clears. S>H Disconnected disconnecting_party_info (party_number=B, connection_ID=b1, party_type=STL_AGENT_ID_TYPE) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA,B Queue Overflow (A) Caller X calls into ACD Group SA and is put on SA's queue. The call then overflows to SB's queue. Call is on both queues. Finally, Agent BB in Group SB gets the call. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of ACD Group SA. * sa1 is the connection ID of ACD Group SA. * SB is the party number of ACD Group SB. * sb1 is the connection ID of ACD Group SB. * BB is the party number of Agent BB. * bb1 is the connection ID of Agent BB. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Routed calling_party_info (party_number=X, queued for connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) ACD Group route_reason=STL_TO_QUEUE_ROUTE SA. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call S>H Call_Routed calling_party_info (party_number=X, overflows connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) to ACD route_reason=STL_TO_QUEUE_ROUTE Group SB. call_extension_indicator=STL_CALL_EXTENSION routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Call is S>H Call_Routed calling_party_info (party_number=X, released connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) from Group route_reason=STL_QUEUE_CLEANUP_ROUTE SA. call_extension_indicator=STL_CALL_EXTENSION routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Call is S>H Call_Routed calling_party_info (party_number=X, routed to connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) Agent BB. route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) routed_to_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SB S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SB Agent BB S>H Call_Connected connecting_party_info (party_number=BB, answers. connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SB Call S>H Disconnected disconnecting_party_info (party_number=BB, clears. connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SB Queue Overflow (B) Caller X calls into ACD Group SA and is put on SA's queue. The call then overflows to SB's queue. Call is on both queues. Finally, Agent AA in Group SA gets the call. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of ACD Group SA. * sa1 is the connection ID of ACD Group SA. * SB is the party number of ACD Group SB. * sb1 is the connection ID of ACD Group SB. * AA is the party number of Agent AA. * aa1 is the connection ID of Agent AA. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Routed calling_party_info (party_number=X, queued for connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) ACD Group route_reason=STL_TO_QUEUE_ROUTE SA. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call S>H Call_Routed calling_party_info (party_number=X, overflows connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) to ACD route_reason=STL_TO_QUEUE_ROUTE Group SB. call_extension_indicator=STL_CALL_EXTENSION routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Call is S>H Call_Routed calling_party_info (party_number=X, released connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) from Group route_reason=STL_QUEUE_CLEANUP_ROUTE SB. call_extension_indicator=STL_CALL_EXTENSION routed_from_party_info (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA,SB Call is S>H Call_Routed calling_party_info (party_number=X, routed to connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) Agent AA. route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA Agent AA S>H Call_Connected connecting_party_info (party_number=AA, answers. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Call S>H Disconnected disconnecting_party_info (party_number=AA, clears. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Ring Threshold Overflow Caller X dials SA. Call is put on queue of ACD Group SA, then is assigned to Agent AA. AA is doing followup on previous calls and forgot to press the NotReady key. Call rings past threshold. Call is re-queued and is assigned to Agent AB. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of ACD Group SA. * sa1 is the connection ID of ACD Group SA. * AA is the party number of Agent AA. * aa1 is the connection ID of Agent AA. * AB is the party number of Agent AB. * ab1 is the connection ID of Agent AB. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Routed calling_party_info (party_number=X, queued for connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) ACD Group route_reason=STL_TO_QUEUE_ROUTE SA. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call is S>H Call_Routed calling_party_info (party_number=X, routed to connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) Agent AA. route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) Ring threshold. Call is S>H Call_Routed calling_party_info (party_number=X, re-queued connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) for ACD route_reason=STL_RNA_FORWARD_ROUTE Group. call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=SA, connection_ID=sa2, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call is S>H Call_Routed calling_party_info (party_number=X, routed to connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) Agent AB. route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AB, connection_ID=ab1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AB, connection_ID=ab1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA Agent AB S>H Call_Connected connecting_party_info (party_number=AB, answers. connection_ID=ab1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Call S>H Disconnected disconnecting_party_info (party_number=AB, clears. connection_ID=ab1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Outbound Call Agent AA dials a customer from the screen. If the DMS-100 CO switch acknowledges with a RETURN-RESULT, we are assured that the agent has gone off-hook so we can generate the Call_Connected message for the agent. Following is the legend for this example: * AA is the party number of Agent AA. * aa1 is the connection ID of Agent aa. * X is the party number of the called party. * x1 is the connection ID of the called party. Activity Dir CallPath Services Program Call or Message Agent AA startsSH Response request_tag=1 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. The agent is S>H Call_Connected connecting_party_info (party_number=AA, off-hook. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE) call_extension_indicator=STL_NO_CALL_EXTENSION track_call_party=AA Call clears. S>H Disconnected disconnecting_party_info (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=AA Outbound Call to Intra-Switch Agent AA dials a Directory Number within the same customer group from the screen. If the DMS-100 CO switch acknowledges with a RETURN-RESULT, we are assured that the agent has gone off-hook so we can generate the Call_Connected message for the agent. Following is the legend for this example: * AA is the party number of Agent AA. * aa1 is the connection ID of Agent aa. * B is the party number of the called party. * b1 is the connection ID of the called party. Activity Dir CallPath Services Program Call or Message Agent AA SH Response request_tag=1 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. The agent is S>H Call_Connected connecting_party_info (party_number=AA, off-hook. connection_ID=aa1, party_type=STL_EXTENSION_PARTY_TYPE dialed_number=B) call_extension_indicator=STL_NO_CALL_EXTENSION track_call_party=AA Call is routed S>H Call_Alerting calling_party_info (party_number=AA, to B. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE) call_extension_indicator=STL_NO_CALL_EXTENSION alerting_party_list (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE dialed_number=B) track_call_party=AA,B S>H Call_Connected connecting_party_info (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) call_extension_indicator=STL_NO_CALL_EXTENSION existing_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE) track_call_party=AA,B Call clears. S>H Disconnected disconnecting_party_info (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) other_disconnected_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE) track_call_party=AA,B Blind Transfer/Host Initiated X dials SA. Call is queued for ACD Group SA, then is assigned to Agent AA. Agent AA then blind transfers the call to ACD Group SB via the terminal. Call is queued, then assigned to Agent BB. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of ACD Group SA. * sa1 is the connection ID of ACD Group SA. * AA is the party number of Agent AA. * aa1 is the connection ID of Agent AA. * aa2 is the connection ID of Agent AA. * SB is the party number of ACD Group SB. * sb1 is the connection ID of ACD Group SB. * BB is the party number of Agent BB. * bb1 is the connection ID of Agent BB. Activity Dir CallPath Services Program Call or Message Call is queued S>H Call_Routed calling_party_info (party_number=X, for ACD Group connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) SA. route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call is routed S>H Call_Routed calling_party_info (party_number=X, to Agent AA. connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, party_group=SA) track_call_party=SA S>H Call_Connected connecting_party_info (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Agent AA calls SH Response request_tag=1 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. Agent AA SH Response request_tag=2 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. Transfer call S>H Call_Held holding_party_info (party_number=AA, is queued for connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, Group SB. party_group=SA) holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=aa2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA S>H Call_Routed calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, party_group=SA) route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Agent AA drops S>H Call_Transferred transferring_party_ID_1 out. (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, party_group=SA) transferring_party_ID_2 (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, party_group=SA) track_call_party=SA,SB Call is routed S>H Call_Routed calling_party_info (party_number=X, to Agent BB. connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_NO_CALL_EXTENSION routed_from_party_info (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) routed_to_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_NO_CALL_EXTENSION alerting_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Agent BB S>H Call_Connected connecting_party_info (party_number=BB, answers. connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA,SB Call clears. S>H Disconnected disconnecting_party_info (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA,SB Blind Transfer/Directory Number to Directory Number Caller X dials B. Call is offered to B, then answered by B. B does a blind transfer to C. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * B is the party number of Party B. * b1 is the connection ID of Party B. * b2 is the connection ID of Party B. * C is the party number of Party C. * c1 is the connection ID of Party C. * BB is the party number of Agent BB. * bb1 is the connection ID of Agent BB. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Alerting calling_party_info (party_number=X, routed connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) to B. call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B S>H Call_Connected connecting_party_info (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B B dials S>H Call_Held holding_party_info (party_number=B, C. connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=b2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B S>H Call_Alerting calling_party_info (party_number=B, connection_ID=b2, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION alerting_party_list (party_number=C, connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B,C S>H Call_Transferred transferring_party_ID_1 (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) transferring_party_ID_2 (party_number=B, connection_ID=b2, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B,C Agent C S>H Call_Connected connecting_party_info (party_number=C, answers connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) the call_type=STL_VOICE call. call_extension_indicator=STL_NO_CALL_EXTENSION existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B,C Call S>H Disconnected disconnecting_party_info (party_number=C, clears. connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B,C Screened Transfer/Directory Number to Directory Number Caller X dials B. Call is offered to B, then answered by B. B calls C, consults with C, then transfers. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * B is the party number of Party B. * b1 is the connection ID of Party B. * b2 is the connection ID of Party B. * C is the party number of Party C. * c1 is the connection ID of Party C. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Alerting calling_party_info (party_number=X, routed connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) to B. call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B S>H Call_Connected connecting_party_info (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B B dials S>H Call_Held holding_party_info (party_number=B, C. connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=b2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B S>H Call_Alerting calling_party_info (party_number=B, connection_ID=b2, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION alerting_party_list (party_number=C, connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B,C S>H Call_Connected connecting_party_info (party_number=C, connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=B, connection_ID=b2, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B,C S>H Call_Transferred transferring_party_ID_1 (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) transferring_party_ID_2 (party_number=B, connection_ID=b2, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B,C Call S>H Disconnected disconnecting_party_info (party_number=C, clears. connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B,C Consultation/Directory Number to Directory Number Caller X dials B. Call is offered to B, then answered by B. B calls C, consults with C, then returns to X. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * B is the party number of Party B. * b1 is the connection ID of Party B. * b2 is the connection ID of Party B. * C is the party number of Party C. * c1 is the connection ID of Party C. Activity Dir CallPath Services Program Call or Message Call is S>H Call_Alerting calling_party_info (party_number=X, routed connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) to B. call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B S>H Call_Connected connecting_party_info (party_number=B, connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B B dials S>H Call_Held holding_party_info (party_number=B, C. connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=b2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B S>H Call_Alerting calling_party_info (party_number=B, connection_ID=b2, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION alerting_party_list (party_number=C, connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B,C S>H Call_Connected connecting_party_info (party_number=C, connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) call_type=STL_VOICE call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=B, connection_ID=b2, party_type=STL_EXTENSION_PARTY_TYPE) track_call_party=B,C S>H Disconnected disconnecting_party_info (party_number=C, connection_ID=c1, party_type=STL_EXTENSION_PARTY_TYPE) other_disconnected_party_list (party_number=B, connection_ID=b2, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B,C Call S>H Disconnected disconnecting_party_info (party_number=B, clears. connection_ID=b1, party_type=STL_EXTENSION_PARTY_TYPE) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=B Screened Transfer/Host Initiated X dials SA. Call is queued for ACD Group SA, then is assigned to Agent AA. Agent AA then calls ACD Group SB via the terminal. Call is queued, then assigned to Agent BB. AA and BB talk, then AA transfers the call via the terminal. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of Party SA. * sa1 is the connection ID of Party SA. * BB is the party number of Party BB. * bb1 is the connection ID of Party BB. * AA is the party number of Party AA. * aa1 is the connection ID of Party AA. * aa2 is the connection ID of Party AA. Activity Dir CallPath Services Program Call or Message Call is queued S>H Call_Routed calling_party_info (party_number=X, for ACD Group connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) SA. route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Call is routed S>H Call_Routed calling_party_info (party_number=X, to agent. connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA Agent answers. SH Response request_tag=1 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. Call is queued S>H Call_Held holding_party_info (party_number=AA, for Group SB. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=aa2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA S>H Call_Routed calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Call is routed S>H Call_Routed calling_party_info (party_number=AA, to Agent BB. connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_NO_CALL_EXTENSION routed_from_party_info (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SB, party_group=SB) routed_to_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Call_Alerting calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION alerting_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Agent answers. S>H Call_Connected connecting_party_info (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Agent B SH Response request_tag=2 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. DMS-100 CO S>H Call_Transferred transferring_party_ID_1 switch (party_number=AA, connection_ID=aa1, provides party_type=STL_AGENT_ID_TYPE, original_group=SA, closure for party_group=SA) transferring_party_ID_2 SA. (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA,SB Call clears. S>H Disconnected disconnecting_party_info (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SB Consultation/Host Initiated X dials SA. Call is queued for ACD Group SA, then is assigned to Agent AA. Agent AA initiates a consultation call to Group SB via the terminal. Call is queued, then assigned to agent BB. AA and BB talk, then AA resumes the original call. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of Party SA. * sa1 is the connection ID of Party SA. * SB is the party number of Party SB. * sb1 is the connection ID of Party SB. * BB is the party number of Party BB. * bb1 is the connection ID of Party BB. * AA is the party number of Party AA. * aa1 is the connection ID of Party AA. * aa2 is the connection ID of Party AA. Activity Dir CallPath Services Program Call or Message Call is queued S>H Call_Routed calling_party_info (party_number=X, for ACD Group connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) SA. route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call is routed S>H Call_Routed calling_party_info (party_number=X, to agent. connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA Agent answers S>H Call_Connected connecting_party_info (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Agent AA calls SH Response request_tag=1 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. Call is queued S>H Call_Held holding_party_info (party_number=AA, for Group SB. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=aa2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA S>H Call_Routed calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Call is routed S>H Call_Routed calling_party_info (party_number=AA, to Agent BB. connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_NO_CALL_EXTENSION routed_from_party_info (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SB, party_group=SB) routed_to_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Call_Alerting calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION alerting_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) track_call_party=SA,SB Agent answers S>H Call_Connected connecting_party_info (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA,SB Agent AA goes SH Response request_tag=2 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges DMS-100 CO S>H Disconnected disconnecting_party_info switch (party_number=AA, connection_ID=aa2, provides party_type=STL_AGENT_ID_TYPE, original_group=SA, closure for SB party_group=SA) other_disconnected_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Original call S>H Call_Connected connecting_party_info (party_number=AA, reconnected connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Call clears S>H Disconnected disconnecting_party_info (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Conference/Host Initiated (A) X dials SA. Call is queued for ACD Group SA, then is assigned to Agent AA. Agent AA initiates a consultation call to Group SB via the terminal. Call is queued, then assigned to Agent BB. AA and BB talk, then AA conferences X back in. AA drops BB and goes back to X. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of Party SA. * sa1 is the connection ID of Party SA. * SB is the party number of Party SB. * sb1 is the connection ID of Party SB. * BB is the party number of Party BB. * bb1 is the connection ID of Party BB. * AA is the party number of Party AA. * aa1 is the connection ID of Party AA. * aa2 is the connection ID of Party AA. Activity Dir CallPath Services Program Call or Message Call is queued S>H Call_Routed calling_party_info (party_number=X, for ACD Group connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) SA. route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call is routed S>H Call_Routed calling_party_info (party_number=X, to Agent AA. connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Connected connecting_party_info (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Agent AA calls SH Response request_tag=1 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. Call is queued S>H Call_Held holding_party_info (party_number=AA, for Group SB. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=aa2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA S>H Call_Routed calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, party_group=SA) route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Call is routed S>H Call_Routed calling_party_info (party_number=AA, to Agent BB. connection_ID=aa2, party_type=STL_AGENT_ID_TYPE original_group=SA, party_group=SA) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_NO_CALL_EXTENSION routed_from_party_info (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SB, party_group=SB) routed_to_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Call_Alerting calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION alerting_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Agent BB S>H Call_Connected connecting_party_info (party_number=BB, answers. connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA,SB Agent AA SH Response request_tag=2 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. Agent AA drops SH Response request_tag=3 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. DMS-100 CO S>H Disconnected disconnecting_party_info switch (party_number=BB, connection_ID=bb1, provides party_type=STL_AGENT_ID_TYPE, original_group=SB, closure for party_group=SB) track_call_party=SA SB. Call clears. S>H Disconnected disconnecting_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Conference/Host Initiated (B) X dials SA. Call is queued for ACD Group SA, then is assigned to Agent AA. Agent AA initiates a consultation call to Group SB via the terminal. Call is queued, then assigned to Agent BB. AA and BB talk, then AA conferences X back in. AA then drops out. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of Party SA. * sa1 is the connection ID of Party SA. * SB is the party number of Party SB. * sb1 is the connection ID of Party SB. * BB is the party number of Party BB. * bb1 is the connection ID of Party BB. * AA is the party number of Party AA. * aa1 is the connection ID of Party AA. * aa2 is the connection ID of Party AA. Activity Dir CallPath Services Program Call or Message Call is queued S>H Call_Routed calling_party_info (party_number=X, for ACD Group connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) SA. route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call is routed S>H Call_Routed calling_party_info (party_number=X, to Agent AA. connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Connected connecting_party_info (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Agent AA calls SH Response request_tag=1 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. Call is queued S>H Call_Held holding_party_info (party_number=AA, for Group SB. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=aa2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA S>H Call_Routed calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, party_group=SA) route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Call is routed S>H Call_Routed calling_party_info (party_number=AA, to Agent BB. connection_ID=aa2, party_type=STL_AGENT_ID_TYPE original_group=SA, party_group=SA) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_NO_CALL_EXTENSION routed_from_party_info (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SB, party_group=SB) routed_to_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Call_Alerting calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION alerting_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB Agent BB S>H Call_Connected connecting_party_info (party_number=BB, answers. connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA,SB Agent AA SH Response request_tag=2 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. Agent AA drops SH Response request_tag=3 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. DMS-100 CO S>H Disconnected disconnecting_party_info switch (party_number=AA, connection_ID=aa2, provides party_type=STL_AGENT_ID_TYPE, original_group=SA, closure for party_group=SA) track_call_party=SA SA. Call clears. S>H Disconnected disconnecting_party_info (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SB, party_group=SB) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA --------------------------------------------------------------------------- Program Flows for Version 1 Specific Features The following program flow is specific to CallPath Server for OS/2 and CallPath Server for AIX: * Conference/Host Initiated (C) Conference/Host Initiated (C) X dials SA. Call is queued for ACD Group SA, then is assigned to Agent AA. Agent AA initiates a consultation call to Group SB via the terminal. Call is queued, then assigned to Agent BB. AA and BB talk, then AA conferences X back in. AA drops BB and goes back to X. Following is the legend for this example: * X is the party number of the caller. * x1 is the connection ID of the caller. * SA is the party number of Party SA. * sa1 is the connection ID of Party SA. * SB is the party number of Party SB. * sb1 is the connection ID of Party SB. * BB is the party number of Party BB. * bb1 is the connection ID of Party BB. * AA is the party number of Party AA. * aa1 is the connection ID of Party AA. * aa2 is the connection ID of Party AA. Activity Dir CallPath Services Program Call or Message Call is queued S>H Call_Routed version_number=STL_VERSION_1 for ACD Group calling_party_info (party_number=X, connection_ID=x1, SA. party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_to_party_list (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) track_call_party=SA Call is routed S>H Call_Routed version_number=STL_VERSION_1 to Agent AA. calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN routed_from_party_info (party_number=SA, connection_ID=sa1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SA) routed_to_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Alerting version_number=STL_VERSION_1 calling_party_info (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN alerting_party_list (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA S>H Call_Connected version_number=STL_VERSION_1 connecting_party_info (party_number=AA, connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION_UNKNOWN existing_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA Agent AA calls SH Response request_tag=1 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. Call is queued S>H Call_Held holding_party_info (party_number=AA, for Group SB. connection_ID=aa1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) holding_party_calling=STL_CALLS_PERMITTED holding_party_ID_2=aa2 holding_party_callback=STL_SWITCH_DEFAULT_CALLBACK held_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA S>H Call_Routed version_number=STL_VERSION_1 calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, party_group=SA) route_reason=STL_TO_QUEUE_ROUTE call_extension_indicator=STL_CALL_EXTENSION routed_to_party_list (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB, program_data=1234 Call is routed S>H Call_Routed version_number=STL_VERSION_1 to Agent BB. calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE original_group=SA, party_group=SA) route_reason=STL_FROM_PILOT_ROUTE call_extension_indicator=STL_NO_CALL_EXTENSION routed_from_party_info (party_number=SB, connection_ID=sb1, party_type=STL_PILOT_PARTY_TYPE, original_group=SB, party_group=SB) routed_to_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB, program_data=1234 Call_Alerting version_number=STL_VERSION_1 calling_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) call_extension_indicator=STL_CALL_EXTENSION alerting_party_list (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) track_call_party=SA,SB, program_data=1234 Agent BB S>H Call_Connected version_number=STL_VERSION_1 answers. connecting_party_info (party_number=BB, connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SB) call_extension_indicator=STL_CALL_EXTENSION existing_party_list (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) track_call_party=SA,SB, program_data=1234 Agent AA SH Response version_number=STL_VERSION_1 request_tag=2 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. Agent AA drops SH Response version_number=STL_VERSION_1 request_tag=3 switch response_type_indicator=STL_POSITIVE_RESPONSE acknowledges. DMS-100 CO S>H Disconnected version_number=STL_VERSION_1 switch disconnecting_party_info (party_number=BB, provides connection_ID=bb1, party_type=STL_AGENT_ID_TYPE, closure for original_group=SB, party_group=SB) SB. track_call_party=SA, remaining_party_list (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE), (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) Call clears. S>H Disconnected version_number=STL_VERSION_1 disconnecting_party_info (party_number=AA, connection_ID=aa2, party_type=STL_AGENT_ID_TYPE, original_group=SA, party_group=SA) other_disconnected_party_list (party_number=X, connection_ID=x1, party_type=STL_UNKNOWN_PARTY_TYPE) track_call_party=SA --------------------------------------------------------------------------- Appendix A. Restart of Switch Connection Following Link Failure When the link connection to the switch fails, such as when the plug becomes loose or the modem fails, the link to the switch is not automatically reconnected once the failure is remedied. However, you can reconfigure the program to enable automatic reconnection or you can manually reconnect each time there is a failure. --------------------------------------------------------------------------- Automatic Restart of Switch Connection Use the following procedure to enable the Server to automatically reestablish the connection to the switch once a link failure condition is remedied: Using SwitchServer/2 1. Insert the Communications Manager API Support diskette shipped with the IBM Communications Manager/2 Application Programmers Guide (Order document number SC31-7012 through your IBM Service Representative.) 2. Copy the file reactx25.exe from the disk to the directory where the CallPath program resides. 3. Add the following statement to the end of the startup.cmd file: start reactx25 4. Start the product as usual with the rcpss2 command which will implement the new startup.cmd file. Using CallPath Server for OS/2 1. Insert the Communications Manager/s API Support diskette shipped with the IBM Communications Manager/2 Application Programmers Guide (Order document number SC31-7012 through your IBM Service Representative.) 2. Copy the file reactx25.exe from the disk into the directory where the CallPath program resides. 3. Add the following line to the end of the startup.cmd file: start reactx25 4. In the CallPath Server/2 configuration, configure the switch for restart on failure. Using CallPath Server for AIX 1. Install PTF 403442 for AIX V3.2 X.25. (This can be ordered through your IBM Service Representative.) 2. Start the communications configuration program by entering the smit command. 3. Navigate through the configuration menus as follows: + Select Devices + Select Communications + Select X.25 Co-Processor/2... + Select Adapter + Select Manage Device Driver + Select Change/Show Characteristics + Select Change/Show General Parameters + Select the appropriate adapter or adapters used by the CallPath system. For each adapter selected, set Automatic Link Restart to enabled. 4. In the CallPath Server/6000 configuration, configure the switch for restart on failure. Note: For CallPath Server for MS Windows NT, automatic restart of the switch connection is not yet available. --------------------------------------------------------------------------- Manual Restart of Switch Connection Use the following procedure to manually restore the link connection: Using SwitchServer/2 1. Using the Communications Subsystem Management Facility, stop and then restart the failed link. 2. Once the link recovers and is in the connected state, restart the switch link from the CallPath user interface. Using CallPath Server for OS/2 1. Using the Link Management Facility, stop and then restart the failed link. 2. Once the link recovers and is in the connected state, restart the switch link from the CallPath user interface. Using CallPath Server for AIX 1. Using the link management facility, xmanage, stop and then restart the failed link. 2. Once the link recovers and is in the connected state, restart the switch link from the CallPath user interface. Using CallPath Server for MS Windows NT 1. The link is established on demand. 2. Restart the switch connection if it fails to establish. If the error is due to a link failure, try rebooting the system. When the link fails, such as when the plug becomes loose or the modem fails, several comment lines and a time stamp are appended to the file linkdbg.log in the switchdm subdirectory of the csasrvr directory (or in the CPSS2 directory for CallPath SwitchServer/2). Diagnostic and cause codes are provided by the X.25 API as they become available and are collected in a flat ASCII text file. If link failures are excessive, the contents of this file may be helpful in analyzing the X.25 API or line problems. The user is responsible for monitoring the size of this file and periodically removing old entries. --------------------------------------------------------------------------- Appendix B. Installing and Configuring the X.25 Interface Adapter Using AIX Version 4.1 If you are using AIX Version 4.1, some installation and configuration parameters are different. It is important that you follow instructions for the correct version of AIX you are running. This appendix applies only to AIX Version 4.1. --------------------------------------------------------------------------- Overview Following is an overview of the tasks required for installing and configuring the X.25 Interface Co-Processor/2 adapter(s) for communications between CallPath Server for AIX and the DMS-100 CO when using AIX Version 4.1. Note: If AIX Version 4.1 or higher is used with an X.25 interface co-processor adapter card, also order AIX X.25 and AIXLINK/X.25 Version 1.1 to support the card. * Installing one or more X.25 Interface Co-Processor/2 adapters * Installing the DMS-100 CO-dependent code feature * Identifying the X.25 Interface Co-Processor/2 adapter to AIX * Configuring the Device Driver for each X.25 Interface Co-Processor/2 adapter by doing the following: o Adding the X.25 Device Driver o Adding and configuring an X.25 port o Configuring the X.25 general parameters o Configuring the X.25 packet parameters o Configuring the X.25 frame parameters * Starting X.25 communication links between CallPath Server for AIX and DMS-100 CO * Configuring the DMS-100 CO Switch Connection(s) * Configuring the DMS-100 CO connection(s) in CallPath Server for AIX * Configuring the DMS-100 CO connection(s) in SMIT These tasks are described in more detail in the following sections. Installing X.25 Interface Co-Processor/2 Adapters Installing One or More X.25 Interface Co-Processor/2 Adapters X.25 Interface Co-Processor/2 adapters provide the communication channel between the DMS-100 CO and the Server. Install the X.25 Co-Processor/2 adapter(s) according to the instructions in X.25 Interface Co-Processor/2 Guide to Operations supplied with the adapter. Continue with "Installing DMS-100 CO Switch-Dependent Code Feature". Installing DMS-100 CO Switch-Dependent Code Feature DMS-100 CO switch-dependent code feature is provided in installp format, the AIX-standard automatic installation format. (Refer to AIX Version 3.2: Commands Reference for more information about installp.) To install the DMS-100 CO-dependent code feature, do the following: 1. Log on as root. 2. If the DMS-100 CO switch-dependent code feature is already installed, make sure it is committed by entering the following command: installp -c csadms 3. Enter the following command: installp -aXF -d/dev/rfd0 all Recommit the Server by entering the following command: installp -c csasrvr 4. Respond to the prompts for inserting the DMS-100 CO switch-dependent code feature installation diskettes. 5. Set up security (see the CallPath Server Planning, Installation, and Problem Determination Guide for additional information on setting up security). 6. Give write permission to the following: chmod g+w /usr/lpp/csasrvr/switchsl/dmslogon.* 7. Give read and execute permission to the following: chmod -R g+rx /usr/lpp/csasrvr/switchdm/* Continue with "Identifying the X.25 Interface Co-Processor/2 Adapter". Identifying the X.25 Interface Co-Processor/2 Adapter Identifying the X.25 Interface Co-Processor/2 Adapter to AIX To identify the installed X.25 Interface Co-Processor/2 adapter to the AIX operating system, do the following: 1. Start the AIX RISC System/6000. 2. Log on as root. 3. Enter the following command at a system prompt to verify that the X.25 Interface Co-Processor/2 adapter is installed and available to the RISC System/6000 server: lsdev -C -H º grep ampx Note: ampx is the physical location of the adapter prior to setting up the X.25 communications. If an adapter is not listed, it is not recognized by AIX. The adapter is either bad or installed incorrectly. 4. Enter the following command to verify that the X.25 LPP installation has been performed: lplpp -h sx25 5. If there are no committed X.25 software items listed, contact your AIX administrator to install the system-supplied X.25 support. Continue with "Configuring the Device Driver for Each X.25 Interface Co-Processor/2 Adapter". Configuring the Device Driver for Each X.25 Interface Co-Processor/2 Adapter Repeat the following tasks for each X.25 Interface Co-Processor/2 adapter installed in the CallPath Server for AIX computer: * Adding the X.25 device driver * Associating each X.25 Interface Co-Processor/2 adapter with its device name * Configuring the device driver * Configuring the X.25 packet parameters * Configuring the X.25 frame parameters These procedures are described next. Adding the X.25 Device Driver (Co-Processor/2) To add the X.25 card device driver, do the following after starting SMIT: 1. Select Devices. 2. Select Communication. 3. Select X.25 Co-Processor/2 or Multiport Adapter. 4. Select Adapter. 5. Select Manage Device Drivers for X.25 Co-Processor/2 or Multiport/2 Adapters. 6. Select Manage X.25 LPP Device Driver. 7. Select Add a Device Driver. 8. If more than one device driver is displayed, select the one you want from the list box. 9. Select Do. 10. Select Done. 11. Select Cancel. Continue with "Adding and Configuring an X.25 Port". Adding the X.25 Device Driver (Co-Processor/1) To add the X.25 card device driver, do the following after starting SMIT: 1. Select Devices. 2. Select Communication. 3. Select X.25 Co-Processor/1 for ISA. 4. Select Adapter. 1. Add an X.25 adapter by following the instructions for IRQ and BASE 10 address configurations. 2. Configure a defined X.25 adapter. 5. Select Manage Device Drivers for X.25 Co-Processor/1 or Multiport/2 Adapters. 6. Select Manage X.25 LPP Device Driver. 7. Select Add a Device Driver. 8. If more than one device driver is displayed, select the one you want from the list box. 9. Select Do. 10. Select Done. 11. Select Cancel. Note: Please refer to the Nortel document, AM and IPE Module Diagnostic and Maintenance Guide 553-3211-50. Continue with "Adding and Configuring an X.25 Port". Adding and Configuring an X.25 Port After configuring the device driver do the following to add or configure an X.25 port: 1. Navigate to Manage X.25 LPP Device Driver within SMIT. 2. Select Manage X.25 Ports. 3. Select Add Port. 4. If more than one adapter drive is displayed, select the one you want from the list box. 5. Change the contents of the displayed fields to reflect the values shown in Figure 9: Figure 9. Adding an X.25 Port Screen +--------------------------------------------------------------------------------+ º Add an X.25 Port º º º ºType or select values in entry fields. º ºPress Enter AFTER making all desired changes. º º º º [Entry Fields] º º Parent Adapter Driver [twd0] º º PORT number (always 0 for X.25 RIC cards) [] º º Local network user address (NUA) [] º º (The server's local address that will be º º recognized by the DMS-100 CO.) º º º º Network identifier [other public] º º Country prefix [] º º PVC - lowest logical channel number [1] º º PVC - number of logical channels [0] º º Incoming SVC - lowest logical channel number [1] º º Incoming SVC - number of logical channels [0] º º Two-way SVC - lowest logical channel number [1] º º Two-way SVC - number of logical channels [1] º º Outgoing SVC - lowest logical channel number [1] º º Outgoing SVC - number of logical channels [0] º º º º º º º º º ºF1=Help F2=Refresh F3=Cancel F4=List º ºEsc+5=Reset Esc+6=Command Esc+7=Edit Esc+8=Image º ºEsc+9=Shell Esc+0=Exit Enter=Do º +--------------------------------------------------------------------------------+ 6. Select Do. 7. Select Done. 8. Select Cancel. Continue with "Configuring the X.25 General Parameters". Configuring the X.25 General Parameters To configure the X.25 general parameters, do the following: 1. Navigate to Manage x.25 LPP Device Driver within SMIT. 2. Select Manage X.25 Ports. 3. Select Change/Show Characteristics of a Port. 4. Select Change/Show X.25 General Parameters. 5. If more than one adapter driver is displayed, select the one you want from the list box. 6. Verify the following parameters: General Parameters Port name sx25a0 Local Network User Address (NUA) Local address Calling address in call request/accept packet allow Enable DLPI interface ONLY no PVC - lowest logical channel number 1 PVC - number of logical channels 0 Incoming SVC - lowest logical channel number 1 Incoming SVC - number of logical channels 0 Two-way SVC - lowest logical channel number 1 Two-way SVC - number of logical channels 1 Outgoing SVC - lowest logical channel number 1 Outgoing SVC - number of logical channels 0 X.23 Configuration Use X.23 XID exchange no X.32 XID identity X.32 XID signature Dial-Up Configuration Connection type Direct/Leased V25bis call establishment method Addressed V25bis DTE call direction Outcall Phone number or address to call Maximum connection delay 10 Enable/disable DSR polling disable DSR polling timeout 30 7. Select Do. 8. Select Done. 9. Select Cancel. Continue with "Configuring the X.25 Packet Parameters". Configuring the X.25 Packet Parameters To configure the X.25 packet parameters, do the following: 1. Navigate to Manage X.25 LPP Device Driver within SMIT. 2. Select Manage X.25 Ports. 3. Select Change/Show Characteristics of a Port. 4. Select Change/Show X.25 Packet Parameters. 5. If more than one adapter driver is displayed, select the one you want from the list box. 6. Verify the following parameters: Packet Parameters Port name sx25a0 CCITT support 1980 or 1984 Packet modulo 8 Type of line DTE Packet layer DTE/DCE line alteration policy per OSI 8208 Disconnect on inactivity No Registration No A-bit off Network Intermediate Data Unit (NIDU) size 200 Default attributes for SVCs Default receive packet size 128 Default transmit packet size 128 Default receive packet window 7 or 2 (must match switch) Default transmit packet window 7 or 2 (must match switch) Default receive throughput class 19200 Default transmit throughput class 19200 Maximum Negotiable Attributes for SVCs Maximum receive packet size 128 Maximum transmit packet size 128 Maximum receive packet window 7 or 2 (must match switch) Maximum transmit packet window 7 or 2 (must match switch) IS08208-Defined Timers T20 restart timer 180 T22 call timer 200 T22 reset timer 180 T23 clear timer 180 T24 window status transmission timer 0 T25 window rotation timer 0 T26 interrupt timer 180 T27 reject response timer 60 T28 registration timer 300 R20 retransmission count restart timer 1 R22 retransmission count reset timer 1 R23 retransmission count clear timer 1 R25 retransmission count window rotation timer 0 R27 retransmission count reject timer 0 R28 retransmission count registration timer 1 Packet-Level Features Fast select mode allow D-bit allow Reverse charging allow Maximum facility field length 109 Interrupt data size 32 7. Select Do. 8. Select Done. 9. Select Cancel. Continue with "Configuring the X.25 Frame Parameters". Configuring the X.25 Frame Parameters To configure the frame parameters, do the following: 1. Navigate to Manage X.25 LPP Device Driver within SMIT. 2. Select Manage X.25 Ports. 3. Select Change/Show Characteristics of a Port. 4. Select Change/Show X.25 Frame Parameters. 5. If more than one adapter driver is displayed, select the one you want from the list box. 6. Verify the following parameters: Frame Parameters Port name sx25a0 T1 retransmission timer 60-255 Each unit represents 50 milliseconds. The T1 timer must be equal to, or greater than, the switch value translated to 50 millisecond units. To translate switch time, multiply the switch time (in seconds) by 20. For example, if the switch uses 4 seconds, use a value of T1=80, or higher. T2 acknowledgement timer 1 T3 idle timer 60 T4 activity timer 30 N1 maximum frame size 5003 N2 retransmission count 10 Frame modulo 8 Frame window size 7 Allow automatic DTE/DCE detection yes-automatic Connection mode active-sendSABM 7. Select Do. 8. Select Done. 9. Select Cancel. If you have more than one X.25 Interface Co-Processor/2 adapter to install, return to "Configuring the Device Driver for Each X.25 Interface Co-Processor/2 Adapter". Otherwise, continue with "Starting X.25 Communication Links". Adding the COMIO Interface To add the COMIO interface, do the following after starting SMIT: 1. Select Devices. 2. Select Communication. 3. Select X.25 Co-Processor/2 or Multiport Adapter. 4. Select Adapter. 5. Select Manage Device Drivers for X.25 Co-Processor/2 or Multiport/2 Adapters. 6. Select Manage X.25 LPP Device Driver. 7. Select Manage X.25 Ports. 8. Select Add COMIO Interface to Port. 9. If more than one adapter drive is displayed, select the one you want from the list box. 10. Select Done. 11. Select Cancel. Starting X.25 Communication Links Starting X.25 Communication Links between CallPath Server for AIX and the DMS-100 CO Switch Before a session with the switch can be started, the link to the switch must be connected. The link you want to start must correspond to the switch session to be run. After installing and configuring the X.25 Co-Processor/2 adapter, as the root user, enter the following to start the communication links: x25cnct device_name where device_name is x25s0, x25s1, x25s2, or x25s3. The x25cnct module resides in the /usr/lpp/csasrvr/switchdm directory. Once the links have been started, if the RISC System/6000 is restarted, the links are restarted automatically by the system. A link can be started by root without restarting the system by entering the x25cnct command. The output resulting from the command is found in the file x25s # lnk.log, where # is 0, 1, 2 or 3. To determine if the links are connected, execute the following command from directory /usr/bin: x25mon -f -n sx25 # where #; is 0, 1, 2 or 3. Configuring the DMS-100 CO Switch Connection(s) Before CallPath Server for AIX can communicate with the DMS-100 CO, the switch connection(s) must be configured by recording the following information in CallPath Server for AIX: Switch description The name to be used in the CallPath Server Management Facility for the DMS-100 CO. Auto-start Whether CallPath Server for AIX should start communications with the DMS-100 CO automatically when the CallPath Server for AIX subsystem is started. Restart on failure Whether CallPath Server for AIX should restart communications with the DMS-100 CO automatically after a fatal error has terminated communications between CallPath Server for AIX and the switch. Switch parameters The following information is required from Table 3: o Netnode ID o Application ID o Service ID o Business Group ID o BCS o Password o Slot number o Local address o Remote Address You can obtain the first six switch log-on parameters from your switch administrator. The last three values correspond to the device name (slot number), local card address (network user address, or NUA), and remote card address (the switch's NUA as provided by the switch administrator) as defined when installing and configuring the X.25 adapter. Separate procedures follow for configuring the DMS-100 CO connection using the CallPath Server Management Facility and using SMIT. Configuring the DMS-100 CO Connection in CallPath Server for AIX To configure the DMS-100 CO in CallPath Server for AIX for a local connection, do the following: 1. Start the CallPath Server Management Facility. 2. Display the CallPath Server Management Facility Set Switch Configuration window in one of the following ways: o From the CallPath Server Management Facility menu bar: 1. Select the Configuration menu. 2. Select the Switch Connection menu option. 3. Select On file. 4. Select the switch from the scrollable list box. o From the switch icon: 1. Click on the Switch icon using the mouse menu button. 2. Select the Configuration option. 3. Type the description for the switch in the "Switch description" field. 4. Select Auto-start if you want DMS-100 CO to start automatically when CallPath Server for AIX starts. 5. Select Restart on failure if you want DMS-100 CO to restart when there is a failure in communications between it and CallPath Server for AIX. 6. Click on the Switch type field. 7. Click on DMS-100. 8. Click on one of the following: o OK to save the configuration information and return to the CallPath Server Management Facility after setting the DMS-100 CO logon parameters o Apply to save the configuration information and return to the Set Switch Configuration window after setting the DMS-100 CO logon parameters The Enter Switch Configuration Data window shown in Figure 10 is displayed. Note: If you are using SMIT instead of the CallPath Server Management Facility, the Enter Switch Configuration window is not available. See "Configuring the Nortel DMS-100 CO Connection in SMIT" for additional CallPath Server for AIX-to-DMS-100 CO connection instructions. Figure 10. Enter Switch Configuration Data Window [Image] View figure. 9. Complete the following fields: Network Node ID Identifies this DMS-100 CO switch. The range of values is 0 to 32767. Service ID Identifies the service profile for this DMS-100 CO switch. The range of values is 0 to 255. BCS Version (level) of service that the DMS-100 CO switch and CallPath Server for AIX are operating under. Acceptable values are in the range of 33-36. Notes: 1. If the switch load is more than two levels higher than the BCS level used in the logon parameters, the switch will not accept it. For example, if the switch is set at level 36 and the BCS logon parameter is set at level 33, the switch will reject the logon. 2. The Level 36 function, DV_SET_FEATURE (log on, log off, ready, and not ready), is supported. Further, the switch event messages indicating the status of the agent are flowed to the application. The BCS level must be set to 36 to implement this request. 3. Multiple-link capability using BCS level 35 and 36 is not supported. 4. The BCS level must be set to 35 or 36 to implement the Query_ACD_Information request. Business Group ID Identifies your switch within the public telephone network. Your switch administrator has the value assigned to you by the telephone company. Application ID Identifier for the host application program to be run. The range of values is 1 to 32,767. Local Address Link address for the RISC System/6000 as registered with the DMS-100 CO switch. Your switch administrator has the value assigned to CallPath Server for AIX. Remote Address The address by which the DMS-100 CO switch identifies itself. Your switch administrator has this value. Slot number Device name assigned to the X.25 slot used. Acceptable values are x25s0, x25s1, x25s2, x25s3, x25s4, x25s5, x25s6, and x25s7. Enter Password The password assigned to the specified business group for this DMS-100 CO switch. Your switch administrator has the 1-to-8 character password. Use uppercase for all alphabetic characters in the password. Note: Once you enter the DMS-100 CO switch password, there is no need to change it unless the switch administrator has changed it for the DMS-100 CO switch or if the password has never been entered. Verify Password The current password again to confirm that you typed it correctly in the "Enter Password" field. Leave blank if "Enter Password" field is blank. 10. Click on OK. Either the CallPath Server Management Facility or the Set Switch Configuration window is displayed, depending on your selection in Step 8. 11. Repeat this procedure for each switch connection starting with Step 2. Configuring the Nortel DMS-100 CO Connection in SMIT To configure the DMS-100 CO in SMIT for a local connection, do the following: 1. Start SMIT. 2. Select Communications Applications and Services 3. Select CallPath Server/6000 4. Select CallPath Server/6000 Configuration 5. Select Set Switch Connection Configuration 6. Select Set Switch Connection Configuration 7. Select the switch connection (SWITCHnn, where nn is a valid 2-digit switch connection) and type (DMS) to configure. Some larger servers may allow valid slot numbers through x25s17. 8. Type the description for the switch in the "Switch description" field. 9. Select Auto-start if you want DMS-100 CO to start automatically when CallPath Server for AIX starts. 10. Select Restart on failure if you want DMS-100 CO to restart when there is a failure in communications between it and CallPath Server for AIX. 11. Complete the following fields: Network Node ID Identifies this DMS-100 CO switch. The range of values is 0 to 32767. Service ID Identifies the service profile for this DMS-100 CO switch. The range of values is 0 to 255. BCS Version (level) of service that the DMS-100 CO switch and CallPath Server for AIX are operating under. Acceptable values are in the range of 33-36. Business Group ID Identifies your switch within the public telephone network. Your switch administrator has the value assigned to you by the telephone company. Application ID Identifier for the host application program to be run. The range of values is 1 to 32,767. Local Address Link address for the RISC System/6000 as registered with the DMS-100 CO switch. Your switch administrator has the value assigned to CallPath Server for AIX. Remote Address The address by which the DMS-100 CO switch identifies itself. Your switch administrator has this value. Slot number Device name assigned to the X.25 slot used. Acceptable values are x25s0, x25s1, x25s2, and x25s3. Password The password assigned to the specified business group for this DMS-100 CO switch. Your switch administrator has the 1-to-8 character password. Use uppercase for all alphabetic characters in the password. Verify password Retype the password for verification. 12. Click on OK. Either the CallPath Server Management Facility or the Set Switch Configuration window is displayed, depending on your selection in Step 8. 13. Repeat this procedure for each switch connection starting with Step 2. --------------------------------------------------------------------------- Appendix C. Notices References in this publication to IBM products, programs, or services do not imply that IBM intends to make them 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 that IBM product, program, or service may be used. Subject to IBM's valid intellectual property or other legally protectable rights, any functionally equivalent product, program, or service may be used instead of the IBM product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, are the responsibility of the user. IBM may have patents or pending patent applications covering subject matter described 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 Director of Licensing IBM Corporation 500 Columbus Avenue Thornwood, NY 10594 USA Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: Site Counsel IBM Corporation P.O. Box 12195 3039 Cornwallis Road Research Triangle Park, NC 27709-2195 USA Such information may be available, subject to appropriate terms and conditions, including in