04.11.2014 Views

Definity ECS Admin for Network Connectivity.pdf - TextFiles.com

Definity ECS Admin for Network Connectivity.pdf - TextFiles.com

Definity ECS Admin for Network Connectivity.pdf - TextFiles.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Distributed Communications System<br />

B Private <strong>Network</strong>ing<br />

Branch-generated call-identification tones<br />

The branch in a CAS network generates call-identification tones and transmits them<br />

to the CAS attendant by way of the RLT. These tones indicate the type of call <strong>com</strong>ing<br />

from the branch or the status of a call extended to or held at the branch. The attendant<br />

hears these tones in the console handset be<strong>for</strong>e being connected to the caller. The<br />

tones may vary by country. See DEFINITY <strong>ECS</strong> Console Operations <strong>for</strong> in<strong>for</strong>mation<br />

on these tones.<br />

CAS Outgoing Call Routing<br />

The centralized attendant at the main has access, through RLTs, to all outgoing trunk<br />

facilities at the branches in a CAS network. The attendant can extend an in<strong>com</strong>ing<br />

LDN call to an outgoing trunk at a branch by dialing the access code and allowing the<br />

caller to dial the rest of the number or by dialing the <strong>com</strong>plete outgoing number.<br />

CAS In<strong>com</strong>ing Call Routing<br />

Calls extended to busy single-line voice terminals at the branch wait automatically. If<br />

there is a call in queue, the user hears a busy signal. When station hunting and send all<br />

calls is administered, the call routes along the administered path. Not answering any<br />

waiting extended call within an administered interval causes the branch switch to<br />

return the call to the attendant. Call Waiting does not apply to multiappearance<br />

terminals; if no appearances are available, busy tone is sent to the attendant, who tells<br />

the caller that the line is busy.<br />

Calls from voice terminals at the branch to an attendant also route over RLTs seized<br />

by the branch switch. A branch caller reaches the attendant by dialing the<br />

attendant-group access code. The access code is administrable; the default is 0. The<br />

conversation between the branch caller and the attendant ties up the seized RLT, but<br />

calls of this type are usually short.<br />

If an extended call returns to the main attendant unanswered, the called party at the<br />

branch does not drop but continues to be alerted until the caller releases. This allows<br />

the attendant to talk to the caller, then extend the call again, if the caller wishes,<br />

without redialing the number.<br />

Considerations<br />

Branch Attendants<br />

• A branch can have an attendant. Access to the branch attendant must be by way of<br />

an individual attendant extension. In<strong>com</strong>ing trunk calls in a CAS network can<br />

bypass branch attendants but can be routed back to them by the centralized<br />

attendant.<br />

• Branch calls terminate on the CAS main switch based on the in<strong>com</strong>ing RLT<br />

trunk-group day-destination or night-service destination. An attendant console is<br />

not always answering or extending in<strong>com</strong>ing CAS calls. If someone other than an<br />

attendant answers a CAS call, that person can extend the call back to the branch<br />

by pressing the FLASH button on a multiappearance voice terminal or flashing the<br />

switchhook on a single-line voice terminal. The branch reaction to Flash Signals<br />

and the branch application of tones is the same whether an attendant or someone<br />

other than an attendant answers or extends the call.<br />

340<br />

<strong>Admin</strong>istration <strong>for</strong> <strong>Network</strong> <strong>Connectivity</strong><br />

CID: 77730 555-233-504 — Issue 1 — April 2000

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!