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

Maintenance <strong>Dem<strong>and</strong></strong> Tests<br />

BRI NPE Crosstalk Test (#617)<br />

This <strong>test</strong> is destructive.<br />

One or more Network Processor Elements (NPEs) reside on each circuit pack with a TDM-bus<br />

interface. The NPE controls port connectivity <strong>and</strong> gain, <strong>and</strong> provides conferencing functions on<br />

a per-port basis. The BRI NPE Crosstalk <strong>test</strong> verifies that the port’s NPE chel talks on the<br />

selected time slot <strong>and</strong> never crosses over to time slots reserved for other connections. If the<br />

NPE is not working correctly, one-way <strong>and</strong> noisy connections may be observed. This <strong>test</strong> is part<br />

of a port’s long <strong>test</strong> sequence <strong>and</strong> executes in approximately 20 to 30 seconds. Crosstalk<br />

<strong>test</strong>ing is performed on both B-Chels (B1 <strong>and</strong> B2) associated with a BRI port. If this <strong>test</strong> fails on<br />

either chel, any endpoint connected to the port is taken out-of-service. This <strong>test</strong> aborts if the port<br />

<strong>and</strong> its associated chels are not in the idle state.<br />

This <strong>test</strong> runs on BRI-PORT (ISDN-BRI Port) <strong>and</strong> TBRI-PT (ISDN Trunk-Side BRI Port).<br />

Table 412: BRI NPE Crosstalk Test (#617) 1 of 2<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

1000 ABORT System resources required to run this <strong>test</strong> are not available. The port<br />

may be busy with a valid call.<br />

1. Enter display port location to determine the station<br />

extension or trunk group/member number of the port.<br />

2. Enter status bri-port location to determine the service<br />

state of the port. If the service state indicates that the port is in use,<br />

wait until the port is idle before re<strong>test</strong>ing.<br />

3. Retry the comm<strong>and</strong> at 1-minute intervals up to 5 times.<br />

4. If the <strong>test</strong> continues to abort, escalate the problem.<br />

1004 ABORT The port has been seized by a user for a valid call.<br />

1. Enter status bri-port location to determine when the port<br />

is available for <strong>test</strong>ing.<br />

2. Retry the comm<strong>and</strong> at 1-minute intervals up to 5 times.<br />

3. If the <strong>test</strong> continues to abort <strong>and</strong> the port is idle, escalate the<br />

problem.<br />

1005 ABORT This <strong>test</strong> is not valid for this type of port. This <strong>error</strong> can be ignored.<br />

1412 ABORT This <strong>test</strong> does not run on media modules or media gateways. Ignore.<br />

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

1 of 2

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!