09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Cause Value 99<br />

Event Data<br />

Problems have been revealed with the state machine implementations of some of the CO<br />

switches for different protocols, and the state machine problems in the CO switches are<br />

most likely not going to be corrected. Communication Manager has not shown any<br />

problems with its state machine implementations for the different protocols.<br />

Change Communication Manager administration to change the message sequence of the<br />

call scenario causing the error, and help solve state machine implementation problems. For<br />

example:<br />

- change the inter-working message on the DS1 form from PROGRESS to ALERTING<br />

- change the “wait” steps in vectors to be “i-silent” so that they do not generate extra<br />

PROGRESS messages in the calling message sequence.<br />

[0x63/0xE3] -<br />

Information element non-existent or not implemented<br />

The equipment that sent this Cause Value received a message that includes Information<br />

Elements that are not recognized because the Information Element identifier is not defined, or it<br />

is defined but has not been implemented by the equipment sending the Cause Value. However,<br />

the Information Element is not mandatory in the message, and the equipment that sent the<br />

Cause Value does not need to parse the Information Element in order to process the message.<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 />

Cause Value 100<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 Information Element encoding.<br />

● Check Communication Manager administration (network generated the Cause Value).<br />

- Sending connected number information with the domestic custom Information Element<br />

identity encoding (0C), but international encoding (4C)is expected.<br />

[0x64/0xE4] -<br />

Invalid information element contents<br />

The equipment that sent this Cause Value received a message that includes an Information<br />

Element that it does recognize and implements, however one or more of the fields contained in<br />

the Information Element are coded in such a way that it has not been implemented by the<br />

equipment that sent this Cause Value.<br />

Communication Manager Release 5.0 Issue 4 January 2008 193

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

Saved successfully!

Ooh no, something went wrong!