Table 65. Test #0 Dial Tone Test
Error Code |
Test Result |
Description/ Recommendation |
|
ABORT |
Could not allocate system resources to run this test.
- Retry the command at 1-minute intervals for a maximum of 5 times.
|
1000 |
ABORT |
System resources required to run this test are not available. The port may be busy with a valid call.
- Use the command display port UUCSSpp to determine the trunk group/member number of the port. Use the status trunk command to determine the service state of the port. If the service state indicates that the port is in use, then the port is unavailable for certain tests. You must wait until the port is idle before retesting.
- Retry the command at 1-minute intervals for a maximum of 5 times.
|
1001 |
ABORT |
System resources required to run this test were not available. This could be due to a failure to seize the port.
- Retry the command at 1-minute intervals for a maximum of 5 times.
|
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.
- If the system has no TDM-BUS errors and is not handling heavy traffic, retry the command at 1-minute intervals for a maximum of 5 times.
|
1004 |
ABORT |
The port was seized by a user for a valid call.
- Use the display port UUCSSpp command to determine the trunk group/member number of the port. Use the status trunk command to determine the service state of the port. If the service state indicates that the port is in use, then the port is unavailable for certain tests. You must wait until the port is idle before retesting.
- If the port status is idle, retry the command at 1-minute intervals for a maximum of 5 times.
|
1005 |
ABORT |
Trunk has been administered as incoming-only; dial tone can only be obtained on outgoing trunks. This is a normal condition. |
1018 |
ABORT |
Test has been disabled via administration.
- Verify that the "Maintenance Tests?" field on the Trunk Group Form is set to "n." To enable the test, issue the change trunk-group x command where "x" equals the number of the trunk group to be tested. Then change the entry in the "Maintenance Tests?" field on the form to "y."
|
2000 |
ABORT |
Response to the test was not received within the allowable time period.
- Retry the command at 1-minute intervals for a maximum of 5 times.
|
|
FAIL |
Trunk was seized, but dial tone could not be detected.
- Test all administered outgoing ports on the board. Failure of 1 indicates a problem toward the CO.
- If all fail, see note below.
- Check for errors on the TONE-BD or TONE-PT. Clear any errors found, and repeat the test.
- If the error has still not cleared, refer the problem to the CO.
- If no service problems exist on the port, continue to use the port until the circuit pack can be replaced (as a last resort). Perform a trunk test call to see if the trunk is operable.
If the dial tone test fails for all ports on a circuit pack, a -5 volt power problem is indicated. To investigate problems with a power unit, refer to "CARR-POW".
|
2002 |
FAIL |
Seizure portion of test failed due to hardware problem. Fault is usually caused by a disconnected trunk.
- If the CO Demand Diagnostic Test (#3) also failed, display the Hardware Error Log. If the CO Demand Diagnostic Test failed because it could not detect ground (indicated by Error Type 1281 in the Hardware Error Log) AND Error Type 3329 or 3585 appears in the Hardware Error Log (with the same last occurred time as Error Type 1281 and 1537), replace the circuit pack.
- Check trunk wiring to ensure good connection; repeat test if wiring correction made.
- Locate another identical CO trunk and swap its wiring with one under test. Repeat test on both trunks and determine if problem follows trunk or remains at original port. If problem follows trunk, refer problem to CO. If problem remains at port, replace circuit pack and repeat test.
|
1009 |
PASS |
Detected tone was not pure dial tone. No action required. |
|
PASS |
Trunk was seized, and dial tone was detected. User-reported troubles on this port should be investigated by using other port tests and by examining trunk or external wiring. |
0 |
NO BOARD |
The test could not relate the internal ID to the port.
- Check to ensure that the board translations are correct. Translate the board, if necessary.
- Issue the busyout board command.
- Issue the reset board command.
- Issue the release busy board command.
- Issue the test board command. This should re-establish the linkage between the internal ID and the port.
|
|