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.

TIE-TRK (Analog Tie Trunk)<br />

b. Error Type 1: digit time-out. This occurs when the far-end PBX began transmitting digits too<br />

late (10 seconds) after receiving the signal indicating ready to receive digits (if any). This<br />

can occur on an incoming immediate, wink, or delay dial line. Check the far-end PBX to<br />

ensure a translation match at both ends. This <strong>error</strong> does not apply to TN497.<br />

c. Error Type 1: rotary dial before wink. This occurs when the far-end PBX starts dialing<br />

before the PBX sends the wink on a wink-start or delay-dial trunk. Check the far-end PBX to<br />

ensure a translation match at both ends. This <strong>error</strong> does not apply to TN497.<br />

d. Error Type 1: rotary dial too early. This occurs when the far-end PBX starts dialing too soon<br />

(about 50ms) after seizure on a wink start or delay dial line. Check the far-end PBX to<br />

ensure a translation match at both ends. This <strong>error</strong> does not apply to TN497.<br />

e. Error Type 1: on-hook before wink. This occurs when the far end goes on-hook before a<br />

wink. Check the far-end PBX to ensure a translation match at both ends. This <strong>error</strong> applies<br />

only to TN439.<br />

f. Error Type 1: on an outgoing wink-start or delay-dial trunk, the wink time was too short<br />

(less than 80ms) for a valid signal. Check the far-end PBX to ensure a translation match at<br />

both ends. This <strong>error</strong> does not apply to TN497.<br />

g. Error Type 15: this is a software audit <strong>error</strong> that does not indicate any hardware<br />

malfunction. Run the short <strong>test</strong> sequence, <strong>and</strong> investigate associated <strong>error</strong>s (if any).<br />

h. Error Type 18: this indicates that the trunk in question has been busied-out by maintenance<br />

personnel.<br />

i. Error Type 130: the circuit pack has been removed or has been insane for more than<br />

11 minutes. To clear the <strong>error</strong>, reinsert or replace the circuit pack. TN439 does not alarm this<br />

<strong>error</strong>. This <strong>error</strong> does not apply to TN497.<br />

j. Error Type 257: the rotary dial rate was too slow — less than 8 pulses per second. Check<br />

the far-end PBX to ensure a translation match at both ends.<br />

k. Error Type 257: the rotary dial rate was too fast — above 12 pulses per second. Check the<br />

far-end PBX to ensure a translation match at both ends.<br />

l. Error Type 257: the time between digits was too short (less than 300ms). Check the far-end<br />

PBX to ensure a translation match at both ends.<br />

m. Error Types 513, 769, 1281: these <strong>error</strong>s do not apply to TN439 <strong>and</strong> TN497.<br />

n. Error Type 1025: this indicates that the trunk is still seized with an incoming call. The<br />

far-end PBX is not releasing the trunk after the call was dropped. Check the far-end PBX for<br />

problems.<br />

Once the trunk is released from the call, the severity of this problem is decreased. If Error<br />

Type 1025 does not appear again, this means that the problem has been corrected. Verify<br />

that Error Type 1025 does not reappear in the Error Log.<br />

Issue 5 May 2009 983

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

Saved successfully!

Ooh no, something went wrong!