Troubleshooting Vectors

Table D-2. Unexpected Command Operations

Command Step

Customer Observation(s)

Cause(s)

messaging split

Vector stuck (with ringback).

Extension unknown to AUDIX.

 

Step skipped, no message left.

AUDIX link down.

 

 

DCS link to remote AUDIX down.

 

 

All DCS trunks busy.

 

 

Queue for AUDIX voice ports is

 

 

full.

 

Vector stuck (with busy).

Remote AUDIX link down.

 

Messages not found.

Message extension is none

 

 

(message is left for VDN that

 

 

accessed the vector).

 

Delay before AUDIX answers.

All AUDIX ports busy, but space

 

 

in queue.

 

Busy tone.

Queue for AUDIX voice ports is

 

 

full.

 

Step skipped.

Split not AUDIX split anymore.

route-to

Step skipped (that is, default

Invalid local extension.

 

treatment).

 

 

 

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.

 

Network reorder.

Digit string inconsistent with

 

 

public network translation.

 

Intercept or reorder tone

Vector processing succeeded

 

heard.

routing off switch, but a problem

 

 

has occurred before routing to its

 

 

final destination.

 

All trunks busy on a quiet

Two switches treating each other

 

system.

as a backup switch.

stop

Call dropped.

Call not queued when vector

 

 

processing stops.

NOTE:

Complete operation details for the route to commands are presented in Appendix G.

D-8Issue 4 September 1995

Page 318
Image 318
AT&T 555-230-520 manual Command Step Customer Observations Causes