Avaya Call Management System: Switch Connections, Administration, and Troubleshooting

Avaya Call Management System
Switch Connections, Administration, and Troubleshooting
December 2011
2011 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avayas standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Web site: http://www.avaya.com/support License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE http://www.avaya.com/support/LicenseInfo/ ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single stand-alone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User. License type(s) Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://www.avaya.com/support/ThirdPartyLicense/
Preventing toll fraud "Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya fraud intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: http://www.avaya.com/support Trademarks Avaya and the Avaya logo are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. All other trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: http://www.avaya.com/support Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Support Web site: http://www.avaya.com/support
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7 7 8 8 9 9 10 11 13 13 14 14 14 14 15 17 17 18 19 19 20 21 22 23 24 25 26 27 28 29 30 32 33 33 33 34 34
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions and terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reasons for reissue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation Web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch and CMS release compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting a TCP/IP switch link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . Local vs remote connections . . Multiple ACDs (switches) . . . . High availability option . . . . . Connecting blocks. . . . . . . . Planning for TCP/IP switch links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switch connections with TCP/IP over a LAN . . . . . . . . . . . . . . . . . . . . Connecting one or more ACDs using TCP/IP over a LAN . . . . . . . . . . . Ethernet ports on the switch . . . . . . . . . . . . . . . . . . . . . . . . . . . Ethernet ports on a CMS computer. . . . . . . . . . . . . . . . . . . . . . . . LAN speeds - 10 Mbps vs 100 Mbps . . . . . . . . . . . . . . . . . . . . . . . C-LAN lead designations for cross-connects . . . . . . . . . . . . . . . . . . Sample configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic configuration with NTS . . . . . . . . . . . . . . . . . . . . . . . . . Multiple ACDs (switches) . . . . . . . . . . . . . . . . . . . . . . . . . . . Two ethernet ports on CMS computer . . . . . . . . . . . . . . . . . . . . Integrating Intuity AUDIX on the link . . . . . . . . . . . . . . . . . . . . . Intuity AUDIX with integrated messaging traffic on the customer network Remote switch on the customer network . . . . . . . . . . . . . . . . . . Two ethernet ports option. . . . . . . . . . . . . . . . . . . . . . . . . . . High availability option . . . . . . . . . . . . . . . . . . . . . . . . . . . . Public network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting with a crossover cable. . . . . . . . . . . . . . . . . . . . . . . . Distance limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parts list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cabling diagram - LAN via crossover cable . . . . . . . . . . . . . . . . . Cabling procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Avaya CMS Switch Connections, Administration, and Troubleshooting
December 2011
Contents
Crossover wiring. . . . . . . . . . . . . . Connecting with a LAN hub or router . . . . Distance limits . . . . . . . . . . . . . . . Parts list . . . . . . . . . . . . . . . . . . Cabling Diagram - LAN via hub or router Cabling procedure . . . . . . . . . . . . . Connecting over a customer LAN . . . . . . Distance limits . . . . . . . . . . . . . . . Parts list . . . . . . . . . . . . . . . . . . Cabling diagram - customer LAN . . . . . Cabling procedure . . . . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
35 36 36 36 37 38 39 39 39 40 40 41 41 42 42 42 43 45 46 47 48 49 50 51 52 53 53 54 56 58 60 61 62 64 65 66 68 70
Administering a TCP/IP switch link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . Local vs remote connections . . Multiple ACDs (switches) . . . . High availability option . . . . . Planning for TCP/IP switch links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administering the link at the CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administering the CMS and switch release options . . . . . . . . . . . . . . . . . Determining switch and CMS compatibility . . . . . . . . . . . . . . . . . . . . Verifying the software version . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the call center release . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the adjunct CMS release (Communication Manager 3.0 and earlier) . . Setting the reporting adjunct release (Communication Manager 3.1 and later) . Administering a TCP/IP connection . . . . . . . . . . . . Administering a C-LAN connection . . . . . . . . . . Adding a second packet interface . . . . . . . . . Adding node names and IP addresses . . . . . . . Adding a C-LAN IP interface . . . . . . . . . . . . Adding an ethernet data module . . . . . . . . . . Adding the processor interface channels . . . . . Adding IP routing . . . . . . . . . . . . . . . . . . Administering a processor ethernet port connection . Displaying the processor ethernet port . . . . . . Adding node names and IP addresses . . . . . . . Adding the processor interface channels . . . . . Administering a Survivable Backup CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administering data collection options . . . . . . . . . . . . . . . . . . . . . . . . . . .
December 2011
Contents
Troubleshooting TCP/IP switch connections . . . . . . . . . . . . . . . . . . . . . . . . . Switch administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CMS computer tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glossary Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73 73 74 75 76 77 79
December 2011
Contents
December 2011
Preface
Avaya Call Management System (CMS) is an application for businesses and organizations that use Avaya communication servers to process large volumes of telephone calls using the Automatic Call Distribution (ACD) feature. Avaya CMS supports solutions for routing and agent selection, multi-site contact centers, remote agents, reporting, interfaces to other systems, workforce management, desktop applications, system recovery, and quality monitoring. Avaya CMS is part of the Operational Effectiveness solution of the Avaya Customer Interaction Suite. This section includes the following topics:

Purpose on page 7 Intended users on page 7 Overview on page 8 Conventions and terminology on page 8 Reasons for reissue on page 9 Documentation Web sites on page 9 Support on page 10
Purpose
This document describes how to connect and administer Avaya communication servers (switches) that are used with the Avaya CMS.
Intended users
This document is written for:

Avaya support personnel Contact center administrators
This document assumes a minimum level of technical knowledge on the part of its readers. It assumes, for example, that a reader knows how to use the switch administration interfaces and how to connect switch hardware.
December 2011
Preface
Overview
Switch and CMS release compatibility on page 11 - Provides an overview of the supported CMS software, supported hardware platforms, required software, and supported software releases. Connecting a TCP/IP switch link on page 13 - Explains how to connect the switch to the CMS computer over a LAN using TCP/IP. Administering a TCP/IP switch link on page 41 - Explains how to administer the switch for the connections to a CMS computer over a LAN using TCP/IP. Troubleshooting TCP/IP switch connections on page 73- Explains how to maintain and troubleshoot the hardware and software components that make up a switch link over a LAN using TCP/IP. Glossary on page 77
Conventions and terminology

The following terminology is used in this document:
Unless specified otherwise, all information and procedures in this document apply to the Sun computers that support the CMS product. In this document, they are referred to as the "CMS computer." Unless otherwise specified, all switch connectivity and administration applies to all models of Avaya switch software and hardware, including the following: - Avaya DEFINITY Server Avaya Professional Services, SI, and R Note: Support for the DEFINITY Server R ended beginning with Communication Manager 2.0. Support for the DEFINITY Server SI ended beginning with Communication Manager 3.0. - DEFINITY One - Avaya IP600 - Avaya S8300-series, S8500-series, S8700-series, and S8800-series Servers - Avaya G-series media gateways (for example, G450, G430, G700, G650, G350, and so on) that are certified for call center configurations - SBS3000 Hosted Bladeserver Chassis and related equipment
Note:
December 2011
Reasons for reissue
Automatic Call Distribution (ACD) is a feature of the switch software. The ACD feature is used to route incoming calls to groups of agents. When this document refers to "connecting to an ACD," it refers to connecting to a switch that has ACD capabilities.
If you see any of the following safety labels in this document, take careful note of the information presented.
!
CAUTION:
CAUTION: Caution statements call attention to situations that can result in harm to software, loss of data, or an interruption in service. WARNING: Warning statements call attention to situations that can result in harm to hardware or equipment. DANGER: Danger statements call attention to situations that can result in harm to personnel. SECURITY ALERT: Security alert statements call attention to situations that can increase the potential for unauthorized use of a telecommunications system.
!
WARNING:
!
DANGER:
!
SECURITY ALERT:
Reasons for reissue

This document was reissued for the following reasons:
Updated the switch release and CMS server matrix to reflect compatibility of CMS R16.3 with different switch release combinations.
Documentation Web sites

All CMS documentation can be found at http://www.avaya.com/support. New issues of CMS documentation will be placed on this Web site when available. Use the following Web sites to view related support documentation:
Information about Avaya products and service http://www.avaya.com
December 2011
Preface
Sun hardware documentation http://docs.sun.com
Support
Contacting Avaya technical support
Avaya provides support telephone numbers for you to report problems or ask questions about your product. For United States support: 1- 800- 242-2121 For international support: See the Support Directory listings on the Avaya Web site.
Escalating a technical support issue

Avaya Global Services Escalation Management provides the means to escalate urgent service issues.
10
December 2011
Switch and CMS release compatibility

Different releases of CMS software are certified to interface with the following switch software releases.
Communication server software release R3V9 DEFINITY R9.1, R9.2 Avaya Call Processing R9.5 Avaya Call Processing R10 Communication Manager 1.1, 1.2, 1.3 Communication Manager 2.0, 2.1, 2.2 Communication Manager 3.0, 3.1 Communication Manager 4.0 Communication Manager 5.0,5.1 Communication Manager 5.2 Communication Manager 5.2.1 Communication Manager 6.0 Communication Manager 6.2 1. Recommended release combination. Yes1 Yes1 Yes
1
CMS software release R3V11 Yes Yes Yes Yes1 Yes Yes Yes No No No No No R12 Yes Yes Yes Yes Yes1 Yes Yes Yes Yes Yes Yes Yes R13.x Yes Yes Yes Yes Yes Yes1 Yes Yes Yes Yes Yes Yes R14.x Yes Yes Yes Yes Yes Yes Yes1 Yes1 Yes Yes Yes Yes R15 No No No No Yes Yes Yes Yes Yes1 Yes Yes Yes R16 No No No No Yes Yes Yes Yes Yes Yes1 Yes Yes R16.x No No No No Yes Yes Yes Yes Yes Yes Yes1 Yes1
Yes Yes Yes No No No No No No
December 2011
11
Switch and CMS release compatibility
12
December 2011
Connecting a TCP/IP switch link

