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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PE-BCHL (PRI Endpoint Port)<br />

Multiple PRI endpoints on one line-side facility are separate <strong>and</strong> distinct within the facility.<br />

Non-overlapping contiguous sets of B-Channels are associated with each PRI endpoint, <strong>and</strong> the<br />

endpoint equipment is expected to initiate calls within these boundaries. The endpoint<br />

application equipment must:<br />

● Use st<strong>and</strong>ard ISDN-PRI signaling<br />

● Adhere to the administered PRI endpoint boundaries when initiating calls<br />

● H<strong>and</strong>le incoming calls appropriately, based on the originating PRI endpoint<br />

Signaling <strong>and</strong> B-Channel States<br />

PRI ports use a separate channel called the D-Channel for call-control <strong>and</strong> signaling messages.<br />

This is called out-of-b<strong>and</strong> signaling. The D-Channel associated with the set of B-Channels is an<br />

ISDN-PRI signaling link’s port (ISDN-PLK). The signaling protocol used on the ISDN-PRI<br />

signaling-link port’s D channel is defined by one of the four selectable ISDN-PRI Specifications:<br />

<strong>Avaya</strong>, CCITT, ECMA, <strong>and</strong> ANSI.<br />

The ISDN-PRI Specification defines the possible service states for a B-Channel. The service<br />

state is negotiated with the far-end terminal adapter, changes over time, <strong>and</strong> can have far- <strong>and</strong><br />

near-end components. The service state is initialized to Out-Of-Service/Far-End, <strong>and</strong> an<br />

attempt is made to negotiate it to In-Service. Use status pri-endpoint extension to<br />

display the service state of a particular PRI endpoint port’s B-Channel.<br />

If a call is present, the Specification defines the permissible call states as well. There are <strong>test</strong>s in<br />

the short <strong>and</strong> long <strong>test</strong> sequences for the PRI endpoint port designed to audit these states <strong>and</strong><br />

ensure agreement between both ends of the PRI wideb<strong>and</strong> connection.<br />

Alarming Based on Service States<br />

A PRI endpoint port’s B-Channel logs a warning alarm when it is placed in a Maintenance/<br />

Far-End or Out-Of-Service/Far-End state. While in such a state, the port is unusable for calls to<br />

the terminal adapter. However, the user can still use the other remaining ports in the PRI<br />

endpoint to make calls to <strong>and</strong> from the terminal adapter. When a warning alarm is raised, use<br />

status pri-endpoint extension to determine the exact state of the port. Other alarms<br />

can be diagnosed by using the short <strong>and</strong> long <strong>test</strong> sequences. Note that a PRI endpoint port’s<br />

B-Channel can be placed in a far-end service state by direct action by the far-end terminal<br />

adapter or by inaction of the far-end terminal adapter. For example, if it does not respond to a<br />

Remote Layer 3 Query (see Remote Layer 3 Query (#637) for ISDN-PLK) the associated PRI<br />

endpoint port’s B-Channels will be placed in the Maintenance/Far-End service state.<br />

A PRI endpoint port is a port on a UDS1 interface circuit pack <strong>and</strong> thus depends on the health of<br />

the circuit pack for proper operation (see the following figure). A problem on the associated<br />

ISDN-LNK’s (ISDN-PRI signaling-link port’s) D-Channel can also affect the PRI endpoint. In<br />

turn, the ISDN-PLK depends on the SYS-LINK (system link) to the packet interface. Keep this<br />

hierarchy of dependencies in mind when diagnosing problems.<br />

Issue 5 May 2009 709

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

Saved successfully!

Ooh no, something went wrong!