AT&T 555-230-520 Medical Alarms User Manual


 
Troubleshooting Vectors
D-18 Issue 4 September 1995
61 Invalid destination The
adjunct routing
command returned
digits that did not represent a valid
destination.
62 Adjunct route cancelled The
adjunct routing step
was cancelled
because another "routing" step (such as a
queue-to main split
step) was
encountered in the vector.
63 Queue before route The
adjunct routing
command was
skipped because the call had already
been queued via a
queue-to main split
or
a
check-backup split
command.
64 Adjunct link error The
adjunct routing
command was
cancelled for one of the following reasons:
Link to the adjunct was down
ASAI protocol violation prevented the
call from completing
Software resources to complete the
call were unavailable
65 Agent not logged in A Direct Agent Call was made to an agent
who was not logged into the relevant split.
Used for adjunct routing request only.
66 Agent not member of split A Direct Agent Call was made to an agent
who is not a member of the relevant split.
Used for adjunct routing request only.
67 Invalid direct agent A Direct Agent Call was made to an agent
extension that is not valid. Used for
adjunct routing request only.
70 Busy step for CO trunk A CO trunk call reached a
busy
step in a
vector without having previously received
answer supervision. As a result, the caller
continues to hear ringback rather than the
busy tone.
80 Time not set A
goto
step with a
time-of-day
conditional
was processed, but the switch time was
not set.
81 No digits collected No digits were collected and a
comparison was requested against a digit
string or “in-table”. The comparison test
was considered false and the next step in
the vector was executed.
Table D-4. Summary of Vector Events
Event Event Event
Type Description Explanation