Server Alarms - Avaya Support

SIP-SGRP (SIP Signaling Group)
Table 325: Descriptions and Recommendations for Error Types 3842-3942 7 of 9
Error
Code
Description/Recommendation
3928 Cause Value 88. A call was denied because a basic incompatibility existed
between the type of call and either the facilities selected by the routing pattern or
the called user. This error may offer a clue if the customer complains of receiving
unexpected intercept tone.
1. Determine the trunk group from the circuit pack or media module and port
number (in the Aux Data field).
2. Check the BCC fields of the pertinent routing patterns.
3. Investigate whether or not the calling and called endpoints are compatible
(for example, some switches may not allow a voice station to call a data
extension).
3942 Cause Value 102. Recovery on timer expiry. No answer to CALL PROCEEDING.
The equipment sending this Cause Value sent or received a Layer 3 Q.931
message. Sending or receiving this message has initiated a Layer 3 timer that has
expired. This Cause Value is being generated in conjunction with Q.931 protocol
error handling procedures. 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.
The repair steps are based on recommendations from Tier 4 ISDN experience:
1. Check the diagnostic information for the timer number that has expired.
2. Check that the protocols at each end of the interface match (for example,
both sides are NI-2).
If the ends of the interface are running different protocols, they might be
running with different values for their Layer 3 timers.
If the protocols at each end of the interface match, the Communication
Manager timer might have expired because:
a. The far-end never saw the message because the message was
corrupted in transmission by noise on the D-Channel. 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-Channel. Perform an external protocol capture on the
D-Channel to confirm the transmission of the suspect message.
7 of 9
Communication Manager Release 5.0 Issue 4 January 2008 1199