This section explains how to connect the CMS computer to the switch using TCP/IP over a local area network (LAN). This section includes the following topics:

Overview on page 13 Switch connections with TCP/IP over a LAN on page 17
Overview
The connection between the CMS computer and a switch allows the CMS software on the computer to receive, store, and format the Automatic Call Distribution (ACD) information it receives from one or more switches. A switch technician should be on-site to make the connection from the CMS computer to the switch and, if necessary, to administer the switch for the ACD feature and CMS. The CMS software will not communicate with the switch if the ACD feature, CMS, or the switch hardware is not properly administered. See Administering a TCP/IP switch link on page 41 for more information. This section includes the following topics:

Local vs remote connections on page 14 Multiple ACDs (switches) on page 14 High availability option on page 14 Connecting blocks on page 14 Planning for TCP/IP switch links on page 15
December 2011
13
Local vs remote connections

This section shows both local and remote connections between the switch and the CMS computer. For clarification, these connections are defined as follows:
Local - The connections between the switch and the CMS computer use facilities local to the switch, such as a direct connection over a LAN. Remote - The connections between the switch and the CMS computer use wide area network (WAN).
Multiple ACDs (switches)

One CMS computer can collect data from up to eight different switches. From the CMS computer point of view, each switch represents one ACD. Each switch requires a link to the CMS computer.
High availability option

The High Availability option provides dual links between the switch and two separate CMS computers. If the customer has purchased the High Availability option, you must connect a link from one ethernet port on the switch to one CMS computer, and a second link from a different ethernet port on the switch to another CMS computer. The High Availability option is not allowed using X.25 links. Note: For the S8300 Server, you cannot have dedicated links to each CMS computer; if you want true duplication, you must use a different solution.
Note:
Connecting blocks
In this section, references are made to 103A connecting blocks, which have one RJ45 connector per block. If needed, you can substitute the 104A connecting block, which has two RJ45 connectors per block. The wiring for both connecting blocks are identical.
14
December 2011
Overview
Planning for TCP/IP switch links

When setting up a switch link using TCP/IP over a LAN, planning information must be gathered before you begin. In particular, you must take into account if the LAN connection includes both a connection to CMS, Intuity AUDIX with integrated messaging, and Avaya Operational Analyst (OA). Some of the information needed includes:
How is the connection being made from the CMS computer to the switch? - Private LAN, no connectivity to customer LAN (uses private LAN addresses).
Preferred method, most robust and reliable, no dependency on customers network A dedicated LAN port on the CMS computer provides the switch link The primary LAN port (the built-in ethernet port) is used for other connectivity (printers, terminals, Avaya CMS Supervisor, Intuity integrated messaging, and Avaya OA) using a different subnet from the switch link If desired, a second ethernet port can be used to provide additional isolation for the CMS link A dedicated LAN hub to connect the links.
- Customer LAN with private segment.

Uses a network switch or router to provide a private network or network segment Minimal dependency on customers network A dedicated LAN port on the CMS computer provides the switch link The primary LAN port (the built-in ethernet port) is used for other connectivity (printers, terminals, Avaya CMS Supervisor, Intuity integrated messaging, and Avaya OA) using a different subnet from the switch link Customer must provide equipment and administer network for private segment Customer LAN administrator must be present during setup.
- Direct connect to Customer LAN, without private segment.

Least preferred method Complete dependency on performance and reliability of customers LAN Allows remote location of endpoints when customer LAN connectivity is convenient Customer LAN administrator must be present during setup.
December 2011
15
If the customer LAN is used, the following information is needed from the customer: - Customer network physical connectivity:

Location of network access point (hub, router, and so on) Distance between the ethernet port on the switch and the network access point (328 ft, 100 m maximum) Wiring to access point, existing or new, Category 5 minimum required.
- Customer network administration:

IP address of switch ethernet ports, CMS computer, Intuity, and gateways Node names of switch ethernet ports, CMS computer, Intuity, and gateways Subnet masks for all LAN segments containing switch ethernet ports or adjuncts Gateway IP address for all LAN segments containing switch ethernet ports, adjuncts, or routers Are all endpoints (switch ethernet ports and adjuncts) on the same local LAN segment? Network routes.
Network administration information needs to be mapped into specific administration fields.
Sanity check of information obtained from customer: - If switch and adjuncts are on different LAN subnets (recommended), gateway IP addresses are different - If switch and adjuncts (CMS or Intuity) are on the same LAN subnet (not recommended):

Gateway IP address (if present) and subnet mask information is valid All IP addresses contain the same subnet address
Without the above information, the technician may not be able to complete the installation. Installations that require the technicians to return because information was not available incur additional charges.
16
December 2011
Switch connections with TCP/IP over a LAN

Any switch either the TN799 C-LAN circuit pack or a processor ethernet port can interface to a CMS computer using a LAN. This connection can be made in the following ways:

Connecting with a crossover cable Connecting with a LAN hub or a network switch (recommended configuration) Connecting over a customer LAN
This section includes the following topics:

Connecting one or more ACDs using TCP/IP over a LAN on page 17 Ethernet ports on the switch on page 18 Ethernet ports on a CMS computer on page 19 LAN speeds - 10 Mbps vs 100 Mbps on page 19 C-LAN lead designations for cross-connects on page 20 Sample configurations on page 21 Ethernet ports on the switch on page 18 Connecting with a crossover cable on page 33 Connecting with a LAN hub or router on page 36 Connecting over a customer LAN on page 39
Connecting one or more ACDs using TCP/IP over a LAN

Any switch equipped with a TN799 C-LAN circuit pack or a processor ethernet port can interface to a CMS computer using a LAN. CMS computers are equipped with at least two ethernet ports for network connections. The connection to the switch must be dedicated to a second ethernet port which is provided on a PCI or SBus card in the CMS server. The primary built-in ethernet port can be used for printers, CMS Supervisor, and connections to Avaya OA. Avaya recommends that these two network connections be on different subnets.
!
Important:
Important: If a CMS computer has a Token Ring card installed, this port cannot be used for the switch link.
Detailed parts lists and cabling diagrams are shown later in this document for each switch that supports a LAN connection.
December 2011
17
Ethernet ports on the switch

The switch provides an ethernet port using either the TN799 C-LAN circuit pack or the processor ethernet port. For connectivity purposes, it does not matter what ethernet port is used, but the correct port must be administered on the switch. The TN799 C-LAN supports CMS links on the following platforms:

DEFINITY Server Avaya Professional Services using the CMC1 Media Gateway DEFINITY Server SI and R using the SCC1 and MCC1 Media Gateway Note: Support for the DEFINITY Server R ended beginning with Communication Manager 2.0. Support for the DEFINITY Server SI ended beginning with Communication Manager 3.0.
Note:
Avaya IP600 DEFINITY One Avaya S8100 Server using the G600, G650, or CMC1 Media Gateway Avaya S8700-series Server using the SCC1, MCC1, or G700 Media Gateway
The processor ethernet port supports CMS links on the following platforms that do not support C-LAN circuit packs:

Avaya IP600 using the TN2314 DEFINITY One using the TN2314 Avaya S8100 Server Avaya S8300-series and S8500-series Servers Avaya S8700-series Servers using the IP Connect option Avaya SBS3000 Hosted Bladeserver Chassis Avaya S8800-series Servers
18
December 2011
Ethernet ports on a CMS computer

CMS computers are equipped with at least two ethernet ports for network connections. The connection to the switch must be dedicated to a second ethernet port which is provided on a PCI or SBus card in the CMS server. The primary, built-in ethernet port can be used for NTS, printers, CMS Supervisor, and connections to Avaya OA. Avaya recommends that these two network connections be on different subnets.
!
Important:
Important: It is recommended that, if possible, the switch connection be isolated to a dedicated LAN port without any other network connections.
LAN speeds - 10 Mbps vs 100 Mbps

All TN799 C-LAN circuit packs support 10 Mbps ethernet connections. The TN799DP and later supports 10 and 100 Mbps ethernet connections as long as all the connecting equipment supports that speed. If you use 10 Mbps hubs between the switch and the CMS, the speed of the connection will be 10 Mbps. The TN799DP C-LAN circuit pack also uses the IP Media Processor adapter (Material ID 848525887) to provide an ethernet modular jack connection on the switch backplane. This adapter must be used to attain 100 Mbps connections. The processor ethernet port on the Avaya IP600, DEFINITY One, and S8xxx servers support 10 Mbps and 100 Mbps, autosensing.
December 2011
19
C-LAN lead designations for cross-connects

The TN799 C-LAN circuit pack ethernet lead designations are as follows: Lead Name 25-Pair Cable Wire Color 25-Pair Cable Connector Pin-out 27 2 28 3 RJ45 Jack Pin-out 1 2 3 6 Terminal Block Pin-out on Connecting Block 3 4 5 6
TD+ TDRD+ RD-
white/orange orange/white white/green green/white
Use this information when making connections from the TN799 when using an IP Media Processor adapter (100 Mbps), a 259A adapter (10 Mbps), or using standard cross-connect wiring (100 Mbps or 10 Mbps).
20
December 2011
Sample configurations
The CMS computer can connect to a switch in a number of ways using a LAN. This section shows some examples of how this can be done. Though several sample configurations are shown, there will be variations not shown here. All but the most basic configurations require planning by the customer and account team. Note: Please note that the IP addressing shown in these examples reflects a basic recommended scheme that can be used if the customer does not have their own addressing requirements.
Note:

