Demand test descriptions and error codes - Avaya Support

Table 230: Descriptions and Recommendations for Error Types 3842-3942 9 of 10
Error
Code
3942
(cont’d)
Description/Recommendation
3. To interpret the receipt of Cause Value 102 from the far-end, look at a trace/
protocol capture of the messaging taking place, and find the last message
received from the far-end before Cause Value 102 is received. The timer
that expired is most likely the Layer 3 timer associated with that last
message. If Communication Manager generated a message in between
those two events that should have stopped the timer, the cause might be:
a. The far-end never saw the message because the message was
corrupted in transmission by noise on the D-Chel. Check for any type of
T1/E1 facility errors.
b. The far-end is experiencing a high traffic condition and did not have the
processing time to parse the sent message before the timer expired.
c. Even though the message was seen to be generated in an internal
Communication Manager trace, the message was never transmitted out
onto the D-Chel. Perform an external protocol capture on the D-Chel to
confirm the transmission of the suspect message.
4. If Communication Manager did not respond to the receipt of the last
message from the far-end, then Communication Manager internal hardware
and software become suspect, and troubleshooting the problem must
proceed from that point.
5. Communication Manager administration that can contribute to seeing timer
expiry errors:
a. Trunk group form: Incoming call handling table. If the Per call CPN/BN
field is incorrectly populated in comparison to how the CO is
programmed to send CPN or BN, it causes Communication Manager to
send a FACILITY message to the CO requesting CPN/BN information
and the CO will never respond. Communication Manager will log many
timer expiry errors against the signaling group (Error Type 1, Aux Data
13).
b. DS1 form: Protocol version: If Communication Manager is running
custom protocol (protocol version A) and is connected to a Nortel DMS
central office running custom protocol, Communication Manager will log
timer expiry errors against the signaling group for DISCONNECT
problems (Error Type 1, Aux Data 4) during high traffic conditions.
840 Maintenance Alarms for Communication Manager, Media Gateways and Servers
9 of 10