AT&T 555-230-520 manual Table D-3. Converse Command Debugging, Placing a Call

Troubleshooting Vectors

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,	Check split administration.
	RONA not used.
	VRU down, RONA leaves call	Check split status.
	in queue.
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	Vector event.
available
VRU timed out awaiting first	VRU error log/trace.
digit.

Second set of digits not collected.

VRU first digit timeout too	Check VRU script.
short.
	Check converse first data
	delay.
Faulty hardware.	Diagnostics
VRU digit count on first prompt	Check VRU script.
in VRU script does not include
"#."

	Converse second delay too	Check administration.
	short.
	No ANI available.	Vector event.
	No digits collected.	Vector event.
	Call not queued (qpos).	Vector event.
DATA PASSING:	Expected wait time not	Vector Event
(Continued)	available because call is not
	queued or the splits/skills that
	the call is queued to are not
	staffed

D-10Issue 4 September 1995