Basic configuration on page 22 Basic configuration with NTS on page 23 Multiple ACDs (switches) on page 24 Two ethernet ports on CMS computer on page 25 Integrating Intuity AUDIX on the link on page 26 Intuity AUDIX with integrated messaging traffic on the customer network on page 27 Remote switch on the customer network on page 28 Two ethernet ports option on page 29 High availability option on page 30 Public network on page 32 Note: In certain permissive-use cases beginning with CMS R12, customers can continue to use an NTS for serial connectivity. Contact Avaya support for information about Avayas permissive use policy and using an NTS with CMS. These sample configurations show NTS connectivity to support releases that allow NTS usage.
Note:
December 2011
21
Basic configuration
In the most basic configuration, you can create a LAN between a CMS computer to a switch using either a crossover cable or a dedicated hub. This setup provides isolation from the customer data network, keeping all switch-to-CMS messaging traffic on a dedicated private network. The CMS computer is directly connected to the switch, and neither is part of another network. This configuration is adequate if there is no NTS, printer, CMS Supervisor traffic, or Intuity Message Manager traffic.
CMS Computer 192.168.1.90 Crossover Cable Ethernet Port Switch 192.168.1.10 Ethernet port (C-LAN or processor)
basic_net1.cdr
CMS computer 192.168.1.90
Hub
Switch 192.168.1.10 Ethernet port (C-LAN or processor)
Ethernet port
Basic_net.cdr
22
December 2011
Basic configuration with NTS

Building on the previous example, the following diagram shows how you can add a LAN hub to provide additional LAN points of connection for NTS equipment. Using the same LAN segment for NTS and switch traffic is not recommended, but can be done if the CMS computer has only one ethernet port. Note: In certain permissive-use cases beginning with CMS R12, customers can continue to use an NTS for serial connectivity. Contact Avaya support for information about Avayas permissive use policy and using an NTS with CMS.
CMS computer 192.168.1.90 Hub Switch 192.168.1.10 Ethernet port (C-LAN or processor)
Note:
Ethernet port
NTS #1 192.168.1.101
NTS #x 192.168.1.1xx
closed_net.cdr
December 2011
23

A CMS computer can collect data from more than one switch. The following figure shows how several ACDs (local or remote) would connect to a CMS computer over a LAN. This example isolates the switch-to-CMS traffic from any other network traffic.
CMS computer 192.168.1.90 Hub Local switch 192.168.1.10 Ethernet port (C-LAN or processor)
Ethernet port
Router
Remote switch 192.168.10.11 Ethernet port (C-LAN or processor)
Remote switch 192.168.20.12 Ethernet port (C-LAN or processor)
multiple_switch.cdr
24
December 2011
Two ethernet ports on CMS computer

If the CMS computer is using a LAN for both switch link traffic and connections to CMS Supervisor, Avaya OA, and other network applications, the CMS computer should be equipped with two ethernet ports. In this configuration, the primary ethernet port is used for all non-switch applications. The secondary ethernet port is dedicated for carrying switch link traffic. This link can be connected using either a LAN hub or a crossover cable. Each ethernet port must be administered on different networks, so switch-to-CMS traffic does not mix with other traffic.
Avaya OA CMS Supervisor
CMS computer
Primary ethernet port 192.168.2.90
Hub Customer network
NTS
Printer Customer application
Switch 192.168.1.10
Hub
Secondary ethernet port 192.168.1.90
Ethernet port (C-LAN or processor)
two_ports.cdr
December 2011
25
Integrating Intuity AUDIX on the link

This configuration shows how you can integrate an Intuity AUDIX system (without integrated messaging) as part of the switch-to-CMS link. The additional traffic load should not cause any loss of data on the link.
CMS Supervisor
Avaya OA
CMS computer
NTS
Printer Customer application
Switch 192.168.1.10
Hub
two_ports_intuity.cdr
Intuity AUDIX without integrated messaging
26
December 2011
Intuity AUDIX with integrated messaging traffic on the customer network

This configuration does have a connection to the customer network. However, the bulk of the traffic is isolated from the switch link using the router and a network switch. The router and network switch separate the integrated messaging traffic originating by the customer PCs from the switch link traffic.
Avaya OA CMS Supervisor
CMS computer
NTS
Printer
Switch 192.168.1.10
Network switch or router Ethernet port (C-LAN or processor)
two_ports_msgmgr.cdr
Intuity AUDIX with integrated messaging
December 2011
27
Remote switch on the customer network

A remote switch can also be connected through the customer network. using a router and a network switch to isolate the switch link traffic from the Message Manager traffic and the other customer network traffic.
CMS Supervisor Remote Switch
NTS CMS computer
Customer network
Printer
Switch 192.168.1.10
Network switch or router Ethernet port (C-LAN or processor)
two_ports_remote.cdr
Intuity AUDIX with integrated messaging
28
December 2011
Two ethernet ports option

This configuration shows the best way to isolate the CMS and Intuity links to the switch. This configuration uses two ethernet ports on the switch. A router must be used to send traffic from the customer network to the Intuity, or if there is a remote switch that connects to the CMS computer. For true link isolation, this is the best option available.
CMS Supervisor Remote Switch
NTS CMS computer
Primary ethernet port
Customer network
Printer
Switch
Secondary ethernet port
Network switch or router
Hub Intuity AUDIX with integrated messaging
two_ports_2clan.cdr
December 2011
29

The High Availability option uses dual links from the switch to different CMS computers. This option helps ensure that CMS data is not lost if one of the links loses connectivity or if one of the CMS computers goes down. This option is available on CMS R3V8 or later, and switch release R8. You can achieve this by using separate IP addresses on separate C-LAN cards on the switch. Additionally, when you use CMS R16 or later with Communication Manager 5.2.1 or later, it supports duplicated Processor Ethernet switch port connections as well, thus removing the requirement for C-LAN cards on the switch. The connection to the Processor Ethernet (PE) applies to High Availability, Survivable CMS and Dual Role CMS. These are all Avaya Professional Services offers. To configure a solution using the PE interface and any of these offers, contact Avaya Professional Services. The following figure shows a typical High Availability C-LAN configuration. Though not shown here, you can use a second Ethernet port on the CMS computers to isolate the NTS, printer, and CMS Supervisor traffic. Note: For the S8300 Server, you cannot have dedicated links to each CMS computer. If you want true duplication, you must use a different solution.
Note:
30
December 2011
December 2011
31
Public network
In a public network where the customer is connected to the Internet, the default IP addressing cannot be used. You must administer IP addressing based on the customer requirements. For switch-to-CMS traffic, this setup is the least desirable way to set up a switch link because of potential message loss on a network that has too much traffic.
CMS computer x.x.x.x Switch x.x.x.x Ethernet port (C-LAN or processor)
Ethernet port
Customer data network NTS #1 x.x.x.x
Internet
NTS #x x.x.x.x
open_net.cdr
32
December 2011
Connecting with a crossover cable

The direct LAN connection is the most basic method to connect the switch to the CMS computer. Any NTSs must connect to a separate ethernet port on the CMS computer.
Distance limits
The distance limit for a direct LAN connection is 328 feet (100 meters).
Parts list
Quantity 1 1 TN799 C-LAN port 259A adapter (102631413), or 258B adapter (103923025), or 356A adapter (104158829), or Category 5 cross-connect hardware and connecting block 6-inch RJ45 crossover cable (846943306 or 104154414) RJ45 UTP Category 5 modular cord 107748063 (5 feet, 1.5 meters) 107748105 (10 feet, 3 meters) 107748188 (15 feet, 4.5 meters) 107742322 (25 feet, 7.6 meters) 107742330 (50 feet, 15.2 meters) 107748238 (100 feet, 30.5 meters) 107748246 (200 feet, 61 meters) 107748253 (300 feet, 91 meters) Ethernet port on the CMS computer Description
1 1
December 2011
33
Cabling diagram - LAN via crossover cable

IP Media Processor adapter (100 Mbps) or 259A (10 Mbps)
Switch (R7 or later) Crossover cord OR TN799 C-LAN Port Cat 5 crossconnect field
Cat 5 connecting block
CMS computer (R3V6 or later)
Ethernet port
Cat 5 wire OR Crossover cord RJ45 Cat 5 modular cord
Cat 5 25-pair cable Built-in ethernet port
Crossover cord
328 ft (100 m)
328 ft (100 m)
Lan_xover.cdr
Cabling procedure
To connect the switch to a CMS computer using a crossover cable: 1. Do one of the following:
Attach an adapter (259A, 258B, or 356A) to the backplane connector of the TN799 C-LAN circuit pack, then attach the plug end of the crossover cable to the adapter. Use jack #1 on the 258B or 356A adapters. Connect the ethernet port of a TN799 C-LAN circuit pack to a Category 5 connecting block using Category 5 cross-connect wiring, then attach the plug end of the crossover cable to the connecting block.
2. Connect one end of an RJ45 Category 5 modular cord to the receptacle end of the crossover cable. 3. Connect the other end of the modular cord to an ethernet port on the CMS computer.
34
December 2011
Crossover wiring
If the standard crossover cable is not available, you can build your own crossover wiring arrangement to flip the transmit and receive leads 3/5 and 4/6 for the LAN connection. The following figure shows how this can be done with a 104A connecting block (Material ID 105164859). When using this device, the distance limit from the switch to the CMS computer is 328 feet (100 meters). From this device, you would connect one RJ45 Category 5 modular cord to the switch C-LAN circuit pack, and another RJ45 Category 5 modular cord to the CMS computer ethernet port.
104A Connecting Block
RDRD+ TDTD+
6 5 4 3
6 5 4 3
RDRD+ TDTD+
RJ45
RJ45
crossover.cdr
December 2011
35
Connecting with a LAN hub or router

The LAN hub or router connection is the recommended method to connect the switch to the CMS computer. The hub or router can be used to connect to more than one switch (multiple ACDs), and to connect to NTS units. This section includes the following topics:

