Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Instructions Manual

							1Administration for Network Connectivity555-233-504 — Issue 1 — April 2000  CID: 77730
1 Networking Overview
This chapter provides background information that will help you understand and use the 
information in the remainder of the book. There are two major sections in this chapter. The first 
section describes how DEFINITY ECS switches can be connected, with a focus on IP connectivity. 
The second section describes IP addressing and subnetting.
DEFINITY Switch Connectivity
This section describes the basic components of a network of DEFINITY switches and how voice and signaling 
data are transmitted between switches for the different types of switch connections. It also provides a summary 
of the administration procedures for connecting switches via an IP network (using the C-LAN and 
TN802B-MedPro circuit packs).
Connectivity Overview
Why connect switches?DEFINITY switches can be connected in various ways for various reasons. The main 
motivation for connecting switches is to enable people within an enterprise to easily 
communicate with one another, regardless of their physical location or the particular 
communications server they are assigned to. Inter-switch connections also enable the 
sharing of communications resources such as messaging and Call Center services.
What kinds of 
connections are 
possible?Tru nk s
Switches communicate with each other over trunk connections. There are several 
kinds of trunks — each kind provides a different set of services for the connection. 
Commonly used trunk types are (Central Office) CO trunks, which provide 
connections to the public telephone network through a central office, and tie trunks, 
which provide connections between switches in a private network.
These and other common trunk types are described in DEFINITY ECS 
Administrator’s Guide, 555-233-506. 
DEFINITY ECS Release 8 introduces the H.323 trunk, which allows voice and fax 
data to be transmitted over the Internet to another DEFINITY system with H.323 
Trunk capability. The H.323 trunk supports Q.931 services such as DCS+ and QSIG. 
						

							DEFINITY Switch Connectivity 1  Networking Overview
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
2
Networks
When two or more switches are connected via tie trunks, they form a private network. 
There are two basic types of networks for Lucent switches:
•Main-satellite/tributary (MS/T) — A network of switches in which a main switch 
is fully functional and provides attendants and CO trunks for connected satellite 
switches. Tributary switches are connected to the main and may have their own 
attendant and CO trunks. The main switch may be connected to one or more 
Electronic tandem networks (ETNs).
•Electronic tandem network (ETN) — A wide-area network of switches in which a 
call can tandem through one or more switches on its way from the originating 
switch to the destination switch. ETNs have a uniform dial plan (UDP), automatic 
alternate routing (AAR), and automatic route selection (ARS).
AT&T provides a service called software-defined network (SDN) that allows you to 
build a private network through the AT&T public network facilities. An ETN can be 
combined with an SDN to form a hybrid (ETN/SDN) network.
The switches in MS/T or ETN networks need to be provisioned with special 
DEFINITY networking software packages.
DCS
Distributed Communications System (DCS) is a messaging overlay for ETN or MS/T 
networks. The overlay provides signaling connections between network nodes that 
enable certain key call features to operate transparently across the DCS network. That 
is, the transparent features appear to operate as if the switches in the DCS network 
were a single switch. For example, the DCS Call Coverage feature enables calls to an 
extension on one switch to be covered by extensions on a remote switch in the 
network.
DCS consists of two components — routing and message signaling. Routing the 
message requires one of several networking software packages. Typically, UDP is 
used singe it is included with DCS at no additional charge.
Although DCS is actually a messaging overlay for an existing network, it is 
commonly thought of as a type of network itself. In this document, we will refer to 
DCS in this way — DCS network will refer to a cluster of switches that are part of an 
existing ETN or MS/T network and are also administered for DCS. 
In addition to the normal tie-trunk connections for the transmission of voice and 
call-control data, DCS requires a special signaling connection to carry the 
information needed to make the DCS features work. This signaling connection, or 
link, between two switches in a DCS network can be implemented in one of three 
ways:
•over a processor interface (PI) channel (on the si model) or a packet gateway 
(PGATE) channel (r model) using the X.25 protocol
•over an ISDN-PRI D-channel (csi, si, or r models)
•over a TCP/IP (either PPP or 10Base-T Ethernet) connection (csi, si, or r models)
Note:The csi model does not support X.25 connections. 
						

							DEFINITY Switch Connectivity 
