Hi, For a significant time now (since about 0.2.0-rc8n) the qozap driver has become very verbose if an ISDN line is not connected... I get the messages below every couple of seconds in the asterisk logs. The "flaw" in the messages is the "Alarm cleared" message - The alarm cannot possibly be cleared because there is no physical media connected into that port!!! (BTW - All ports are in TE mode.) Can anyone suggest a cleanup in qozap.c that will prevent it telling Asterisk that the channel is up unless it actually has come back up? I do not understand the zaptel/bristuff internals well enough to be able to find where this is occuring. I also get a solid kernel crash with no Oops if I unload the qozap module - Again this does not happen in the older versions of the qozap module. I am using Kernel 2.6.10. Many thanks for any pointers, Steve. Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: Detected alarm on channel 4: Red Alarm Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable to disable echo cancellation on channel 4 Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: Detected alarm on channel 5: Red Alarm Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable to disable echo cancellation on channel 5 Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: Detected alarm on channel 7: Red Alarm Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable to disable echo cancellation on channel 7 Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: Detected alarm on channel 8: Red Alarm Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable to disable echo cancellation on channel 8 Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: Detected alarm on channel 10: No Alarm Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable to disable echo cancellation on channel 10 Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: Detected alarm on channel 11: No Alarm Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable to disable echo cancellation on channel 11 Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm cleared on channel 4 Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm cleared on channel 5 Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm cleared on channel 7 Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm cleared on channel 8 Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm cleared on channel 10 Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm cleared on channel 11 Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 2 Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No D-channels available! Using Primary channel 6 as D-channel anyway! Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 2 Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No D-channels available! Using Primary channel 6 as D-channel anyway! Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 3 Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No D-channels available! Using Primary channel 9 as D-channel anyway! Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 3 Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No D-channels available! Using Primary channel 9 as D-channel anyway! Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 4 Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No D-channels available! Using Primary channel 12 as D-channel anyway! Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 4 Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No D-channels available! Using Primary channel 12 as D-channel anyway!
Alberto Pastore
2006-Oct-20 00:20 UTC
[asterisk-users] vISDN, mISDN, bristuff [was: Re: Bristuff qozap drivers problem]
Same similar problems here, with qozap and bristuff 0.3.0: with physical media connected, I get a layer 1 down message that keeps rolling up EVEN DURING AN INCOMING CALL on that BRI span, and prevents asterisk from placing outbound calls... until I restart asterisk (luckily, no kernel crashes so far). Can anyone give me his opion/experience about vISDN or mISDN alternatives? Maybe I'm running bristuff in the wrong way, but I'm starting to think that bristuff is not the best way to make a stable ISDN PBX. I don't like very much the way bristuff kind of messes up with asterisk sourcecode (especially chan_zap/libpri). Steve Davies ha scritto:> Hi, > > For a significant time now (since about 0.2.0-rc8n) the qozap driver > has become very verbose if an ISDN line is not connected... I get the > messages below every couple of seconds in the asterisk logs. > > The "flaw" in the messages is the "Alarm cleared" message - The alarm > cannot possibly be cleared because there is no physical media > connected into that port!!! (BTW - All ports are in TE mode.) > > Can anyone suggest a cleanup in qozap.c that will prevent it telling > Asterisk that the channel is up unless it actually has come back up? I > do not understand the zaptel/bristuff internals well enough to be able > to find where this is occuring. > > I also get a solid kernel crash with no Oops if I unload the qozap > module - Again this does not happen in the older versions of the qozap > module. I am using Kernel 2.6.10. > > Many thanks for any pointers, > Steve. > > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: > Detected alarm on channel 4: Red Alarm > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable > to disable echo cancellation on channel 4 > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: > Detected alarm on channel 5: Red Alarm > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable > to disable echo cancellation on channel 5 > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: > Detected alarm on channel 7: Red Alarm > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable > to disable echo cancellation on channel 7 > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: > Detected alarm on channel 8: Red Alarm > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable > to disable echo cancellation on channel 8 > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: > Detected alarm on channel 10: No Alarm > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable > to disable echo cancellation on channel 10 > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:6025 handle_init_event: > Detected alarm on channel 11: No Alarm > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:1445 zt_disable_ec: Unable > to disable echo cancellation on channel 11 > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm > cleared on channel 4 > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm > cleared on channel 5 > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm > cleared on channel 7 > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm > cleared on channel 8 > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm > cleared on channel 10 > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:6020 handle_init_event: Alarm > cleared on channel 11 > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got > event: Alarm (4) on Primary D-channel of span 2 > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No > D-channels available! Using Primary channel 6 as D-channel anyway! > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got > event: No more alarm (5) on Primary D-channel of span 2 > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No > D-channels available! Using Primary channel 6 as D-channel anyway! > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got > event: Alarm (4) on Primary D-channel of span 3 > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No > D-channels available! Using Primary channel 9 as D-channel anyway! > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got > event: No more alarm (5) on Primary D-channel of span 3 > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No > D-channels available! Using Primary channel 9 as D-channel anyway! > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got > event: Alarm (4) on Primary D-channel of span 4 > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No > D-channels available! Using Primary channel 12 as D-channel anyway! > Oct 19 13:22:23 NOTICE[6485]: chan_zap.c:8122 pri_dchannel: PRI got > event: No more alarm (5) on Primary D-channel of span 4 > Oct 19 13:22:23 WARNING[6485]: chan_zap.c:2197 pri_find_dchan: No > D-channels available! Using Primary channel 12 as D-channel anyway! > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users-- -- Alberto Pastore B-Press Srl - Gruppo MSoft P.IVA 01697420030 P.le Lombardia, 4 - 28100 Novara - Italy Tel. 0321-499508 Fax 0321-492974 http://www.msoft.it
On Thu, Oct 19, 2006 at 01:42:01PM +0100, Steve Davies wrote:> Hi, > > For a significant time now (since about 0.2.0-rc8n) the qozap driver > has become very verbose if an ISDN line is not connected... I get the > messages below every couple of seconds in the asterisk logs.Have you tried version >= 0.3.0-PRE-1s? It seems to have made many such messages debug messages. -- Tzafrir Cohen sip:tzafrir@local.xorcom.com icq#16849755 iax:tzafrir@local.xorcom.com +972-50-7952406 jabber:tzafrir@jabber.org tzafrir.cohen@xorcom.com http://www.xorcom.com
On 10/20/06, Tzafrir Cohen <tzafrir.cohen@xorcom.com> wrote:> On Thu, Oct 19, 2006 at 01:42:01PM +0100, Steve Davies wrote: > > Hi, > > > > For a significant time now (since about 0.2.0-rc8n) the qozap driver > > has become very verbose if an ISDN line is not connected... I get the > > messages below every couple of seconds in the asterisk logs. > > Have you tried version >= 0.3.0-PRE-1s?Yes, I tried it before I posted the message - I believe this is an intentional change in the alerting, but I am concerned that it shows "Alarm cleared" which is NOT correct. The cable is still unplugged, and the alarm has not cleared. The latest (PRE-1u) also still crashes on unload :( Regards, Steve