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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

Error<br />

Type<br />

Aux<br />

Data<br />

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

CO-TRK (Analog CO Trunk)<br />

769 57392 CO not releasing after call is dropped from PBX end, or the loop is not open<br />

after a disconnect. After several occurrences, an off-board or on-board<br />

warning alarm is generated. Refer problem to CO.<br />

2561 57345 Single polarity ringing current. This <strong>error</strong> results from abnormal ringing<br />

current, but does not prevent the incoming call from being accepted. One<br />

cause could be that the reverse current detector associated with the port is<br />

failing. (Will not be detected by any <strong>test</strong>s.) Another cause could be that<br />

normal current is not detected. In this case, neither incoming nor outgoing<br />

calls can be completed, <strong>and</strong> the dial tone <strong>test</strong> will also fail. The last cause<br />

could be that certain types of noise are present on the CO line during the<br />

silent period of ringing. First check for other <strong>error</strong>s. If the count for this <strong>error</strong><br />

is very high (255), <strong>and</strong> every <strong>test</strong> passes, then either the reverse current<br />

detector is defective or the CO line is noisy. If the CO line is suspect, make<br />

Tip <strong>and</strong> Ring observations. If the line is determined to be noisy, refer the<br />

problem to the CO. If the reverse current detector is defective, ignore this<br />

<strong>error</strong>.<br />

2817 57360 Ground but no ringing. This <strong>error</strong> occurs on an incoming call on a<br />

ground-start trunk. If ringing is not detected within 5 seconds of the Tip being<br />

grounded, the call is still accepted. If the CO is of the No. 5ESS. switch type,<br />

ringing delays of more than 5 seconds during heavy traffic are fairly common.<br />

Check for other <strong>error</strong>s.<br />

2817 57393 The loop is opening too slowly after a disconnect. This <strong>error</strong> indicates an<br />

on-board problem, although the trunk may be functional. Check for other<br />

<strong>error</strong>s.<br />

3073 57376 No loop current on incoming call. The incoming destination has already<br />

answered <strong>and</strong> no loop current has been detected. If this is a hard fault, the<br />

dial tone <strong>test</strong> <strong>and</strong> every outgoing call should also fail. Check for other <strong>error</strong>s.<br />

3329 57408 Trunk <strong>error</strong>. No Tip ground detected on outgoing call. This <strong>error</strong> occurs<br />

when an attempt is made to seize a ground-start CO trunk for an outgoing<br />

call <strong>and</strong> Tip ground is not detected or the caller hangs up before Tip ground<br />

is detected.<br />

1. Busyout the affected port, <strong>and</strong> run a long <strong>test</strong>. Observe the <strong>test</strong><br />

results. If any <strong>test</strong>s fail, refer to the description of the <strong>test</strong>s <strong>and</strong> the<br />

associated <strong>error</strong> <strong>codes</strong>. Release the port.<br />

2. 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<br />

CO. Busyout the affected port, <strong>and</strong> run a long <strong>test</strong>. If Dial Tone Test #0<br />

passes, ignore this <strong>error</strong>. Release the port.<br />

2 of 3<br />

Issue 5 May 2009 287

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

Saved successfully!

Ooh no, something went wrong!