On 2/23/06, <b class="gmail_sendername">Geoff Manning</b> <<a href="mailto:geoffm33@gmail.com">geoffm33@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How would you categorize a Yellow Alarm sensed by the Asterisk side in a Legacy PBX integration?<br><br>We have a Mitel SX200 connected to an Asterisk(1.2.4) with a TE110P.<br><br>Twice today (first time in over a month) we received a Yellow Alarm on the TE110P. I have been able to clear it easily by restarting zaptel.
<br><br>Thanks in advance!<br>
</blockquote></div><br><br>So we had another Yellow Alarm last night and I have retrieved the logs from the Mitel. It had a Red Alarm.<br><br>Here seems to be the order of events:<br><br>Mitel PBX:<br> ³2006-FEB-24 02:44:54 T1/BRI card at 02 06 00 00 ³
<br> ³ has exceeded the service loss frame threshold ³<br><br> ³2006-FEB-24 02:44:54 Tot alarm went from No Alarm to MAJOR ³<br> ³ Alarm level change due to Bay 02 trunks ³
<br><br> ³2006-FEB-24 02:44:54 T1/BRI card at 02 06 00 00 ³<br> ³ removed from service & transmitting yellow alarm ³<br><br>Asterisk:<br>Feb 24 02:45:43 WARNING[24210] chan_zap.c: Detected alarm on channel 1: Yellow Alarm
<br><br>Mitel PBX (This is when we manually reset the card on the Asterisk to clear the alarm):<br><br> ³2006-FEB-24 05:25:45 T1/BRI card at 02 06 00 00 ³<br> ³ is in red alarm condition due to loss of sync ³
<br><br> ³2006-FEB-24 05:26:08 T1/BRI card at 02 06 00 00 ³<br> ³ alarm condition is now cleared ³<br><br> ³2006-FEB-24 05:26:08 Tot alarm went from MAJOR to No Alarm ³
<br> ³ Alarm level change due to Bay 02 trunks <br><br>Asterisk:<br><br>Feb 24 05:26:54 NOTICE[24210] chan_zap.c: Alarm cleared on channel 1<br><br><br><br>So it seems the Mitel is reaching a loss threshold and setting yellow alarm. Asterisk is in turn detecting the yellow alarm. I guess it's a problem with the Mitel then. We've had problems with it in the past but they cleared up and we hadn't had an issue in months. Nothing has changed at either end but we've been hit with issues for the last 3 days.
<br><br>Here is what I have found about the alarms:<br><br><dl><dt><b><font color="#004a73" face="Arial, Helvetica, sans-serif" size="3">Red
Alarm</font><font color="#004a73" face="Arial, Helvetica, sans-serif" size="2"><br>
</font></b><font face="Arial, Helvetica, sans-serif" size="2">This is
a local equipment alarm. It indicates that the incoming signal has been
corrupted for a number of seconds. The red alarm shows up visually on
the equipment that detects the failure. This equipment will then begin
sending a yellow alarm as its outbound signal.</font>
</dt></dl>
<dl><dt><b><font color="#004a73" face="Arial, Helvetica, sans-serif" size="3">Yellow
Alarm</font><font color="#004a73" face="Arial, Helvetica, sans-serif" size="2"><br>
</font></b><font face="Arial, Helvetica, sans-serif" size="2">The yellow
alarm alerts the network that a failure has been detected. The yellow
alarm pattern has a number of different definitions. The most common
D4 definition is to set 1 bit of every channel to a ZERO.</font>
</dt></dl><br>