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

Page 774 of 1536 Chapter 3 — DPNSS1/DASS2 features description and implementation
— Call Detail Recording (CDR) records are not printed at the originating or
terminating PBX, during route optimization. CDR records are printed at
tandem nodes when the non-optimum path is released. The CDR records
contain the same information as if the call had occurred on the new path
at the time that the original trunks were seized. The cost of the call (that
is, the Periodic Pulse Metering information) that has been optimized is
the sum of the cost before route optimization plus the cost after
optimization. The originator of the original call is shown as the originator
of the new call, at the originating PBX. The terminator of the call is
shown as the terminator of the new call, at the terminating PBX. At
transit PBXs, normal information is printed, showing original tandem
connections being released as if for calls being cleared at the time of
route optimization, and new tandem connections being released as if for
calls being originated at the time of route optimization.
If an optimized call does not use any trunks, that is, the originating party
and terminating party are on the same PBX, then CDR records show the
call as being cleared as normal.
— A call that has been call-forwarded may be optimized upon being
answered only if it has undergone alternative routing. If the forwarded
call was not alternatively routed, it may have used a non-optimum path.
— A call that has been picked up or that has undergone hunting may be
optimized upon being answered only if it has undergone alternative
routing.
— A Ring Again new call may be optimized only if it has undergone
alternative routing.
— A call transferred to another party may be optimized only after the call
transfer has been completed. A call transferred to a ringing set may be
optimized only after being answered.
— A call that has been rerouted due to Step Back on Congestion may be
optimized after it is answered.
— During a group hunt, a call to a Pilot DN which has been defined as a
trunk access code may be optimized upon being answered only if it has
undergone alternative routing.
— A call which is camped-on or call-waiting to a set may not be optimized
until the call is answered on the set
553-3011-315 Standard 10.0 May 1999