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

DCS Over ISDN-PRI<br />

D-channel<br />

considerations<br />

Enhanced DCS<br />

considerations<br />

• The gateway node serves as the terminating node to the D-channel DCS network<br />

as well as the terminating node to the traditional DCS network.<br />

A PBX serving as an ISDN DCS Gateway node introduces some interesting<br />

situations when administering processor channels in an associated traditional DCS<br />

PBX. In a traditional DCS network, (BX.25 processor channel links) Remote<br />

Port in the “Processor Channel Assignments” <strong>for</strong>m refers to the processor<br />

channel of the destination PBX. In an Integrated DCS network, Remote Proc<br />

Chan in the “Processor Channel Assignments” <strong>for</strong>m refers to the processor<br />

channel of the Gateway PBX (if the destination PBX is an ISDN DCS PBX), not<br />

the destination PBX.<br />

On the contrary, Machine-ID in the “Processor Channel Assignments” <strong>for</strong>m<br />

refers to the destination PBX, either an ISDN DCS PBX or a traditional DCS<br />

PBX. The Gateway PBX number must not be used in this field if the destination<br />

PBX is an ISDN DCS PBX.<br />

• If the DCS link fails, the administrator can choose to allow calls to continue<br />

without class of restriction checking or to block all DCS calls to inward-restricted<br />

stations.<br />

LWC considerations • LWC cannot be successfully activated toward any system that is not capable of<br />

storing the messages, either internally or in an associated adjunct.<br />

• Messages from one node, through an intermediate node, to a remote node do not<br />

require storage capability at the intermediate node.<br />

• LWC transparency is supported <strong>for</strong> all DCS configurations except <strong>for</strong> cases when<br />

either the activating node or the remote node is either an ENHANCED<br />

DIMENSION PBX or a System 85 R2V1.<br />

• Retrieval of LWC messages is permitted only from a terminal at the node where<br />

the messages are stored.<br />

• DCS LWC cannot be activated from an attendant console.<br />

Trunk Group<br />

Busy/Warning<br />

Indication<br />

considerations<br />

• Trunk Group Busy and Trunk Group Warning Indication is particularly useful<br />

with the Attendant Control of Trunk Group Access feature. The indicators alert<br />

the attendant when control of access to local and remote trunk groups is necessary.<br />

324<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!