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.

TSC-ADM (Administered Temporary Signaling Connections)<br />

MO Name in Log Alarm<br />

Level<br />

No alarms are generated for Administered Temporary Signaling Connections (TSC-ADM, also<br />

called ADM TSCs).<br />

Administered temporary signaling connections (TSC) provide a path through ISDN-PRI<br />

networks for supplementary D-chel messages. ISDN-PRI applications such as the Distributed<br />

Communications System (DCS) use temporary signaling connections to exchange user<br />

information across an ISDN-PRI network. What makes Administered TSCs unique is that these<br />

particular TSCs stay active for an extended period of time, similar to a permanent data<br />

connection. These ADM TSCs are used for DCS features that require Non-Call Associated<br />

(NCA) TSCs, <strong>and</strong> the ADM TSC provides the logical chel function in a DCS network.<br />

An NCA TSC is a virtual connection established within a D-chel without associating any B-Chel<br />

connections. The connection provides user-to-user service by exchanging USER<br />

INFORMATION messages without associated B-Chel connections.<br />

An Administered TSC is a special NCA TSC defined for the DCS over the ISDN-PRI D-chel.<br />

The ADM TSC has an administratively defined endpoint <strong>and</strong> is established for an extended<br />

period of time.<br />

There are two types of ADM TSCs:<br />

● Permanent: these are established by the originating PBX (near-end ADM TSC) or by the<br />

terminating PBX (far-end ADM TSC). Once these ADM TSCs are established, they remain<br />

active.<br />

● As-Needed: these are established only when needed.<br />

ADM TSC maintenance provides a strategy to verify that a far end can respond to an ISDN-PRI<br />

USER INFORMATION TSC heartbeat message, thereby indicating that user-user signaling is<br />

functioning. In addition, maintenance can retrieve the status of the ADM TSC’s connection<br />

state.<br />

Since ADM TSCs are administered on a per signaling-group basis, the health of an ADM TSC<br />

also depends on the state of the D-chel or D-chel pair administered per signaling group. See<br />

ISDN-SGR (ISDN-PRI Signaling Group) documentation for details on ISDN-PRI NFAS <strong>and</strong><br />

D-chel backup maintenance.<br />

The two administration comm<strong>and</strong>s for ADM TSCs are as follows:<br />

● add signaling-group number<br />

● change signaling-group number<br />

Initial Comm<strong>and</strong> to Run Full Name of MO<br />

TSC-ADM none none Administered Temporary<br />

Signaling Connections<br />

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

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

Saved successfully!

Ooh no, something went wrong!