Specifications
Task: administering exceptions CentreVu CMS Administration
Administering VDN exceptions 8-25
Reference
CentreVu
CMS begins checking when a call connects to the VDN and
ends when the call is disconnected, sent to another VDN, sent to an
external destination, or transferred. The call remains connected to the
VDN if:
• The call routes to another vector (by the JRWRYHFWRU step).
• The call is sent (by a URXWHWR or DGMXQFWURXWLQJ step) to an
extension (other than a VDN) internal to the local switch.
• The “Time in vector” exception may include time in more than
one vector because of the JRWRYHFWRU command.
• Some exception types need the appropriate step in the vector to
which the VDN is assigned. For example, to get exceptions on
unsuccessful Look Ahead Interflow attempts, the VDN's vector
must have at least one URXWHWR step which routes calls to a
vector on a remote switch.
Number of
unsuccessful
adjunct routing
attempts
Shows an occurrence counted against the
threshold each time an DGMXQFWURXWLQJstep
fails. A failure occurs when the adjunct host
computer does not take routing control of the call.
The failure can occur because the connection to
the adjunct is down or busy, or because the adjunct
software rejects control. This exception cannot
trigger more than once within an interval.
Rolling Average
Speed of Answer
Shows the rolling average speed of answer for the
measured VDN to
CentreVu
CMS via the ASA
message. An occurrence is counted when
CentreVu
CMS receives an ASA that exceeds the
time limit specified for a VDN. An exception is
generated when the threshold is reached. The
rolling ASA for the VDN is switch-based. The
exception can be triggered once per interval.
In this field... Administer this exception type...