Avaya 03-300430 User Manual

c. Error Type 357: this error indicates the TDM bus was switched to the other bus due to TDM 

bus corruption. The Aux Data value is not meaningful and no action is required. Look for 
other TDM-BUS errors to determine the cause of this error.

d. Error Type 513: some time slots are corrupted in the specified TDM bus. The Minor alarm 

is raised when there are more than 50 bad time slots in the bus. The Aux Data indicates the 
number of bad time slots found by the test.

e. Error Type 769: some time slots are corrupted in the specified TDM bus. The Warning 

alarm is raised when there are more than 10 bad time slots but less than or up to 50 bad 
ones in the bus. The Aux Data value indicates the number of bad time slots found by the 
test.

f. Error Type 769: this error indicates the idle time slot test found less than 10 bad time slots 

in the TDM bus. The Aux Data value indicates the number of bad time slots found by the 
test. There is no alarm associated with this error.

g. Error Type 1025: the daily TDM bus switch was not successful. The active Expansion 

Interface (PN) cannot talk on the bus that software was trying to switch into. There is no 
alarm associated with this error.

h. Error Type 3872, 3873, 3874, and 3877: these errors indicate communication problems 

which may be causing message loss. TDM bus maintenance may switch the Control 
Channel bus and/or Tone bus to the other bus. Test the TDM bus using test tdm P and 

follow the procedures according to the Error Codes reported from the test. The Aux Data 
value shows the Angel ID number for which a downlink message was lost.

Investigate tests in the order presented below. Clearing Error Codes associated with the one 
test may also clear errors generated from other tests in the sequence.

1. D = Destructive; ND = Nondestructive

Control Channel test on the Control Channel Bus (#296)

X

X

ND

Digit Detection test on the Non-Control Channel Bus (#297)

X

X

ND

Idle Time Slot test (#294)

X

X

ND