Filter
Top Products
Troubleshooting Vectors
D-10 Issue 4 September 1995
Table D-3. Converse Command Debugging
SYMPTOM CAUSES EVIDENCE
PLACING A CALL:
Converse step skipped. VRU down (RONA). Vector event.
Split queue full Vector event.
Call stuck in converse. VRU port doesn’t answer,
RONA not used.
Check split administration.
VRU down, RONA leaves call
in queue.
Check split status.
DATA PASSING:
First set of digits not
collected.
Converse first delay too short. Check administration.
No ANI available. Vector event.
No digits collected. Vector event.
Call not queued (qpos). Vector event.
Expected wait time not
available
Vector event.
VRU timed out awaiting first
digit.
VRU error log/trace.
VRU first digit timeout too
short.
Check VRU script.
Check converse first data
delay.
Faulty hardware. Diagnostics
Second set of digits not
collected.
VRU digit count on first prompt
in VRU script does not include
"#."
Check VRU script.
Converse second delay too
short.
Check administration.
No ANI available. Vector event.
No digits collected. Vector event.
Call not queued (qpos). Vector event.
DATA PASSING:
(Continued)
Expected wait time not
available because call is not
queued or the splits/skills that
the call is queued to are not
staffed
Vector Event