Tracking Unexpected Vector Events

Table D-4. Summary of Vector Events

 

 

Event

 

Event

 

Event

 

 

Type

 

Description

 

Explanation

220

 

EWT call not queued

 

A goto test for a call or converse data

 

 

 

 

passing requested EWT for a call not in

 

 

 

 

queue. In this case, the wait time was

 

 

 

 

assumed to be infinite and the

 

 

 

 

comparison was based on EWT > largest

 

 

 

 

possible threshold.

221

 

EWT not sent to VRU

 

The EWT “wait” time for the call was not

 

 

 

 

sent to the VRU for a converse-on passing

 

 

 

 

wait vector step because the call was not

 

 

 

 

queued or the splits/skills that the call was

 

 

 

 

queued to were unstaffed.

222

 

System clock change

 

The system clock was changed, therefore

 

 

 

 

any calculations involving time (i.e., ASA

 

 

 

 

and EWT) will be inaccurate.

230

 

II-digits not avail - digits

 

A goto test requested a comparison of II-

 

 

 

 

digits against a digit string and II-digits

 

 

 

 

were not available for the call. The

 

 

 

 

comparison test was considered false

 

 

 

 

and the next step in the vector was

 

 

 

 

executed.

231

 

II-digits not avail - table

 

A goto test requested a comparison if II-

 

 

 

 

digits against “in-table” and II-digits were

 

 

 

 

not available for the call. The comparison

 

 

 

 

test was considered false and the next

 

 

 

 

step in the vector was executed.

520

 

Split queue is full

 

A queue-to main split, check-backup split,

 

 

 

 

or messaging split command was

 

 

 

 

executed, but the call did not queue to the

 

 

 

 

split because the queue (if administered)

 

 

 

 

was full. To prevent this condition, use a

 

 

 

 

goto step...if calls queued in split...>...

 

 

 

 

before each queue-to main split or check-

 

 

 

 

backup split step so that an alternative

 

 

 

 

treatment may be provided for these

 

 

 

 

cases.

521

 

Not vector-controlled

 

The split accessed by a queue-to main

 

 

 

 

split or check-backup split command is

 

 

 

 

not vector-controlled. As a result, the step

 

 

 

 

is skipped.

522

 

AAS split cannot queue

 

A queue to main split, check backup split,

 

 

 

 

or messaging split command was

 

 

 

 

executed on an auto-available split (AAS),

 

 

 

 

but the call did not queue to the split

 

 

 

 

because all the agents were logged out

 

 

 

 

by Redirection on No Answer (RONA).

 

 

 

 

 

Issue 4 September 1995 D-21

Page 331
Image 331
AT&T 555-230-520 manual Queue-to main split, check-backup split