19.08.2013 Views

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix A-Disconnection Causes<br />

ISDN Disconnection Causes<br />

A-10<br />

Table A-2 ISDN Disconnection Causes<br />

Disconnection Cause<br />

Number Summary Description<br />

1 Unallocated<br />

(unassigned<br />

number)<br />

2 No route to<br />

specified transit<br />

network<br />

(national use)<br />

3 No route to<br />

destination<br />

4 Send special<br />

information tone<br />

5 Misdialed trunk<br />

prefix (national<br />

use)<br />

6 Channel<br />

Unacceptable<br />

7 Call awarded<br />

and being<br />

delivered in an<br />

Established<br />

channel<br />

No route to the number exists in the ISDN<br />

network or the number was not found in the<br />

routing table.<br />

• Ensure that the number appears in the<br />

routing table.<br />

• Ensure that it is a valid number and that<br />

correct digits were dialed.<br />

The route specified (transit network) between<br />

the two networks does not exist.<br />

No physical route to the destination number<br />

exists although the dialed number is in the<br />

routing plan.<br />

• The PRI D-Channel is malfunctioning.<br />

• Incorrect connection of the span or WAN.<br />

Return the special information tone to the<br />

calling party indicating that the called user<br />

cannot be reached.<br />

A trunk prefix has erroneously been included in<br />

the called user number.<br />

The sending entity in the call does not accept<br />

the channel most recently identified.<br />

The incoming call is being connected to a<br />

channel previously established for similar calls.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!