adjunct routing link

Step skipped

• Invalid link extension

• No trunks available

• COR/FRL restricted

• Time out. Application does not respond within the time specified in the wait-time command or within the time length of the recorded announcement.

• Digit string inconsistent with networking translation

• ASAI link down

• Invalid route destination returned from adjunct

Busy tone

Busy local destination has no available coverage points

Network reorder or intercept

• The digit string supplied by the adjunct is inconsistent with public network translation

• The digit string is inconsistent with the networking translation

Intercept or reorder tone is heard

Vector processing succeeded routing off Communication Manager, but a problem has occurred before routing to the final destination

All trunks are busy on a quiet system

Two Communication Manager treating each other as a backup Communication Manager

Step skipped

The Port Network (PN) link is down

A variable represents an invalid number such as out of range or null. The variable is assigned the pound (#) sign character and an event is generated.

announcement

Announcement not heard

• The announcement board is not present

• The announcement is not administered

• The announcement is not recorded

• The announcement is being rerecorded

• All ports are busied out

• The announcement restore is in progress

• The link to the announcement circuit pack is down

Extra delay before hearing announcement

• The announcement queue is full

• All of the integrated announcement ports are busy

• The analog announcement is busy

Vector processing stops

The analog announcement does not answer

Listening to silence after announcement

The announcement is the last step

Incomplete announcement

• The agent becomes available

• The previous adjunct routing link step succeeds

busy

Ringback heard instead of busy tone

Unanswered CO trunk

check

Call does not enter queue or terminate to agent

Step condition not met

check and queue-to

Call does not enter queue or terminate to agent

• Queue length specified on the Hunt Group screen has been exceeded

• Invalid split

• Split not vector-controlled

• Already queued to three different splits

• No queue

• Queue or check status indicates space when queue is full due to direct agent calls

• Best keyword is used but consider series is not defining best data

Call apparently answered in wrong order

• Call being re-queued at different priority

• Call superseded by higher priority call, including direct agent call

Call is not routed to remote best location

No trunk available

collect digits

Announcement not heard while waiting for digits, but network billing indicates that the call was answered

• Announcement board not present

• Announcement not administered

• Announcement not recorded

• Announcement being rerecorded

• All ports busied out

• Announcement restore in progress

• Dial ahead digit exists

Collect step and announcement skipped

• TTR not in system

• Link to PN that has TTR is down

• TTR queue full

Delay before hearing announcement

• All TTR ports busy, but space in queue

• Announcement queue full

• All integrated announcement ports busy

• Analog announcement busy

Vector stuck

Analog announcement does not answer

Dial-ahead digits not recognized

• Dial-ahead digits entered prior to first collection step

• Call transferred

• LAI attempt made

• TTR released

• 24 digits already provided

• Call Prompting time-out since the last digit was entered

Vector processing halted at collect step. Announcement heard again upon return.

Call put on hold, transferred, or conferenced

Insufficient digits collected. Call routed to intercept.

• Caller dialed the pound (#) sign too soon

• Caller dialed * without reentering correct digits

• Call Prompting inter-digit time out

Caller information button denied

• No digits were collected

• Display not in Normal mode

Collect announcement not heard and first collected digit incorrect

System does not contain all TN748C Vintage 5 or later circuit packs

Incomplete announcement

• Agent becomes available

• First digit dialed

consider

Local split/skill best (in primary vector or status poll vector)

If split or skill number is correct, split or skill has no agents logged in, no queue slots available, or all agents are in the Aux Work mode

Remote location is never best

No BSR application plan assigned to Primary VDN. Location number not assigned in application plan. Missing routing number for Status Poll VDN. No vector assigned to Status Poll VDN. Step in Status Poll vector is initializing best data before reply-best step.

A step is skipped

A variable represents an invalid number, such as out of range or null and an event is generated

VRU script not executed

Queue full. No queue. Invalid split. Split not vector-controlled. VRU down.

Ani digits not passed

ANI not available

Qpos digits not passed

Call not queued to a non-converse split

No data returned from VRU

No TTRs available

VRU script terminated prematurely

Agent becomes available. VRU script attempted to transfer the call.

Wait digits not passed

Call not queued or no working agents in splits where call is queued.

disconnect

Announcement not heard

• Announcement board not present

• Announcement not administered

• Announcement not recorded

• Announcement being rerecorded

• All ports busied out

• Announcement restore in progress

Extra delay

• Announcement queue is full

• All integrated announcement ports busy

• All analog announcements busy

Vector stuck

Analog announcement does not answer

goto step

Branch is not made to the specified step

• Step condition not met

• System time not set

goto vector

Branch is not made to the specified vector

Step condition not met

Vector stuck

Goto vector with no steps or with all failed steps

messaging

Vector stuck with ringback

A variable represents an invalid number such as out of range or null. The variable is assigned the pound (#) sign and an event is generated.

messaging split

Vector stuck with ringback

Extension unknown to the messaging system

Step skipped, no message left

• Messaging-system link is down

• DCS link to the remote messaging system is down

• All DCS trunks busy

• Queue for messaging-system voice ports is full

Vector stuck with busy tone

Remote messaging-system link down

Messages not found

Message extension is none. Message is left for VDN that accessed the vector.

Delay before messaging-system answers

All messaging-system ports are busy, but there is space in the queue

Busy tone

Queue for the messaging-system voice ports is full

Step skipped

Split not a messaging-system split anymore

reply-best

Status poll VDN/vector not processing any calls

Incoming call not ISDN or SIP. No application plan defined for BSR application. Status Poll VDN routing number missing from or wrong in application plan.

Step skipped

• Invalid local extension

• No trunks available

• COR/FRL restricted

• Digit string inconsistent with networking translation

• Busy local destination (route to digits without coverage and route to number)

• No digits collected

• Step condition not met

Network reorder

Digit string inconsistent with public network translation

Intercept or reorder tone heard

Vector processing succeeded routing off Communication Manager, but a problem has occurred before routing to its final destination

All trunks busy on a quiet system

Two Communication Manager treating each other as a backup Communication Manager.

set

A variable or digits buffer is assigned the pound (#) sign

stop

Call dropped

Call not queued when vector processing stops

wait-time

Audible feedback longer than delay interval

• Queuing for an announcement or for a TTR

• Stop command executed

Audible feedback shorter than delay interval

• Agent becomes available

• Previous adjunct routing link step succeeds

Music not heard

• No music port administered

• Music source disconnected or turned off

Alternate audio or music source not heard

• Announcement board not present

• Audio or music source not administered

• Audio or music source not recorded

• Audio or music source being rerecorded

• All ports busied out

• Announcement restore in progress