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

							Distributed Communications System 
341
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
•When an analog-station call goes to coverage, the station drops from the call. This 
is the exception to the branch leaving the extended-to party ringing. If the main 
attendant extends a call to an analog station and that call goes to coverage and 
later returns to the main attendant, the call is treated as an incoming LDN call and 
the attendant must re-extend the call, if requested by the user.
•On an incoming CAS call to the main attendant, the Name field from the 
trunk-group form for that RLT displays to the attendant. Therefore, you should 
administer the field to provide meaningful branch identification information.
•Music-on-Hold feature at branch applies to two stages of LDN calls: during call 
extension and Remote Hold.
Interactions •Abbreviated Dialing
The main attendant can use an Abbreviated Dialing button to extend CAS calls 
after obtaining branch dial tone.
•Attendant Auto-Manual Splitting
The SPLIT lamp and button do not function on CAS main calls extended via the 
RLT trunk. Attendant conference does not function on CAS calls.
•Attendant Control of Trunk-Group Access
If a branch attendant has control of an outgoing RLT trunk group, new 
attendant-seeking calls route to the branch attendant.
•Attendant Override of Diversion
Use Attendant Override of Diversion with CAS.
•Attendant Serial Calling
Attendant Serial Calling does not work for CAS calls.
•Automatic Alternate Routing and Automatic Route Selection
CAS calls can be routed using AAR and ARS.
•Busy-Indicator Buttons
Busy indicators can identify incoming calls over an RLT. You can also use Busy 
indicators to dial after the attendant starts to extend a call.
•Call Coverage
Redirect calls to a centralized attendant by Call Coverage. Do not redirect calls to 
a CAS backup extension for backup service via Send All Calls to the backup 
extension’s coverage path.
•Call Detail Recording
If the CAS main RLT trunk has the CDR option selected, CDR records generate 
for incoming CAS calls.
•Call Forwarding
Do not forward calls to a CAS extension. 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
342
•DCS Operation
If an RLT trunk group is administered as a DCS trunk, the following interaction 
applies: On an incoming CAS call to the attendant, the DCS message displays 
instead of the name of the incoming RLT trunk group. Upon answering the call, 
the attendant hears call-identification tones, indicating that the call is a CAS call. 
Use a TRUNK-NAME button to obtain the name of the RLT trunk group.
•DXS and DTGS Buttons
DXS and DTGS buttons at the main attendant console can be used with CAS. 
However, with DXS buttons, it takes a few seconds before the attendant hears 
ringback tone.
•Emergency Access to the Attendant
CAS Branch Emergency Access calls generated by a Feature Access Code route 
Off-Hook Alert to the branch attendant group. If there is no attendant in the 
branch, the call routes to the branch’s administered Emergency Access 
Redirection Extension. When the branch switch is in CAS Backup Service, the 
calls route to the backup station and the call is treated as a normal call.
•Hunt Groups
If an incoming CAS call directs to a hunt group, the call does not redirect to the 
hunt group’s coverage path. Depending on the circumstances, the attendant can 
get a busy tone or ringing.
•Leave Word Calling 
If a message is left for a branch user and the attendant at the CAS switch tries to 
retrieve the message by using LWC message retrieval, permission is denied.
•Night Service — Night Console Service
When the CAS main enters night service, CAS calls terminate at the CAS main 
night-service destination. When the branch enters Night Service, CAS calls route 
to the branch night console, the LDN night station, or the TAAS.
•Night Service — Trunk Answer from Any Station
In a multiswitch DCS environment with CAS, the result of transferring incoming 
trunk calls via Night Service Extension or Trunk Answer from Any Station varies 
depending on the home switch of the transferred-to station, the home switch of the 
connected trunk, and the type of night-service function chosen (Night Service 
Extension, Trunk Answer From Any Station, or both).
•Nonattendant Console Handling of CAS Calls
The CAS branch calls terminate at the CAS main based on the incoming RLT 
trunk-group day destination or night-service destination. You can also answer a 
CAS call by the Trunk Answer Any Station feature. 
						

							Distributed Communications System 
