Nortel TFC002 User manual

Centralized Attendant Service Description and engineering
Meridian 1
Centralized Attendant Service
Description and engineering
Document Number: 553-2681-100
Document Release: Standard 5.00
Date: August 1996
Year Publish FCCTM
© 1979, 1996
All rights reserved
Printed in the United States of America
Information is subject to change without notice. Northern Telecom reserves the right to make changes in design
or components as progress in engineering and manufacturing may warrant.This equipment has been tested
and found to comply with the limits for a Class A digital device pursuant to Part 15 of the FCC rules, and the
radio interference regulations of Industry Canada.These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment.This equipment
generates, uses and can radiate radio frequency energy, and if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user will be required to correct the
interference at their own expense.
SL-1 and Meridian 1 are trademarks of Northern Telecom.

Page iii of xii
Centralized Attendant Service Description and engineering
Revision history
August 1996 Standard, Release 5.00. Reissued for X11 Release 22.0x.
December 1994 Standard, Release 4.00. Reissued to include editorial changes and indexing.
Due to the extent of the changes, revision bars are not used.
December 1992 Standard, Release 3.00. This document is reissued to include technical
content updates. Revision bars are omitted.
December 1991 Standard, Release 2.00. This document is reissued to include technical
content updates. Due to the extent of changes, revision bars are omitted.
December 1990 Standard, Release 1.00. Reissued for compliance with Northern Telecom
standard 164.0.

Page v of xii
Centralized Attendant Service Description and engineering
Contents
Feature description . . . . . . . . . . . . . . . . . . . . . . . . . 1
Feature packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Feature interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Call Waiting Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Camp-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Coordinated Dialing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Departmental Directory Number . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Dial “0” calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Directory Number Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Flexible Attendant Directory Number . . . . . . . . . . . . . . . . . . . . . . . 9
Listed Directory Number calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Message Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Night Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Property Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Recorded Overflow Announcement . . . . . . . . . . . . . . . . . . . . . . . . 11
Remote Peripheral Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Room Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Silent Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Station Category Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Timed Reminder Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Transfer to Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Trunk Group Busy Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Equipment specification and operation . . . . . . . . 15
Tone and Digit Switch cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Page vi of xii Contents
553-2681-100 Standard 5.00 August 1996
Release Link Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
QPC250 Release Link Trunk specifications . . . . . . . . . . . . . . . . . . 17
Operation at the Remote site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Operation at the Main site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Installation and connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Engineering information . . . . . . . . . . . . . . . . . . . . 25
Memory and real-time requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Traffic measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Trunks (TFC002) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Queue (TFC003) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Console (TFC004) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Calculating the number of RLT circuits . . . . . . . . . . . . . . . . . . . . . . . 28
Calculating the number of CAS attendants . . . . . . . . . . . . . . . . . . . 30
Implementation and operation . . . . . . . . . . . . . . . 47
Feature implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
CAS Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
CAS Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Main operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Remote operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Page vii of xii
Centralized Attendant Service Description and engineering
List of figures
Figure 1
Typical CAS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Figure 2
QPC250 RLT cross-connections to QPC70 CO trunk . . . . . . . . . . . . . 23
Figure 3
TFC003 measurements at a Remote site when a call waits for an
RLT to become idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Page ix of xii
Centralized Attendant Service Description and engineering
xii
List of tables
Table 1
Meridian 1 precise tones with CAS . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 2
Meridian 1 tone interruptions with CAS . . . . . . . . . . . . . . . . . . . . . . . 16
Table 3
Release Link Trunk requirements
Average speed of answer ≤2.00 seconds; average RLT delay ≤2.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 4
Release Link Trunk requirements
Average speed of answer ≤2.00 seconds; average RLT delay ≤4.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table 5
Release Link Trunk requirements
Average speed of answer ≤2.00 seconds; average RLT delay ≤6.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table 6
Release Link Trunk requirements
Average speed of answer ≤4.00 seconds; average RLT delay ≤2.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 7
Release Link Trunk requirements
Average speed of answer ≤4.00 seconds; average RLT delay ≤4.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Page x of xii List of tables
553-2681-100 Standard 5.00 August 1996
Table 8
Release Link Trunk requirements
Average speed of answer ≤4.00 seconds; average RLT delay ≤6.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 9
Release Link Trunk requirements
Average speed of answer ≤5.00 seconds; average RLT delay ≤2.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 10
Release Link Trunk requirements
Average speed of answer ≤5.00 seconds; average RLT delay ≤4.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Table 11
Release Link Trunk requirements
Average speed of answer ≤5.00 seconds; average RLT delay ≤6.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Table 12
Release Link Trunk requirements
Average speed of answer ≤6.00 seconds; average RLT delay ≤2.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 13
Release Link Trunk requirements
Average speed of answer ≤6.00 seconds; average RLT delay ≤4.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 14
Release Link Trunk requirements
Average speed of answer ≤6.00 seconds; average RLT delay ≤6.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 15
Release Link Trunk requirements
Average speed of answer ≤8.00 seconds; average RLT delay ≤2.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 16
Release Link Trunk requirements
Average speed of answer ≤8.00 seconds; average RLT delay ≤4.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

