88  Section 6

be processed.

Cause No. 97 - Message type non-existent or not implemented

This cause indicates that the equipment sending this cause has received a message with a mes- sage type it does not recognize either because this is a message not defined, or defined and not implemented by the equipment sending this cause.

Cause No. 98 – Message not compatible

This cause indicates that the message received is not compatible with the call state or the mes- sage type is non-existent or not implemented.

Cause No. 99 – Info non-existent or not implemented, call processed

This cause is sent when the equipment sending this cause has received a message which includes the information elements not recognized because the information element identifier is not define or it is defined but not implemented by the equipment sending the cause. However, the information element is not required for the equipment sending the cause to process the message.

Cause No. 100 – Invalid information element contents

This cause is returned when the equipment sending this cause has received an information ele- ment that it has implemented; however one or more field of the information element are coded in such as way (e.g., truncated, invalid extension bit, invalid field values, etc) that has not been implemented by the equipment sending this cause.

Cause No. 101 – Message not compatible with call state/Protocol error threshold

This cause is returned when the equipment sending this cause has received a message that procedures indicate is not a permissible message to receive at this time.

or

This cause indicates that the switch sending this cause is clearing the call because a threshold has been exceeded for multiple protocol errors during an active call.

Cause No. 102 - Timeout disconnect (Recovery on timer expiration)

This cause indicates that a procedure has been initiated by the expiry of a timer in association with error handling procedures.

Cause No. 103 – Parameter non-existent or not implemented – passed on (National use)/ Mandatory Information Element of incorrect length [VN 4 only]

This cause indicates that the equipment sending this cause has received a message which includes parameter(s) not recognized because the parameter(s) are not defined of are defined but not implemented by the equipment sending this cause. This cause indicates that the parameter(s) were ignored. In addition, if the equipment sending this cause is an intermediate point, then this cause indicates that the parameter(s) were passed unchanged.

or

This cause indicates that the equipment sending this cause has received a message with a mandatory information element of incorrect length.

Cause No. 110 – Message with unrecognized parameter discarded [Q.850 only]

This cause indicates that the equipment sending this cause has discarded a received message that includes a parameter that is not recognized.

Cause No. 111 – Protocol Error, unspecified

This cause is used to report a protocol error event only when no other cause in this class applies.

Among other things, this cause may be displayed if you failed to dial a “9” or “8” for an outside line, if required. Also may be returned if you have some types of restrictions as to the number of

Page 98
Image 98
Telos NX12 user manual Cause No Message type non-existent or not implemented, Cause No Message not compatible