Unexpected Command Operations

Unexpected Command Operations

The following table indicates and explains the unexpected operations the customer may encounter in using the Call Vectoring commands.

Table D-2. Unexpected Command Operations

 

 

Command Step

 

Customer Observation(s)

 

Cause(s)

 

 

adjunct routing

 

Step skipped (that is, default

 

Invalid link extension.

 

 

treatment).

 

No trunks available.

 

 

 

 

 

 

 

 

COR/FRL restricted.

 

 

 

 

Timeout. (Application did not

 

 

 

 

respond within the time specified

 

 

 

 

in the wait-timecommand

 

 

 

 

and/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.

 

Digit string supplied by adjunct

 

 

 

 

inconsistent with public network

 

 

 

 

translation.

 

 

 

 

Digit string inconsistent with

 

 

 

 

networking 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 backup switch.

 

 

Step skipped.

 

Port Network (PN) link down.

 

 

 

 

 

Issue 4 September 1995 D-3

Page 313
Image 313
AT&T 555-230-520 manual Unexpected Command Operations