Page 8 of 64
Feature description
553-2681-100 Standard 5.00 August 1996
Conference
Attendant-controlled conference connections, involving telephones or trunks,
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
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.
