Switch Integration Requirements

Overview

This section contains information about switch integration processes, terms, and requirements, including:

• An explanation of switch integration and the links available for use with DEFINITY� Enterprise Communications Server (ECS) switches
• A list of supported features
• An explanation of Distributed Communications System (DCS) operations
• Configuration diagrams showing the basic setup methods for connection through a local area network (LAN) link

Purpose

The information in this section will help you to understand the basic requirements of the LAN link switch integration before administering the integration.

Introduction

Switch integration is the sharing of information between a voice messaging system and a switch to provide a seamless interface to callers and subscribers. A fully integrated voice messaging system uses information sent from the switch to answer telephone calls and also sends information back to the switch.

Information from the switch allows the Intuity AUDIX system to react to telephone calls arriving on analog voice ports. Depending on the information received, the Intuity AUDIX system plays a greeting, provides an automated attendant, permits a subscriber to retrieve messages, or directs unanswered incoming telephone calls to the correct mailbox.

The Intuity AUDIX system also sends information back to the switch. This information tells the switch to update message waiting indicators (MWIs) or to transfer the telephone call to another extension.

If the Intuity AUDIX system does not receive information from or send information to the switch, it is nonintegrated. If the system is nonintegrated, callers must enter the extension number for the mailbox or service that they want to reach. Also, they cannot transfer through the Intuity AUDIX system to another extension. When the link between the switch and the Intuity AUDIX system is down, calls will still cover to the Intuity AUDIX system but the calls are treated as nonintegrated calls.

Integration Types for DEFINITY Communications Systems

The Intuity AUDIX system uses different types of switch integrations for different types of switches. For DEFINITY Enterprise Communications Server (ECS) switches, an Intuity AUDIX system can use one of the following integrations:

• LAN link
• DCIU link
• Mode code (inband) communication

The Intuity AUDIX system supports the use of only one type of switch integration on a single Intuity AUDIX system at a time, although the DEFINITY ECS switches can support more.

LAN Link

The LAN link allows the DEFINITY ECS and the Intuity AUDIX system to communicate over a private, dedicated LAN or by using a customer's LAN. The DEFINITY ECS is a server, and the Intuity AUDIX system is a client that always initiates the communications session. This link uses a LAN circuit card installed in the Intuity AUDIX system and a C-LAN circuit pack (TN799 or later) installed in the DEFINITY ECS. The two systems use TCP/IP and a specialized DEFINITY protocol to communicate. The LAN link provides the same functionality as a DCIU link.
 

Note: To use the LAN link, the DEFINITY ECS must be Release 7 or later and equipped with a C-LAN circuit pack (TN799 or later). The Intuity AUDIX system must be Release 4.4 or later and equipped with a LAN interface card.

Digital Communications Interface Unit Link

The Digital Communications Interface Unit (DCIU) link allows the Intuity AUDIX system and a DEFINITY Communications System or ECS to communicate digitally over a serial RS-232 interface using BX.25 (X.25) signaling. This link uses a DCIU or EICON circuit card installed in the Intuity AUDIX system and cabled to a Avaya System 75, DEFINITY Communication System Generic 1 (G1), Generic 3 (G3), DEFINITY ECS Release�5/6 (R5/6). Release 7 (R7) or later systems can also support DCIU integrations if the appropriate hardware is available, as in the case of upgraded switches.
 

Note: The Release 6 and later csi switches do not support a DCIU link.

DCIU is also referred to as Switch Communication Interface (SCI), Processor Interface (PI), Packet Gateway (PGATE), and X.25.

Mode Code (Inband)

The mode code (inband) link allows the Intuity AUDIX system and a DEFINITY ECS to communicate using the same analog telephone lines that connect the two systems for call answer and message retrieval. This integration uses touch tone signaling, call-progress signals, and switch hook flashes over the ordinary tip and ring analog wiring to transfer information about the telephone call between the two systems. This integration does not require a separate signaling link as needed for DCIU or LAN integrations.

Features Overview

The table for Comparison of Integration Types summarizes the features available with the different types of integrations for DEFINITY systems.
 

Table: Comparison of Integration Types

