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

							Distributed Communications System 
331
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
•Signaling Group form (signaling group 2)
•Trunk Group form
•Routing Pattern form
•Gateway Channel form
•Processor Channel form
Administration for switch 2
•
Dial Plan form
•Uniform Dial Plan formTSC Local Enabled Establish Dest. Far-end Appl.
Index Ext. Ext. PBX-ID
1 4900 y permanent 5900 2 dcs
2 4901 y permanent 5901 - gateway
Group # Grp Type Used for 
DCS?DCS Sig. 
MethodPBX ID
2 isdn-pri y d-chan 2
Routing 
Pattern #Trunk 
Group #FRL Del TSC CA-TSC 
Request
2 2 0 3 y at-setup
Signaling Group TSC 
IndexProcessor 
ChannelApplication
2 2 57 audix
Proc 
ChannelApplication Inter. 
LinkChannel Remote 
Proc. 
ChannelPBX 
ID
57 gateway 1 2 2 -
59 audix 1 1 1 1
Start Dig. Len Usage
44ext
54ext
Ext Code Type Location Code
4xxx UDPcode 221 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
332
•AAR Digit Conversion form
•AAR Analysis Table
•Signaling Group form (signaling group 4)
•Trunk Group form
•Routing Pattern form
3-Node public/private 
network with AUDIXThe D-channel signaling feature expands the domain of DCS networks by supporting 
configurations that include public network ISDN facilities utilizing network services 
including Software Defined Network (SDN). By eliminating the need for dedicated 
private line facilities, this feature allows geographically dispersed DCS networks to 
be cost effective. Figure 6 shows a 3-node network. Matching 
PatternMin Max Del Replacemen
t StringNet Conv
222 7 7 3 - ext n
Dialed 
StringMin Max Rte Pat Call Type Node 
Num
221 7 7 1 aar 1
TSC 
IndexLocal 
Ext.Enabled Establish Dest. Far-end
Ext.Appl 
PBX-ID
1 5900 y permanent 4900 1 dcs
2 5901 y permanent 4901 - audix
Group # Grp Type Used for DCS? DCS Sig. 
MethodPBX ID
1 isdn-pri y d-chan 1
Routing 
Pattern #Trunk 
Group #FRL Del TSC CA-TSC 
Request
1 1 0 3 y at-setup 
						

							Distributed Communications System 
333
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
Figure 6. 3-Node public/private network
The following tables show you how you would complete each of the necessary forms.
AUDIX administration
•
AUDIX Translations form
AUDIX  SWITCH 1  SWITCH 2
SWITCH 3
1/1
1/2
1/31/1
1/2
1/32/1
2/2
2/3
2/44/1
4/2
TSCTSC TSC  TSC Link
1/3
1/21/1 5/1 AUDIX 1
AUDIX 2
AUDIX 3DCS 1-2
AUDIX 2
DCS 1-3
AUDIX 3
D
C
S
2
-
3
D
C
S
2
-
3 D
C
S
1
-
3D
C
S
1
-
3 A
U
D
I
X
3
A
U
D
I
X
3
AT&T
NETWORK
G3i
PBX ID 2
RNX 222
G3i
PBX ID 3
RNX223 G3i
PBX ID 1
RNX 221
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
BX.25D CHANNEL
D
-
C
H
A
N
N
E
L
D
-
C
H
A
N
N
E
L 1 1 2  1
2
1
Switch 
NumberAUDIX 
PortSwitch 
Port*
* Switch Port refers to the processor channel that is used for AUDIX in the
PBX.
Logical 
ChannelData 
Link
115911
225721
335831 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
334
Administration for switch 1
•
Dial Plan form
•Uniform Dial Plan form
•AAR Digit Conversion form
•AAR Analysis Table
•Signaling Group form (signaling group 2)
•Trunk Group formStart Dig. Len Usage
44ext
54ext
64ext
Ext Code Type Location 
Code
5xxx UDPcode 222
6xxx UDPcode 223
Matching 
PatternMin Max Del Replacemen
t StringNet Conv
221 7 7 3 - ext n
Dialed String Min Max Rte Pat Call Type Node Num
222 7 7 2 aar 2
223 7 7 3 aar 3
TSC 
IndexLocal
Ext.Enabled Establish Dest. 
Ext.Far-end
PBX-IDAppl
1 4900 y permanent 5900 2 dcs
2 4901 y permanent 5901 - gateway
3 4902 y permanent 6902 3 dcs
4 4903 y permanent 6903 - gateway
Group # Grp Type Used for DCS? DCS Sig. Method PBX ID
2 isdn-pri y d-chan 2
3 isdn-pri y d-chan 3 
						

							Distributed Communications System 