Distance limits on page 36 Parts list on page 36 Cabling Diagram - LAN via hub or router on page 37 Cabling procedure on page 38
Distance limits
The distance limit for a single hub or router LAN connection is 328 feet (100 meters) from the switch to the hub or router, and another 328 feet (100 meters) from the hub or router to the CMS computer. If the distance between the switch and the CMS computer is more than 328 feet (100 meters), you can daisy-chain up to four separate hubs or routers.
Parts list
Quantity 1 1 Description Ethernet port on the switch (TN799 C-LAN or processor ethernet port) IP Media Processor adapter for 100 Mbps (848525887), or 259A adapter for 10 Mbps (102631413), or Category 5 cross-connect hardware and connecting block RJ45 UTP Category 5 modular cord 107748063 (5 feet, 1.5 meters) 107748105 (10 feet, 3 meters) 107748188 (15 feet, 4.5 meters) 107742322 (25 feet, 7.6 meters) 107742330 (50 feet, 15.2 meters) 107748238 (100 feet, 30.5 meters) 107748246 (200 feet, 61 meters) 107748253 (300 feet, 91 meters)
36
December 2011
Quantity 1 1 LAN hub or router
Description
Ethernet port on the CMS computer
Cabling Diagram - LAN via hub or router

IP Media Processor adapter (100 Mbps) or 259A adapter (10 Mbps)
Switch (R7 or later) RJ45 Cat 5 modular cord OR TN799 C-LAN Port Cat 5 crossconnect field
Cat 5 connecting block Hub or router RJ45 Cat 5 modular cord AC power RJ45 Cat 5 modular cord
Ethernet port
Cat 5 25-pair cable Processor ethernet port
Cat 5 wire OR RJ45 Cat 5 modular cord
328 ft (100 m)
328 ft (100 m)
lan_ded.cdr
December 2011
37
Cabling procedure
To connect the switch to a CMS computer using a LAN hub: 1. Do one of the following depending on your hardware configuration:
Attach an adapter (IP Media Processor or 259A) to the backplane connector of the TN799 C-LAN circuit pack. Attach one end of an RJ45 Category 5 modular cord to the adapter. Connect the ethernet port of a TN799 C-LAN circuit pack to a Category 5 connecting block using Category 5 cross-connect wiring. Attach one end of an RJ45 Category 5 modular cord to the connecting block. Attach one end of an RJ45 Category 5 modular cord to the processor ethernet port on the switch. On the Avaya IP600, DEFINITY One, and S8100 Server, the processor ethernet port is found on the processor interface cable assembly of the TN2314 processor circuit pack. Attach one end of an RJ45 Category 5 modular cord to either the EXT1 or EXT2 ethernet port on a G700 Media Gateway. A G700 Media Gateway can be controlled by either an S8300 Server or an S87xx Server.
2. Connect the other end of the modular cord to a port on the LAN hub or router. 3. Connect another RJ45 Category 5 modular cord to a different port on the LAN hub or router. 4. Connect the other end of the modular cord to an ethernet port on the CMS computer. 5. Connect and apply power to the LAN hub or router.
38
December 2011
Connecting over a customer LAN

Using a customer network is another method to connect a switch to the CMS computer. This method is not recommended except in special cases. The LAN hub or router method should be used for most installations. This section includes the following topics:

Distance limits on page 39 Parts list on page 39 Cabling diagram - customer LAN on page 40 Cabling procedure on page 40
Distance limits
The distance limit using a customer network must be locally engineered.
Parts list
Quantity 1 1 Description Ethernet port on the switch (TN799 C-LAN or processor ethernet port) IP Media Processor adapter for 100 Mbps (848525887), or 259A adapter for 10 Mbps (102631413), or Category 5 cross-connect hardware and connecting block RJ45 UTP Category 5 modular cord 107748063 (5 feet, 1.5 meters) 107748105 (10 feet, 3 meters) 107748188 (15 feet, 4.5 meters) 107742322 (25 feet, 7.6 meters) 107742330 (50 feet, 15.2 meters) 107748238 (100 feet, 30.5 meters) 107748246 (200 feet, 61 meters) 107748253 (300 feet, 91 meters) Ethernet port on the CMS computer
December 2011
39
Cabling diagram - customer LAN

IP Media Processor adapter (100 Mbps) or 259A adapter (10 Mbps)
Switch (R7 or later) RJ45 Cat 5 modular cord OR TN799 C-LAN Port Cat 5 crossconnect field
Cat 5 connecting block Customer network (locally engineered)
Ethernet port
Cat 5 25-pair cable Processor ethernet port
Cat 5 wire OR RJ45 Cat 5 modular cord
RJ45 Cat 5 modular cord
Distance limit locally engineered
Lan_custnet.cdr
Cabling procedure
To connect the switch to a CMS computer using a customer LAN: 1. Do one of the following depending on your hardware configuration:
Attach an adapter (IP Media Processor or 259A) to the backplane connector of the TN799 C-LAN circuit pack. Attach one end of an RJ45 Category 5 modular cord to the adapter. Connect the ethernet port of a TN799 C-LAN circuit pack to a Category 5 connecting block using Category 5 cross-connect wiring. Attach one end of an RJ45 Category 5 modular cord to the connecting block. Attach one end of an RJ45 Category 5 modular cord to the processor ethernet port on the switch. On the Avaya IP600, DEFINITY One, and S8100 Server, the processor ethernet port is found on the processor interface cable assembly of the TN2314 processor circuit pack. Attach one end of an RJ45 Category 5 modular cord to either the EXT1 or EXT2 ethernet port on a G700 Media Gateway. A G700 Media Gateway can be controlled by either an S8300 Server or an S87xx Server.
2. Connect the other end of the modular cord to a port on the customer data network. 3. Connect from the customer data network to an ethernet port the CMS computer.
40
December 2011
Administering a TCP/IP switch link

This section provides the procedures to administer TCP/IP over a LAN. This section includes the following topics:

Overview on page 41 Administering the link at the CMS on page 45 Administering the CMS and switch release options on page 46 Administering data collection options on page 52 Administering a TCP/IP connection on page 53
Overview
The CMS application can collect and process Automatic Call Distribution (ACD) data from an Avaya switch. However, before CMS can collect and process the ACD data, a special hardware interface on the switch must be properly administered. Each switch can use a number of different interfaces to communicate to a CMS computer. For additional information about switch administration, refer to the appropriate switch administration documents. This section includes the following topics:

Local vs remote connections on page 42 Multiple ACDs (switches) on page 42 High availability option on page 42 Planning for TCP/IP switch links on page 43
December 2011
41
Local vs remote connections

The switch and the CMS computer can be connected in local and remote arrangements. For clarification, these arrangements are defined as follows:
Local - The connections between the switch and the CMS computer use facilities local to the switch, such as a direct connection over a LAN. Remote - The connections between the switch and the CMS computer use WAN.

One CMS computer can collect data from up to eight different switches. From the CMS computer point of view, each switch represents one ACD. Each switch requires a link to the CMS computer.

The High Availability option provides dual links between the switch and two separate CMS computers. If the customer has purchased the High Availability option, you must connect a link from one C-LAN circuit pack or processor ethernet port to one CMS computer, and a second link from a different C-LAN circuit pack or processor ethernet port to another CMS computer. The High Availability option is not allowed using X.25 links. Note: For the S8300 Server, you cannot have dedicated links to each CMS computer; if you want true duplication, you must use a different solution.
Note:
42
December 2011
Overview
Planning for TCP/IP switch links

When setting up a switch link using TCP/IP over a LAN, planning information must be gathered before you begin. In particular, you must take into account if the LAN connection includes both a connection to CMS, Intuity AUDIX with integrated messaging, and Avaya Operational Analyst (OA). Some of the information needed includes:
How is the connection being made from the CMS computer to the switch? - Private LAN, no connectivity to customer LAN (uses private LAN addresses).
Preferred method, most robust and reliable, no dependency on customers network A dedicated LAN port on the CMS computer provides the switch link The primary LAN port (the built-in ethernet port) is used for other connectivity (printers, terminals, Avaya CMS Supervisor, Intuity integrated messaging, and Avaya OA) using a different subnet from the switch link If desired, a second ethernet port can be used to provide additional isolation for the CMS link A dedicated LAN hub to connect the links.
- Customer LAN with private segment.

Uses a network switch or router to provide a private network or network segment Minimal dependency on customers network A dedicated LAN port on the CMS computer provides the switch link The primary LAN port (the built-in ethernet port) is used for other connectivity (printers, terminals, Avaya CMS Supervisor, Intuity integrated messaging, and Avaya OA) using a different subnet from the switch link Customer must provide equipment and administer network for private segment Customer LAN administrator must be present during setup.
- Direct connect to Customer LAN, without private segment.

Least preferred method Complete dependency on performance and reliability of customers LAN Allows remote location of endpoints when customer LAN connectivity is convenient Customer LAN administrator must be present during setup.
December 2011
43
If the customer LAN is used, the following information is needed from the customer: - Customer network physical connectivity:

Location of network access point (hub, router, and so on) Distance between the ethernet port on the switch and the network access point (328 ft, 100 m maximum) Wiring to access point, existing or new, Category 5 minimum required.
- Customer network administration:

IP address of switch ethernet ports, CMS computer, Intuity, and gateways Node names of switch ethernet ports, CMS computer, Intuity, and gateways Subnet masks for all LAN segments containing switch ethernet ports or adjuncts Gateway IP address for all LAN segments containing switch ethernet ports, adjuncts, or routers Are all endpoints (switch ethernet ports and adjuncts) on the same local LAN segment? Network routes.
Network administration information needs to be mapped into specific administration fields.
Sanity check of information obtained from customer: - If switch and adjuncts are on different LAN subnets (recommended), gateway IP addresses are different - If switch and adjuncts (CMS or Intuity) are on the same LAN subnet (not recommended):

Gateway IP address (if present) and subnet mask information is valid All IP addresses contain the same subnet address
Without the above information, the technician may not be able to complete the installation. Installations that require the technicians to return because information was not available incur additional charges.
44
December 2011
Administering the link at the CMS
Administering the link at the CMS