List of tables Page xi of xii
Centralized Attendant Service Description and engineering
Table 17
Release Link Trunk requirements
Average speed of answer ≤8.00 seconds; average RLT delay ≤6.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 18
Release Link Trunk requirements
Average speed of answer ≤10.00 seconds; average RLT delay ≤2.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 19
Release Link Trunk requirements
Average speed of answer ≤10.00 seconds; average RLT delay ≤4.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 20
Release Link Trunk requirements
Average speed of answer ≤10.00 seconds; average RLT delay ≤6.00
seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 21
CAS attendant requirements
Average speed of answer ≤2.00 seconds . . . . . . . . . . . . . . . . . . . . . . . 41
Table 22
CAS attendant requirements
Average speed of answer ≤4.00 seconds . . . . . . . . . . . . . . . . . . . . . . . 42
Table 23
CAS attendant requirements
Average speed of answer ≤5.00 seconds . . . . . . . . . . . . . . . . . . . . . . . 43
Table 24
CAS attendant requirements
Average speed of answer ≤6.00 seconds . . . . . . . . . . . . . . . . . . . . . . . 44
Table 25
CAS attendant requirements
Average speed of answer ≤8.00 seconds . . . . . . . . . . . . . . . . . . . . . . . 45
Table 26
CAS attendant requirements
Average speed of answer ≤10.00 seconds . . . . . . . . . . . . . . . . . . . . . . 46

Page 1 of 64
Centralized Attendant Service Description and engineering
14
Feature description
The Centralized Attendant Service (CAS) feature allows customers with
multiple locations to centralize their attendant services at a single location. A
typical CAS configuration consists of one or more Remote locations, each
served by its own switch and attendants, and a Main site location, where the
CAS attendants are located (see Figure 1). Each Remote location has access
to the Main CAS attendant through Release Link Trunks (RLT), which can
be either analog or digital. In addition, the Remote locations are
interconnected by TIE trunks.
The types of calls that require attendant assistance and can be handled by a
CAS attendant are as follows:
— Listed Directory Number (LDN) calls
— Dial “0” calls (“0” is optional if the Flexible Attendant Directory
Number is used)
— Recalls, intercepts, or transfers to attendant
— Operator-assisted calls for restricted telephones, giving access to
wide-area transmission service (WATS), Foreign Exchange (FX), and
Central Office (CO) trunks
When any of the preceding calls are placed, an idle Release Link Trunk
(RLT) at the Remote site is seized and the calls are presented to the CAS
attendant. If an idle RLT is not available, the calls are queued until one
becomes available. The CAS attendant can extend the call to a local or
Remote telephone.

Page 2 of 64 Feature description
553-2681-100 Standard 5.00 August 1996
When a call is released by the attendant, the RLT is released. Information
tones sent from the Remote site allow the CAS attendant to identify the type
of incoming call and to confirm features, such as Camp-On, during call
processing.
The system can serve as either a Main or a Remote site. Operation is
compatible with AT&T Technical Advisory Manual 10 (TA-10). CAS is
therefore compatible with any system that meets the specifications in that
document.
Figure 1
Typical CAS configuration
Remote
PBX
Attendant
Remote
PBX
Attendant
Main
PBX
CAS
Attendant
Remote
PBX
Attendant
Tie trunks
RLT
RLT
Release Link
Trunk(s) (RLT)
Tie trunks
Tie trunks
553-4030

