Server Alarms - Avaya Support

SIP-SGRP (SIP Signaling Group)
Table 325: Descriptions and Recommendations for Error Types 3842-3942 3 of 9
Error
Code
Description/Recommendation
3846 Cause Value 6. The far-end switch has indicated that the B-Channel (trunk) is not
acceptable for use in the call for which it was requested.
This could indicate an administration problem (for example, the local switch and
the far-end switch have different B-Channels administered), or could reflect the
occurrence of a normal race condition (for example, the local switch has
requested use of a B-Channel that the far-end switch had just reserved for use
on another call).
1. From the circuit pack or media module and port number (in the Aux Data
field), determine the trunk group against which the error was reported.
2. Enter status trunk for the indicated trunk. Refer to DS1 ISDN Trunk
Service States and ISDN-PRI Trunk Service States sections of ISDN-TRK
(DS1 ISDN Trunk) for recovery suggestions.
3858 Cause Value 18. The switch sent a message to the far-end switch or terminal
adapter that did not respond in the time allowed. The remote device/endpoint did
not respond with an ALERTING/PROGRESS/CONNect indication within the time
administered in the T303 or T310 timers Q.931 specification. Cause Value 18
indicates high traffic conditions in the serving network or noisy conditions on the
span carrying the D-channel messaging. The noise is causing the loss of
messages being sent to the remote device. The remote device might also be
unable to respond to the incoming SETUP message. This Cause Value has
end-to-end significance and should always be passed back through the network to
the user.
3878 Cause Value 38. The far-end switch has indicated that the network is not
functioning correctly and that the condition may last a relatively long period of
time (for example, immediately re-attempting the call may not be successful).
The network is out of order.
1. From the circuit pack or media module and port number (in the Aux Data
field), determine the trunk group against which the error was reported.
2. Consult with the network provider to determine the nature and expected
duration of the out-of-service condition.
3. Consider modifying every routing pattern containing this trunk group to route
calls around the network that is out of service.
3 of 9
Communication Manager Release 5.0 Issue 4 January 2008 1195