Filter
Top Products
Communication Manager Maintenance-Object Repair Procedures
876 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Digital Loop-Around Test (#171)
The Digital Looparound test checks the data line port’s ability to transmit and receive data on
the TDM Bus. Data is sent through an available Maintenance/Test digital port over the TDM
Bus, internally looped through the data line port back onto the TDM Bus, and received again by
the same Maintenance/Test digital port.
Only one of the two digital ports on a Maintenance/Test circuit pack is used for this test, and that
port must be the first such port; such as port 02. If port 02 is in use, out-of-service, or not
present, the test aborts. This test may fail if the Maintenance/Test digital port used by the test is
not functioning properly. If there are any M/T-DIG errors in the Error Log, see M/T-BD
(Maintenance/Test Circuit Pack) on page 1705 to clear them first.
This test will pass regardless of any customer equipment that may be connected to the port, as
long as the equipment is not using the port.
Table 300: Test #171 Digital Loop-Around Test
Error
Code
Test
Result
Description / Recommendation
ABRT Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
1000 ABRT System resources required to run test are not available. The port may be in
use on a valid call. Use status data-module to determine when the port
is available for testing.
1. Retry the command at 1-minute intervals up to 5 times.
1005
1007
ABRT Data Channel 3 is not administered. This port is required to run this test.
1. Verify that data channel 3 is not administered with list
data-module. Administer data channel 3 with add data-module,
and run this test again.
1016 ABRT Data Channel 3 is busy. The port may be in use on a valid call. Use status
data-module to determine when the port is available for testing.
1. Retry the command at 1-minute intervals a maximum of 5 times.
1020 ABRT An existing Error Type #769 on this port prevented the test from running.
1. Follow the procedure following the Error Log Table for Error Type #769.
1 of 4