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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

QSIG<br />

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

Path Retention<br />

Path Retention is a generic mechanism <strong>for</strong> retaining a network connection that can be<br />

used by supplementary services during call establishment.<br />

The Originating PBX invokes path retention <strong>for</strong> one supplementary service or <strong>for</strong><br />

several simultaneous supplementary services. Invoking a particular supplementary<br />

service means retaining the network connection if the Terminating PBX encounters<br />

the appropriate conditions. The Originating PBX is in<strong>for</strong>med of the reason <strong>for</strong><br />

retaining the connection. It then decides (<strong>for</strong> example, by consulting the calling user)<br />

whether to invoke the supplementary service. Under some circumstances in which the<br />

network connection is retained, more than one of the supplementary services <strong>for</strong><br />

which path retention has been invoked may be applicable.<br />

Successive retentions of the network connection by the Terminating PBX following a<br />

single path-retention invocation by the Originating PBX are possible. This is a result<br />

of different conditions being encountered at the Terminating PBX. When an attempt<br />

is made to invoke a supplementary service <strong>for</strong> which the network connection has been<br />

retained, a further condition can be encountered that can cause the network<br />

connection to be retained again <strong>for</strong> the same or a different supplementary service.<br />

Path retention is specified in terms of a Path Retention entity existing within the<br />

Coordination Function at the Originating PBX and at the Terminating PBX.<br />

QSIG Centralized Attendant Services<br />

QSIG Centralized<br />

Attendant Service<br />

(QSIG-CAS)<br />

DEFINITY <strong>ECS</strong> supports two versions of CAS: RLT-CAS and QSIG-CAS.<br />

The CAS feature enables one or more Branch PBXs to concentrate their attendants on<br />

one Main PBX. CAS provides transparency between PBXs of most features that are<br />

normally available to the basic attendant service.<br />

RLT-CAS uses an analog RLT network to optimized trunk utilization. QSIG-CAS<br />

does not use RLT. By using QSIG Transfer and QSIG Path Replacement or QSIG<br />

Diversion with Rerouting, the same optimization as using RLT can be ac<strong>com</strong>plished<br />

with QSIG-CAS. Using QSIG CAS, you eliminate the need to have a separate analog<br />

RLT network.<br />

All current QSIG features and RLT-CAS features are available with QSIG-CAS.<br />

Potential Drawbacks<br />

There are a few potential drawbacks when using QSIG-CAS:<br />

1 Unlike RLT, QSIG Path Replacement does not work immediately. This means<br />

that resources are being utilized longer during QSIG-CAS as opposed to<br />

RLT-CAS.<br />

2 Unlike RLT, QSIG Path Replacement is not guaranteed.<br />

3 Like RLT, QSIG Path Replacement does not enable a branch PBX to act as a<br />

gateway PBX.<br />

4 No path replacement functionality takes place during or after a conference.<br />

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