[asterisk-r2] chan_dahdi.c: Detected alarm on channel 2: Red Alarm

[Moises Silva]

Any Zaptel/DAHDI alarms are beyond the scope of openr2. Alarms mean a
hardware connection reliability problem. Considering that the hardware
connections are not working, that may cause false positives in CAS
signaling in openr2.

Moy

On Tue, Feb 24, 2009 at 4:46 AM, Vicky Noverto <vicky.noverto at gmail.com> wrote:
> Hi,
>
> I'm having problem with on and off red alarm on TE121. I'm using Trixbox
> with E1 MFC/R2 implementation using philipine telco provider.
> The alarm keep raise and clear in every 5-10 minutes on every channel. If
> the alarm raise, all the call drop. Here is the output:
>
> [Feb 24 17:30:26] DEBUG[4067] chan_dahdi.c: Chan 2 - Alarm Raised
> [Feb 24 17:30:26] WARNING[4067] chan_dahdi.c: Detected alarm on channel 2:
> Red Alarm
> [Feb 24 17:30:26] WARNING[4067] chan_dahdi.c: Zap alarm on chan 2.
> [Feb 24 17:30:26] DEBUG[4067] chan_dahdi.c: Chan 3 - Alarm Raised
> [Feb 24 17:30:26] WARNING[4067] chan_dahdi.c: Detected alarm on channel 3:
> Red Alarm
> [Feb 24 17:30:26] WARNING[4067] chan_dahdi.c: Zap alarm on chan 3
> ....................
> [Feb 24 16:39:53] NOTICE[4067] chan_dahdi.c: Alarm cleared on channel 2
> [Feb 24 16:39:53] WARNING[4067] chan_dahdi.c: Zap alarm on chan 2.
> [Feb 24 16:39:53] DEBUG[4067] chan_dahdi.c: Chan 3 - Alarm Cleared
> [Feb 24 16:39:53] NOTICE[4067] chan_dahdi.c: Alarm cleared on channel 3
> [Feb 24 16:39:53] WARNING[4067] chan_dahdi.c: Zap alarm on chan 3.
>
> and also from the log, i see this :
> [Feb 24 17:00:56] DEBUG[4067] chan_dahdi.c: Chan 15 - Bits changed from 0x08
> to 0x00
> [Feb 24 17:00:56] DEBUG[4067] chan_dahdi.c: Chan 15 - ABCD Rx << [SEIZE]
> 0x00
> [Feb 24 17:00:56] DEBUG[4067] chan_dahdi.c: Chan 15 - ABCD Tx >> [SEIZE ACK]
> 0x0C
> [Feb 24 17:00:56] DEBUG[4067] chan_dahdi.c: Chan 15 - ABCD Raw Tx >> 0x0D
> [Feb 24 17:00:56] NOTICE[4067] chan_dahdi.c: New MFC/R2 call detected on
> chan 15.
> [Feb 24 17:00:56] DEBUG[4067] chan_dahdi.c: Chan 15 - Bits changed from 0x00
> to 0x08
> [Feb 24 17:00:56] DEBUG[4067] chan_dahdi.c: Chan 15 - ABCD Rx << [CLEAR
> FORWARD] 0x08
> [Feb 24 17:00:56] NOTICE[4067] chan_dahdi.c: Chan 15 - Far end disconnected.
> Reason: Normal Clearing
> [Feb 24 17:00:56] NOTICE[4067] chan_dahdi.c: MFC/R2 call disconnected on
> chan 15
> [Feb 24 17:00:56] DEBUG[4067] chan_dahdi.c: Chan 15 - Call ended
> [Feb 24 17:00:56] DEBUG[4067] chan_dahdi.c: Chan 15 - ABCD Tx >> [IDLE] 0x08
> [Feb 24 17:00:56] DEBUG[4067] chan_dahdi.c: Chan 15 - ABCD Raw Tx >> 0x09
> [Feb 24 17:00:56] NOTICE[4067] chan_dahdi.c: MFC/R2 call end on chan 15
>
> but no call have been made in chan 15.
> Is there anyone have problem with this and solve. Please advice. THanks.
>
> Regards,
> Vicky Noverto
>
>
>
>
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>



-- 
"I do not agree with what you have to say, but I’ll defend to the
death your right to say it." Voltaire