Telos TWOx12 - Page 173

TELOS TWOX12 USER’S MANUAL
TECHNICAL DATA & TROUBLESHOOTING
CHAPTER 8 161
CLASS 1.6 (Protocol error; e.g. unknown message)
Cause No. 96 – Mandatory Info missing
This cause indicates that the equipment sending this cause has received a message which is
missing an information element which must be present in the message before that message
can 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
message 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
message 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
element 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.