Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Instructions Manual
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Instructions Manual
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
![Page 222
Configuration 5B:R8csi R8r (2 C-LANs)
R8si 3 C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
202
Enable links and processor channels
You must enable links and processor channels before the connections can be used.
To enable a link, open its data module screen (ch da [ext]) and set the Enable
Link? field to y.
[note: to view a list of assigned data modules and their extensions, enter the “list
data-module” command (l da)]
To enable the...](http://img.usermanuals.tech/thumb/3002/85170/w64_definity-ecs-r8-2-administration-for-network-connectivity_d-221.png "Page 222
Configuration 5B:R8csi R8r (2 C-LANs)
R8si 3 C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
202
Enable links and processor channels
You must enable links and processor channels before the connections can be used.
To enable a link, open its data module screen (ch da [ext]) and set the Enable
Link? field to y.
[note: to view a list of assigned data modules and their extensions, enter the “list
data-module” command (l da)]
To enable the...")
Configuration 5B:R8csi R8r (2 C-LANs) R8si 201 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 3 C-LAN Administration > Submit the screen End Session - LocalThe Local and Remote Session numbers can be any value between 1 and 256 (si model) or 384 (r model), but they must be consistent between endpoints. For each connection, the Local Session number on this switch must equal the Remote Session number on the remote switch and vice versa. It is allowed, and sometimes convenient, to use the same number for the Local and Remote Session numbers. Session - Remote Mach ID Destination switch ID identified on the dial plan of the destination switch. For Processor Channel 32: (connection to Switch 2 through Switch 1) Enable Set to y. Appl. Set to dcs for DCS signaling. Mode Node-3 is the server. Set node-2 to client (c). Interface Link This must match the link number assigned on the node-3 data module screen. Interface ChanFor TCP/IP, interface channel numbers are in the range 5000 – 64500. This number must match the Destination Port number on the Switch-3 Processor Channel screen. Destination NodeName of the far-end node for this channel. This must be a name entered on the Node Names screen. Destination PortFor TCP/IP, interface channel numbers are in the range 5000 – 64500. The recommended values are: 5001 for CMS, 5002 for Intuity AUDIX, and 5003 for DCS connections that are not gateways. These three values should be reused for multiple instances of these applications. The combination of Link, Interface Channel, and Mach ID must be unique. This number must match the Destination Port number on the Switch-2 Processor Channel screen. Session - LocalFor each connection, the Local Session number on this switch must equal the Remote Session number on the remote switch and vice versa. Session - Remote Mach ID Destination switch ID identified on the dial plan of the destination switch. Field Conditions/Comments 2 of 2
Configuration 5B:R8csi R8r (2 C-LANs) R8si 3 C-LAN Administration Administration for Network Connectivity CID: 77730 555-233-504 — Issue 1 — April 2000 202 Enable links and processor channels You must enable links and processor channels before the connections can be used. To enable a link, open its data module screen (ch da [ext]) and set the Enable Link? field to y. [note: to view a list of assigned data modules and their extensions, enter the “list data-module” command (l da)] To enable the processor channels, open the processor channel screen (ch com p) and set the Enable field to y for each assigned processor channel. Note:1. You must disable a link or processor channel before you can change its parameters. Note:2. The busy-out command overrules the data module Enable Link? field. Note:3. On the C-LAN boards, low-level connectivity can remain intact when higher-level applications such as DCS are not functioning. For example, an external ping to a C-LAN’s ethernet port could be successful even when the board is busied-out. When debugging connectivity problems, pinging only checks low-level connectivity.
203Administration for Network Connectivity555-233-504 — Issue 1 — April 2000 CID: 77730 4 Networking Example This chapter provides an example of a complex network. It describes procedures for administering trunk groups, dial plans, signaling groups, and data links for a four-switch network with an Intuity AUDIX and a CMS. The network example is unchanged from the example in Issue 1 (for R7) of this book. The screens have been updated for R8. Overview This section shows a high-level diagram of the example network and lists the administration tasks that need to be completed for each node to set up the network. NOTE:The term node is used in this chapter, as in the other chapters, to mean a network interface such as a port on the C-LAN board. Traditionally, in a DCS network of DEFINITY switches, node has been used to refer to a switch. In this chapter a “DCS node” is referred to as a “Switch Node.” Thus, a Switch Node (a switch) can have many nodes (network interfaces). The Dial Plan and AAR Digit Analysis Table screens both have fields that still use node to refer to a switch.
Overview 4 Networking Example Administration for Network Connectivity CID: 77730 555-233-504 — Issue 1 — April 2000 204 Network Diagram The following diagram shows a high-level view of the example network. X.25 ISDN ppp 10BaseT Hub Customer NetworkData RouterEthernet Switch Node 2 DEFINITY ECS R6si Switch Node 4 DEFINITY ECS R7csi Switch Node 3 DEFINITY ECS R7si Intuity AUDIX CMS Switch Node 1 DEFINITY ECS R7r Gateway
Overview 205 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 4 Networking Example Task Summary The following matrix summarizes the administration tasks required to set up this network. Administration TaskSwitch Node 1 R7rSwitch Node 2 R6siSwitch Node 3 R7csiSwitch Node 4 R7siCMSIntuity AUDIX DS1 Circuit Pack X X X X Synchronization PlanXXX X Trunk Groups X X X X Dial Plan X X X X Uniform Dialing PlanXXX X AAR Digit AnalysisXXX X Signaling Group X X Hunt Group X X X ISDN TSC Gateway Channel AssignmentX Interface Links X Node Names X X X X IP Route X X X X Data Modules X X X X Processor Channel AssignmentsXXX XXX Routing Patterns X X X X Bus Bridge X Intuity Translations for DCS AudixX CMS Server TranslationsX
Link/Channel/TSC Map 4 Networking Example Administration for Network Connectivity CID: 77730 555-233-504 — Issue 1 — April 2000 206 Link/Channel/TSC Map The link/channel/TSC map shows the link, processor channel, and temporary signaling connection numbers, and the connection types for each Switch Node in the network. Node 2 Node 3 Node 4 DEFINITY ECS R8csiDEFINITY ECS R6siDEFINITY ECS R8siEthernet ISDN- PRI cydfec8b KLC 101999 BX.25 ppp DEFINITY ECS R8r gateway Node 1 Processor channels 11 (N2) 12 13 2 14 (N4) 15 16 10(CMS) 1 (Int) 4 3 Processor channelsInterface channels 11 12 13 59 N1 N3 N4 Int11 12 13 2 Link 2 Processor channelsC-LAN interface channels 14 15 16 1 N1 N2 N3 Int CMS0 0 0 5002 5001 Link 1 C-LAN interface channels 5003 6004 6005 Link 4 PI interface channels 11 12 13 2 Link 2 1 1 1 1 (N3) N2-N3 N3-N4 N3-Int1 1 1 1 Sig GrpSig Grp Index 1 2 3 4Index 1 2 3 4 Extn 1901 1902 1903 1904Extn 3901 3902 3903 3904N3 N2 N4 Int 10BaseT hub CMSIntuity AUDIX C-LAN interface channels 5001 5002 6021 6031 Link 1 RouterISDN X.25 Gateway– ISDN IP Gateway– X.25 IP Gateway–
Network Map 207 Administration for Network Connectivity 555-233-504— Issue 1 — April 2000 CID: 77730 4 Networking Example Network Map The network map shows the RNX, trunk group, hunt group numbers, data module type, and extension for each Switch Node in the network. For TCP/IP connections, the node name and IP address is shown for each node. Ethernet LAN10BaseT hub cydfec9b KLC 101999 router192.168.1.200 192.168.2.200 intuity 192.168.1.70 ethernet1 192.168.1.11 ppp41 192.168.1.41ppp14 192.168.1.14 Exts. 3000-3999 Exts. 2000-2999 Exts. 4000-4999 Exts. 1000-1999 cms192.168.2.90 Voice - ISDN TG 13 TAC 713 Voice TG 12 TAC 712 Voice TG 14 TAC 714 PPP Data TG 24 TAC 724 BX.25 Data TG 22 TAC 722 CMS Intuity AUDIX Node 1 R8r Gateway RNX 221 RNX 223 RNX 222 Node 3 R8si Node 2 R6si Node R8csi 4 Ext. 1111 REM-AUDIX HG 99 Ext. 3111 REM-AUDIX HG 99 Ext. 2111 DS1 DS1 DS1DS1 PGATE PI DTE Ext. 1992 PI DTEExt. 2992 Ext. 1191 C-LAN C-LAN Ext. 4991 7400D RNX 224 DS1DS1REM-AUDIX HG 99 Ext. 4111 Ext. 1194
Switch-Node 1 Administration 4 Networking Example
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
208
Switch-Node 1 Administration
This section displays the filled-in screens for the administration of Switch Node 1.
DS1 Circuit Packs
Connection to Switch
Node 2
Connection to Switch
Node 3
add ds1 1c19 Page 1 of 2
DS1 CIRCUIT PACK
Location: 01c19 Name: Switch 1 to Switch 2
Bit Rate: 1.544 Line Coding: b8zs
Line Compensation: 1 Framing Mode: esf Signaling Mode: common-chan
Interface Companding: mulaw Idle Code: 11111111 DMI-BOS? n
Slip Detection? n Near-end CSU Type: other
add ds1 1c18 Page 1 of 2
DS1 CIRCUIT PACK
Location: 01c18 Name: Switch 1 to Switch 3
Bit Rate: 1.544 Line Coding: b8zs
Line Compensation: 1 Framing Mode: esf
Signaling Mode: isdn-priConnect: pbx ____Interface: network Country Protocol: 1
Protocol Version: a
Interface Companding: mulaw CRC? n Idle Code: 11111111
DCP/Analog Bearer Capability: 3.1kHz
Slip Detection? n Near-end CSU Type: other
Switch-Node 1 Administration
209
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
4 Networking Example
Connection to Switch
Node 4
Dial Plan
add ds1 1c17 Page 1 of 2
DS1 CIRCUIT PACK
Location: 01C17 Name: Switch 1 to Switch 4
Bit Rate: 1.544 Line Coding: b8zs
Line Compensation: 1 Framing Mode: esf Signaling Mode: robbed bit
Interface Companding: mulaw Idle Code: 11111111 DMI-BOS? n
Slip Detection? n Near-end CSU Type: other
display dialplan
DIAL PLAN RECORD
Local Node Number: 1
ETA Node Number:
Uniform Dialing Plan: 4-digit ETA Routing Pattern:
UDP Extension Search Order: local-extensions-first
FIRST DIGIT TABLE
First Length
Digit - 1 - - 2 - - 3 - - 4 - - 5 - - 6 -
1: extension
2: extension
3: extension
4: extension
5:
6:
7: dac
8: fac
9: fac
0: attd
*: dac
#: dac
Switch-Node 1 Administration 4 Networking Example
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
210
Signaling Group
Page 1
Page 2 – Administered
NCA TSC Assignment
Synchronization Plan
change signaling group next Page 1 of 5
SIGNALING GROUP
Group Number: 1
Group Type:
Associated Signaling? y Max number of NCA TSC: 5_
Primary D-Channel: 01c1824 Max number of CA TSC: 23 Trunk Group for NCA TSC: 13 Trunk Group for Channel Selection: ___
Supplementary Service Protocol: a__
Page 2 of 5
ADMINISTERED NCA TSC ASSIGNMENT
Service/Feature: __________ As-needed Inactivity Time-out (min): __
TSC Local Adj. Mach.
Index Ext. Enabled Established Dest. Digits Appl. Name ID
1: 1901_
y permanent 3901___________ dcs____ _______ 3_
2: 1902_ y permanent 3902___________ gateway _______ __
3: 1903_ y permanent 3903___________ gateway _______ __
4: 1904_
y permanent 3904___________ gateway _______ __
5:
:
16:
Page 1 of X
SYNCHRONIZATION PLAN
SYNCHRONIZATION SOURCE (circuit pack location)
Stratum: 4
Port Network: 1 Primary: 01c20 Secondary: ___
Location Name Slip Type Location Name Slip Type
01c17
DCS Node 4_____ n UDS1-BD _____ _______________ _ ___
01c18 DCS Node 3____ n TBRI-BD _____ _______________ _ ___
01c19 DCS Node 2
_____ n_____ _______________ _ ___
01c20 AT&T __________ y _____ _______________ _ ___
_____ _______________ _ _____ _______________ _ ___
_____ _______________ _ _____ _______________ _ ___
_____ _______________ _ _____ _______________ _ ___
_____ _______________ _ _____ _______________ _ ___
NOTE: TN722B & TN464B DS1 sources result in stratum 4, type II synchronization