3
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
1  Networking Overview
TCP/IP signaling connections were introduced with DEFINITY Release 7. Starting 
with R7, X.25 was no longer sold with new systems. R7 and later new systems ship 
with only TCP/IP connections or ISDN-PRI for DCS signaling. However, existing 
systems with X.25 and/or ISDN-PRI DCS signaling can be upgraded to the latest 
version and keep those signaling links, or a new system can be added to an existing 
DCS network. Connections to the CMS Call Center and Intuity AUDIX adjuncts can 
use either X.25 or 10Base-T DCS signaling.
When a DCS network uses a mixture of two or three of the different DCS signaling 
types, one or more switches in the network must act as a gateway. A gateway switch 
is connected between two switches using different signaling protocols and the 
gateway enables the two end switches to communicate by converting the signaling 
messages between the two protocols. A gateway switch can provide conversion 
between two or all three of the signaling protocols, but only one protocol can be used 
for DCS signaling between any two switches. 
What is transmitted 
between connected 
switches?A telephone call consists of voice (bearer) data and call-signaling data. If the call is 
over a DCS network, DCS signaling data is also required. The DCS signaling data is 
sent over a separate path from the voice and call-signaling data.
Call-signaling data
The call-signaling data includes messages necessary to set up the call connection, 
maintain the connection during the call, and remove the connection when the call is 
finished. 
DCS-signaling data
The DCS-signaling data is separate from the call-signaling data. How it gets 
transmitted depends on the connection type, which determines the type of signaling 
protocol used.
How does the data 
move between 
switches?Figure 1 shows some of the major components of switch connections. Before R7, a 
call from switch 1 to switch 2, which consists of voice and signaling data, is sent 
through a trunk circuit pack across a TDM transmission facility to a trunk circuit pack 
in switch 2. Releases 7 and later add alternate pathways for the call data. In R8 and 
later releases, Q.931 signaling is used, which enables support for DCS+ and QSIG. 
The C-LAN circuit pack enables signaling data to be packetized and sent over a LAN, 
WAN, or the Internet. The IP Interface (TN802B) circuit pack enables voice data and 
non-DCS signaling data to be sent over IP facilities. 
						

							DEFINITY Switch Connectivity 1  Networking Overview
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
4
Figure 1. Components of Switch Connectivity
What do the 
components do?
The function of each circuit pack shown in Figure 1 is described below.
Processor
The processor board is the main control element in handling the call. This is the 
UN332B for the r model, the TN 790B for the si model, and the TN798B for the csi 
model.
PGATE (r only)
On the r model, the PGATE board (TN577) connects the processor to the packet bus 
and terminates X.25 signaling.
NetPkt (si only)
The Network control/Packet Interface (NetPkt) board (TN794) replaces the NETCON 
(TN777B) and the PACCON (TN778) circuit packs in the R7si model. It also 
replaces the LAPD portion of the PI (TN765) circuit pack.
PGate (r)
NetPkt (si)
PI (si)
C-LAN
Processor
 Signaling Data
Interface to Transmission 
Facilities
Tie-Trunk Circuit Packs
DS1, ISDN-PRI, Analog
C-LAN
Tie Trunk
Vo ic e  D a t a
WAN 
PPP
DEFINITY DEFINITY
Switch 2
Switch 1
IP 
Interface
MedPro 
mode 
or IP trunk 
mode
IP 
Interface
MedPro 
mode 
or IP trunk 
mode
LAN
or
10/100BaseT10BaseT 
						

							DEFINITY Switch Connectivity 
