25.06.2013 Views

2.0 Mb DTI/PRI Administration and Maintenance Guide Book ... - Home

2.0 Mb DTI/PRI Administration and Maintenance Guide Book ... - Home

2.0 Mb DTI/PRI Administration and Maintenance Guide Book ... - Home

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.

Chapter 3 — DPNSS1/DASS2 features description <strong>and</strong> implementation Page 787 of 1536<br />

Figure 118<br />

RO/TAT Interworking within multiple DPNSS1/MCDN gateways, after RO/TAT<br />

Station A<br />

1<br />

Station A calls B<br />

Option 11<br />

2<br />

Option 11<br />

Station C<br />

Outgoing Gateway<br />

Node<br />

Node<br />

2<br />

Station C <strong>and</strong> A are bridged.<br />

Station C rings.<br />

Option 11<br />

Gateway<br />

Node<br />

Option 11<br />

T<strong>and</strong>em<br />

Node<br />

Station B<br />

553-8016.EPS<br />

Abnormal RO/TAT interworking scenarios<br />

The following are possible scenarios whereby the RO/TAT Interworking<br />

feature may function abnormally.<br />

— RO fails or is not configured, <strong>and</strong> TAT is configured.<br />

In the case of a DPNSS1/MCDN gateway, TAT optimises the <strong>PRI</strong> trunks<br />

on the MCDN side, but the DPNSS1 trunks are not optimised on the<br />

DPNSS1 side.<br />

In the case of an MCDN/DPNSS1 gateway, RO is not activated <strong>and</strong> the<br />

DPNSS1 side is not optimised. Since the DPNSS1 trunks remain, TAT<br />

is not invoked at the gateway node, even though it is equipped.<br />

Therefore, if RO is not activated, the RO/TAT Interworking<br />

functionality is not invoked.<br />

Option 11C <strong>2.0</strong> <strong>Mb</strong> <strong>DTI</strong>/<strong>PRI</strong> <strong>Administration</strong> <strong>and</strong> <strong>Maintenance</strong> guide

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

Saved successfully!

Ooh no, something went wrong!