Feature description Page 3 of 64
Centralized Attendant Service Description and engineering
The attendant at the Remote location is automatically assigned a separate
CAS key/lamp pair above the fifth loop key to control the CAS feature.
Additionally, a signal remote key is automatically assigned above the fifth
loop key on the consoles at the CAS Main location. On the M1250 and
M2250 consoles, the C/H key acts as the CAS key. If an Attendant Console
is not required at the Main location, up to ten multi-line telephones can be
equipped with a CAS key to control CAS operation.
Feature packaging
The following packages are required for Centralized Attendant Service:
— Centralized Attendant Service Main (CASM) is package 26 and
— Centralized Attendant Service Remote (CASR) is package 27.
Feature interactions
Access to special services
Special service circuits, such as WATS and FX trunks, can be either located
and controlled at one location or distributed among various locations with
each switch controlling access locally.
When special service circuits are located at the Main site, the CAS attendants
have trunk-group busy indicators and control of trunk-group access. In this
case, all Remote locations access the special-service circuits through TIE
trunks. TIE Trunk Group Access Restrictions (TGAR) at the Main site can be
arranged to provide dial access to the special services or to automatically
route incoming calls to the CAS attendants to control access manually.
If the special-service circuits are situated at a Remote location, they can be
dial-accessed and controlled through TGAR, or a unique access code can be
assigned to access the local attendant and bypass selection of a release link
trunk (RLT). The local-attendant directory number (DN) can also be used by
those who desire attendant-controlled connections.
Alarm lamps
Centralized Attendant Service (CAS) attendants do not receive major or
minor alarm indications for Remote locations. These alarms are provided at
the local console at each Remote location.

Page 4 of 64 Feature description
553-2681-100 Standard 5.00 August 1996
Attendant End-to-End Signaling
Pressing the CAS key, while using Attendant End-to End-Signaling (AEES),
may block the DTMF tones.
Attendant Overflow Position
CAS and Attendant Overflow Position (AOP) are incompatible with each
other. If both are enabled, CAS takes precedence over AOP.
Automatic Identification of Outward Dialing
When Automatic Identification of Outward Dialing (AIOD) using the
data-link method is used in conjunction with CAS, each location must be
individually connected to its respective Central Office (CO) or toll center in
order for telephone detail billing for all locations to be provided.
Where possible, the CDR option is recommended for passive cost control and
cost allocation when arranged in a CAS network. This is practical only if the
Main location and all Remote locations are Meridian 1 sites. An alternative is
to provide toll restriction at all Remote locations and force all toll calls to be
routed through CAS attendants for manual record keeping.
Automatic Number Identification
When Automatic Number Identification (ANI) using direct toll trunks to the
Central Automatic Message Accounting (CAMA) center is used in
conjunction with CAS, each location must be individually connected to its
respective Central Office (CO) or toll center for telephone detail billing in
order for all locations to be provided.
Where possible, the CDR option is recommended for passive cost control and
cost allocation when arranged in a CAS network. This is practical only if the
Main location and all Remote locations are Meridian 1 sites. An alternative is
to provide toll restriction at all Remote locations and force all toll calls to be
routed through CAS attendants for manual record keeping.
Background Terminal
CAS and Background Terminal (BGD) are incompatible. If both are enabled,
CAS takes precedence over BGD.

Feature description Page 5 of 64
Centralized Attendant Service Description and engineering
Barge-In and Busy Verify
CAS attendants are able to “barge-in” on trunks located at the Main location
and busy-verify telephones at the Main location, but are not able to perform
these functions for Remote locations. The local console at each Remote
location can barge-in or busy-verify its local trunks and telephones. Neither
the CAS attendant nor the local attendant can barge-in on an idle or busy
Release Link Trunk (RLT).
Basic or Network Alternate Route Selection
Where least-cost routing to all special services and toll routes is desired, the
Basic or Network Alternate Route Selection (BARS/NARS) feature can be
provided at the Main CAS location and accessed through TIE trunks from all
Remote locations. This eliminates potential supervision problems with
tandem TIE trunk connections that occur when BARS/NARS is provided
separately at each location. The centralized BARS/NARS feature can be used
only if all special-service outgoing toll calls are placed through the Main
CAS location.
To ensure adequate Class of Service restrictions for controlling access to
special services and toll routes, the following actions can be taken:
— Supply two separate TIE trunk routes from each Remote location to the
Main location. One should be unrestricted or conditionally toll-denied,
and the other toll-denied.
— Assign Trunk Group Access Restriction (TGAR) codes to control access
from telephones at each Remote location to one or the other of these two
trunks’ routes.
Busy Lamp Field Array
The busy-lamp field indicates the status of telephones for the Main
location only.
Call Detail Recording
When a CAS network is equipped with Call Detail Recording (CDR), the
following points should be noted:
— The CDR should be located at the Main site. This also applies to any
special service trunks.

