Demand test descriptions and error codes - Avaya Support
19.12.2012 • Views
Share Embed Flag

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
ePAPER READ
DOWNLOAD ePAPER
support.avaya.com

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

START NOW

TIE-DS1 (DS1 Tie Trunk)<br />

i. Error Type 769: the DS1 Interface circuit pack or media module detects a hardware <strong>error</strong><br />

on the DS1 tie trunk. This <strong>error</strong> usually occurs after an occurrence of Error Type 513. The<br />

trunk has received the belated “on-hook” that it has been waiting for from the far-end switch.<br />

The trunk is restored to in-service/idle <strong>and</strong> can be used for calls. Aux Data 57393 indicates<br />

delayed external release on PBX disconnect. This <strong>error</strong> can be ignored.<br />

j. Error Type 1793: the DS1 Interface circuit pack or media module is out-of-service. See the<br />

appropriate DS1-BD (DS1 Interface Circuit Pack), UDS1-BD (UDS1 Interface Circuit Pack),<br />

or MG-DS1 (DS1 Interface Media Module) documentation for details.<br />

k. Error Type 2305: reorder message. The trunk could not be seized. This <strong>error</strong> causes the<br />

Trunk Seizure <strong>test</strong> (#136) to run <strong>and</strong> is only a problem if the Seizure <strong>test</strong> fails (in which case<br />

Error Type 1025 also appears). In this case, the trunk may be put in “Ready-for-Service”<br />

state (shown as “disconnected” by the status comm<strong>and</strong>), which allows only incoming calls.<br />

Run the Trunk Seizure <strong>test</strong> (#136) <strong>and</strong> follow its procedures.<br />

l. Error Type 2562: retry Failure <strong>error</strong>. This <strong>error</strong> is logged only. It is not a hardware failure<br />

<strong>and</strong> hence does not start any <strong>test</strong>ing or generate any alarms. This <strong>error</strong> comes from call<br />

processing <strong>and</strong> is generated when a second attempt (retry) to seize an outgoing trunk fails.<br />

m. Error Type 2817: glare <strong>error</strong>. This <strong>error</strong> is logged only. It is not a hardware failure <strong>and</strong><br />

hence does not start any <strong>test</strong>ing or generate any alarms. This <strong>error</strong> is the result of a<br />

simultaneous seizure of a 2-way trunk from both the near <strong>and</strong> the far ends. Attempt to place<br />

the call again. If the <strong>error</strong> persists, execute the DS1 Tie Trunk Seizure <strong>test</strong> (#136) <strong>and</strong> follow<br />

its procedures.<br />

n. Error Type 3840: Port Audit <strong>and</strong> Update <strong>test</strong> (#36) failed due to an internal system <strong>error</strong>.<br />

Enter status trunk, <strong>and</strong> verify the status of the trunk. If the trunk is out-of-service, enter<br />

release trunk to put it back to in-service. Retry the <strong>test</strong> comm<strong>and</strong>.<br />

Issue 5 May 2009 977

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!