5
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
1  Networking Overview
C-LAN
The C-LAN circuit pack (TN799B) enables signaling data to be transmitted via the 
TCP/IP protocols across a LAN or WAN. Signaling types include call setup and 
teardown, registration of IP softphones, TSCs, QSIG and DCS signaling.
The C-LAN circuit pack provides the data link interface between the switch processor 
and the transmission facilities. C-LAN prepares the signaling information for TCP/IP 
transmission over one of two pathways — either via an Ethernet LAN or a point to 
point protocol (PPP) connection — depending on how the data link is administered. If 
the link is administered for an ethernet connection, the signaling data is sent out on a 
10Base-T network, which is connected directly to the C-LAN ethernet port. If the link 
is administered for a PPP connection, C-LAN inserts the signaling data on the TDM 
bus for subsequent inclusion (via the switching fabric) in the same DS1 bit stream as 
the voice transmissions.
The C-LAN board can be inserted in any available port slot. Up to 10 C-LAN boards 
can be used in the DEFINITY ECS R8r and R8si models — up to 2 C-LAN boards 
can be used in the R8csi model. Each C-LAN board has 17 ports; port 17 is used for 
the LAN interface and the other 16 can be used for PPP connections. Up to 508 
sockets are available on each C-LAN circuit pack.
IP-Interface
The IP Interface circuit pack (TN802B) enables two switches to transmit voice data 
between them over an IP network. The TN802B normally operates in the MedPro 
mode, which enables support of applications that comply with the H.323-v2 
protocols. It can also operate in the IP Trunk mode to support R7 IP trunks that 
emulate DS1 connections.
Tie-Trunk Circuit Packs
The tie-trunk circuit packs provide an interface between the switch and the 
transmission facilities for voice data, call-signaling data and data. See System 
Description, 555-230-211 for descriptions of tie-trunk (and other) circuit packs.
Pre-R7 circuit packs PI (si only)
The PRI functionality of the Processor Interface (PI) board (TN765) is replaced by 
the NetPkt board (TN794) in R7. The PI board will no longer be shipped with new 
systems starting with R7. The PI board is needed in switches upgraded to R7 and later 
releases only if existing X.25 connections are retained. The PI board has 4 data links 
that can connect to DS1 tie trunks over the TDM bus for interface to DCS or ISDN 
applications. The PI board terminates BX.25 and ISDN-PRI link access procedure on 
the D-Channel (LAPD). 
NETCON (si only)
The network controller (NETCON) board (TN77B) is replaced by the NetPkt board 
(TN794) starting in R7. For pre-R7 systems, NETCON provides an interface to the 
processor for the port circuit packs on the TDM bus. 
						

							DEFINITY Switch Connectivity 1  Networking Overview
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
6
PACCON (si only)
The Packet Controller (PACCON) board (TN778) is replaced by the NetPkt board 
(TN794) starting in R7. For pre-R7 systems, PACCON provides an interface to the 
processor for D-Channel signaling over the packet bus.
The following table gives a summary of the different types of call connections and 
how the voice and signaling data are transmitted between switches.
For DCS+, X.25, and ppp connection types, the signaling and voice data are sent 
together over tie-trunk facilities as TDM-multiplexed frames. The DCS signaling data 
is sent as packets over a permanent virtual circuit (PVC) on tie-trunk facilities.
For C-LAN Ethernet connections, the signaling and voice data are sent together over 
tie-trunk facilities as TDM-multiplexed frames. The DCS signaling data is sent as 
TCP datagrams over an IP network through the C-LAN.
Connection 
Ty p eTie Trunk LAN or WAN
Voice & Call-
Signaling DCS 
Signaling VoiceCall & DCS 
Signaling
ISDN
(DCS+)
& QSIGT1/E1 facilities 
using ISDN-PRI or 
DS1 B-ChannelTSCs on the 
ISDN-PRI 
D-ChannelTSCs on the 
ISDN-PRI 
D-Channel 
X.25T1/E1 facilities 
using ISDN-PRI or 
DS1 B-Channel
OR
Analog trunkPacket PVC
C-LAN 
PPPT1/E1 facilities 
using ISDN-PRI or 
DS1 B-Channel
OR
Analog trunkPacket PVC
C-LAN 
EthernetT1/E1 facilities 
using ISDN-PRI or 
DS1 B-Channel
OR
Analog trunkTCP
Packet
(DCS 
signaling 
only)
IP 
Interface
R7—DS1 
emulation
(IP Trunk 
mode)Packet PVC
(X.25)RTP
Packet
(IP Interface 
in ip trunk 
mode)TCP
Packet 
(C-LAN)
IP 
Interface
R8 — H.323 
trunk
(MedPro 
mode)
RTP
Packet 
(IP Interface 
in medpro 
mode)TCP
Packet 
(C-LAN) 
						

							DEFINITY Switch Connectivity 
