09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Denial Events<br />

Cause Value 98<br />

[0x62/0xE2] -<br />

Message type, not compatible with call state, or non-existent, or not implemented<br />

The equipment that sent this Cause Value received a message, and the procedures in the<br />

protocol specification indicate that this is not a permissible message to receive while in this call<br />

state. A STATUS message was received indicating an incompatible call state.<br />

This Cause Value has local significance only. The ISDN network between the user and the<br />

equipment generating the Cause Value might:<br />

● Send no cause indication through the network<br />

● Send a more generic Cause Value through the network<br />

Troubleshooting<br />

Table 53: Cause Value 97, 98, 101 Diagnostic Information 2 of 2<br />

Message Type Identifier Message<br />

72 FACILITY REJECT<br />

75 STATUS ENQUIRY<br />

79 CONGESTION CONTROL<br />

Maintenance Message<br />

0F SERVICE<br />

07 SERVICE ACKNOWLEDGE<br />

2 of 2<br />

● Check that the protocols at each end of the interface match (for example, both sides are<br />

AT&T Custom or both sides are NI-2). If the ends of the interface are running different<br />

protocols, they might be running with different call state machines, or different message<br />

type encoding.<br />

● Check the diagnostic information generated by Communication Manager for the message<br />

type identifier of the message that violates protocol. See Table 53: Cause Value 97, 98,<br />

101 Diagnostic Information on page 191.<br />

● Call state problems are reported with STATUS messages. The equipment sending the<br />

Cause Value uses the CALL STATE IE of the STATUS message to indicate the call state.<br />

To determine the call state of the other end of the interface, run the message sequence of<br />

the call through the SDL flow charts of the appropriate side (user or network) and the<br />

appropriate protocol (TR41449/41459, TR1268, A211 etc.). If the call state at the other end<br />

of the interface does not agree with that reported in the STATUS message and both sides<br />

are already running the same protocol, then a problem with the implementation of the state<br />

machine exists on either side.<br />

192 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!