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.

ATM-SGRP (ATM Signaling Group)<br />

g. Error Type 2305: The Remote Layer 3 Query (#637) failed. A specific message was sent to<br />

the far-end switch, <strong>and</strong> it did not respond within the time allowed.<br />

1. Investigate elements of the ATM D-Chel(s) (ATM-DCH) for both this switch <strong>and</strong> the<br />

far-end switch.<br />

If Test #637 fails twice in a row, the B-Chels are alarmed <strong>and</strong> made unavailable for<br />

outgoing calls (although incoming calls are still accepted). When Test #637 succeeds <strong>and</strong><br />

the far-end switch starts responding properly, the ATM trunk (B-Chels) are placed back into<br />

normal operation <strong>and</strong> their alarms retired.<br />

h. Error Type 3585: A SERV or SERV ACK ISDN D-chel message has been received by a<br />

non-US-type interface (country option other than 1 on the DS1 administration screen).<br />

However, these messages are used only for duplex NFAS signaling, which is supported by<br />

country protocol 1.<br />

Thus, there may be a mismatch in administration between the local <strong>and</strong> far-end switches.<br />

1. Consult with the customer’s network provider to determine whether the D-Chel is set<br />

up correctly on the far-end switch.<br />

i. Error Type 3840-3928: These Error Types report certain <strong>error</strong> messages received by the<br />

ATM-SGRP Signaling Group for one of its associated B-Chels. The Aux Data field is the<br />

port number of the B chel from which the message was received.<br />

The <strong>error</strong> code generated equals 3840+x, where x is a Cause Value defined by the ISDN<br />

PRI Specification. Note that there is no recommended action for these Error Types;<br />

selected ISDN cause values are placed in the log when they are received, but no direct<br />

action or alarming is performed solely in response to receiving them. They provide added<br />

data that may prove useful when tracking down obscure networking <strong>and</strong> routing problems.<br />

See Table 48: Descriptions <strong>and</strong> repair recommendations (Error Types 3840-3928) for<br />

more information.<br />

Table 48: Descriptions <strong>and</strong> repair recommendations (Error Types 3840-3928) 1 of 5<br />

Error<br />

Code<br />

Description Recommendation<br />

3842 A request has been<br />

made to use a transit<br />

network or common<br />

carrier that cot be<br />

accessed.<br />

From the circuit pack <strong>and</strong> port number (in the Aux Data<br />

field), determine the trunk group against which the <strong>error</strong><br />

was reported.<br />

1. Check every routing pattern containing this trunk<br />

group for validity of interexchange carriers requested<br />

(IXC field).<br />

1 of 5<br />

Issue 5 May 2009 173

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

Saved successfully!

Ooh no, something went wrong!