Function	DCIU and LAN	Mode Code	Mode Code Notes
Connection Information:
Calling Party ID	Yes	Yes
Called Party ID	Yes	Yes
Internal vs. External Call	Yes	Yes	Can provide internal and external personal greetings.
Direct vs. Redirected Call	Yes	Yes
Busy vs. No Answer	Yes	No	Cannot provide personal greeting for busy/no answer.
Call Disconnect Message	Yes	No	Mode Code uses "wink" online.
Distributed Communications Networking	Yes	No
MWI Control
Message Waiting Indicator (MWI) Status	Yes	No	Cannot provide "Integrated Notification" of new messages in other services, such as Message Center or LWC on switch.
MWI On/Off	Yes	Yes
MWI Audit	Yes	No	Can refresh one at a time.
Transfer Type
Transfer Out of AUDIX	Enhanced	Basic	Basic transfer through switch-hook flash. Possibility of toll fraud.1
Transfer Into AUDIX	NA	NA	Functionality is provided by switch.
Maintenance Features:
Call Screening/Bridging	No	No
*R for Call Answer	Yes	Yes
Busy Out Voice Ports	Yes	No
"Link Alive" Messages	Yes	No
Time of Day Clock Sync	Yes	No
DCS Transparency	Yes	No	Future work for Mode Code switches.
Digital Networking	NA	NA	Not dependent on switch integration.

1 With "Basic Transfer," calls transferred to the switch look like direct calls from the Intuity AUDIX system. They follow the switch's coverage path for the "transfer-to" destination. With "Enhanced Transfer," the Intuity AUDIX system provides the original calling and called party information, along with an indication of whether the switch should allow the call to follow the coverage path for the destination endpoint. Since basic transfer does not provide this information, it can potentially increase the risk of toll fraud. Always monitor your system for evidence of toll fraud and take corrective action immediately if you suspect that there could be a problem.

Distributed Communications System Operations

The Intuity AUDIX system can work with a maximum of 20 DEFINITY switches if the switches are connected in a Distributed Communications System (DCS) network. A DCS network is an arrangement that allows multiple switches in the same or remote locations to work together as one switch. To make DCS networking operate, switches share the same uniform dialing plan and send call information over signaling links between the systems. The following table lists the types of connections possible with each DEFINITY model and adjunct endpoints.
 

Table: Comparison of Connection Types and Supported Endpoints

DEFINITY ECS Model	Connection Type	Endpoint
R7csi and later	Ethernet	CMS, Intuity AUDIX System, DCS
	Synchronous PPP	DCS
	ISDN/PRI DS0	DCS+
R7si and later	Ethernet	CMS, Intuity AUDIX System, DCS
	Synchronous PPP	DCS
	ISDN/PRI DS0	DCS+
	BX.25	CMS, Intuity AUDIX System, DCS, DEFINITY AUDIX
R7r and later	Ethernet	CMS, Intuity AUDIX System, DCS
	Synchronous PPP	DCS
	ISDN/PRI DS0	DCS+
	BX.25	CMS, Intuity AUDIX System, DCS, DEFINITY AUDIX
Pre-R7 Switches	BX.25	CMS, Intuity AUDIX System, DCS, DEFINITY AUDIX
	ISDN/PRI DS0	DCS+

In a DCS network, extensions on the local switch receive telephone calls from remote extensions as if the remote extension were on the local switch. Callers receive names or extensions on their displays and can use some of the features on the remote switch.
 

Note: Detailed examples of the following types of DCS networks include: Traditional D-channel (private network only and public network access/egress) Integrated (private or public networks) See DEFINITY ECS Release 8 Administration for Network Connectivity, 555-233-501, Issue 2, for descriptions of these types of networks.

General DCS Communications with a Intuity AUDIX System

In a DCS network with a Intuity AUDIX system, the Intuity AUDIX system connects directly to only one switch. That switch is referred to as the "host" switch, and all other switches in the DCS network are "remote." In this book, the host switch is assumed to be a DEFINITY ECS R7 switch or later. Remote switches can be different releases of the DEFINITY switch product line, and the switches can be in the same or a different geographical location. A remote switch does not need to have a direct data link connection to the Intuity AUDIX system to use the Intuity AUDIX system.

In a DCS network, logical paths on physical links provide connectivity for the transmission of message information between each switch and the Intuity AUDIX system through the host switch. See the figure for DCS Network for an illustrated example of a DCS network.

DCS network connectivity is as follows:

