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

Error<br />

Code<br />

Description Recommendation<br />

3878 The far-end switch has<br />

indicated that the<br />

network is not<br />

functioning correctly<br />

<strong>and</strong> that the condition<br />

may last a relatively<br />

long period of time (for<br />

example, immediately<br />

re-attempting the call<br />

may not be successful).<br />

3890 A request to use a<br />

network service (e.g.,<br />

SDN) has been denied.<br />

Administration<br />

somewhere on the<br />

network has indicated<br />

that the requested<br />

service has not been<br />

subscribed to or<br />

purchased for this<br />

trunk.<br />

3892 Protocol detail; may<br />

offer a clue if customer<br />

is having ISDN calls<br />

denied with an<br />

unexpected intercept<br />

tone.<br />

Network is out of order.<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. Consult with the network provider to determine the<br />

nature <strong>and</strong> expected duration of the out of service<br />

condition.<br />

3. Consider modifying every routing pattern containing<br />

this trunk group to route calls around the network that<br />

is out of service.<br />

This could be a local administration problem only, or a<br />

mismatch between the local administration <strong>and</strong> that of the<br />

network provider.<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. Display the trunk group form: If the trunk group is<br />

Call-by-Call (Service Type is “cbc”), check every<br />

routing pattern form containing this trunk group to see<br />

if the Service/Feature fields contain the correct<br />

network services purchased for this trunk. If the trunk<br />

group is not Call-by-Call, check that the Service Type<br />

field contains the single network service purchased<br />

for this trunk.<br />

3. If local administration appears correct, consult with<br />

the customer <strong>and</strong>/or the network provider to<br />

determine the services that the customer has<br />

subscribed to for this trunk group.<br />

If customer is complaining of unexpected intercept tones<br />

when accessing ISDN trunks or PRI endpoints <strong>and</strong> no other<br />

cause can be found, escalate the problem <strong>and</strong> provide the<br />

next tier with this Error Log information.<br />

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

2 of 4

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

Saved successfully!

Ooh no, something went wrong!