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 136: Descriptions <strong>and</strong> Recommendations for Error Types 3842-3942 1 of 4<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 />

3843 No route to destination.<br />

Request received to<br />

route call through a<br />

transit network that is<br />

recognized but not<br />

allowed to carry the call<br />

or not able to serve the<br />

destination.<br />

3846 The far-end switch has<br />

indicated that the<br />

B-Chel (trunk) is not<br />

acceptable for use in<br />

the call for which it was<br />

requested.<br />

3858 Similar to Error Type 1.<br />

The switch sent a<br />

message to the far-end<br />

switch or terminal<br />

adapter that did not<br />

respond in the time<br />

allowed.<br />

The equipment sending this cause event does not<br />

recognize the transit network.<br />

1. From the circuit pack or media module <strong>and</strong> port<br />

number (in the Aux Data field), determine the trunk<br />

group against which the <strong>error</strong> was reported.<br />

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

group for validity of interexchange carriers requested<br />

(IXC field).<br />

This could indicate an administration problem (for example,<br />

the local switch <strong>and</strong> the far-end switch have different<br />

B-Chels administered), or could reflect the occurrence of a<br />

normal race condition (for example, the local switch has<br />

requested use of a B-Chel that the far-end switch had just<br />

reserved for use on another call).<br />

1. From the circuit pack or media module <strong>and</strong> port<br />

number (in the Aux Data field), determine the trunk<br />

group against which the <strong>error</strong> was reported.<br />

2. Enter status trunk for the indicated trunk. Refer to<br />

DS1 ISDN Trunk Service States <strong>and</strong> ISDN-PRI Trunk<br />

Service States sections of ISDN-TRK for recovery<br />

suggestions.<br />

Follow same recommendations as for Error Type 1.<br />

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

1 of 4

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

Saved successfully!

Ooh no, something went wrong!