Avaya 03-300430 Home Security System User Manual


  Open as PDF
of 2574
 
Communication Manager Maintenance-Object Repair Procedures
2404 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Table 857: Test #135 Internal Loop-Around Test
Error
Code
Test
Result
Description / Recommendation
1002 ABRT The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or it may have time slots out-of-service due
to TDM-BUS errors.
1. If system has no TDM-BUS errors and is not handling heavy traffic,
repeat test at 1-minute intervals up to 5 times.
1003 ABRT The system could not allocate a tone receiver for the test. The system
may be oversized for the number of Tone Detectors present or some Tone
Detectors may be out-of-service.
1. Resolve any TTR-LEV errors.
2. Resolve any TONE-PT errors.
3. If neither condition exists, retry reset board location at
1-minute intervals up to 5 times.
1004 ABRT Received an incoming call on a port of the UDS1 circuit pack during the
test.
1. Enter busyout board location to put every trunk or port of the
UDS1 Interface circuit pack in the out-of-service state.
2. Retry reset board location at 1-minute intervals up to 5 times.
1015 ABRT Ports on the UDS1 Interface circuit pack have not been busied out.
1. Enter busyout board location to put every trunk or port of the
UDS1 Interface circuit pack into the out-of-service state.
2. Retry reset board location.
1039 ABRT The UDS1 Interface circuit pack is providing timing for the system.
Executing this test could cause a major system disruption.
If the UDS1 Interface circuit pack needs to be tested, set the
synchronization reference to another UDS1 Interface circuit pack or to the
IPSI or Tone-Clock circuit pack via the following command sequence:
1. Enter disable synchronization-switch.
2. Enter set synchronization location.
3. Enter enable synchronization-switch.
2000 ABRT Response to the test request was not received within the allowable time
period. If Error Type 1538 is present in the Error Log, follow the
maintenance strategy recommended for this Error Type.
1 of 4