ATT DEFINITY Generic 3 Call Vectoring/Expert Agent Instructions Manual

Converse Command Debugging
Issue  4 September 1995
D-11
VRU time d out awaiting first 
digit.
VRU error log/trace.
VRU first digit timeout too 
short.Check VRU sc ript. Check 
converse second data 
delay.
Inter-digit timeout too short on 
first prompt and collect.Check VRU sc ript.
Faulty hardware. Diagnostics.
Digits incomp lete.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...

Troubleshooting Vectors
D-12Issue  4 September 1995 
Tracking Unexpected Vector Events
If you have an SAT terminal, you can display unexpected vector events. A vector 
event is an error that results from resource exhaustion or from faulty vector 
programming, rather than from a DEFI NI TY software error.  For exam ple, failures 
involving the 
route-to command are usually due to an invalid extension entered 
by the user.
By disp laying ve ctor events, you can do the following:
nDiagnose and correct each...

Tracking Unexp ected Vector Events
Issue  4 September 1995
D-13
nREPORT PERIOD.  This o ption allows you to s pecify a report period.  This 
period consists of an 
Interval field, a From date/time stamp, and a To 
date/time stamp . Valid entries for the 
Interval field include (h)our, (d)ay, 
(w)eek, and (a)ll.  Both stamps consist of a series of numb ers that 
represent a period of time, as follows:  
1 through 12 (month), 1 through 31 
(day), 
0 through 23 (hour), 0 through 59 (minutes). If the field...

Troubleshooting Vectors
D-14Issue  4 September 1995 
nEvent Data 1 is a 9- character fields that contains data in one of two 
formats:
—
/< number2> (for example, 12/5), where  is 
the vector number associated with the vector event, and where 
 is the step number associated with the vector event. 
This format is used for events to which an event type in the range of 
0 through 499 is assigned.
—
Split (for examp le, Split 89), where  is the sp lit 
associated number associated with the vector event. This...

Tracking Unexp ected Vector Events
Issue  4 September 1995
D-15
Table D-4. Summary of Vector Events
Event Event Event
Type Description Explanation
1 Call dropped; call not q ueued 
at 
stop ste p.Vector processing ended without the call 
being queued to a split and, as a result, 
the call cannot be answered. This implies 
that some default condition was not 
programme d or that the vector was 
designed to not always answer the call. 
Also, call was subsequently dropped.
2 Vector with no stepsThe call...

Troubleshooting Vectors
D-16Issue  4 September 1995 
11 No announcement available During an announcement ste p, a c ollect 
digits
 step that contains an 
announcement, or a 
disconnect ste p, the 
announcement was not available for one 
of the following reasons:
nAnnouncement was not recorded
nAnalog announcement was busied out
nIntegrated announcement board was 
not installed
nIntegrated announcement ports were 
busied out
nIntegrated announcement was being 
recorded or restored
20 Call cannot be...

Tracking Unexp ected Vector Events
Issue  4 September 1995
D-17
32 Prompting buffer overflowThe prompting digit buffer already 
contained the maximum of 24 digits when 
a d ditional dial-ahead digits were entered 
by the caller. These a dditional di gits are 
not stored.
40 Messaging step failed A messaging step failed because the 
Messaging Adjunct was not available.
NOTE: Event types 540 and 541 may be 
observed for the same call at the same 
time.
50 Route -to step failed A 
route-to step failed to...

Troubleshooting Vectors
D-18Issue  4 September 1995 
61 Invalid d estinationThe adjunct routing command returned 
digits that did not represent a valid 
destination.
62 Ad junct route cancelledThe 
adjunct routing ste p was cancelled 
b e cause another routing step (such as a 
queue-to main split step) was 
encountered in the vector.
63 Queue before routeThe 
adjunct routing command was 
skip ped because the call had already 
been queued via a 
queue-to main split or 
a 
c heck-backup split command.
64...

Tracking Unexp ected Vector Events
Issue  4 September 1995
D-19
90 Wait step music failed A wait-time step with music was 
accessed, but the music was not 
connected.  Music may not b e 
administered correctly.
91 Wait step ringback failed A 
wait-time step with ringback was 
accessed, but the ringback was not 
connected.
100 Redirect unanswered callThe call was sent to an agent via a vector, 
but, due to the Redirection on No Answer 
(RONA) feature, the call was redirected 
from the ringing agent.
101...

Troubleshooting Vectors
D-20Issue  4 September 1995 
125 Data return no digits On a converse-on step, the converse 
agent activated data return b ut d i d not 
return any digits. 
126 Data return timeout On a 
converse-on step, the converse 
agent activated data return b ut timed out 
while waiting to return digits.  Vector 
processing continued at the next vector 
step.
140 Coverage conference deniedCoverage to a VDN in a coverage path 
was denied because more than one party 
was active on the call.
150...