09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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.

Denial Events<br />

Table 54: Cause Value 102, Signaling Group Error Type 1, Aux Data information<br />

Aux<br />

Data<br />

Value<br />

Timer<br />

Name<br />

Troubleshooting<br />

Timer<br />

Value<br />

Description<br />

1 T302 4s SETUP_ACK messages (overlap receiving mode)<br />

2 T303_1 4s SETUP message 1st timer expiration<br />

3 T303_2 4s SETUP message 2nd timer expiration<br />

4 T305 4/30s DISCONNECT message<br />

5 T308_1 4s RELEASE message 1st expiration<br />

6 T308_2 4s RELEASE message 2nd expiration<br />

7 T310 10s CALL_PROCEEDING message<br />

8 T313 4s CONNECT message<br />

9 T313_2 4s “no longer used”<br />

10 T316 120s RESTART message<br />

11 TL3 30s Layer 3 timer expired (d-channel dropped)<br />

12 T309 90s d-channel reestablishment expiration stable calls are<br />

dropped<br />

13 T_WRN h FACILITY message (waiting for ACK or REJ)<br />

14 T321 120s SERVICE message (waiting for ACK)<br />

15 TSM h retransmission of SERVICE on d-channel switchover<br />

16 TM100 h ISDN-BRI maintenance (MIM timer)<br />

● Check the diagnostic information for the timer number that has expired. See Cause Values<br />

and their meanings/interpretations on page 151.<br />

● Check that the protocols at each end of the interface match (for example, both sides are<br />

AT&T Custom or both sides are NI-2).<br />

- If the ends of the interface are running different protocols, they might be running with<br />

different values for their Layer 3 timers.<br />

- If the protocols at each end of the interface match, the Communication Manager timer<br />

might have expired because:<br />

196 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s

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

Saved successfully!

Ooh no, something went wrong!