Hi All, I am getting these events in asterisk message log: NOTICE[16647] chan_zap.c: Got event 4 (Alarm)... NOTICE[16647] chan_zap.c: Alarm cleared on channel 1 after that asterisk exits silently until I restart it. Sometimes zapata drivers also get in a state where I need to physically restart the machine. Does anyone have any suggestions how to troubleshoot these alarm events? Roberts
Hello there, With extended logging options the events just before Asterisk dying look like this: [Oct 14 00:52:45] VERBOSE[2496] logger.c: == Starting post polarity CID detection on channel 1 [Oct 14 00:52:45] DEBUG[2496] dsp.c: dsp busy pattern set to 500,500 [Oct 14 00:52:45] VERBOSE[3188] logger.c: -- Starting simple switch on 'Zap/1-1' [Oct 14 00:52:47] NOTICE[3188] chan_zap.c: Got event 4 (Alarm)... [Oct 14 00:52:47] DEBUG[3188] chan_zap.c: Ignoring Polarity switch to IDLE on channel 1, state 9 [Oct 14 00:52:47] DEBUG[3188] chan_zap.c: Polarity Reversal event occured - DEBUG 2: channel 1, state 9, pol= 0, aonp= 0, honp= 0, pdelay600, tv= -123711628 [Oct 14 00:52:48] NOTICE[3188] chan_zap.c: Alarm cleared on channel 1 [Oct 14 00:52:48] DEBUG[3188] chan_zap.c: Ignore switch to REVERSED Polarity on channel 1, state 9 [Oct 14 00:52:48] DEBUG[3188] chan_zap.c: Ignoring Polarity switch to IDLE on channel 1, state 9 [Oct 14 00:52:48] DEBUG[3188] chan_zap.c: Polarity Reversal event occured - DEBUG 2: channel 1, state 9, pol= 0, aonp= 0, honp= 0, pdelay600, tv= -123710540 And that is the last event. Channel 1 is FXO port where my BT line is plugged in. Can anyone suggest if it seems this may be a card fault, or have I misconfigured something? I would really appreciate your help, I cannot afford to have asterisk die randomly. Roberts On Mon, 2008-10-06 at 08:26 +0100, Roberts Klotins wrote:> Hi All, > > I am getting these events in asterisk message log: > NOTICE[16647] chan_zap.c: Got event 4 (Alarm)... > NOTICE[16647] chan_zap.c: Alarm cleared on channel 1 > > after that asterisk exits silently until I restart it. Sometimes zapata > drivers also get in a state where I need to physically restart the > machine. Does anyone have any suggestions how to troubleshoot these > alarm events? > > Roberts > > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > AstriCon 2008 - September 22 - 25 Phoenix, Arizona > Register Now: http://www.astricon.net > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users
On Mon, Oct 06, 2008 at 08:26:30AM +0100, Roberts Klotins wrote:> Hi All, > > I am getting these events in asterisk message log: > NOTICE[16647] chan_zap.c: Got event 4 (Alarm)... > NOTICE[16647] chan_zap.c: Alarm cleared on channel 1 > > after that asterisk exits silently until I restart it. Sometimes zapata > drivers also get in a state where I need to physically restart the > machine. Does anyone have any suggestions how to troubleshoot these > alarm events?What versions of asterisk and zaptel? zaptel should not be sending and clearing an alarm in such a case. I think it was solved in recent versions of zaptel (raising the threashold for detecting an alarm). OTOH, Asterisk should not crash just because. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Thanks for the reply. asterisk-1.4.21.2 zaptel-1.4.12.1 I have posted a more detailed error log in this thread. Roberts On Tue, 2008-10-14 at 11:54 +0200, Tzafrir Cohen wrote:> On Mon, Oct 06, 2008 at 08:26:30AM +0100, Roberts Klotins wrote: > > Hi All, > > > > I am getting these events in asterisk message log: > > NOTICE[16647] chan_zap.c: Got event 4 (Alarm)... > > NOTICE[16647] chan_zap.c: Alarm cleared on channel 1 > > > > after that asterisk exits silently until I restart it. Sometimes zapata > > drivers also get in a state where I need to physically restart the > > machine. Does anyone have any suggestions how to troubleshoot these > > alarm events? > > What versions of asterisk and zaptel? > > zaptel should not be sending and clearing an alarm in such a case. I > think it was solved in recent versions of zaptel (raising the threashold > for detecting an alarm). > > OTOH, Asterisk should not crash just because. >