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

Create successful ePaper yourself

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

● Maintenance/Far-End (MTC/FE)<br />

This state is reached when the far end does not respond after a certain amount of time to<br />

messages sent over the signaling link for a particular trunk. This state is different from<br />

OOS/FE since the signaling link must have initially been up <strong>and</strong> the B-Chels in service.<br />

The switch will periodically send messages to the far end to try to negotiate the trunk<br />

(B-Chel) into service. The trunk is unusable for outgoing calls but will service incoming call<br />

requests from the far end. Note that transitions into MTC/FE do not drop stable calls.<br />

Therefore, if the service state changes from in service to MTC/FE, then stable calls are<br />

unaffected.<br />

● Maintenance/Near-End (MTC/NE)<br />

The trunk (B-Chel) is in this state if the signaling chel (ISDN-PLK) is busied out by the<br />

system technician. The trunk (B-Chel) is also temporarily in this state if the system<br />

technician enters <strong>test</strong> trunk grp#/mem# long. This comm<strong>and</strong> executes the<br />

ISDN-PRI <strong>test</strong> call. This <strong>test</strong> changes the state of the trunk member to MTC/NE for the<br />

duration of the <strong>test</strong> unless a call request comes in from the far end. In that case, the <strong>test</strong><br />

would abort. Note that transitions into MTC/NE do not drop stable calls. In this state, the<br />

B-Chel is not usable for new incoming or outgoing calls.<br />

● Pending States<br />

In addition to one of the previous components, the service state may have a pending<br />

component, indicating that the switch is waiting for a reply from the far end. These service<br />

states remain in effect until either a response is received or the allotted waiting time<br />

expires.<br />

- Pending-in-Service<br />

The near end is awaiting a far-end response to a B-Chel maintenance message<br />

requesting that a B-Chel be transitioned to in service.<br />

The far-end has a certain amount of time to respond to the message. The service state<br />

will be PINS until either a response is received or the timer expires.<br />

- Pending-Maintenance<br />

This state is supported only by systems using country protocol 1 (including US). The<br />

near end is awaiting a far-end response to a maintenance message requesting that a<br />

B-Chel be transitioned to the maintenance service state. The far-end has a certain<br />

amount of time to respond to the message. The service state will be PMTC until either<br />

a response is received or the timer expires.<br />

● Call Activity States<br />

The in-service state also has a call activity component.<br />

- Active<br />

A call is connected over the B-Chel (for example, in service active).<br />

- Idle<br />

There is no call currently on the B-Chel (for example, in service).<br />

560 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!