Telos ZephyrExpress user manual Cause No Check number, redial, Cause No No route to network

Note that in some cases there may be more than one meaning. This can frequently be evaluated by whether the message has been received by the calling party or the called party.

Cause No. 1 - Check number, redial

This cause indicates that the called party cannot be reached because, although the called party number is in a valid format, it is not currently allocated(assigned).

Cause No. 2 - No route to network

This cause indicates that the equipment sending this cause has received a request to route the call through a particular transit network which it does not recognize. The equipment sending this cause does not recognize the transit network either because the transit net- work does not exist or because that particular transit network, while it does exist, does not serve the equipment which is sending this cause.

Cause No. 3 - No route to destination. Prefix 1 dialed in error

This cause indicates that the called party cannot be reached because the network through which the call has been routed does not serve the destination desired. This cause is supported on a network-dependent basis.

or

A 1 was dialed when not required. Redial without the 1.

Cause No. 4 - No prefix 1

The prefix 1 is required for this number.

Cause No. 6 - Channel unacceptable

Channel on called unit is not available.

Cause No. 8 - Call is proceeding

Call in process, please stand by.

Cause No. 14 - Excess digits received, call is proceeding

More digits were dialed than expected. Called number has been truncated to the ex- pected number.

Cause No. 16 - Far end disconnect / Normal call clearing

This cause indicates that the call is being cleared because one of the users involved in the call or the switch has requested that the call be cleared. Under normal situations, the source of this cause is not the network.

Cause No. 17 - Busy, try again later

This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the

TROUBLESHOOTING 9-19