19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Polycom</strong> <strong>RMX</strong> 1500/<strong>2000</strong>/4000 Administrator’s <strong>Guide</strong><br />

Table A-2 ISDN Disconnection Causes (Continued)<br />

86 Call Having the<br />

Requested Call Identity<br />

Has Been Cleared<br />

87 User Not Member of<br />

CUG<br />

88 Incompatible<br />

Destination<br />

90 Non-Existent CUG CUG does not exist.<br />

91 Invalid Transit Network<br />

Selection (national use)<br />

95 Invalid Message,<br />

Unspecified<br />

96 Mandatory Information<br />

Element is Missing<br />

97 Message Type Non-<br />

Existent or Not<br />

Implemented<br />

98 Message is Not<br />

Compatible with the<br />

Call State, or the<br />

Message Type is Non-<br />

Existent or Not<br />

Implemented<br />

99 An Information Element<br />

or Parameter Does Not<br />

Exist or is Not<br />

Implemented<br />

100 Invalid Information<br />

Element Contents<br />

101 The Message is Not<br />

Compatible with the<br />

Call State<br />

102 Recovery on Timer<br />

Expired<br />

Disconnection Cause<br />

Number Summary Description<br />

A RESUME message cannot be executed by the network as<br />

a result of the call having been cleared while suspended.<br />

A CUG member was called by a user that is not a member of<br />

the CUG or a CUG call was made to a non CUG member.<br />

User-to-user compatibility checking procedures in a point-topoint<br />

data link have determined that an incompatibility exists<br />

between Bearer capabilities.<br />

The transit network selection is of an incorrect format. No<br />

route (transit network) exists between the two networks.<br />

Invalid message received. No other disconnection cause<br />

applies.<br />

A message was received with an information element<br />

missing.<br />

A message was received that is of a type that is not defined<br />

or of a type that is defined but not implemented.<br />

An unexpected message or unrecognized message<br />

incompatible with the call state has been received<br />

A message was received containing elements or parameters<br />

that are not defined or of a type that is defined but not<br />

implemented.<br />

A message other than SETUP, DISCONNECT, RELEASE, or<br />

RELEASE COMPLETE has been received which has one or<br />

more mandatory information elements containing invalid<br />

content.<br />

A STATUS message indicating any call state except the Null<br />

state has been received while in the Null state.<br />

An error handling procedure timer has expired.<br />

A-10 <strong>Polycom</strong>, Inc.

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

Saved successfully!

Ooh no, something went wrong!