Lucent Technologies R5SI Manual Do Utilizador
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Object Repair Procedures
Page 10-828
ISDN-TRK (DS1 ISDN Trunk)
10
j. 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-end and far-end for this trunk that is effecting
the end user (that is, customer receives unexpected intercept tones when
accessing ISDN trunks). This may indicate that the ISDN trunk is not
administered on the far-end.
mismatch between the near-end and far-end for this trunk that is effecting
the end user (that is, customer receives unexpected intercept tones when
accessing ISDN trunks). This may indicate that the ISDN trunk is not
administered on the far-end.
The Aux field contains the physical name of the ISDN trunk in decimal.
Then, verify that the far-end has this trunk administered. If problems
persist, then busy-out the ISDN trunk to take it out of the hunt group.
Then, verify that the far-end has this trunk administered. If problems
persist, then busy-out the ISDN trunk to take it out of the hunt group.
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 busy-out the ISDN trunk to take it out of the hunt
group.
incoming call that uses this trunk is answered by the called endpoint. If
problems persist, then busy-out the ISDN trunk to take it out of the hunt
group.
System Technician-Demanded Tests:
Descriptions and Error Codes
Descriptions and Error Codes
Always investigate tests in the order presented in the table below when
inspecting errors in the system. By clearing error codes associated with the
inspecting errors in the system. By clearing error codes associated with the
NPE
Crosstalk Test
, for example, you may also clear errors generated from other tests
in the testing sequence.
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.
the far-end with an ISDN RESTART message. This state is
called the "active" state.
4, 7, 8
260,
263
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.
reached a ringing state, was cleared unexpectedly by the
far-end with an ISDN RESTART message.
1, 3, 6
9, 265
9, 265
A call that has not yet reached a ringing state was cleared
unexpectedly by the far-end with an ISDN RESTART
message.
unexpectedly by the far-end with an ISDN RESTART
message.
11, 12
19,
531,
267,
268
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.
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.
Aux Data values of concern; any others can be ignored.