343
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
Emergency (911) CallsThe Enhanced 911 (E911) systems installed in many jurisdictions in the U.S. are 
equipped so that by dialing a service code (911 in the U.S.) a victim of a fire, 
accident, crime, or medical emergency may quickly access a public safety agency that 
will dispatch the appropriate response. The public E911 system maintains a database 
that stores location and background information to aid public safety agencies in 
responding quickly with the appropriate assistance. Information about the calling 
party can be triggered by the transmission of a Caller’s Emergency Service 
Identification (CESID) number over Centralized Automatic Message Accounting 
(CAMA) trunks when the call originates from behind a PBX. 911 calls from a station 
on a PBX not equipped with CAMA trunks (or an adjunct computer system 
associated with CAMA trunks) will not provide the E911 system with the information 
required to identify the location of the person placing the call. Instead, the E911 
system will only be able to identify the location of the trunk termination at the PBX.
This feature allows transmission of identifying information in the form of the CESID 
over CAMA trunks as to the extension number of a DID station associated with the 
calling party. The calling party may be at or near a station on a remote port network, 
or may be at a remote location served by an off-premises station.
How to administer 
Emergency (911) Calls
Interactions
None.Form Field
ARS Digit Analysis Table
•All
CAMA Numbering Format
•All
Class of Restriction
•Calling Party 
Restriction
Feature Access Code
•ARS Access Code1
•ARS Access Code2
Route Pattern
•All
Trunk Group (CAMA)
•All 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
344
Extended Trunk Access
Use Extended Trunk Access (ETA) in conjunction with Uniform Dial Plan (UDP) to 
allow DEFINITY ECS to send any unrecognized number (such as an extension not 
administered locally) to another switch for analysis and routing. Such unrecognized 
numbers can be Facility Access Codes, Trunk Access Codes, or extensions that are 
not in the UDP table. Non-UDP numbers are administered on either the First Digit 
Table (on the Dial Plan Record form) or the Second Digit Table. They also are not 
administered on the ETA Call Screening Table. ETA helps you make full use of 
automatic routing and UDP.
How to administer ETA
!CAUTION:
Switches can be chained together using ETA. However, you must ensure that 
switches do not route in a circular ETA call setup. Switch A can route to switch 
B, and switch B can route to switch C. But, if switch A routes to switch B and 
switch B routes to switch A, you create a circular ETA call setup. 
Detailed descriptionHistorically, ETA has been used by satellite switches to access stations, trunks, and 
features at the main switch. ETA frees you from having to enumerate the entire dial 
plan for the main or satellite complex. Calls that would get intercept treatment 
without ETA are routed to a remote switch to be reprocessed. The following 
processing takes place when ETA is administered:
•ETA call is identified because it fails all other routing possibilities.
•The dialed string is not in the ETA Call Screening Table.
•An available route pattern is selected based on the Dial Plan form ETA Routing 
Pattern or ETA Node Number entries.
•The dialed string is sent to the remote switch.
Examples of ETA 
administrationCASE #1
•ETA Route Pattern — Not administered
•ETA Node Number — Not administered
In this case, ETA is not active. It is not used to route undefined dialed strings.
CASE #2
•ETA Route Pattern — Administered
•ETA Node Number — Not administeredForm Field
Dial Plan Record
(First Digit and Second Digit Tables)
•ETA Routing Pattern
•ETA Node Number 
ETA Call Screening Table
•Call Screening Entry 
						

							Distributed Communications System 