7
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
1  Networking Overview
For IP Trunk connections, the voice data is sent over IP facilities as RTP datagrams 
using the IP Interface assembly (TN802 or TN802B) — each packet can potentially 
take a different route through the network. The call and DCS signaling data are sent 
as datagram packets over an IP network using the C-LAN interface. The R7 type of IP 
trunk (IP Interface operating in ip trunk mode) can also use tie-trunk PVC facilities 
for the DCS signaling.
Release 8 Hardware Requirements
For the three DEFINITY ECS switch models — csi, si, and r — Release 8 IP trunking (H.323) and IP Softphone 
connections require at least one IP Interface (TN802B) circuit pack and at least one C-LAN (TN799B) circuit 
pack. DEFINITY One requires only the IP Interface circuit pack.
IP InterfaceThe IP Interface assembly (J58890MA-1 L30) is a 3-slot wide TN802B circuit pack 
that provides voice processing over IP connections. The IP Interface assembly 
contains an NT processor, which is automatically administered by the DEFINITY 
software. The TN802B can be administered to operate in medpro mode for H.323 
trunks and IP softphones, or in ip trunk mode for R7-type IP Trunk connections. 
C-LANThe C-LAN circuit pack, TN799B, provides call setup, TSCs, QSIG, and DCS 
signaling over IP connections.
Note:The TN799B must be used to handle call signaling for the TN802B in 
MedPro mode. However, the previous version of C-LAN (TN799) can be 
used for call signaling with the TN802 or the TN802B operating in IP 
Trunk mode. The TN799 can also be used for DCS signaling connections 
on a switch that is using the TN802B in MedPro mode, as long as there 
are TN799Bs to handle the call signaling for the TN802B.
Hardware Requirements for Upgrades from Pre-R7 Switches
DEFINITY release 7 introduced several hardware changes that are also required for release 8. This section 
summarizes the hardware changes needed for pre-R7 switches upgrading to R8 for each switch model and each 
type of non-H.323 connectivity.
R8r modelThe following table shows the hardware required for an upgrade to an R8r. 
Connection Type Hardware Required
BX.25 (Existing 
systems only)PGATE (TN577)
TCP/IP
(ethernet and ppp)C-LAN (TN799B)
ISDN-PRI No hardware changes required 
						

							DEFINITY Switch Connectivity 1  Networking Overview
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
8
R8si modelThe following table shows the hardware required for an upgrade to an R8si. 
R8csi modelThe following table shows the hardware required for an upgrade to an R8csi. Connection Type Hardware Required
BX.25 (Existing 
systems only)
•PI (TN765)
•NetPkt (TN794) — replaces the NetCon (TN777B) and the 
PACCON (TN778) circuit packs
•
Upgraded processor (TN790B)
•In duplicated systems, a second NetPkt Control 
Assembly and a new DUPINT (TN792)
TCP/IP
(ethernet and ppp)
•C-LAN (TN799B)
•NetPkt (TN794) — replaces the NetCon (TN777B) and the 
PACCON (TN778) circuit packs
•
Upgraded processor (TN790B)
•In duplicated systems, a second NetPkt Control 
Assembly and a new DUPINT (TN792)
•Expansion Interface (TN570) if there is an EPN and 
there are packet-based applications (such as TCP/IP 
over the C-LAN or ISDN-PRI over the TN464). The 
TN776 EI can be used only when the switch has no 
packet-based applications.
ISDN-PRI
•NetPkt (TN794) — replaces the NetCon (TN777B) and the 
PACCON (TN778) circuit packs
•
Upgraded processor (TN790B)
•In duplicated systems, a second NetPkt Control 
Assembly and a new DUPINT (TN792)
•Expansion Interface (TN570) if there is an EPN.
ISDN-PRI capabilities formerly provided by the PI and 
PACCON circuit packs are now provided by the NetPkt. 
Note that you do not need to replace the TN767 with the 
TN464 since NetPkt supports D-channel signaling over the 
TDM bus.
Connection Type Hardware Required
BX.25 (Existing systems 
only)The csi model does not support BX.25 connectivity.
TCP/IP
(ethernet and ppp)
•C-LAN (TN799B)
•Upgraded processor (TN798B)
ISDN-PRI
•Upgraded processor (TN798B) 
						

							DEFINITY Switch Connectivity 
