09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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.

Communication Manager Maintenance Object Repair Procedures<br />

Table 144: Descriptions and repair recommendations (Error Types 3840-3928) 4 of 5<br />

Error<br />

Code<br />

Description Recommendation<br />

3894 Protocol detail; may<br />

offer a clue if customer<br />

is having ISDN calls<br />

denied with an<br />

unexpected intercept<br />

tone.<br />

3905 Protocol detail; may<br />

offer a clue if customer<br />

is having ISDN calls<br />

denied with an<br />

unexpected intercept<br />

tone.<br />

3906 Protocol detail; may<br />

offer a clue if customer<br />

is having ISDN calls<br />

denied with an<br />

unexpected intercept<br />

tone.<br />

3909 A request to use a<br />

network service has<br />

been made, but the<br />

network has rejected<br />

the request because<br />

the requested service<br />

is not implemented.<br />

Do the following:<br />

1. Eliminate any transitory state mismatch problems<br />

(test port location for the trunk port shown in<br />

the Aux Data field). Service State Audit Test (#256) is<br />

the important test in the sequence.<br />

2. If Test #256 passes yet the customer continues to<br />

complain of unexpected intercept tones when<br />

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

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

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

Do the following:<br />

1. If customer is complaining of unexpected intercept<br />

tones when accessing ISDN trunks or PRI endpoints<br />

and no other cause can be found, escalate the<br />

problem and provide the next tier with this Error Log<br />

information.<br />

Do the following:<br />

1. If customer is complaining of unexpected intercept<br />

tones when accessing ISDN trunks or PRI endpoints<br />

and no other cause can be found, escalate to the<br />

problem and provide the next tier with this Error Log<br />

information.<br />

Follow the recommendations for Error Type 3890.<br />

552 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s<br />

4 of 5

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

Saved successfully!

Ooh no, something went wrong!