19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

If <strong>error</strong> count associated with this Error Type is very high (i.e., 255) <strong>and</strong> if Alarm Status on<br />

the Hardware Error Report is “n” (not alarmed), then the existence of this Error Type<br />

indicates that, despite the fact that many inline <strong>error</strong> messages have been received, every<br />

Call Seizure <strong>test</strong> has passed. Problems at the CO may cause this condition rather than<br />

problems with the PBX.<br />

f. Error Types 1025/1281: logged for every version of the CO-TRK/CO-BD. However, no<br />

MINOR alarms will be generated for Central Office Trunks [TN747B] with vintages V8 or<br />

greater. Any failures received by this <strong>test</strong> will still be logged as Error type 1025/1281.<br />

Check for the use of MFT/Range extenders. If there are extenders present, <strong>and</strong> there are<br />

no other complaints or maintenance <strong>error</strong>s against this trunk, then there is a good chance<br />

that Test #3 failed due to excessive loop current <strong>and</strong> may be ignored.<br />

g. Error Type 3840: <strong>test</strong> calls made by the Automatic Transmission Measurement System<br />

(ATMS) returned measurements in the unacceptable range.<br />

Error Type 3841: measurements were in the marginal range. Enter list <strong>test</strong>call<br />

detail to examine the specific transmission parameters that are out of spec, <strong>and</strong><br />

investigate the trunk for that kind of noise. If the noise is acceptable, then the AMTS<br />

thresholds administered on the trunk group screen should be changed.<br />

Table 76: CO Trunk Errors with No Tests 1 of 3<br />

Error<br />

Type<br />

Aux<br />

Data<br />

Error Description <strong>and</strong> Repair Action<br />

1 57347 Port <strong>error</strong>. Ringing without ground. This <strong>error</strong> is detected on an incoming call<br />

on a ground-start CO trunk. The CO trunk circuit pack has not detected a Tip<br />

ground before ringing current is detected. This may indicate that the ground<br />

detector is not working. However, the call will be accepted. Busyout the<br />

affected port, <strong>and</strong> run a long <strong>test</strong>. Observe the <strong>test</strong> results. If any <strong>test</strong>s fail,<br />

refer to the description of the <strong>test</strong>s <strong>and</strong> the associated <strong>error</strong> <strong>codes</strong>. Release<br />

the port. If users continue to report troubles, check for other <strong>error</strong>s <strong>and</strong> make<br />

<strong>test</strong> calls to determine whether the problem should be referred to the CO.<br />

257 50176 Battery reversal detected. This is usually caused by the CO. This is detected<br />

if the direction of the loop current changes from normal to reverse for at least<br />

40 msec. Could occur if the trunk was just installed <strong>and</strong> for some reason the<br />

Tip <strong>and</strong> Ring wires were reversed at the PBX. If battery reversals occur<br />

during dialing, wrong numbers may result. Refer problem to CO. Ask them to<br />

remove the battery reversal option.<br />

513 57364 Ground detector stuck active. After several occurrences, an on-board minor<br />

alarm is generated. Run the short <strong>test</strong> sequence. If <strong>test</strong> aborts with Error<br />

Code 1000, disconnect Tip <strong>and</strong> Ring <strong>and</strong> repeat short <strong>test</strong>. If <strong>test</strong> still aborts,<br />

replace circuit pack. If <strong>test</strong> passes, refer problem to CO. If any other <strong>error</strong><br />

code is received, pursue that problem.<br />

286 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers<br />

1 of 3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!