345
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
In this case, the ETA Route Pattern routes undefined dialed strings. However, since 
an ETA Node Number is not specified, non-call-related DCS messages are not routed.
CASE #3
•ETA Route Pattern — Not administered
•ETA Node Number — Administered
In this case, the ETA Node Number provides the route pattern. Non-call-related DCS 
messages also can route since a node number is supplied.
CASE #4
•ETA Route Pattern — Administered
•ETA Node Number — Administered
In this case, the ETA Route Pattern routes undefined dialed strings while the ETA 
Node Number routes DCS messages. Nodes themselves do not have to be 
administered for ETA. ETA should not be used over tandem-tie trunks.
Interactions•Abbreviated Dialing
Abbreviated Dialing calls are routed via ETA.
•Attendant
Attendants calls are routed via ETA.
•Data-Call Setup
Analog and digital endpoints can access ETA. The digit string goes to the remote 
switch like any other digit string is sent. The remote switch handles the data-call 
setup from that point forward.
•Facility Restriction Levels
It is possible to restrict trunks that are being used in conjunction with ETA by 
assigning FRLs.
•Last Number Dialed
If a number is routed via ETA to a remote switch and you want to reaccess that 
number, then reaccess uses ETA.
•Modem Pooling
Modems in Modem Pools are treated like all other trunks.
•Remote Access
Remote-access trunks are able to access the ETA feature just as any other trunk or 
station does. 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
346
Extension Number Portability
Extension Number Portability (ENP) gives you the ability to assign any extension to 
any switch in an ENP subnetwork. Stations can be moved across switches while 
retaining the original extension number, as long as the switches are part of the ENP 
subnetwork. EPN is used in conjunction with Automatic Alternate Routing (AAR) 
and Uniform Dial Plan (UDP). 
How to administer ENP
•
AAR Digit Conversion form — Assign all 3-digit ENP codes as home, and if using 
a 5-digit UDP, associate the ENP codes with the leading, or 10 thousands, digit 
(that is, the fifth digit of the extension). For example, for extension number 73446, 
“7” is the 10 thousands digit.
•ENP Numbering Plan form — Associate the leading one or two digits of 
extensions in the ENP subnetwork with a 3-digit ENP code, used to construct a 
7-digit AAR-like ENP number.
•Node Number Routing form — Associate a route pattern with each node in the 
ENP subnetwork.
•Uniform Dialing Plan form — Enter the number of digits in the plan (4 or 5) and 
the Extension Codes for non-home extensions in the ENP subnetwork as 
ENPNode (node number routed).
Detailed descriptionThe ENP Numbering Plan allows you to set 4- or 5-digit extensions in the ENP 
subnetwork to a 7-digit AAR-like number that is sent to other nodes in the network. 
Only the first 1 or 2 leading digits of the extension are significant. 
ENP Codes are distinguished from AAR location codes because ENP Codes are home 
on every node within the ENP subnetwork, and ENP Codes are administered in the 
ENP Numbering Plan table as well as in the AAR Analysis table. Since ENP Codes 
are home on every node, they cannot be used as AAR location codes.
UDP extensions are converted to ENP numbers if node number routing is specified 
for the extensions in the UDP table. 
Note:One ENP code is required for a 4-digit ENP subnetwork. A 5-digit 
UDP requires one ENP code for each leading digit of extensions 
used within the ENP subnetwork.
DCS message signaling links are not required to support ENP. As a result, many 
multiple switch configurations are possible with ENP. Typically the ENP network 
will be a subnetwork of a UDP or Electronic Tandem Network (ETN).Form Field
AAR and ARS Digit Conversion Table
•All
Extension Number Portability Numbering 
Plan
•All
Node Number Routing
•All
Uniform Dialing Plan 
•Ext Code 
						

							Distributed Communications System 
347
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
Interactions•Distributed Communications System
If you use DCS, the ENP node numbers must correspond to DCS node numbers.
Inter-PBX Attendant Service
Inter-PBX Attendant Service (IAS) allows attendants for multiple branches to be 
concentrated at a main location. Incoming trunk calls to the branch, as well as 
attendant-seeking voice-terminal calls, route over tie trunks to the main location.
How to administer 
Inter-PBX Attendant 
Service
Detailed description 
Inter-PBX Attendant Service calls are incoming tie-trunk calls from a branch location 
to the main-location attendant group. If no attendant in the group is immediately 
available, the calls are queued. When an attendant becomes available, the call routes 
to that attendant. Extended calls are treated as incoming calls to the main location.
DEFINITY ECS can be a branch or main location. Users at each branch can access 
other branch locations through the main location. A branch can have local attendants. 
Users access these local attendants normally.
Interactions •Attendant Control of Trunk-Group Access
If a call at a branch attempts to access a controlled trunk group, the call routes to a 
branch attendant, if there is one. If there is no branch attendant, the call routes to 
the attendant group at the main location.
•Attendant Display and DCS Attendant Display
In a DCS environment, an incoming call from a branch displays at the attendant 
console at the main location as a local call.
In a non-DCS environment, an incoming call displays at the attendant console at 
the main location as an incoming tie-trunk call.
•Attendant Recall
If an attendant at the main location holds a call, the calling parties at the branch 
cannot recall the attendant.
•Call Coverage
A call redirected to a coverage path with the attendant group as a coverage point 
skips that coverage point. It goes to the next coverage point at the branch, if 
administered, or continues to ring at the previous coverage point. If the attendant 
group 0 is the only coverage point, it continues to ring at the principal’s extension.Form Field
Tie Trunk Group (Main)
•Incoming Destination
Console Parameters (Branch)
•IAS (Branch)
•IAS Tie Trunk Group No.
•IAS Att. Access Code
Tie trunk group (Branch)
•All 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
348
•Centralized Attendant Service
CAS and Inter-PBX attendant calling cannot be used at the same time.
•Dial Access to Attendant
Administer Dial Access to Attendant via the dial platform to the same digit on 
both the IAS main switch and the IAS branch switch. On the branch switch, 
administer the PBX attendant access code (Console Parameters form) to match the 
main PBX attendant-group dial access code.
•Night Service
Inter-PBX Attendant Calls deactivates when a branch goes into night service, and 
reactivates when the branch comes out of night service.
Private Network Access
Use Private Network Access to allow calls to other switching systems in a private 
network. These calls do not use the public network. They are routed over 
customer-dedicated facilities.
How to administer 
Private Network Access
•
Trunk Group Forms — Set the Group Type field to access, aplt, tandem, tie, 
or isdn and the Service Type field to access, tie, or tandem. Complete COR 
digit treatment and common type fields for tie trunk groups associated with a 
private network.Form Field
Trunk Groups
Access
APLT
ISDN-BRI
ISDN-PRI
Tandem
•All
Class of Restriction
•Advanced Private Line 
Termination
Feature Access Code (FAC)
•Automatic Alternate 
Routing Access Code
AAR and ARS Digit Analysis Table
•All
AAR and ARS Digit Conversion Table
•All
Node Number Routing
•All
Station
•COR 
						

							Distributed Communications System 
