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 825 of 1536<br />

Prompt Response Description<br />

NCNI (O)-7 Request CNI after the defined number of digits<br />

are received.<br />

If NCNI = 0, the CNI request does not depend<br />

on the number of digits received.<br />

If NCNI is defined to be greater than the<br />

number of digits required for routing the call,<br />

the CNI will not be requested but the call will<br />

be routed.<br />

CNIE (NO), YES Request CNI after an ESN code is dialed.<br />

This R2MFC route requests/(does not<br />

request) CNI after an ESN code is dialed. The<br />

ESN code could be a Distant Steering Code<br />

(DSC), a Trunk Steering Code (TSC), the<br />

NARS Access Code 1 (AC1) or the NARS<br />

Access Code 2 (AC2).<br />

NCNI <strong>and</strong> CNIE are prompted when the<br />

following occurs:<br />

the MFC package is equipped<br />

TKTP = DID or TIE<br />

MFC = R2MF, <strong>and</strong><br />

the MFC signaling table is defined on the<br />

route.<br />

If NCNI > 0 <strong>and</strong> CNIE = YES, CNI is requested<br />

when either one of the conditions is first met.<br />

CNIT (NO), YES Request CNI only if the dialed station has<br />

Malicious Call Trace Allowed (MCTA) Class of<br />

Service.<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!