335
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
•Routing Pattern form
•Gateway Channel form
•Processor Channel form
Administration for switch 2
•
Dial Plan form
•Uniform Dial Plan form
•AAR Digit Conversion formRouting 
Pattern #Trunk 
Group #FRL Del TSC CA-TSC 
Request
2203yat-setup
3303yat-setup
Signaling Group TSC Index Processor 
ChannelApplication
2260 audix
2461 audix
Proc 
ChannelApplication Inter.
LinkChannel Remote 
Proc.
ChannelPBX ID
59 audix 1 1 1 1
57 gateway 1 2 2 -
58 gateway 1 3 3 -
Start Dig. Len Usage
44ext
54ext
64ext
Ext Code Type Location Code
4xxx UDPcode 221
6xxx UDPcode 223
Matching 
PatternMin Max Del Replacement 
StringNet Conv
222 7 7 3 - ext n 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
336
•AAR Analysis Table
•Signaling Group form
Signaling group 4
Signaling group 5
•Trunk Group form
•Routing Pattern form
Administration for switch 3
•
Dial Plan formDialed String Min Max Rte Pat Call Type Node Num
221 7 7 1 aar 1
223 7 7 3 aar 3
TSC Local Enabled Establish Dest. Far-end Appl.
Index Ext. Ext. PBX-ID
1 5900 y permanent 4900 1 dcs
2 5901 y permanent 4901 - audix
TSC Local Enabled Establish Dest. Far-end Appl.
Index Ext. Ext. PBX-ID
1 5905 y permanent 6905 3 dcs
Group # Grp Type Used 
for 
DCS?DCS 
Sig. 
MethodPBX ID NCA-TSC 
Sig. Group
*
* This field is only used for tandeming.
1 isdn-pri y d-chan 1 -
3 isdn-pri y d-chan 5
Routing 
Pattern #Trunk 
Group #FRL Del TSC CA-TSC 
Request
1103yat-setup
3303yat-setup
Start Dig. Len Usage
44ext
54ext
64ext 
						

							Distributed Communications System 
337
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
•Uniform Dial Plan form
•AAR Digit Conversion form
•AAR Analysis Table
•Signaling Group form (signaling group 4)
•Trunk Group form
•Routing Pattern formExt Code Type Location Code
4xxx UDPcode 221
5xxx UDPcode 222
Matching 
PatternMin Max Del Replacement 
StringNet Conv
223 773- extn
Dialed String Min Max Rte 
PatCall Type Node Num
221 771 aar 1
222 772 aar 2
TSC 
IndexLocal
Ext.Enable
dEstablish Dest. 
Ext.Far-end 
PBX-IDAppl.
1 6905 y permanent 5905 2 dcs
2 6902 y permanent 4902 1 dcs
3 6903 y permanent 4903 - audix
Group # Grp Type Used for 
DCS?DCS Sig. Method PBX ID
1 isdn-pri y d-chan
Routing 
Pattern #Trunk 
Group #FRL Del TSC CA-TSC 
Request
1103
*
* Should be blank if SDN network routing requires 7 digits.
yat-setup 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
338
Centralized Attendant Service
Centralized Attendant Service (CAS) allows attendants in a private network of 
switching systems to be concentrated at a central or main location. Thus, CAS 
reduces the number of attendants required at a branch. For example, a chain of 
department stores can have a centralized attendant location at the main store to handle 
calls for the branch stores.
How to administer CAS
Form Field Page
System-Parameters Customer-Options Async. Transfer Mode 
(ATM) PNC?5-289
Synchronization Plan Synchronization Source
Synchronization Reference
Stratum
Duplication-Related System Parameters Enable Operation of PNC 
Duplication5-106
Fiber Link Administration
ATM-PNC All
Circuit Packs
Cabinet
Form Field Page
Attendant Console
•Feature Button Assignments
— cas-backup -trunk-name5-38
Console-Parameters
•CAS
•RLT Trunk Group Number
•CAS Back-Up Ext
•Timed Reminder on Hold
•Return Call Timeout (sec)5-90
Station (multi-appearance)
•Feature Button Assignments
— cas-backup
— flash
— trunk name
— night serv6-30
Trunk Group (RLT)
•All 7-238
Feature Access Code (FAC)
•CAS Remote Hold Access Code 5-120 
						

							Distributed Communications System 
