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

DPNSS1 Route Optimization<br />

The DPNSS1 Route Optimization feature has been developed to optimize<br />

trunk usage within a DPNSS1 network, by replacing non-optimum call paths<br />

through a DPNSS1 private network with optimum paths. An optimum path is<br />

the path that uses only the first choice routes to link two PBXs across the<br />

network. The first choice is determined by the programming of the network<br />

numbering <strong>and</strong> routing at each PBX. This optimization applies to established<br />

simple voice calls which were routed during set-up, or transferred or<br />

attendant-extended to another party.<br />

Route optimization is initiated by the originating PBX, after recognizing that<br />

a DPNSS1 call may have been set up over a non-optimum path due to<br />

alternative routing or call modification. If the call is ringing, the originating<br />

PBX waits for an answer signal before initiating optimization. If the call has<br />

been transferred, on answer, or attendant-extended to a another party, then the<br />

transfer or extension signaling sequence initiates the optimization.<br />

The originating PBX sends a Route Optimization Request message, which<br />

contains a Call Reference Number (CRN) field, to the terminating PBX. The<br />

CRN is used as a destination address to route the call back to the originating<br />

PBX <strong>and</strong> uniquely identify the call being optimized (the Originating Line<br />

Identity sent in the Initial Service Request Message is used for this purpose).<br />

The set-up message for the backward call contains a field that identifies the<br />

call set-up as route optimization. This causes the call, throughout its path, to<br />

be restricted to only first choice routes.<br />

If the route optimization request call set-up successfully gets back to the<br />

originating PBX, a conference is established at the originating node between<br />

the originating party, the original path still carrying the speech, <strong>and</strong> the silent<br />

new path. A message of acknowledgment is returned to the terminating PBX<br />

on the new path. Upon receiving this acknowledgment, the terminating PBX<br />

replaces the old path with the new (optimized) path, <strong>and</strong> sends a connect<br />

indication across the new path to the originating PBX. The old path is<br />

silenced. Upon receiving the connect indication, the originating PBX<br />

terminates the conference, connects the originating party to the optimized<br />

path, <strong>and</strong> clears the original path.<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!