Avaya 03-300430 User Manual
Denial Events
170 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Problems have been revealed with the state machine implementations of some of the CO
switches for different protocols, and the state machine problems in the CO switches are
most likely not going to be corrected. Communication Manager has not shown any
problems with its state machine implementations for the different protocols.
switches for different protocols, and the state machine problems in the CO switches are
most likely not going to be corrected. Communication Manager has not shown any
problems with its state machine implementations for the different protocols.
Change Communication Manager administration to change the message sequence of the
call scenario causing the error, and help solve state machine implementation problems. For
example:
call scenario causing the error, and help solve state machine implementation problems. For
example:
- change the inter-working message on the DS1 form from PROGRESS to ALERTING
- change the “wait” steps in vectors to be “i-silent” so that they do not generate extra
PROGRESS messages in the calling message sequence.
Cause Value 99
[0x63/0xE3] -
Information element non-existent or not implemented
The equipment that sent this Cause Value received a message that includes Information
Elements that are not recognized because the Information Element identifier is not defined, or it
is defined but has not been implemented by the equipment sending the Cause Value. However,
the Information Element is not mandatory in the message, and the equipment that sent the
Cause Value does not need to parse the Information Element in order to process the message.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
Information element non-existent or not implemented
The equipment that sent this Cause Value received a message that includes Information
Elements that are not recognized because the Information Element identifier is not defined, or it
is defined but has not been implemented by the equipment sending the Cause Value. However,
the Information Element is not mandatory in the message, and the equipment that sent the
Cause Value does not need to parse the Information Element in order to process the message.
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.
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 administration (network generated the Cause Value).
- Sending connected number information with the domestic custom Information Element
identity encoding (0C), but international encoding (4C)is expected.
Cause Value 100
[0x64/0xE4] -
Invalid information element contents
The equipment that sent this Cause Value received a message that includes an Information
Element that it does recognize and implements, however one or more of the fields contained in
the Information Element are coded in such a way that it has not been implemented by the
equipment that sent this Cause Value.
Invalid information element contents
The equipment that sent this Cause Value received a message that includes an Information
Element that it does recognize and implements, however one or more of the fields contained in
the Information Element are coded in such a way that it has not been implemented by the
equipment that sent this Cause Value.