The following table describes the available exceptions for calls in vector processing:
Name |
Description |
Time in vector (max) |
The maximum acceptable time in seconds that a call can spend in vector processing. This exception can only be triggered once per interval. |
Number calls abandoned while in vector |
The maximum number of calls that can be abandoned while in the vector for processing. This exception can only be triggered once per interval. |
Number calls forced busy |
The maximum number of calls that can receive a forced busy signal from the vector during an interval. This exception can only be triggered once per interval. |
Number calls disconnected |
The maximum number of calls that can be disconnected during vector processing. Disconnects can be caused by the disconnect vector command, by the vector disconnect timer, or because a call reached the end of vector processing without being queued. This exception can only be triggered once per interval. |
Number calls in ACD split queue |
The maximum number of vector calls that can be in a split/skill queue. |
Number unsuccessful look ahead interflow attempts |
The maximum number of vector calls that fail to interflow to another ACD system during an interval. The route-to vector command causes a call to interflow. This exception can only be triggered once per interval. |
Number unsuccessful adjunct routing attempts |
The maximum number of failed attempts for a vector call to connect to an adjunct host computer during an interval. This exception can only be triggered once per interval.. |
Supervisor sends a malicious call trace report to the specified output method.