• The host switch and the Intuity AUDIX system exchange messages over Logical Path 1.
• Using a LAN link, the remote switch and the Intuity AUDIX system exchange messages over the same logical path (not shown in this diagram). The data messages are carried over a LAN between the systems.
• Using an X.25 or ISDN link, the remote switch and the Intuity AUDIX system exchange messages over Logical Path 2. For X.25, the data messages are carried over dedicated facilities between the systems. For ISDN, the data messages are carried over DS1 tie trunks.
• Using a Mode Code link, the remote switch and the Intuity AUDIX system exchange messages over the DCS tie trunks to the host switch, and then over the voice lines to the Intuity AUDIX system. The data messages are also carried over the same lines.
• The host switch and the remote switch exchange messages over Logical Path 3.
• The remote Intuity AUDIX system hunt group can be a coverage point in a call coverage path at a remote switch that is in the DCS network.

Use DEFINITY ECS Release 8 Administration for Network Connectivity, 555-233-501, Issue 2, to establish and administer the basic DCS network. Use this book to add the Intuity AUDIX system to an existing DCS network.

DCS Networking with a LAN Link Between the Host Switch and the Intuity AUDIX System

When a LAN link is in use between the host switch and the Intuity AUDIX system, the DCS network can use DCIU (X.25, BX.25), ISDN PRI, or LAN links to the remote switches from the host. Each remote switch is associated with an internal, administrable TCP port on the host switch so that the host switch can provide gateway services. Gateway services convert the protocols used in other DCS connections to a protocol that operates with the LAN link. Because of the protocol conversion, earlier version switches operating with other protocols can remain in a DCS network and use existing connections if the DEFINITY ECS R7 or later is equipped with a TN577 Packet Gateway (r) or TN765 Processor Interface (si) circuit pack. If the DEFINITY ECS R7 or later does not have these circuit packs installed, DCIU connections in an existing DCS network need to be removed and replaced with LAN connections using the C-LAN (TN799 or later) circuit pack.

The Intuity AUDIX system on the host switch has separately administered logical channels to each of the supported remote switches mapped to TCP ports on the host switch. This administration allows the Intuity AUDIX system to communicate with the remote switches.

The LAN integration into a DCS network allows the Intuity AUDIX system to support a total of 20 DCS switches. For Release 4.4 and earlier, the switches are numbered from 1 to 20 on the Intuity AUDIX system. For Release 5, the 20 switches can be numbered from 1 to 64. The number must match the number assigned on the DEFINITY ECS. All Intuity AUDIX system features can be activated from both the host and remote switches.

In a network in which a remote switch is connected to the host by a LAN link, the Intuity AUDIX system can send message waiting indicator (MWI) information directly to a remote switch over the LAN. All other information, however, must be sent through the host switch.

LAN Link Connectivity

The LAN link integration requires use of an Ethernet connection to the DEFINITY ECS. The initial release of the integration over the LAN link supports 10baseT (10 Mbps) connectivity only. The Intuity AUDIX system can be connected in a public network or a private network.

Use of the C-LAN Circuit Pack (TN799 or Later) with the Intuity AUDIX System

The DEFINITY ECS R7 or later can support two C-LAN circuit packs. Each C-LAN circuit pack (TN799 or later) can support 17 ports per circuit pack. Of these ports, only one port supports an Ethernet connection required for use with the Intuity AUDIX system. The Intuity AUDIX system LAN link does not operate with the synchronous point-to-point protocol (PPP) provided by the other ports. The other ports can be used for other DEFINITY ECS switches for PPP connection as a part of a DCS network.

DEFINITY TCP Ports

The DEFINITY ECS relies on internal, administered TCP ports to process the information being sent to and from the Intuity AUDIX system. All DEFINITY switches on the LAN should use TCP Port 5002 as the port to the Intuity AUDIX system. If the system will be part of a DCS network, the each remote switch should use the same TCP port number, 5003, since each switch on the LAN has a distinct IP address. For non-IP remote switches, the same host switch will act as the gateway, and a TCP Port number in the range from 6001 to 6999 must be assigned for each switch.

LAN Connectivity Methods

The LAN link connectivity will be done in one of several ways:

• A direct connection from the Intuity AUDIX system's LAN circuit card, using a crossover cable, to the C-LAN circuit pack (TN799 or later) installed in the DEFINITY ECS
• One connection from the Intuity AUDIX system's LAN circuit card, through a dedicated 10baseT Ethernet hub, to the C-LAN circuit pack (TN799 or later) installed in the DEFINITY ECS
• One connection from the Intuity AUDIX system's LAN circuit card to the customer's LAN and a separate connection from the customer's LAN to the C-LAN circuit pack (TN799 or later) installed in the DEFINITY ECS

