Avaya 03-300430 User Manual

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, every Call 
Seizure test has passed.  Problems at the CO may cause this condition rather than 
problems with the PBX.

f. Error Types 1025/1281: logged for every version 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.

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.

g. Error Type 3840: test calls made by the Automatic Transmission Measurement System 

(ATMS) returned measurements in the unacceptable range.
Error Type 3841: measurements were in the marginal range.  Use list testcall 
detail to examine the specific transmission parameters that are out of spec, and 

investigate the trunk for that kind of noise.  If the noise is acceptable, then the AMTS 
thresholds administered on the trunk group screen should be changed.

 / 

: The associated tests for these error types do not run on a G700 Media 

Gateway, and abort with Error Code 1412.

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.

257

50176

Battery reversal detected.  This is usually caused by the CO (often seen with 

step-by-step and cross-bar offices in connection with outgoing calls).  This is 

detected if the direction of the loop current changes from normal to reverse 

for at least 40 msec.  Could occur if the trunk was just installed and for some 

reason the Tip and Ring wires were reversed at the PBX.  If battery reversals 

occur during dialing, wrong numbers may result.  Refer problem to CO.  Ask 

them to remove the battery reversal option.

 1 of 3