Cause No. 97 - Message type nonexistent or not implemented

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

Cause No. 99 - Information element non existent or not implemented

This cause indicates the equipment sending this cause received a message that includes an information element identifier not recognized because the information element identifier is undefined, or it is defined but not implemented by the equipment sending this cause.

Cause No. 100 - Invalid information element contents

This cause indicates the equipment sending this cause received an information element that it has implemented; however one or more fields of the information element are coded in a way that has not been implemented by the equipment.

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

This cause indicates the equipment sending this cause received a message that procedure indicate is not permissible at this time.

or

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

Cause No. 102 - Timeout disconnect

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

Cause No. 111 - Protocol Error, Unspecified

Among other things, this cause can be displayed if you failed to dial the appropriate code for an outside line from an internal system (usually the digit 7, 8, or 9). Also may be returned if you have some types of restrictions as to the number of calls, etc.

Cause No. 118 -

Cause No. 127 - SW56 disconnect/Internetworking, unspecified

This cause indicates that an interworking call (usually a call to SW56 service)

has ended. May also be seen in the case of a non-specific rejection by your long distance carrier (try again at a different rate).

TROUBLESHOOTING 9-23

Page 165
Image 165
Telos ZephyrExpress Cause No Message type nonexistent or not implemented, Cause No Invalid information element contents