Demand test descriptions and error codes - Avaya Support

The meanings of Aux Data values are shown below; ignore any others.
Table 160: ISDN Trunk - Error 3585 Aux Data Values
Aux
Data
Cause
0 A idle trunk received a restart.
10 A call in a stable, talking state was cleared unexpectedly by the far end with
an ISDN RESTART message. This state is called the “active” state.
4,
7,
8,
260,
263
1,
3,
6,
9,
265
11,
12,
19,
531,
267,
268
A call that has not reached the active state, but has at least reached a
ringing state, was cleared unexpectedly by the far end with an ISDN
RESTART message.
A call that has not yet reached a ringing state was cleared unexpectedly by
the far end with an ISDN RESTART message.
A call that was in the process of clearing anyway has been cleared by the far
end with an ISDN RESTART message. If this condition occurs frequently, it
may mean that the far end is attempting to clear trunks that it thinks are in a
“hung” state. The RESTART message brings the trunk to an idle condition.
m. Error Type 3841: An ISDN trunk selected by the near end has been rejected 10 times by
the far end without a successful call. This may indicate a service-state mismatch between
the near and far ends for this trunk that is affecting the end user (that is, customer receives
unexpected intercept tones when accessing ISDN trunks). This may indicate that the ISDN
trunk is not administered at the far end.
The Aux field contains the physical name of the ISDN trunk in decimal. Using this decimal
name, verify that the far end has this trunk administered.
The Warning alarm will be retired automatically whenever an outgoing or incoming call that
uses this trunk is answered by the called endpoint. If problems persist, then busyout the
ISDN trunk to take it out of the hunt group.
566 Maintenance Alarms for Communication Manager, Media Gateways and Servers