Consider the following when working with VDN exceptions:
To administer VDN exceptions, the Call Vectoring feature must be enabled.
The Time in Vector
exception type might include the time that a call spends in more than one vector.
CMS starts monitoring for VDN exceptions when a call connects to the VDN and stops when the call is disconnected, sent to another VDN, sent to an external destination, or transferred. The call remains connected to the VDN if one of the following occurs:
The call is routed to another vector through a go to vector command.
The call is sent through a route to or adjunct routing link command to a non-VDN extension that is internal to the local ACD system.
Some VDN exception types require specific vector routing commands. For example, to get exceptions for unsuccessful interflow attempts, the vector must have at least one route to command that routes calls to a vector on a remote ACD.