9
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
1  Networking Overview
DEFINITY Connection types and capacities
This subsection gives an overview of the types of connections that can be set up with DEFINITY switches and 
adjuncts and capacities for some connectivity parameters. 
Types of connectionsThis table lists the types of connections possible with each DEFINITY model and 
adjunct. 
If an R8 switch is connected to two endpoints by different connection types, it acts as 
a gateway (protocol converter) between the endpoints.DEFINITY ECS 
R8 Model Connection Type Endpoint
R8csiEthernet DCS, CMS, Intuity 
AUDIX
Synchronous PPP DCS
ISDN-PRI DCS+
H.323 Trunk DCS+
R8siEthernet DCS, CMS, Intuity 
AUDIX
Synchronous PPP DCS
ISDN-PRI DCS+
BX.25 DCS, CMS, Intuity 
AUDIX, 
DEFINITY AUDIX
H.323 Trunk DCS+
R8rEthernet DCS, CMS, Intuity 
AUDIX
Synchronous PPP DCS
ISDN-PRI DCS+
BX.25 DCS, CMS, Intuity 
AUDIX, 
DEFINITY AUDIX
H.323 Trunk DCS+ 
						

							DEFINITY Switch Connectivity 1  Networking Overview
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
10
DEFINITY CapacitiesThe following table shows maximum allowable values and ranges for several 
connectivity parameters for DEFINITY ECS Release 8. Note that some or all maxima 
may not be achievable, depending on specific switch/traffic configurations.
csi si r
Circuit Packs
*
* Circuit pack abbreviations:
C-LAN: Control LAN (TN799B)
NetPkt: Network Control/Packet Interface (TN794)
PI: Processor Interface (TN765; used only for X.25 connections retained from pre-R7 systems)
PGATE: Packet Gateway (TN577)
IP-Interface: Used in the Medpro mode (TN802B)
2 C-LAN
X IP-Interface (medpro)10 C-LAN
1 NetPkt
2 PI
14 IP-Interface (medpro)10 C-LAN
4 PGATE
46 IP-Interface (medpro)
Audio Streams per 
IP-Interface 
board
†
† The number of audio streams per board is 22 if only one call uses a compression codec, even if all
other calls use the G711.
31 for G711 codec
22 for compression 
codecs31 for G711 codec
22 for compression 
codecs31 for G711 codec
22 for compression 
codecs
H.323 IP Trunks
+ IP Stations300 300 1000
Processor 
Channels:
X.25
ethernet/pppna
1–1281–64
1–2561–128
1–384
Interface Channels 
(listen ports):
X.25
ethernet/pppna
5000–64,5001–64
5000–64,5001–64
5000–64,500
ISDN-TSC 
Gateway Channelsna 128 256
Links per System 25 25 33
Links per Circuit 
Pack:
PI
PGATE
C-LANna
na
1 ethernet, 16 ppp4
na
1 ethernet, 16 pppna
4
1 ethernet, 16 ppp
IP Routes 270 400 650
Hop Channels
(X.25 only)na 128 256