All of these configurations support the use of DCS networking.

Direct Connectivity

The Intuity AUDIX system can connect to the DEFINITY ECS using a simple crossover cable. See the figure for Direct Connectivity for an example. On the Intuity AUDIX system side, the connection is from the LAN circuit card to the hub. On the DEFINITY ECS side, the connection is from the C-LAN circuit pack (TN799 or later) to the hub.

Dedicated Hub Connectivity

The Intuity AUDIX system can connect to the DEFINITY ECS using a dedicated�10baseT hub. See the figure for Dedicated Hub Connectivity. On the Intuity AUDIX system side, the connection is from the LAN circuit card to the hub. On the DEFINITY ECS side, the connection is from the C-LAN circuit pack (TN799 or later) to the hub.

Customer LAN Connectivity

The Intuity AUDIX system can connect to a router on the customer LAN. In this configuration, the DEFINITY ECS C-LAN circuit pack (TN799 or later or TN799B) also connects to the customer LAN. See the figure for Customer LAN Connectivity.

DCS Connectivity

The Intuity AUDIX system can be connected for use with a Distributed Communications System (DCS) network either directly to the LAN or to the host switch through the LAN. The Intuity AUDIX system is associated with the host switch because of the voice ports connected between the systems and the hunt group on the host switch that redirects calls to those voice ports.

In the network, only a DEFINITY ECS that is connected to the Intuity AUDIX system on the LAN and configured to provide gateway services can serve as the host switch. Gateway services allow DCS networking operations with remote switches connected to the host through LAN, DCIU (X.25 and BX.25), and ISDN PRI D-Channel links, making it unnecessary to connect remote switches to the LAN. Gateway services also provide translation and forwarding facilities on separate TCP logical ports on the host DEFINITY. The TCP logical ports are administered on both the Intuity AUDIX system and the DEFINITY ECS.

If another DEFINITY ECS in the DCS network is connected to the LAN, the DEFINITY ECS can receive MWI updates directly from the Intuity AUDIX system over the LAN. However, it must receive messages from the Intuity AUDIX system through the host switch for all other activities.

The figure for DCS Connectivity shows an example of a DCS network with the host switch and the Intuity AUDIX system integrated over a LAN. This configuration provides Intuity AUDIX messaging transparency in a DCS network. It consists of a single Intuity AUDIX system connected to multiple switches via a host or gateway switch. The voice lines to and from the Intuity AUDIX system terminate in a Uniform Call Distribution (UCD) group on the host switch. Thus, the host switch is a tandem point for all voice connections between the Intuity AUDIX system and the other remote switches in the DCS network.
 

Note: This document does not take into account administration of the DEFINITY ECS in an Expert Agent Selection (EAS) environment. Contact the Design Center for assistance in planning a system using either of those two features.

This example is used as the basis for the procedures given in Administration for Switch-to-Intuity AUDIX System Link and DCS Administration. See the procedures in those sections for examples of how you would administer the different types of switches to communicate with the Intuity AUDIX system.

Analog Connectivity

Analog connectivity involves the wiring from the DEFINITY analog ports to the Intuity AUDIX analog ports. This wiring carries the voice and multimedia components of messages coming into or leaving the Intuity AUDIX system.

Use of DEFINITY ECS Circuit Packs That Do Not Support the Intuity AUDIX System

Do not use the following DEFINITY circuit packs for analog ports connected to the Intuity AUDIX system:
 

Use of the following circuit packs will cause the integration to fail.

• TN746

Do not connect the voice ports to TN746 circuit packs. The TN746 circuit pack uses 24 Volts and does not work. Connection to the TN746 causes the Intuity AUDIX system to go into alarm. The Intuity AUDIX system requires 48 Volts which is supplied by the TN746B circuit pack.

• TN793 vintage 5 or earlier, or TN2793 vintage 3 or earlier

Do not connect the voice ports to these vintages of the TN793 or TN2793 circuit packs. These circuit packs have a problem related to neon message waiting lamps (causes electrical damage) and cut-through timing (results in possible toll fraud issues). Later vintages of these circuit packs will work.