In addition to the switch administration presented in this section, you must also set up the switch link on the CMS computer using the swsetup option of the cmssvc command. This procedure is documented in your CMS software installation document. To set up the switch link: 1. Using the cmssvc command, turn off CMS. 2. Using the cmssvc command, access the swsetup option. When you access this option, you are queried for the following information:

Switch name Switch model (see Determining switch and CMS compatibility on page 47) Is Vectoring enabled on the switch (if authorized)? Is Expert Agent Selection (EAS) enabled on the switch (if authorized)? Does the Central Office have disconnect supervision? Local and remote port The local and remote port assignments must be symmetrical between the switch and the CMS. The standard CMS provisioning procedure is to set the local and remote port assignments equal to the switch processor channel used for the link. For example, if you use processor channel 10, set the local and remote port to 10.
Transport method used to connect to the switch (TCP/IP). For TCP/IP, the IP address or hostname, and TCP port (the default is 5001).
If the CMS computer has two ethernet ports, it is possible that the system might attempt to route packets from one interface to another. To prevent this, edit the /etc/rc2.d/S98cms_ndd file and add the following line to the end of the file: ndd -set /dev/ip ip_forwarding 0 If the file already has this line, quit out of the file and make no changes.
December 2011
45
Administering the CMS and switch release options

This section contains release option administration that must be done before you administer the switch to CMS computer link. The following administration must be done:

Determining switch and CMS compatibility on page 47 Verifying the software version on page 48 Verifying the call center release on page 49 Setting the adjunct CMS release (Communication Manager 3.0 and earlier) on page 50 Setting the reporting adjunct release (Communication Manager 3.1 and later) on page 51
46
December 2011
Determining switch and CMS compatibility

The following table reflects the recommended settings for the G3 Version, Call Center Release, Adjunct CMS Release, and CMS Setup switch type based on the software release of the switch. You can set the G3 Version, Call Center Release, or Adjunct CMS Release to an earlier version, but you will not have access to all of the features of the recommended release. Switch software release Switch administration CMS administration CMS setup switch model Definity-R9/10 Definity-R9/10 MultiVantage-R11 Communication Mgr 2 Communication Mgr 3.0 Communication Mgr 3.1 Communication Mgr 4/5 Communication Mgr 4/5 Communication Mgr 4/5 Communication Mgr 5.2 Communication Mgr 5.2 Communication Mgr 6.x Communication Mgr 6.x
G3 Version DEFINITY R9.1, R9.21 Avaya Call Processing R9.5, R10.x Communication Manager 1.x Communication Manager 2.x Communication Manager 3.0 Communication Manager 3.1 Communication Manager 4.0 Communication Manager 5.0 Communication Manager 5.1 Communication Manager 5.2 Communication Manager 5.2.1 Communication Manager 6.0 Communication Manager 6.2
1. R9 is not a bugfix load.
Call Center Release 9.1 or later 9.1 or later 11.1 or later 12.0 or later 3.03 3.1 4.0 5.0 5.1 5.2 5.2 6.0 6.2
Reporting Adjunct Release R3V9 R3V9 R3V11 R122 R13 R13.1 R14 R14 R14 R15 R16 R16.x R16.x
V9 V10 V11 V12 V13 V13 V14 V15 V15 V15 V15 V16 V16
December 2011
47
2. Beginning the CMS R12, the release numbering scheme dropped the "3V" designation. For example, instead of CMS R3V12, it is now CMS R12. 3. Beginning with Communication Manager 3.0, the Call Center release numbering has been realigned to match the same release numbering scheme.
Verifying the software version

Use the System Parameters Customer Options form to verify the software version. If the software version is not correct, apply a new license file that has the correct version.
display system-parameters customer-options OPTIONAL FEATURES G3 Version: VXX Location: 1 Platform: 6 Page 1 of 11
RFA System ID (SID): 1 RFA Module ID (MID): 1
Platform Maximum Ports: Maximum Stations: Maximum XMOBILE Stations: Maximum Off-PBX Telephones - EC500: Maximum Off-PBX Telephones OPS: Maximum Off-PBX Telephones - SCCAN:
10000 450 100 5 0 0
USED 2756 22 5 0 0 0
(NOTE: You must logoff & login to effect the permission changes.)
Field G3 Version
Definition Enter the appropriate software release of the switch. If you set this field to an earlier release number, you will not have access to the latest features. Apply a new license file that has the correct version. The G3 Version must be set to V8 or later to use the High Availability option.
48
December 2011
Verifying the call center release

Use the first Call Center Optional Features page of the System Parameters Customer Options form to set the Call Center Release. If the release number is not correct, apply a new license file that has the correct version.
display system-parameters customer-options CALL CENTER OPTIONAL FEATURES Call Center Release: X.X ACD? BCMS (Basic)? BCMS/VuStats Service Level? BSR Local Treatment for IP & ISDN? Business Advocate? Call Work Codes? DTMF Feedback Signals For VRU? Dynamic Advocate? Expert Agent Selection (EAS)? EAS-PHD? Forced ACD Calls? y y y n y y n n y y n Reason Codes? Service Level Maximizer? Service Observing (Basic)? Service Observing (Remote/By FAC)? Service Observing (VDNs)? Timed ACW? Vectoring (Basic)? Vectoring (Prompting)? Vectoring (G3V4 Enhanced)? Vectoring (3.0 Enhanced)? Vectoring (ANI/II-Digits Routing)? Vectoring (G3V4 Advanced Routing)? Vectoring (CINFO)? Vectoring (Best Service Routing)? Vectoring (Holidays)? Vectoring (Variables)? to effect the permission changes.) y n y y y y y y y n y y y y y y Page 6 of 11
Lookahead Interflow (LAI)? y Multiple Call Handling (On Request)? n Multiple Call Handling (Forced)? n PASTE (Display PBX Data on Phone)? y (NOTE: You must logoff & login
Field Call Center Release
Definition Enter a Call Center Release number that matches the set of Call Center features you want to use. If you set this field to something other than your current Call Center load, you will not have access to the latest Call Center features. Apply a new license file that has the correct version.
Note:
Note: Beginning with Communication Manager 3.0, the Call Center release numbering has been realigned to match the same release numbering scheme.
December 2011
49
Setting the adjunct CMS release (Communication Manager 3.0 and earlier)
Use the following page of the System Parameters Features form to set the Adjunct CMS Release. Depending on the switch software release, this field will be found on different pages.
change system-parameters features FEATURE-RELATED SYSTEM PARAMETERS AGENT AND CALL SELECTION MIA Across Splits or Skills? ACW Agents Considered Idle? Call Selection Measurement: Service Level Supervisor Call Selection Override? Auto Reserve Agents: ASAI Copy ASAI UUI During Conference/Transfer? Call Classification After Answer Supervision? Send UCID to ASAI? CALL MANAGEMENT SYSTEM Adjunct CMS Release: BCMS/VuStats LoginIDs? BCMS/VuStats Measurement Interval: BCMS/VuStats Abandon Call Timer (seconds): Validate BCMS/VuStats Login IDs? Clear VuStats Shift Data: Remove Inactive BCMS/VuStats Agents? Page 12 of 15
y y predicted-wait-time y none n n n RXX y half-hour 2 n on-login n
Field Adjunct CMS Release
Definition Enter the software release of the CMS computer. If you set this field to an earlier release number, you will not have access to the latest CMS features. Note: Beginning with CMS R12, the release numbering scheme dropped the "3V" designation. For example, instead of R3V12, it is now R12.
50
December 2011
Setting the reporting adjunct release (Communication Manager 3.1 and later)
Use the following page of the System Parameters Features form to set the Reporting Adjunct Release. Depending on the switch software release, this field will be found on different pages.
change system-parameters features FEATURE-RELATED SYSTEM PARAMETERS AGENT AND CALL SELECTION MIA Across Splits or Skills? ACW Agents Considered Idle? Call Selection Measurement: Service Level Supervisor Call Selection Override? Auto Reserve Agents: ASAI Copy ASAI UUI During Conference/Transfer? Call Classification After Answer Supervision? Send UCID to ASAI? CALL MANAGEMENT SYSTEM Reporting Adjunct Release: BCMS/VuStats LoginIDs? BCMS/VuStats Measurement Interval: BCMS/VuStats Abandon Call Timer (seconds): Validate BCMS/VuStats Login IDs? Clear VuStats Shift Data: Remove Inactive BCMS/VuStats Agents? Page 12 of 17
y y predicted-wait-time y none n n n XXX y half-hour 2 n on-login n
Field Reporting Adjunct Release
Definition Enter the software release of the CMS computer. If you set this field to an earlier release number, you will not have access to the latest CMS features. Note: Beginning with CMS R12, the release numbering scheme dropped the "3V" designation. For example, instead of R3V12, it is now R12.
December 2011
51
Administering data collection options

In addition to administering the switch link described in this document, you must also administer and understand the following data collection options:

Enable CMS measuring for hunt groups, trunk groups, and VDNs Assign measured extensions and multiple splits or skills Measured trunks versus unmeasured facilities Interactions with CMS measurements and IP trunk groups
For more details about these data collection options, see Forms and fields used to enable CMS measurements in Administering Avaya Aura Call Center Features.
52
December 2011
Administering a TCP/IP connection

The administration for a TCP/IP connection over a LAN is different if you are using a C-LAN circuit pack or if you are using a processor ethernet port as described in Ethernet ports on the switch on page 18. This section includes the following topics:

Administering a C-LAN connection on page 53 Administering a processor ethernet port connection on page 64 Administering a Survivable Backup CMS on page 70
Administering a C-LAN connection

Use the procedures in this section to administer a TCP/IP connection to a C-LAN circuit pack. This section contains examples of the administration forms with detailed explanations for the required fields. Use the forms in the order shown. Form change system-parameter maintenance (G3csi, DEFINITY Server CSI, DEFINITY One, and S8100 Server only) add data-module change node-names ip change ip-intefaces change communication-interface processor-channels add ip-route Purpose Adding a second packet interface
Adding an ethernet data module Adding node names and IP addresses Adding a C-LAN IP interface Adding the processor interface channels Adding IP routes (if needed)
Note:
Note: If the customer has purchased the High Availability option, you must administer a link from one ethernet port on the switch to one CMS computer, and a second link from a different ethernet port on the switch to another CMS computer.
December 2011
53

Adding a second packet interface on page 54 Adding node names and IP addresses on page 56 Adding a C-LAN IP interface on page 58 Adding an ethernet data module on page 60 Adding the processor interface channels on page 61 Adding IP routing on page 62
Adding a second packet interface

Use the Maintenance-Related System Parameters form to add a second packet interface. This is only required on G3csi, DEFINITY Server CSI, DEFINITY One, or S8100 Server.
change system-parameter maintenance MAINTENANCE-RELATED SYSTEM PARAMETERS MINIMUM MAINTENANCE THRESHOLDS ( Before Notification ) TTRs: 4 CPTRs: 1 Call Classifier Ports: 0 MMIs: 0 VCs: 0 TERMINATING TRUNK TRANSMISSION TEST ( Extension ) Test Type 100: Test Type 102: ISDN MAINTENANCE ISDN-PRI Test Call Extension: 30999 DS1 MAINTENANCE DS0 Loop-Around Test Call Extension: SPE OPTIONAL BOARDS Bus Bridge: 01A03 Packet Intf1? y Packet Intf2? y Inter-Board Link Timeslots Pt0: 6 Pt1: 1 Pt2: 1 Page 2 of 3
Test Type 105:
ISDN-BRI Service SPID:
54
December 2011
Field Packet Intf2 Bus Bridge
Definition Enter y to add a second packet interface. Enter the equipment location of the C-LAN circuit pack that does the bus bridge functionality when the packet bus is activated. This must be administered for the C-LAN to work.
Inter-Board Link Timeslots - The total number of timeslots allocated cannot greater than 11. Inter-Board Link Timeslot Pt0 Enter the number of timeslots (1-9) used by this port. Port 0 carries the bulk of messaging traffic between the switch and the CMS. The default of 6 should be adequate, but can be increased if needed to improve traffic flow. Enter the number of timeslots (1-3) used by this port. Port 1 is a low traffic port and should always be set to 1. Enter the number of timeslots (1-3) used by this port. Port 2 is a low traffic port and should always be set to 1.
Inter-Board Link Timeslot Pt1 Inter-Board Link Timeslot Pt2
December 2011
55
Adding node names and IP addresses

Use the Node Names form to assign the name and IP address of the CMS computer and any switches that are networked with the CMS computer. With the High Availability option, you will assign two switch node names and two CMS computer node names.
change node-names ip Name 3net cmshost cmshost2 default gateway gateway2 switchhost switchhost2 IP NODE NAMES Name Page 1 of 1
IP Address IP Address 192.168.3 .0 . . . 192.168.1 .90 . . . 192.168.3 .90 . . . 0 .0 .0 .0 . . . 192.168.1 .211 . . . 192.168.4 .211 . . . 192.168.1 .10 . . . 192.168.4 .10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 8 of 8 administered node-names were displayed ) Use list node-names command to see all the administered node-names Use change node-names ip xxx to change a node-name xxx or add a node-name
56
December 2011
Field Name
Definition Enter the host name of the CMS computer, any switches that are networked with the CMS computer, and any gateway hosts used in the network. The node names can be entered in any order. The names are displayed in alphabetical order the next time the form is displayed. The default node name entry is display-only and is not used for this application. For consistency, use the CMS computer host name as defined during the CMS Setup procedure. See your CMS software installation document for more information. These names are also used in the IP interfaces, data module, IP routing, and other forms. If you change the node name in this form, it is automatically updated on the other forms.
Note:
Note: Do not use special characters in the node name. Special characters are not allowed in the /etc/hosts file on the CMS computer.
IP Address
Enter the IP address of the CMS computer, the switches, and any required gateways.
!
CAUTION:
CAUTION: Plan out the network before you assign any IP addresses. Any future changes that require a change to IP addresses will cause a service disruption.
December 2011
57
Adding a C-LAN IP interface