349
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
Detailed descriptionPrivate networks can include:
•Common-control switching arrangement (CCSA)
•Distributed Communications Systems (DCS) and Enhanced DCS (EDCS)
•Electronic tandem network (ETN)
•Enhanced private-switched communications service (EPSCS)
•Tandem-tie-trunk network (TTTN)
•Italian Traslatore Giunzione Uscente/Entrante/Interno (TGU/TGE/TGI) trunks
Unless prohibited by the COR, all incoming private network trunks, except CCSA, 
can access outgoing trunks without attendant or terminal-user assistance. All 
incoming CCSA calls must route to an attendant or a terminal user.
When off-network calling is part of the CCSA and EPSCS, long-distance calls route 
as far as possible over these networks before terminating on the public network. Thus, 
charges for toll calls are reduced. The COR you administer to individual system users 
determines whether access to this capability is allowed or denied.
In Italy, TGU/TGE/TGI trunks provide private network access between 2 switching 
systems. They also provide some feature transparency for COR (Inward Restriction), 
DID (when reaching busy stations), and Intrusion.
Interactions •Attendant Call Waiting
Call Waiting is provided via Italian TGU/TGE (main and satellite) trunks. Call 
Waiting also is provided in Italy and all other countries through DCS.
•Attendant Intrusion
Attendant Intrusion is provided on satellite switches via TGU/TGE trunks. 
Attendant Intrusion also is provided through DCS. 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
350
Uniform Dial Plan 
Uniform Dial Plan (UDP) provides a common 4- or 5-digit dial plan (specified in the 
Dial Plan Record) that can be shared among a group of switches. Interswitch dialing 
and intraswitch dialing both require 4- or 5-digit dialing. UDP is used with an 
electronic tandem network (ETN); main, satellite, and tributary switches; and 
Distributed Communications Systems (DCS). In addition, UDP can provide uniform 
4- or 5-digit dialing between 2 or more private-switching systems without ETN, main, 
satellite, and tributary switches, or DCS.
How to administer UDP
Note:On the Uniform Dialing Plan form, if you change the Ext Code 
and Type fields from a 4-digit or 5-digit extension number to 
none, a warning message informs you that all UDP extension 
codes will be lost. The same warning message displays when you 
change the Ext Code and Type extension numbers from 4-digits 
to 5-digits or from 5-digits to 4-digits.
Detailed descriptionUDP routes calls off the local switch by converting the extension number into a 
private-network number with 7 digits. This number is formed by prepending a 3-digit 
code (of the form XXX) to the (last) 4 digits of the extension number. 3 types of 
conversion are supported: UDPCode, AARCode, and ENPNode.
•For UDPCode and AARCode, XXX is a 3-digit private-network location code, 
and the result is analyzed and routed via Automatic Alternate Routing (AAR). 
UDPCode conversion prohibits digit conversion via AAR; AARCode conversion 
permits it, just as if you dialed the AAR number instead of the extension.
•For ENPCode, XXX is called an Extension Number Portability (ENP) code. It is 
not used for routing; node-number routing is used instead. The ENP code is 
chosen based on the first 1 or 2 digits of the dialed string. Because it is not used 
for routing, the ENPCode can be independent of location.Form Field
Dial Plan Record
Second Digit Table
•Uniform Dial Plan
•UDP Extension Search Order
Uniform Dial Plan
•All
AAR and ARS Digit Analysis Table
•All
AAR and ARS Digit Conversion 
Table
•All
Node Number Routing
•Route Pat
Extension Number Portability 
Numbering Plan
•All
Route Pattern 
•All