Avaya Definity SI, Руководство по обслуживанию, Страница: 1772 / 2968

Maintenance Object Repair Procedures
555-233-123 10-986 Issue 4 May 2002
h. An unexpected SERVICE or SERVICE ACK was received. Possibilities
include:
■
Translations conflict
■
Protocol differences
■
ESS may be using NI3 protocol which is not currently implemented
in DEFINITY
■
B-channel negotiation problem (glare)
i. This error indicates a failure of the DS1/UDS1 Interface circuit pack. When
running the Short Test Sequence, the results of the Signaling Link State
Check Test (#255) are important.
j. Two Service State Audit attempts have failed (see Test #256). The trunks
will not be usable for any outgoing calls (although incoming calls will be
accepted) until the test passes and the trunk state is changed to in-service
(use status trunk trunk_group/trunk_member to investigate trunk
status).
k. Error Type 3585 appears when the switch receives an ISDN RESTART
message for an ISDN trunk. Calls are cleared with the RESTART message.
Therefore, this error type may be associated with a dropped call report
from a user.
The following Aux Data values for Error Type 3585 represent the trunk’s
ISDN call state at the time the unexpected request to restart the channel
was received from the remote switch. This information can be useful if
dropped calls (cutoffs) are being reported by users of the ISDN-PRI trunks.
The meanings of the various Aux Data values are shown below.
Aux Data values of concern; any others can be ignored.
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 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.
1, 3, 6
9, 265 A call that has not yet reached a ringing state was cleared
unexpectedly by the far-end with an ISDN RESTART message.
11, 12
19, 531,
267,
268 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.