Page 6 of 64 Feature description
553-2681-100 Standard 5.00 August 1996
— Downstream processing of the CDR tapes must correlate tandem calls
from a Remote site through the Main site by means of TIE trunks to
special services. A record showing the facilities used or telephones
involved in any tandem connection is given separately for each location.
The CDR downstream processing must rebuild the tandem call based on
the time correlation and trunk-route correlation. Every effort should be
made to ensure time synchronization between the Main and Remote
locations.
— Incoming calls completed by a CAS attendant show only the record for
the completed connection to the destination, the same as if a local
attendant had served the call.
Call Forward External Deny
A CAS local attendant is considered an internal directory number (DN) and
is not excluded when Call Forward External Deny (CFXD) is activated on a
telephone.
Call Park
Call Park is limited to the local switch and cannot be accessed from an RLT.
An RLT cannot be parked at the Main location.
Call Party Name Display
The telephone number, or access code and Route Member number, of the
originating telephone or trunk at the Remote location is not displayed to the
CAS attendant answering the call. Instead, the access code and member
number of the RLT, over which the call is presented, is indicated.
Calls to TIE trunks
The CAS attendant can connect an incoming CO call to a Directory Number
(DN) at another site, or transfer calls to the connecting site. The operation is
the same as that for completing a Listed Directory Number (LDN) or transfer
call at the Main site, except that the attendant dials a trunk access code that
corresponds to a TIE line, rather than a DN. When a second dial tone is sent
from the Remote site, the attendant dials the DN.
This type of call is limited in the following ways:
— The Recall on No-Answer feature is inactive.
— The Camp-On feature is inactive.

Feature description Page 7 of 64
Centralized Attendant Service Description and engineering
— The Call Transfer feature operates according to the capabilities of the
system on which the call transfer is being attempted.
— Disconnect supervision must either be provided by the incoming CO
trunk or be repeated by the TIE trunk from the Remote site. If not, the
Meridian 1 disallows these types of connections.
Call Waiting Indication
Calls waiting in queue for RLT at each Remote location are not included in
the Call Waiting Indication given to the CAS attendants. Calls that have
seized an RLT and are queued for service at the Main location are included in
the Call Waiting Indication.
Camp-On
When the CAS attendant attempts to complete a call to a telephone that is
busy,thecall is automaticallycamped-onto the busy telephone,provided that
a call is not already camped-on to that telephone. The Remote site transmits
a camped-on confirmation tone (a 100-ms burst of 440-Hz tone) to the CAS
attendant over the RLT and then connects to the calling party. If the calling
party wants to wait, the CAS attendant releases and a disconnect signal is
transmitted to the RLT, which releases. When the camped-on telephone goes
on hook, the camped-on call is automatically presented.
If the called telephone does not answer within the specified time, the Remote
site seizes an idle RLT and presents the calling party to the CAS attendant.
Whenthe CAS attendantanswers, answer supervisionis detectedbythe RLT,
and the Remote site sends a 100-ms burst of 440-Hz tone to the CAS
attendant so that the attendant can answer appropriately. The CAS attendant
can then release from the calling party with the Release key, or from the
called telephone, by operating the Release Destination key.
Direct inward dialing (DID) calls to a busy telephone can be routed to an RLT
and can provide the attendant with the same tone as for a dial “0” call. This
occurs only for telephones that have a Call Forward Busy Allowed (CFA)
Class of Service and no other forwarding or hunting arrangements defined.

