Lucent Technologies Release 7 Manuale Utente
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-431
CO-TRK (Analog CO Trunk)
9
Aux data 57424
—
No loop current on outgoing call
Aux data 57484
—
No dial tone on outgoing call
These errors will cause the Dial Tone Test (#0) to run and are only
considered a problem if the Dial Tone Test fails (in which case Error Type
1537 will also show up). In this case, the trunk may be put in
"Ready-for-Service" state (shown as "disconnected" by status command),
which allows only incoming calls. Run the Dial Tone Test (#0) and follow its
outlined procedures.
considered a problem if the Dial Tone Test fails (in which case Error Type
1537 will also show up). In this case, the trunk may be put in
"Ready-for-Service" state (shown as "disconnected" by status command),
which allows only incoming calls. Run the Dial Tone Test (#0) and follow its
outlined procedures.
If error count associated with this error type is very high (i.e., 255) and if
Alarm Status on the Hardware Error Report is "n" (not alarmed), then the
existence of this error type indicates that, despite the fact that many in-line
error messages have been received, all Call Seizure Tests have passed.
Problems at the CO may cause this condition rather than problems with
the PBX.
Alarm Status on the Hardware Error Report is "n" (not alarmed), then the
existence of this error type indicates that, despite the fact that many in-line
error messages have been received, all Call Seizure Tests have passed.
Problems at the CO may cause this condition rather than problems with
the PBX.
e. These errors will be logged for all versions of the CO-TRK/CO-BD.
However, no MINOR alarms will be generated for Central Office Trunks
[TN747B] with vintages V8 or greater. Any failures received by this test will
still be logged as Error type 1025/1281.
[TN747B] with vintages V8 or greater. Any failures received by this test will
still be logged as Error type 1025/1281.
Check for the use of MFT/Range extenders. If there are extenders present,
and there are no other complaints or maintenance errors against this
trunk, then there is a good chance that Test #3 failed due to excessive
loop current and may be ignored.
and there are no other complaints or maintenance errors against this
trunk, then there is a good chance that Test #3 failed due to excessive
loop current and may be ignored.
f. Error 3840 indicates that test calls made by the Automatic Transmission
Measurement System (ATMS) returned measurements in the
unacceptable range. Error 3841 indicates measurements were in the
marginal range. Use list testcall detail to examine the specific
transmission parameters which are out of spec, and investigate the trunk
for that kind of noise. If the noise is acceptable, then the AMTS thresholds
administered on page 4 of the trunk group form should be changed.
unacceptable range. Error 3841 indicates measurements were in the
marginal range. Use list testcall detail to examine the specific
transmission parameters which are out of spec, and investigate the trunk
for that kind of noise. If the noise is acceptable, then the AMTS thresholds
administered on page 4 of the trunk group form should be changed.
Table 9-180.
CO Trunk Errors with No Tests
Error
Type
Aux
Data
Error Description and Repair Action
1
57347
Port error. Ringing without ground. This error is detected on an incoming
call on a ground-start CO trunk. The CO trunk circuit pack has not detected
a Tip ground before ringing current is detected. This may indicate that the
ground detector is not working. However, the call will be accepted. Busyout
the affected port, and run a long test. Observe the test results. If any tests
fail, refer to the description of the tests and the associated error codes.
Release the port. If users continue to report troubles, check for other errors
and make test calls to determine whether the problem should be referred to
the CO.
call on a ground-start CO trunk. The CO trunk circuit pack has not detected
a Tip ground before ringing current is detected. This may indicate that the
ground detector is not working. However, the call will be accepted. Busyout
the affected port, and run a long test. Observe the test results. If any tests
fail, refer to the description of the tests and the associated error codes.
Release the port. If users continue to report troubles, check for other errors
and make test calls to determine whether the problem should be referred to
the CO.
Continued on next page