Avaya S8700 - Page 1893

M/T-DIG (Maintenance/Test Digital Port)
Issue 1 May 2002
8-1171555-233-143
Digital Port Sanity Test (#565)
This test verifies that the port circuitry involved in the digital trunk testing on the
Maintenance/Test digital port is functioning properly. This circuitry is common to
both Maintenance/Test digital ports on the Maintenance/Test circuit pack.
Therefore, this test is only run for port 2. The test will abort when run on port 3, as
described in Table 8-480.
This test operates by connecting the two Maintenance/Test digital ports on the
TDM bus so that they talk and listen to each other. Then four self-tests are
attempted: (a) sending data from port 2 to port 3 in asynchronous mode; (b)
sending data from port 3 to port 2 in asynchronous mode; (c) sending data from
port 2 to port 3 in synchronous mode; and (d) sending data from port 3 to port 2 in
synchronous mode. The test passes if all four of these self-tests are successful.
The test will stop as soon as any one of these self-tests fails.
This test will abort if an ISDN test call is in progress on either Maintenance/Test
digital port when the test is requested or if an ISDN test call is initiated while the
Digital Port Sanity test is in progress.
Table 8-480. Test #565 Digital Port Sanity Test
Error
Code
Tes t
Result Description / Recommendation
1000 ABORT One of the Maintenance/Test digital ports is busy with background
maintenance.
1. Either wait for the port to become idle, or busyout both Maintenance/Test
digital ports on the Maintenance/Test circuit pack via the busyout port
UUCSS02 and busyout port UUCSS03 commands, respectively.
2. Release the ports (if they were busied out) via the release port UUCSS02
and release port UUCSS03 commands, respectively.
3. Retry the command at 1-minute intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1002 ABORT 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 the system has no TDM-BUS errors, and if not handling heavy traffic,
repeat the test at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
Continued on next page