Page 8 of 64 Feature description
553-2681-100 Standard 5.00 August 1996
Conference
Attendant-controlledconferenceconnections,involvingtelephones ortrunks,
require TIE trunk connections between the Main and Remote locations for
each Remote party. RLTs cannot be conferenced. TIE trunk networks must
be engineered with this fact considered.
Attendants must be trained to conference through TIE trunks, as well as to
handle potential difficulties with transmission and supervision. Alternatively
(and preferably), Remote locations can access the local console by dialing the
local-attendant DN for attendant conference and other special services
available at the Remote location.
Coordinated Dialing Plan
The Coordinated Dialing Plan (CDP) routes calls from the Remote to the
Main, and from the Main to the Remote.
Departmental Directory Number
When CAS is active at the Remote Attendant Console, Departmental Listed
Directory Number (DLDN) calls at that Remote site are handled at the CAS
Main as if the DLDN feature were not active.
Dial “0” calls
When the Remote site translates a dial “0” request, the calling telephone or
trunk is connected to an idle RLT and the call is presented to the CAS
attendant. When the CAS attendant answers, the RLT detects answer
supervision, transmits two 100-ms bursts of 440-Hz tone to the attendant, and
connects the calling telephone or trunk to the CAS attendant. The call is then
handled as a Listed Directory Number (LDN) call. See “Flexible Attendant
Directory Number” below for Flexible Attendant DN information.
The CAS attendant is restricted in placing dial “0” calls on hold. If the Call
Hold DN (CHDN) is dialed, the overflow tone is sent to the CAS attendant.
Directory Number Expansion
With DN Expansion, Attendant DNs and RLT access codes can be up to
seven digits.

Feature description Page 9 of 64
Centralized Attendant Service Description and engineering
Flexible Attendant Directory Number
Each Remote location can be assigned two attendant DNs to provide access
to the attendants. The Customer Data Block (LD15) allows the modification
of these two DNs. The DN assigned must be a DN taken from the numbering
plan and must not conflict with any other DN. The first is called the attendant
DN (ATDN). Calls to this DN are presented over an RLT to the CAS
attendant if the Remote location is in CAS service. If it is desired that “0” be
the access code for the attendants, then “0” must be specified as the ATDN.
If the Remote location is not in CAS service, the call is presented to the local
attendant or to the night number.
The second DN is called the Local Attendant DN (LADN). Calls to this DN
are presented to the local attendant or to the night number. A call dialed to the
LADN is never terminated on an RLT.
These DNs cannot be made Do Not Disturb (DND) busy, and if they appear
on a Lamp Field Array the associated LED is always dark.
Listed Directory Number calls
Calls to the Listed Directory Number (LDN) of the Main site are treated in
the normal manner: an Incoming Call Indication (ICI) is presented to the
attendant, and normal call-handling procedures are used. If the Remote
location is in the CAS deactivated mode, LDN calls to the Remote location
are also handled in the normal manner by the attendant at the Remote
location.
When the CAS feature is activated at the Remote location, LDN calls to that
location are presented to the CAS attendant with an RLT X ICI indication,
where X represents the RLT route location of the Remote site. If the CAS
attendant console is equipped with a numeric display, the RLT access code
and route member number are displayed.
When the CAS attendant selects the incoming call by operating the loop key
or the ICI key, answer supervision is sent to the Remote site over the RLT.
Two 100-ms bursts of 440 Hz are given, if defined in the Customer Data
Block (LD15). The RLT X ICI indication identifies the call and prompts the
appropriate verbal response.

Page 10 of 64 Feature description
553-2681-100 Standard 5.00 August 1996
After obtaining the desired party’s number, the CAS attendant presses the
signal Remote (SIG REM) key, which is assigned automatically and is
locatedabove the LPK5 key. TheMain siterespondsby sendinga timed flash
over the RLT to the Remote site. This signal prompts the Remote site to
connect a register or Digitone receiver to the RLT. When an idle register or
Digitone receiver has been applied to the RLT, a dial tone from a Tone and
Digit Switch (TDS) at the Remote location is sent to the CAS attendant. The
CAS attendant then keys in the destination DN on the dial pad. When
outpulsing is completed, the CAS attendant hears a ring-back or a busy tone.
At this time, the CAS attendant can disconnect from the RLT by operating the
release (RLS) key.
If all RLTs from a Remote location are in use, LDN calls are queued and
routed to an RLT when one becomes idle.
Message Registration
CAS and Message Registration (MR) are incompatible with each other. If
both are enabled, CAS takes precedence over MR.
Night Service
Night Service at the Main CAS attendant location is applicable to calls at the
Main location and to calls routed over the RLT from Remote locations.
Calls from Remote locations over an RLT can be transferred by the
night-answer location at the Main site back to the Remote location over a TIE
trunk; however, the RLT is held for the duration of the call.
Night Service is activated separately by each Remote location at its local
console or telephone. This is usually prearranged for a given time of day, or
it is in response to a call from the Main CAS attendant, and it is done before
the Main CAS attendant activates Night Service. If the CAS attendant
activates Night Service before the Remote locations do, then all calls routed
to the RLT by the Remote site are directed to the night location at the
Main site.
The three types of Night Service offered on Meridian 1—flexible,
night-answer telephone, or Trunk Answer From Any Station (TAFAS)—can
be assigned independent of any CAS arrangements. CAS service and Night
Service are independent, and when both features are activated, CAS takes
precedence.