Use of DEFINITY ECS Circuit Packs That Support the Intuity AUDIX System

The following analog port circuit packs support the Intuity AUDIX system:

• TN746B vintage 8 or later
• TN742
• TN793 vintage 6 or later
• TN2793 vintage 4 or later

Simultaneous Ringing Considerations

Each analog circuit pack supports 8, 16, or 24 analog voice connections. Depending on the circuit pack and the required number of voice ports, you might need to spread out the voice port assignments over more than one circuit pack. For example, if you are using a�16-port circuit pack, use no more than 4 ports of circuits 1–8 and 4 ports of circuits 9–16 on that circuit pack. If you still need more Intuity voice ports, select a circuit pack that is at least one-quarter carrier distance away from the first circuit pack.

For example, if your system has 12 voice ports and you assign the first 8 ports to the circuit pack in slot 3, assign the other�4 voice ports to a circuit pack in slot 7 or higher. See more about circuit pack characteristics in the DEFINITY ECS System Description.
 

Failure to adhere to these considerations can result in ring blockage on the Intuity AUDIX system.

Voice Port Connectivity

Use ordinary tip and ring analog wiring to connect the messaging system to the switch.

1. Run modular cables from each tip and ring board together to the tip and ring distribution panel. For more information, see the figure for Typical Analog Wiring Between Switch and Messaging System.
2. Run a 25-pair cable from the distribution panel to an analog-line circuit pack on the switch.
    
   

   Note: This is one of many ways to connect between the switch and messaging system using wiring inside your building. It is subject to the same distance limitations as stations. The key element is the connection of the T/R circuits through the 25-pair cable to the switch.

Installation Considerations

Before installation, be sure that the installer has all of the necessary information and that the demarcation for the LAN is clearly understood.

LAN Information Needed for the Installation

Complete the planning worksheets in Switch Integration Planning before the installation. Completing the planning worksheets ensure that the installer has all of the needed information. Some of the information needed includes:

• How the connection is being made from the Intuity AUDIX system to the switch:
• Private LAN, no connectivity to customer LAN (uses private LAN addresses):
• Preferred option, most robust and reliable, no dependency on customer's network.
• Crossover cable used for ease of connections.
• Hub can be used instead of crossover cable to extend distances, if desired; up to four hubs can be used.
• Customer LAN with private segment:
• Preferred option when Avaya Intuity Message Manager is needed.
• Uses switch or router to provide a private collision domain.
• Minimal dependency on customer's network.
• 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 option.
• Complete dependency on performance and reliability of customer's LAN.
• Allows remote location of endpoints when customer LAN connectivity is convenient.
• Customer LAN administrator must be present during setup.
• If option b or c is chosen, the following information is needed from the customer:
• Customer network physical connectivity questions:
• Location of 10BaseT network access point (hub, router, and so on).
• Distance between C-LAN and network access point (328 ft., 100 m maximum).
• Wiring to access point, existing or new, Category 3 minimum required.
• Customer network administration questions:
• IP address of C-LANs, adjuncts, and gateways?
• Node names of C-LANs, adjuncts, and gateways?
• Subnet masks for all LAN segments containing C-LANs or adjuncts?
• Gateway IP address for all LAN segments containing C-LANs, adjuncts, or routers?
• Are all endpoints (C-LANs and adjuncts) on the same local LAN segment?

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

• Sanity check of information obtained from customer:
• If C-LAN and adjuncts are on the same LAN segment:
• Gateway IP address and subnet mask information is valid.
• All IP addresses contain the same subnet address.
• If C-LAN and adjuncts are on different LAN segments, gateway IP addresses are different.

Without the above information, the Avaya technician will be unable to complete the installation. Installations that require the technicians to return because information was not available incur additional charges.

LAN Connectivity Demarcation

Avaya service technicians dispatched for Intuity AUDIX system installation and maintenance might not troubleshoot the customer's LAN. The demarcation point for the Intuity AUDIX system connected into the customer's LAN is the back of the LAN circuit card. The LAN cable, the connector at the end of the cable for connection to the Intuity AUDIX system, and LAN administration not performed on the Intuity AUDIX system are the responsibility of the customer unless specified by contract. After the system is placed into service, the customer is responsible for maintaining the IP addresses and administration on the Intuity AUDIX system, unless otherwise specified in the contract.

http://www.avaya.com Avaya UCS Information Development