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.

Signaling Link Hardware Check (#636) in the <strong>test</strong> sequence. When the link does recover,<br />

the B-Chels will be negotiated back to the In-Service state <strong>and</strong> their alarms will be retired.<br />

When this <strong>error</strong> occurs, the state of the Signaling Group is changed to out of service. Verify<br />

this with status signaling-group grp#.<br />

d. Error Type 513: the secondary signaling chel connection has been lost for more than 90<br />

seconds. If the primary signaling chel is not in service, B-Chels will be placed in the ISDN<br />

Maintenance/Far-End state. The B-Chels will not be usable for outgoing calls, although<br />

incoming calls will still be accepted. The switch will automatically attempt to recover the<br />

signaling link. Note the results of the Secondary Signaling Link Hardware Check (#639).<br />

When the link does recover, the B-Chels will be negotiated back to the In-Service state <strong>and</strong><br />

their alarms will be retired.<br />

When this <strong>error</strong> occurs, the state of the Signaling Group is changed to out of service (verify<br />

using status signaling-group grp#).<br />

e. Error Type 1793: The Layer 2 Query Test failed for the primary signaling chel. See Layer 2<br />

Status Query Test (#647)<br />

f. Error Type 2049: The Layer 2 Query Test failed for the secondary signaling chel. See Layer<br />

2 Status Query Test (#647)<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. Investigate elements of<br />

the ISDN PRI D-Chel(s) ISDN-PLK (ISDN-PRI Signaling Link Port) for both this switch <strong>and</strong><br />

the far-end switch. If Test #637 fails twice in a row, the B-Chels will be alarmed <strong>and</strong> made<br />

unavailable for outgoing calls (although incoming calls will still be accepted). When<br />

Test #637 succeeds <strong>and</strong> the far-end switch starts responding properly, the DS1 ISDN Trunk<br />

(B-Chels) will be placed back into normal operation, <strong>and</strong> their alarms will be 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 NFAS D-chel backup signaling that is<br />

supported only by country protocol 1.<br />

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

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

correctly at the far-end switch.<br />

i. Error Types 3842 - 3942: These Error Types report certain <strong>error</strong> messages received by the<br />

ISDN-PRI Signaling Group for one of its associated B-Chels. The aux data field shows for<br />

which B-Chel (port number) the message was received.<br />

The <strong>error</strong> code generated equals 3840+x, where “x” is a cause value defined by the<br />

ISDN-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 />

Table 157 provides more information.<br />

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

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

Saved successfully!

Ooh no, something went wrong!