Server Alarms - Avaya Support

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
Event Data
● 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 the diagnostic information generated by Communication Manager for the message
type identifier of the unrecognized message.
Table 53: Cause Value 97, 98, 101 Diagnostic Information 1 of 2
Message Type Identifier Message
0D SETUP ACKNOWLEDGE
0F CONNECT ACKNOWLEDGE
01 ALERTING
02 CALL PROCEEDING
03 PROGRESS
05 SETUP
07 CONNECT
4D RELEASE
4E RESTART ACKNOWLEDGE
5A RELEASE COMPLETE
6A FACILITY ACKNOWLEDGE
6E NOTIFY
7B INFORMATION
7D STATUS
20 USER INFORMATION
45 DISCONNECT
46 RESTART
62 FACILITY
1 of 2
Communication Manager Release 5.0 Issue 4 January 2008 191