339
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
Detailed description Each branch in a CAS has its own LDN or other type of access from the public 
network. Incoming trunk calls to the branch, as well as attendant-seeking voice 
terminal calls, route to the centralized attendants over release link trunks (RLT).
The CAS attendants are at the main location. The main location can be a DEFINITY 
ECS, a DEFINITY System Generic 1 or 3, a DEFINITY System Generic 2.1, a 
System 85, a DIMENSION PBX, or a System 75 (V3).
The CAS main switch operates independently of the CAS branch switches. Operation 
for CAS main-switch traffic is identical to operation of a stand-alone switch.
Each branch in a CAS network connects to the main by way of RLTs. These trunks 
provide paths for:
•Sending incoming attendant-seeking trunk calls at the branch to the main for 
processing and extending them back to the branch (both parts of a call use the 
same trunk)
•Returning timed-out waiting and held calls from the branch to the main
•Routing calls from the branch to the main
A branch can connect to only one main.
CAS Queues
Two queues are associated with CAS calls: one at the main and one at the branch. If 
idle RLTs are available from the branch to the main, RLTs are seized and CAS calls 
are queued at the main along with other attendant-seeking calls. If all RLTs are in use, 
CAS calls to the attendant are queued at the branch in a RLT queue. The length of the 
queue can vary from 1 to 100, as set during administration of the RLT group.
CAS Backup Service
Backup service sends all CAS calls to a backup extension in the branch if all RLTs 
are maintenance-busy or out of service, or if the attendant presses a backup button 
that is not lighted.
•To activate the feature and provide notification that backup service is in effect, 
assign the backup extension to a Backup button and associated status lamp.
•The status lamp remains lighted as long as backup service is in effect.
•To deactivate the feature, the attendant presses the Backup button while the status 
lamp is lighted. 
Calls are not sent to the backup extension unless all RLTs are maintenance-busy or 
out of service.
CAS Remote Hold
The attendant can put a CAS call from a branch on Remote Hold. The branch holds 
the call and drops the RLT. After a time-out (same as the timed reminder for an 
attendant-held call), the branch automatically attempts to route the call back to the 
attendant. The returning call can queue for the RLT. Attendants should use Remote 
Hold when they have to put a call on hold to keep RLTs from being tied up 
unnecessarily. 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
340
Branch-generated call-identification tones
The branch in a CAS network generates call-identification tones and transmits them 
to the CAS attendant by way of the RLT. These tones indicate the type of call coming 
from the branch or the status of a call extended to or held at the branch. The attendant 
hears these tones in the console handset before being connected to the caller. The 
tones may vary by country. See DEFINITY ECS Console Operations for information 
on these tones.
CAS Outgoing Call Routing
The centralized attendant at the main has access, through RLTs, to all outgoing trunk 
facilities at the branches in a CAS network. The attendant can extend an incoming 
LDN call to an outgoing trunk at a branch by dialing the access code and allowing the 
caller to dial the rest of the number or by dialing the complete outgoing number.
CAS Incoming Call Routing
Calls extended to busy single-line voice terminals at the branch wait automatically. If 
there is a call in queue, the user hears a busy signal. When station hunting and send all 
calls is administered, the call routes along the administered path. Not answering any 
waiting extended call within an administered interval causes the branch switch to 
return the call to the attendant. Call Waiting does not apply to multiappearance 
terminals; if no appearances are available, busy tone is sent to the attendant, who tells 
the caller that the line is busy.
Calls from voice terminals at the branch to an attendant also route over RLTs seized 
by the branch switch. A branch caller reaches the attendant by dialing the 
attendant-group access code. The access code is administrable; the default is 0. The 
conversation between the branch caller and the attendant ties up the seized RLT, but 
calls of this type are usually short.
If an extended call returns to the main attendant unanswered, the called party at the 
branch does not drop but continues to be alerted until the caller releases. This allows 
the attendant to talk to the caller, then extend the call again, if the caller wishes, 
without redialing the number.
Considerations Branch Attendants
•
A branch can have an attendant. Access to the branch attendant must be by way of 
an individual attendant extension. Incoming trunk calls in a CAS network can 
bypass branch attendants but can be routed back to them by the centralized 
attendant.
•Branch calls terminate on the CAS main switch based on the incoming RLT 
trunk-group day-destination or night-service destination. An attendant console is 
not always answering or extending incoming CAS calls. If someone other than an 
attendant answers a CAS call, that person can extend the call back to the branch 
by pressing the FLASH button on a multiappearance voice terminal or flashing the 
switchhook on a single-line voice terminal. The branch reaction to Flash Signals 
and the branch application of tones is the same whether an attendant or someone 
other than an attendant answers or extends the call.