Avaya 03-300430 Home Security System User Manual


  Open as PDF
of 2574
 
Event Data
Issue 1 June 2005 171
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
Send no cause indication through the network
Send a more generic Cause Value through the network
Troubleshooting
Check that the protocols at each end of the interface match (for example, both sides are
AT&T Custom or both sides are NI-2). If the ends of the interface are running different
protocols, they might be running with different Information Element encoding.
Check Communication Manager diagnostics for the IE identifier of the Information Element
that contains the information that violates protocol.
The PROGRESS INDICATOR IE information that Communication Manager generates
should not affect call completion. There is no way to modify how Communication Manager
generates this information.
See Table 45, Cause Value 96 & 100 Diagnostic Information,
on page 166.
Cause Value 101
[0x65/0xE5] -
Message not compatible with call state/
Protocol threshold exceeded (NI-2: National ISDN 2)
Cause Value 101 indicates that the equipment that sent this Cause Value received a message
that it does recognize, and procedures in the protocol specification indicate that it is not
permissible to receive the message while in this call state.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
Send no cause indication through the network
Send a more generic Cause Value through the network
Cause Value 101 (NI-2) can also mean that an established call or an establishing call is being
cleared because the threshold for multiple signaling protocol errors occurring during an active
call has been exceeded.
Troubleshooting
Check that the protocols at each end of the interface match (for example, both sides are
AT&T Custom or both sides are NI-2). If the ends of the interface are running different
protocols, they might be running different call state machines.
Check the Communication Manager diagnostic information for the message type identifier
that is in violation of the protocol. Table 46: Cause Value 97, 98, 101 Diagnostic
Information on page 168