Previous page Next page

Error Log Entries and Test to Clear Values
Table 44. DS1 ISDN Trunk Error Log Entries
Error Type
Aux Data
Associated Test
Alarm Level
On/Off Board
Test to Clear Value
0*
0
Any
Any
Any
test port GGGVSpp
1(a)
Any
None


test port GGGVSpp
15(b)
Any
Audit and Update Test (#36)



18
0
busyout trunk grp/mbr


release trunk grp/mbr
19(c)
0
None



129(d)

None
WARNING
OFF
test port GGGVSpp
130(e)

None
WARNING
ON
test port GGGVSpp
257(f)
Any
None


test port GGGVSpp
513(g)
Any
None
WARNING
OFF
test port GGGVSpp
769(h)
Any
None


test port GGGVSpp
1025
0
None



1793(i)
Any
None


test port GGGVSpp
3073(j)
Any
Service State Audit (#256)


test port GGGVSpp
3585(k)
Any
None


none
3841(l)
Any
None
WARNING
OFF
None
*Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate test description and follow the recommended procedures.
**Major or minor alarms may be downgraded to Warning alarms based on the value used in the set options command.

Notes:

Table 45. 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
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.


Previous page Next page