Converse-on command debugging

Last Updated : Dec 22, 2016 |

Symptom

Cause

Analysis

Making a call

Converse-on step skipped

VRU down (RONA)

Vector event

Split queue full

Vector event

Call stuck in converse

VRU port does not 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 unavailable

Vector event

VRU timed out awaiting first digit

VRU error log/trace

VRU first digit time-out 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 the pound (#) sign

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

Expected Wait Time unavailable because call is not queued or the splits/skills that the call is queued to are not staffed

Vector Event

VRU timed out awaiting first digit

VRU error log/trace

VRU first digit time-out too short

Check VRU script. Check converse second data delay

Inter-digit time-out too short on first prompt and collect

Check VRU script

Faulty hardware

Diagnostics

Digits incomplete

Converse data delay too short.

Check administration

Faulty hardware

Diagnostics

Second set of digits is the same as the first digits passed

VRUs first prompt timed out

Check administration

Faulty hardware

Diagnostics

Data return

No digits returned to Communication Manager

Flash not recognized by Communication Manager

VRU error log or trace

Check flash timing on VRU

Converse data return FAC not administered

Check administration

VRU does not return FAC

VRU script. Transfer attempt vector event

VRU returns incorrect FAC

VRU script. Transfer attempt vector event

Digit time-out during FAC

Transfer attempt event

Converse data return FAC overlaps with other entries in the dial plan

Check dial plan

Faulty hardware

Diagnostics

Not all digits returned to Communication Manager

Digit time out after FAC

None unless VRU logs being dropped by Communication Manager

Overflow of Call Prompting buffer

Vector event

Faulty hardware

Diagnostics

Collect announcement not heard

Too many digits returned by VRU.

Check VRU script

Faulty hardware

Diagnostics

Vector events

The agent variable is used with the converse-on command in non-VDN Return Destination (VRD) vectors.

Check that the agent variable is used as a converse-on operand in VRD vectors.