Feature description Page 11 of 64
Centralized Attendant Service Description and engineering
When Night Service is activated at a Remote site, any calls in the RLT queue
are automatically rerouted to the assigned night-answer location or TAFAS,
as applicable. Calls in progress on the RLT are completed by the CAS
attendants.
Property Management System
CAS and Property Management System (PMS) are incompatible with each
other. If both are enabled, CAS takes precedence over PMS.
Recorded Overflow Announcement
TheRecorded Overflow Announcementfeaturecannot be associatedwith the
RLT x (x = key number) ICI key on the CAS Main Attendant Console.
Remote Peripheral Equipment
For CAS operation, each Remote Peripheral Equipment (RPE) location in a
CAS network is considered to be part of the site to which it is connected. This
means that the Remote end of the RPE connection shares the same numbering
plan as the local end of the connection and that the Remote end is identified
to the CAS attendant as part of the local site.
Room Status
CAS and Room Status (RMS) are incompatible with each other. If both are
enabled, CAS takes precedence over RMS.
Silent Hold
The attendant may wish to hold incoming calls at the Remote site when
unable to camp them onto a busy telephone. To accomplish this, the Silent
Hold feature is provided. When the attendant activates Silent Hold, the CO
trunk is placed in the hold state at the Remote site, and the RLT is released.
After the timed reminder has timed out, the RLT is reseized and the CO trunk
is reconnected to the CAS attendant.

Page 12 of 64 Feature description
553-2681-100 Standard 5.00 August 1996
When the attendant decides to place the call on hold, the attendant presses the
signal Remote (SIG REM) key to send a flash to the RLT. The attendant
receives a dial tone from the Remote site and dials the DN assigned for the
Silent Hold code. The hold code is outpulsed to the Remote site and is
translated, and the CO trunk is placed on hold. The Remote site then sends a
hold confirmation tone (four to six 50-ms bursts of 440-Hz tone) to the
attendant, who then releases the RLT by operating the release (RLS) key. The
Remote site recognizes the disconnect signal and releases the RLT.
A recall occurs after the recall timer has elapsed. An idle RLT is seized, and
the held call is presented to the CAS attendant. When the attendant answers,
the Remote site receives answer supervision, transmits an information tone
(four to six 50-ms bursts of 440-Hz tone) to the attendant, and removes the
hold condition from the CO trunk. The attendant can then complete the call.
The CAS attendant can also hold the RLT at the console by operating the
HOLD key. This differs from Silent Hold in that the CO trunk is held at the
Main site (over the RLT) rather than at the Remote end.
Station Category Indication
When CAS is active, calls from a Remote telephone to the Attendant DN
(ATDN) appear on the Remote Incoming Call Indication (ICI) key lamp at
the CAS Main regardless of Station Category Indication (SCI).
Timed Reminder Recall
If the Remote site is programmed to recall the attendant on “no answer” calls,
then after the prescribed timeout (during which the telephone has not
answered or the CO trunk has not disconnected), an idle RLT is seized and
thecall is presented tothe CAS attendant. Thistime, a differentattendantmay
answer the call; however, an RLT X ICI indication is still received.
When the CAS attendant answers the call, the Remote site detects answer
supervision over the RLT, sends a ring-back tone for 2 seconds to the
attendant, and then connects the call. The ICI and the ring-back tone prompt
the attendant to answer in the appropriate manner. During the answer, the
CAS attendant and the calling party talk over the ring-back of the called
telephone. The attendant can press the release destination (RLS DEST) key
to stop the ring-back.