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 />

Detailed description<br />

Each branch in a CAS has its own LDN or other type of access from the public<br />

network. In<strong>com</strong>ing trunk calls to the branch, as well as attendant-seeking voice<br />

terminal calls, route to the centralized attendants over release link trunks (RLT).<br />

The CAS attendants are at the main location. The main location can be a DEFINITY<br />

<strong>ECS</strong>, a DEFINITY System Generic 1 or 3, a DEFINITY System Generic 2.1, a<br />

System 85, a DIMENSION PBX, or a System 75 (V3).<br />

The CAS main switch operates independently of the CAS branch switches. Operation<br />

<strong>for</strong> CAS main-switch traffic is identical to operation of a stand-alone switch.<br />

Each branch in a CAS network connects to the main by way of RLTs. These trunks<br />

provide paths <strong>for</strong>:<br />

• Sending in<strong>com</strong>ing attendant-seeking trunk calls at the branch to the main <strong>for</strong><br />

processing and extending them back to the branch (both parts of a call use the<br />

same trunk)<br />

• Returning timed-out waiting and held calls from the branch to the main<br />

• Routing calls from the branch to the main<br />

A branch can connect to only one main.<br />

CAS Queues<br />

Two queues are associated with CAS calls: one at the main and one at the branch. If<br />

idle RLTs are available from the branch to the main, RLTs are seized and CAS calls<br />

are queued at the main along with other attendant-seeking calls. If all RLTs are in use,<br />

CAS calls to the attendant are queued at the branch in a RLT queue. The length of the<br />

queue can vary from 1 to 100, as set during administration of the RLT group.<br />

CAS Backup Service<br />

Backup service sends all CAS calls to a backup extension in the branch if all RLTs<br />

are maintenance-busy or out of service, or if the attendant presses a backup button<br />

that is not lighted.<br />

• To activate the feature and provide notification that backup service is in effect,<br />

assign the backup extension to a Backup button and associated status lamp.<br />

• The status lamp remains lighted as long as backup service is in effect.<br />

• To deactivate the feature, the attendant presses the Backup button while the status<br />

lamp is lighted.<br />

Calls are not sent to the backup extension unless all RLTs are maintenance-busy or<br />

out of service.<br />

CAS Remote Hold<br />

The attendant can put a CAS call from a branch on Remote Hold. The branch holds<br />

the call and drops the RLT. After a time-out (same as the timed reminder <strong>for</strong> an<br />

attendant-held call), the branch automatically attempts to route the call back to the<br />

attendant. The returning call can queue <strong>for</strong> the RLT. Attendants should use Remote<br />

Hold when they have to put a call on hold to keep RLTs from being tied up<br />

unnecessarily.<br />

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

555-233-504 — Issue 1 — April 2000 CID: 77730<br />

339

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

Saved successfully!

Ooh no, something went wrong!