Use the IP Interfaces form to assign a C-LAN circuit pack as an IP interface. With the High Availability option, you will assign two separate C-LAN IP interfaces.
!
CAUTION:
CAUTION: If the IP interface is already administered, do not change the administration. Changing the administration could cause failure with IP telephones and other adjunct links.
Page IP INTERFACES 1 of 1
change ip-interface XXyXX
Type: Slot: Code/Suffix: Node Name: IP Address: Subnet Mask: Gateway Address: Enable Ethernet Port? Network Region: VLAN:
C-LAN XXyXX TN799 D clan-iptarts1 10 .100.100.99 255.0 .0 .0 10 .100.100.254 y 10 n
ETHERNET OPTIONS Auto? n Speed: 10Mbps Duplex: Half
Number of CLAN Sockets Before Warning: 400
Field Enabled Type Slot Code/Sfx Node Name
Definition Enter y to enable the C-LAN IP interface. After initial administration, you must disable the interface before you make any changes. Enter C-LAN. Enter the equipment location of the C-LAN circuit pack. This is a display-only field that shows the designation number of the circuit pack installed in the specified slot. Enter the switch node name assigned on the Node Names form. In this example, enter switchhost. The same node name cannot be assigned to two different IP interfaces. Identifies which portion of an IP address is a network address and which is a host identifier. Use the default entry, or check with the LAN administrator on site if connecting through the customer LAN.
Subnet Mask
58
December 2011
Field Gateway Address
Definition Enter the address of a network node that will serve as the default gateway for the IP interface. If the application goes to points off the subnet, the gateway address of the router is required. If the switch and CMS computer are on the same subnet, a gateway is not required. If using ethernet only, and a gateway address is administered, no IP routes are required. For a C-LAN IP interface, use 1. Enter y if this is on a virtual LAN or n for a standard LAN. Enter the number of CLAN sockets available before the system issues a warning. Enter y for auto-negotiation or n for manual speed and duplex settings. Enter either 10Mbps or 100Mbps. Enter either full or half.
Net Rgn VLAN Number of CLAN Sockets Before Warning Auto Speed Duplex
December 2011
59
Adding an ethernet data module

Use the Data Module form to assign the Ethernet port of the C-LAN circuit pack.
add data-module 2000 DATA MODULE Data Extension: Type: Port: Link: 2000 ethernet 01A0317 8 Name: ethernet data module Page 1 of 1
Network uses 1s for Broadcast Address? y
Field Data Extension Type Port Link Name Network uses 1s for Broadcast Address
Definition Enter an unassigned extension number. Enter ethernet. Enter the equipment location of the C-LAN circuit pack (TN799). For the ethernet link, always use circuit 17 (for example, 01A0317). Enter a TCP/IP link number (1-25 for csi/si, 1-33 for r). This entry is also used on the Processor Channel form. Enter a name for the data module. This name will display when you list the assigned data modules. This sets the host portion of the IP address to 0s or 1s. The default is yes (all 1s). Use the default if the private network contains only Avaya switches and adjuncts. Enter n only if the network includes non-Avaya switches that use the 0s method of forming broadcast addresses.
60
December 2011
Adding the processor interface channels

Use the Processor Channel form to assign the processor channel attributes. With the High Availability option, you will assign two separate processor channels.
change communication-interface processor-channels PROCESSOR CHANNEL ASSIGNMENT Proc Gtwy Interface Destination Chan Enable Appl. To Mode Link/Chan Node Port 1: y mis s 8 5001 cmshost 0 2: y mis s 9 5001 cmshost2 0 3: n 0 4: n 0 5: n 0 6: n 0 7: n 0 8: n 0 9: n 0 10: n 0 11: n 0 12: n 0 13: n 0 14: n 0 15: n 0 16: n 0 Page 1 of X Mach ID
Session Local/Remote 1 1 2 2
Field Proc Chan
Definition Select a processor channel for this link. The standard CMS provisioning procedure is to use channel 1 on G3r or DEFINITY Server R, and channel 10 on G3csi, DEFINITY Server CSI, G3si, or DEFINITY Server SI. Enter y. Enter mis. Leave blank for the local CMS-to-switch link. Enter s for server. Enter the TCP/IP link number used on the ethernet data module form. Enter the TCP channel number (5000-64500). The default for CMS is 5001 and is defined during CMS setup. See your CMS software installation document for more information. Enter the node name of the CMS computer as assigned on the Node Names form. In these examples, cmshost is used. Use the default of 0.
Enable Appl Gtwy To Mode Interface Link Interface Chan
Destination Node Destination Port
December 2011
61
Field Session Local/ Session Remote
Definition The local and remote port assignments must be symmetrical between the switch and the CMS. The standard CMS provisioning procedure is to set the local and remote port assignments equal to the switch processor channel used for this link. For example, if you use processor channel 10, set the local and remote port to 10. Not used for CMS.
Mach ID
Adding IP routing
Use the IP Routing form to set up the IP routes from the switch to the CMS computer. This is required when:

