Call Vectoring
Issue 1.0 May 2003
133
Call Detail Recording
You can administer the Feature Related System Parameters form so that the VDN
extension is used in place of the Hunt Group or Agent extension. This overrides the “Call to
Hunt Group - Record” option of CDR for Call Vectoring calls.
If a vector interacts with an extension or group that has Call Forwarding All Calls active,
normal Call Forwarding/CDR interactions apply.
For incoming calls to a VDN, the duration of the call is recorded from the time answer
supervision is returned.
If answer supervision is returned by the vector, and the call never goes to another
extension, then the VDN extension is recorded as the called number in the CDR record.
If the call terminates to a hunt group, then the VDN, hunt group, or agent extension is
recorded as the called number as per the administration described above.
If the call terminates to a trunk, then the following two CDR records are generated:
●
An incoming record with the VDN as the called number and the duration from the time
answer supervision was provided to the incoming trunk.
●
An outgoing record containing the incoming trunk information as the calling number and
the dialed digits and the outgoing trunk information as the called number.
Outgoing vector calls generate ordinary outgoing CDR records with the originating
extension as the calling number.
No Ineffective Call Attempt records are generated for Call Vectoring
route-to
commands that are unsuccessful.
Call Detail Recording — Account Code Dialing
If a
route-to number
command in a vector specifies an CDR account code, vector
processing continues at the next step.
Call Park
Calls cannot be parked on a VDN.
Call Waiting Termination
If an extension is busy and has call waiting termination administered, the
route-to
with cov n
operation is considered unsuccessful and vector processing continues at the
next step.
Route-to with cov y
is successful (call will wait) and vector processing
terminates.
