Avaya 03-300430 User Manual

[0x62/0xE2] -
Message type, not compatible with call state, or non-existent, or not implemented
The equipment that sent this Cause Value received a message, and the procedures in the 
protocol specification indicate that this is not a permissible message to receive while in this call 
state. A STATUS message was received indicating an incompatible 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

●

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 call state machines, or different message 
type encoding.

●

Check the diagnostic information generated by Communication Manager for the message 
type identifier of the message that violates protocol. See 

●

Call state problems are reported with STATUS messages. The equipment sending the 
Cause Value uses the CALL STATE IE of the STATUS message to indicate the call state. 
To determine the call state of the other end of the interface, run the message sequence of 
the call through the SDL flow charts of the appropriate side (user or network) and the 
appropriate protocol (TR41449/41459, TR1268, A211 etc.). If the call state at the other end 
of the interface does not agree with that reported in the STATUS message and both sides 
are already running the same protocol, then a problem with the implementation of the state 
machine exists on either side.

72

 FACILITY REJECT

75

 STATUS ENQUIRY

79

CONGESTION CONTROL

0F

 SERVICE

07

 SERVICE ACKNOWLEDGE

 2 of 2