The switch and the CMS computer are on different subnets, or When a Gateway Address is not administered for the C-LAN IP interface.
The following example shows an IP route. This route shows how you get from a gateway (for example, a router) to a network.
add ip-route 1 IP ROUTING Route Number: Destination Node: Network Bits: Gateway: Board: Metric: Route Type: 1 3net 24 Subnet Mask: 255.255.0 gateway2 01C02 0 Network Page 1 of 1
.0
Field Route Number
Definition If you are going through a router, you must set up IP route 1 from the switch to the router and set up IP route 2 from the switch to the CMS computer. The example above shows a simple IP route. This field represents the node name of the destination for this route. You would typically enter the node name for the CMS computer or a router, depending on your configuration. Enter a value from 0-30. Enter a subnet mask.
Destination Node
Network Bits (R1.1 and later) Subnet Mask (R1.1 and later)
62
December 2011
Field Gateway
Definition Enter the node name of the gateway by which the destination node is reached for this route. This is either the local C-LAN port of the first intermediate node between the C-LAN port and the final destination. For example, if there were one or more routers between the C-LAN port and the final destination node (the CMS computer), the gateway would be the node name of the first router. Enter the equipment location of the C-LAN circuit pack that provides this route. It is possible to have more than one C-LAN circuit pack, but most configurations will only have one C-LAN. Specifies the complexity of this IP route. Enter 0 if there are no intermediate nodes between the C-LAN port and the ethernet port on the CMS computer. A metric value of 1 is used only on a switch that has more than one C-LAN circuit pack installed. See Administration for Network Connectivity for more information about using this field.
C-LAN Board
Metric
December 2011
63
Administering a processor ethernet port connection

Use the procedures in this section to administer a TCP/IP connection over a LAN when connected to a processor ethernet port. If the processor ethernet port is not enabled, you must apply a new license file to the switch.
display system-parameters customer-options OPTIONAL FEATURES Multinational Locations? n Multiple Level Precedence & Preemption? n Multiple Locations? n Personal Station Access (PSA)? Posted Messages? PNC Duplication? Port Network Support? n y n n Page 5 of 11
Station and Trunk MSP? n Station as Virtual Extension? n System Management Data Transfer? Tenant Partitioning? Terminal Trans. Init. (TTI)? Time of Day Routing? Uniform Dialing Plan? Usage Allocation Enhancements? TN2501 VAL Maximum Capacity? n n n n y y y
Processor and System MSP? n Private Networking? y Processor Ethernet? y Remote Office? n Restrict Call Forward Off Net? y Secondary Data Module? y
Wideband Switching? n Wireless? n
(NOTE: You must logoff & login to effect the permission changes.)
Field Processor Ethernet
Definition Verify that the processor ethernet port is enabled.
64
December 2011
Displaying the processor ethernet port

Use the IP Interfaces form to display the IP address to the processor ethernet port. Use this form to verify that the IP interface has been administered.
!
CAUTION:
CAUTION: In most cases, the IP interface is already administered. Do not change the administration. Changing the administration could cause failure with IP telephones and other adjunct links.
display ip-interface procr IP INTERFACES
Type: PROCR
Node Name: procr IP Address: 192.9 .22 .245 Subnet Mask: 255.255.255.0 Enable Ethernet Port? y Network Region: 1
December 2011
65
Adding node names and IP addresses

Use the Node Names form to assign the name and IP address of the CMS computer and any gateways that are networked with the CMS computer. With the High Availability option, you will assign two CMS computer node names.
change node-names ip Name 3net cmshost cmshost2 default gateway gateway2 IP NODE NAMES Name Page 1 of 1
IP Address IP Address 192.168.3 .0 . . . 192.168.1 .90 . . . 192.168.3 .90 . . . 0 .0 .0 .0 . . . 192.168.1 .211 . . . 192.168.4 .211 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 8 of 8 administered node-names were displayed ) Use list node-names command to see all the administered node-names Use change node-names ip xxx to change a node-name xxx or add a node-name
66
December 2011
Field Name
Definition Enter the host name of the CMS computer and any gateway hosts used in the network. The processor ethernet port can be displayed on this form, but cannot be changed. The node names can be entered in any order. The names are displayed in alphabetical order the next time the form is displayed. The default node name entry is display-only and is not used for this application. For consistency, use the CMS computer host name as defined during the CMS Setup procedure. See your CMS software installation document for more information. These names are also used in the IP interfaces, data module, IP routing, and other forms. If you change the node name in this form, it is automatically updated on the other forms.
Note:
Note: Do not use special characters in the node name. Special characters are not allowed in the /etc/hosts file on the CMS computer.
IP Address
Enter the IP address of the CMS computer and any required gateways.
!
CAUTION:
CAUTION: Plan out the network before you assign any IP addresses. Any future changes that require a change to IP addresses will cause a service disruption.
December 2011
67
Adding the processor interface channels

Use the Processor Channel form to assign the processor channel attributes. With the High Availability option, you will assign two separate processor channels.
change communication-interface processor-channels PROCESSOR CHANNEL ASSIGNMENT Proc Gtwy Interface Destination Chan Enable Appl. To Mode Link/Chan Node Port 1: y mis s p 5001 cmshost 0 2: n 0 3: n 0 4: n 0 5: n 0 6: n 0 7: n 0 8: n 0 9: n 0 10: n 0 11: n 0 12: n 0 13: n 0 14: n 0 15: n 0 16: n 0 Page 1 of X Mach ID
Session Local/Remote 1 1
Field Proc Chan Enable Appl Gtwy To Mode Interface Link Interface Chan
Definition Select a processor channel for this link. Enter y. Enter mis. Leave blank for the local CMS-to-switch link. Enter s for server. Enter p for the processor ethernet port. Enter the TCP channel number (5000-64500). The default for CMS is 5001 and is defined during CMS setup. See your CMS software installation document for more information. Enter the node name of the CMS computer as assigned on the Node Names form. In these examples, cmshost is used. Use the default of 0.
Destination Node Destination Port
68
December 2011
Field Session Local/ Session Remote
Definition The local and remote port assignments must be symmetrical between the switch and the CMS. The standard CMS provisioning procedure is to set the local and remote port assignments equal to the switch processor channel used for this link. For example, if you use processor channel 10, set the local and remote port to 10. Not used for CMS.
Mach ID
December 2011
69
Administering a Survivable Backup CMS

Use the Survivable Processor form to associate a survivable backup CMS for either:

a CLAN port on a specific ESS server, or a processor ethernet port on a specific ESS or LSP server
The Survivable Processor form is administered on the main server. The translations are sent to the ESS server or LSP during a file sync. After the file sync, the information on Page 2 is used by the LSP or the ESS server to connect to the CMS. Note: For more information about the Survivable CMS offer, contact Avaya Professional Services.
Note:
On Page 1 of the form, everything but the Network Region is prepopulated based on what was already administered on the Node Name form and the System Parameters ESS form.
add survivable-processor ESS1 SURVIVABLE PROCESSOR - PROCESSOR ETHERNET Node Name: IP Address: ID: Type: ESS1 192.0.9.0 30 LSP Page 1 of 4
Network Region: 1
Field Network Region
Definition Enter the network region in which the LSP or ESS server resides.
70
December 2011
Use Page 2 of the Survivable Processor form to administer the CMS that is connected to a CLAN or processor ethernet interface.
add survivable-processor ESS1 SURVIVABLE PROCESSOR - PROCESSOR CHANNELS Proc Chan Enable 1: y 2: n 3: n 4: n 5: n 6: n 7: n 8: n 9: n 10: n 11: n 12: n 13: n 14: n 15: n 16: n Interface Mode Link/Chan s p 5001 Destination Node Port cmshost 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Page 2 of 4
Appl. mis
Session Local/Remote 7 7
Field Proc Chan Enable
Definition Displays the processor channel for this link. Enter one of the following values in this field: Enter n if this processor channel is disabled on the LSP or the ESS server. Enter i (inherit) if this link is to be inherited by the LSP or ESS server. Generally, you would use the inherit option in the following cases: - The main server connects to the adjuncts using a CLAN and you want the ESS server to use the same connectivity. - The main server connects to the adjuncts using the main servers PE interface and you want the LSP or ESS server to connect to the adjunct using its PE interface. Enter an o (override) to override the processor channel information sent in the file sync from the main server. The override option causes the near-end (servers end of the link) address of the link to change to a p when the translations are sent from the main server to the LSP or the ESS server. Generally, you would want the override option when an adjunct connects to the main server using a CLAN and you want the adjunct to connect to the LSP or the ESS servers processor ethernet interface. When you enter an o in the enable field, you can enter the processor channel information for the LSP or the ESS server in the remaining fields. Displays mis.
Appl
December 2011
71
Field Mode Interface Link Enter s for server.
Definition
Enter p in this field when the physical link is the processor ethernet interface on an LSP or ESS. Enter the CLAN link number when the physical link is a CLAN on an ESS. Enter the TCP channel number (5000-64500). The default for CMS is 5001 and is defined during CMS setup. See your CMS software installation document for more information. Enter the node name of the CMS computer as assigned on the Node Names form. In these examples, cmshost is used. Use the default of 0. The local and remote port assignments must be symmetrical between the switch and the CMS. The standard CMS provisioning procedure is to set the local and remote port assignments equal to the switch processor channel used for this link. For example, if you use processor channel 10, set the local and remote port to 10.
Interface Chan
Destination Node Destination Port Session Local/ Session Remote
72
December 2011
Troubleshooting TCP/IP switch connections

TCP/IP link troubleshooting can be done at the switch and at the CMS computer. This section describes tests you can run from either system. The information in this section includes:

Switch administration on page 73 Switch tests on page 74 CMS computer tests on page 76
Switch administration
Check all switch administration. See the following sections:

Administering a TCP/IP switch link on page 41 Verifying the software version on page 48 Setting the adjunct CMS release (Communication Manager 3.0 and earlier) on page 50 Setting the reporting adjunct release (Communication Manager 3.1 and later) on page 51.
With Communication Manager 3.1, you have the option to set the CMS adjunct release to either R13 or R13.1. R13 features are compatible with Communication Manager 3.0 and R13.1 features are compatible with Communication Manager 3.1. When selecting the CMS adjunct release, make sure that the features you want to use are compatible with the Communication Manager and Call Center Release. For example, if you want to use features specific to Communication Manager 6.0, the Reporting Adjunct Release on the switch should be set to R16.x, the ACD on the CMS must be administered as Communication Manager 6.0, and the CMS installed must be r16.xyy.y.
December 2011
73
Switch tests
Using the system administration terminal on the switch, you can use the following commands to test the TCP/IP link: ping ip-address X.X.X.X board CCs [packet-length YYYY repeat ZZZ] (where X.X.X.X is the IP address of the CMS computer, CCs is the equipment location of the C-LAN circuit pack, YYYY is the size of the test packet, and ZZZ is the number of times the test will be repeated) The packet length and repeat options are available with R8 or later. This command sends a test message to the specified IP address to request a remote echo. The results will be either pass or fail, and will show how long the test took to complete. The packet length defaults to 64 bytes, with a maximum of 1500 bytes. ping node-name XXX board CCs [packet-length YYYY repeat ZZZ] (where XXX is the node name of the CMS computer, CCs is the equipment location of the C-LAN circuit pack, YYYY is the size of the test packet, and ZZZ is the number of times the test will be repeated) The packet length and repeat options are available with R8 or later. This command sends a test message to the specified node name to request a remote echo. The results will be either pass or fail, and will show how long the test took to complete. The packet length defaults to 64 bytes, with a maximum of 1500 bytes. netstat ip-route This command displays the destination IP address, gateway IP address, C-LAN circuit pack used for the route, and the interface for the route. status processor-channels X (where X is the processor channel used for the TCP/IP link) This command displays the current status of the processor channel used for the TCP/ IP link, and the last time and reason that the channel went down. status link X (where X is the TCP/IP link number) This command displays the status for the TCP/IP link. Page 1 of the test shows whether the link is connected and is in service. Page 3 of the test shows whether the link is up or down. If the link is not up, there is a problem in translations or connectivity. status data-module XXXX (where XXXX is the extension number of the ethernet data module) This command displays the status for the ethernet data module. This shows which port is connected and if the port is in service.
74
December 2011
Switch tests
status sys-link CCsc (where CCsc is the cabinet, carrier, slot, and circuit of the system link in question) This command displays the status data for a specific system link. Each system link can be listed using the list sys-link command. The status includes the type and operational state of the link, the associated processor channel (if any), active alarms and path status, and a list of all hardware components that make up the link path. status packet This command displays the packet interface status. trace-route [ip-address X.X.X.X] [node-name nodename] board CCs (where X.X.X.X is the IP address of the CMS computer, nodename is the node name of the CMS computer, and CCs is the cabinet, carrier, and slot number of the C-LAN circuit pack) This command works for R8 or later using the TN799B C-LAN circuit pack. This command displays the hops traversed from source to destination, along with the IP addresses of the hop points and final destination, and the observed round-trip delay from the source to each hop point. If no reply is received from a hop point, the IP address is blank. list measurements clan ethernet CCsc (where CCsc is the cabinet, carrier, slot, and circuit number of the ethernet port on the C-LAN circuit pack) This command works for R8 or later. This command displays Cyclic Redundancy Check and collision counts for the past 24 hours in 15-minute intervals. N/A is displayed if the data cannot be retrieved for any interval.
Additional references
See the switch maintenance documents for more details on these test commands.
December 2011
75
CMS computer tests

Using the system console on the CMS computer, you can use the following commands to test the TCP/IP link. More information about the UNIX commands can be found by printing out the manual pages (man command). netstat This command displays general network status information. ping X.X.X.X (where X.X.X.X is the IP address of the switch) This command sends a test message to the specified IP address to request a remote echo. The results will be either alive or no answer. ping XXX (where XXX is the node name of the switch) This command sends a test message to the specified node name to request a remote echo. The results will be alive, no answer, or unknown host. traceroute X.X.X.X (where X.X.X.X is the IP address of the switch) This command traces the route that an IP packet follows from the CMS computer to the switch. There are more options to the command other than the IP address. Check the manual page for traceroute for more options. snoop This command allows you to capture and inspect network packets. spray hostname (where hostname is the name of the switch) This command sends a stream of packets to a selected host, and reports how many were received and the transfer rate. Maintenance > Connection Status (from CMS Main Menu) This CMS command displays status information for the switch links. /usr/sbin/ndd /dev/tcp tcp_smallest_anon_port tcp_largest_anon_port This command allows you to display the possible range of talk ports randomly assigned by the CMS when communicating with the switch. These ports are called ephemeral ports. You should also check the /etc/hosts and /etc/defaultrouter files to verify that the IP addresses and host names are accurate.
76
December 2011
Glossary
Automatic Call Distribution (ACD) A switch feature. ACD is software that channels high-volume incoming call traffic to agent groups (splits or skills). Also an agent state where the extension is engaged in an ACD call, with the agent either talking to the caller or the call waiting on hold. CMS Call Management System (CMS). A software product used by business customers that have an Avaya telecommunications switch and receive a large volume of telephone calls that are processed through the Automatic Call Distribution (ACD) feature of the switch. The HSI controller card is a 4-port serial communications card. Each of the four ports is used for a single physical X.25 link. It is an add-on package that is needed by CMS for multiple ACDs. A group of extensions that receive special-purpose calls in an efficient, cost-effective manner. Normally, calls to a split arrive over one or a few trunk groups. A private switch system providing voice-only or voice and data communications services (including access to public and private networks) for a group of terminals within a customer premises. Technical Service Center. The Avaya organization that provides technical support for Avaya products. A communications protocol that provides interworking between dissimilar systems. It is the de facto standard for UNIX systems.
High Speed Serial Interface (HSI) Split
Switch
TSC Transmission Control Protocol/ Internet Protocol (TCP/IP)
December 2011
77
Transmission Control Protocol/Internet Protocol (TCP/IP)
78
December 2011
Index
Index
A
administering data collection options . . . . . . . . . . . . . 52 LAN (R7 and later) . . . . . . . . . . . . . . . 53
C
common G3 switch administration. . . . . . . . . . 46 connecting LAN Generic 3 (R7 and later) . . . . . . . . . . . 17 one or more ACDs using a LAN . . . . . . . . . 17
D
data collection options . . . . . . . . . . . . . . . 52
G
Generic 3 (R7 and later) administering a LAN . . . . . . . . . . . . . . 53 connecting a LAN . . . . . . . . . . . . . . . . 17 Glossary . . . . . . . . . . . . . . . . . . . . . 77
H
helplines . . . . . . . . . . . . . . . . . . . . . 10 high availability option . . . . . . . . . . . . . . 14, 42
L
LAN (R7 and later) administration . . . . . . . . . . . . . . . . . 53 connections . . . . . . . . . . . . . . . . . . 17
M
multiple ACDs (switches) . . . . . . . . . . . . . 14, 42
T
TCP/IP testing CMS . . . . . . . . . . . . . . . . . . . . . . 76 switch . . . . . . . . . . . . . . . . . . . . . 74 traceroute . . . . . . . . . . . . . . . . . . . . . 75
December 2011
79
Index
80
December 2011

Avaya Call Management System: Switch Connections, Administration, and Troubleshooting

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Avaya Call Management System: Switch Connections, Administration, and Troubleshooting

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Avaya Call Management System: Switch Connections, Administration, and Troubleshooting

Uploaded by

Copyright:

Available Formats

Avaya Call Management System

Switch Connections, Administration, and Troubleshooting

Avaya CMS Switch Connections, Administration, and Troubleshooting

Administering data collection options . . . . . . . . . . . . . . . . . . . . . . . . . . .

Avaya CMS Switch Connections, Administration, and Troubleshooting

Avaya CMS Switch Connections, Administration, and Troubleshooting

Avaya CMS Switch Connections, Administration, and Troubleshooting

Avaya support personnel Contact center administrators

Avaya CMS Switch Connections, Administration, and Troubleshooting

Conventions and terminology

Avaya CMS Switch Connections, Administration, and Troubleshooting

Reasons for reissue

Reasons for reissue

Documentation Web sites

Information about Avaya products and service http://www.avaya.com

Avaya CMS Switch Connections, Administration, and Troubleshooting

Sun hardware documentation http://docs.sun.com

Escalating a technical support issue

Avaya CMS Switch Connections, Administration, and Troubleshooting

Switch and CMS release compatibility

Yes Yes Yes No No No No No No

Avaya CMS Switch Connections, Administration, and Troubleshooting

Switch and CMS release compatibility

Avaya CMS Switch Connections, Administration, and Troubleshooting

Connecting a TCP/IP switch link

Overview on page 13 Switch connections with TCP/IP over a LAN on page 17

Avaya CMS Switch Connections, Administration, and Troubleshooting

Connecting a TCP/IP switch link

Local vs remote connections

Multiple ACDs (switches)

High availability option

Avaya CMS Switch Connections, Administration, and Troubleshooting

Planning for TCP/IP switch links

- Customer LAN with private segment.

- Direct connect to Customer LAN, without private segment.

Avaya CMS Switch Connections, Administration, and Troubleshooting

Connecting a TCP/IP switch link

- Customer network administration:

Network administration information needs to be mapped into specific administration fields.

Avaya CMS Switch Connections, Administration, and Troubleshooting

Switch connections with TCP/IP over a LAN

Switch connections with TCP/IP over a LAN

This section includes the following topics:

Connecting one or more ACDs using TCP/IP over a LAN

Avaya CMS Switch Connections, Administration, and Troubleshooting

Connecting a TCP/IP switch link

Ethernet ports on the switch

Avaya CMS Switch Connections, Administration, and Troubleshooting

Switch connections with TCP/IP over a LAN

Ethernet ports on a CMS computer

LAN speeds - 10 Mbps vs 100 Mbps

Avaya CMS Switch Connections, Administration, and Troubleshooting

Connecting a TCP/IP switch link

C-LAN lead designations for cross-connects

TD+ TDRD+ RD-

white/orange orange/white white/green green/white

Avaya CMS Switch Connections, Administration, and Troubleshooting

Switch connections with TCP/IP over a LAN