Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! As part of the implementation of issue 8587, a check was incldued for MWI messages preceded by Ring Pulse Alert Signals (RPAS). The RPAS is answered by chan_dahdi as a standard call and the MWI message is processed. As part of the implementation, if the MWI message was included, the channel was hung up. This did not take into account that possibility of MWI messages included into the to standard CID spills. I believe this is the case here and the MWI portion of the CID spill is causing the channel to hang up. You can look at commit 169154 for a fix or simply remove the ast_hangup calls immediately after the message MWI: channel %d no message waiting!\n and MWI: Channel %d no message w Using 1.6.1-169788, now it just never answers: -- Starting simple switch on 'DAHDI/4-1' [Jan 22 15:33:01] NOTICE[28000]: chan_dahdi.c:7144 ss_thread: Got event 18 (Ring Begin)... [Jan 22 15:33:04] NOTICE[28000]: chan_dahdi.c:7144 ss_thread: Got event 2 (Ring/Answered)... [Jan 22 15:33:04] NOTICE[28000]: chan_dahdi.c:7316 ss_thread: MWI: Channel 4 no message waiting! and that's it. Started bug 14313. sean ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
- sean darcy seandar...@gmail.com wrote: OK. Calmer now. If fact a 410 would have the same problem. I'll make the fix on our machines. Should I file a bug, or does the 169154 commit already fix it? sean The issues has been corrected in trunk and the 1.6.1 branch. Sicne we have addressed the issue and if it works for you, then I don't see the need for a bug report. If you have any other concerns or have any other problems with it, then go ahead and submit a bug report. Doug ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
On Friday 16 January 2009 20:27:57 sean darcy wrote: Tilghman Lesher wrote: On Friday 16 January 2009 17:43:21 sean darcy wrote: Danny Nicholas wrote: Why not do a zap restart instead of restarting asterisk? You could write an AGI to do the ZR when the condition occurred and lines where empty. Yes, a cron job to restart zaptel would cut off any call then existing. But how would I test for it? I can imagine: exten=s,n,ExecIf(some damn thing, System(service dahdi restart)) It's the some damn thing I can't imagine. How do you test if dahdi is acting up? Not a service restart, but a dahdi restart. You can't restart the dahdi service without first stopping Asterisk, anyway. if [ `../asterisk-trunk/contrib/scripts/astcli core show channels | wc -l` = 3 ]; then asterisk -rx 'dahdi restart'; fi Wow. I'll try that tomorrow. Put it as the cmd right after answer(), right? Or maybe, h,1 ? Well anyway, at least I'll be able to receive calls over pstn with dahdi. No, I'd actually recommend that as a cron job. It's basically, restart if idle. -- Tilghman ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
Tilghman Lesher wrote: On Friday 16 January 2009 20:27:57 sean darcy wrote: Tilghman Lesher wrote: On Friday 16 January 2009 17:43:21 sean darcy wrote: Danny Nicholas wrote: Why not do a zap restart instead of restarting asterisk? You could write an AGI to do the ZR when the condition occurred and lines where empty. Yes, a cron job to restart zaptel would cut off any call then existing. But how would I test for it? I can imagine: exten=s,n,ExecIf(some damn thing, System(service dahdi restart)) It's the some damn thing I can't imagine. How do you test if dahdi is acting up? Not a service restart, but a dahdi restart. You can't restart the dahdi service without first stopping Asterisk, anyway. if [ `../asterisk-trunk/contrib/scripts/astcli core show channels | wc -l` = 3 ]; then asterisk -rx 'dahdi restart'; fi Wow. I'll try that tomorrow. Put it as the cmd right after answer(), right? Or maybe, h,1 ? Well anyway, at least I'll be able to receive calls over pstn with dahdi. No, I'd actually recommend that as a cron job. It's basically, restart if idle. Any possibility of actually fixing dahdi? sean ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
On Saturday 17 January 2009 11:04:33 sean darcy wrote: Tilghman Lesher wrote: On Friday 16 January 2009 20:27:57 sean darcy wrote: Tilghman Lesher wrote: On Friday 16 January 2009 17:43:21 sean darcy wrote: Danny Nicholas wrote: Why not do a zap restart instead of restarting asterisk? You could write an AGI to do the ZR when the condition occurred and lines where empty. Yes, a cron job to restart zaptel would cut off any call then existing. But how would I test for it? I can imagine: exten=s,n,ExecIf(some damn thing, System(service dahdi restart)) It's the some damn thing I can't imagine. How do you test if dahdi is acting up? Not a service restart, but a dahdi restart. You can't restart the dahdi service without first stopping Asterisk, anyway. if [ `../asterisk-trunk/contrib/scripts/astcli core show channels | wc -l` = 3 ]; then asterisk -rx 'dahdi restart'; fi Wow. I'll try that tomorrow. Put it as the cmd right after answer(), right? Or maybe, h,1 ? Well anyway, at least I'll be able to receive calls over pstn with dahdi. No, I'd actually recommend that as a cron job. It's basically, restart if idle. Any possibility of actually fixing dahdi? One thing I would suggest is using the TDM410, instead of the TDM400. The problem may be hardware related. -- Tilghman ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
- sean darcy seandar...@gmail.com wrote: Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! As part of the implementation of issue 8587, a check was incldued for MWI messages preceded by Ring Pulse Alert Signals (RPAS). The RPAS is answered by chan_dahdi as a standard call and the MWI message is processed. As part of the implementation, if the MWI message was included, the channel was hung up. This did not take into account that possibility of MWI messages included into the to standard CID spills. I believe this is the case here and the MWI portion of the CID spill is causing the channel to hang up. You can look at commit 169154 for a fix or simply remove the ast_hangup calls immediately after the message MWI: channel %d no message waiting!\n and MWI: Channel %d no message w ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! As part of the implementation of issue 8587, a check was incldued for MWI messages preceded by Ring Pulse Alert Signals (RPAS). The RPAS is answered by chan_dahdi as a standard call and the MWI message is processed. As part of the implementation, if the MWI message was included, the channel was hung up. This did not take into account that possibility of MWI messages included into the to standard CID spills. I believe this is the case here and the MWI portion of the CID spill is causing the channel to hang up. You can look at commit 169154 for a fix or simply remove the ast_hangup calls immediately after the message MWI: channel %d no message waiting!\n and MWI: Channel %d no message w Thanks. That's a lot better idea than calling Digium Monday and yelling bloody murder. Why in the world would they screw up and obsolete their own hardware? sean ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
sean darcy wrote: Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! As part of the implementation of issue 8587, a check was incldued for MWI messages preceded by Ring Pulse Alert Signals (RPAS). The RPAS is answered by chan_dahdi as a standard call and the MWI message is processed. As part of the implementation, if the MWI message was included, the channel was hung up. This did not take into account that possibility of MWI messages included into the to standard CID spills. I believe this is the case here and the MWI portion of the CID spill is causing the channel to hang up. You can look at commit 169154 for a fix or simply remove the ast_hangup calls immediately after the message MWI: channel %d no message waiting!\n and MWI: Channel %d no message w Thanks. That's a lot better idea than calling Digium Monday and yelling bloody murder. Why in the world would they screw up and obsolete their own hardware? sean OK. Calmer now. If fact a 410 would have the same problem. I'll make the fix on our machines. Should I file a bug, or does the 169154 commit already fix it? sean ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
- sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! This message occurs when the pstn sends a FSK spill indicating the message waiting status of the FXO port in question. This may encoded in the caller ID indicator or may be contained in its own message spill. This is output as a NOTICE logging message. Regards, Doug Bailey ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! This message occurs when the pstn sends a FSK spill indicating the message waiting status of the FXO port in question. This may encoded in the caller ID indicator or may be contained in its own message spill. This is output as a NOTICE logging message. Regards, Doug Bailey I'm not sure I understand all that, but why does asterisk hang up? It means I can't receive any calls on that pstn line. AFAICS, only restarting asterisk allows calls to be received. A cron job to restart every 5 minutes? sean ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
On Fri, Jan 16, 2009 at 4:10 PM, sean darcy seandar...@gmail.com wrote: Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! This message occurs when the pstn sends a FSK spill indicating the message waiting status of the FXO port in question. This may encoded in the caller ID indicator or may be contained in its own message spill. This is output as a NOTICE logging message. Regards, Doug Bailey I'm not sure I understand all that, but why does asterisk hang up? It means I can't receive any calls on that pstn line. AFAICS, only restarting asterisk allows calls to be received. A cron job to restart every 5 minutes? sean ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users I hear Zaptel is pretty stable.. -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell) +12024369784 (Skype) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
Yes, BUT .. not 100% and discontinued in 1.4.22 on ... -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Steve Totaro Sent: Friday, January 16, 2009 3:39 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] pstn hangs up: MWI no message waiting ?? On Fri, Jan 16, 2009 at 4:10 PM, sean darcy seandar...@gmail.com wrote: Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! This message occurs when the pstn sends a FSK spill indicating the message waiting status of the FXO port in question. This may encoded in the caller ID indicator or may be contained in its own message spill. This is output as a NOTICE logging message. Regards, Doug Bailey I'm not sure I understand all that, but why does asterisk hang up? It means I can't receive any calls on that pstn line. AFAICS, only restarting asterisk allows calls to be received. A cron job to restart every 5 minutes? sean ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users I hear Zaptel is pretty stable.. -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell) +12024369784 (Skype) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
Why not do a zap restart instead of restarting asterisk? You could write an AGI to do the ZR when the condition occurred and lines where empty. -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Steve Totaro Sent: Friday, January 16, 2009 3:39 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] pstn hangs up: MWI no message waiting ?? On Fri, Jan 16, 2009 at 4:10 PM, sean darcy seandar...@gmail.com wrote: Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! This message occurs when the pstn sends a FSK spill indicating the message waiting status of the FXO port in question. This may encoded in the caller ID indicator or may be contained in its own message spill. This is output as a NOTICE logging message. Regards, Doug Bailey I'm not sure I understand all that, but why does asterisk hang up? It means I can't receive any calls on that pstn line. AFAICS, only restarting asterisk allows calls to be received. A cron job to restart every 5 minutes? sean ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users I hear Zaptel is pretty stable.. -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell) +12024369784 (Skype) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
Sounds like an awful hack. What does DAHDI do that Zaptel does not? Sounds more like a post for the bugs list On Fri, Jan 16, 2009 at 4:48 PM, Danny Nicholas da...@debsinc.com wrote: Why not do a zap restart instead of restarting asterisk? You could write an AGI to do the ZR when the condition occurred and lines where empty. -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Steve Totaro Sent: Friday, January 16, 2009 3:39 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] pstn hangs up: MWI no message waiting ?? On Fri, Jan 16, 2009 at 4:10 PM, sean darcy seandar...@gmail.com wrote: Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! This message occurs when the pstn sends a FSK spill indicating the message waiting status of the FXO port in question. This may encoded in the caller ID indicator or may be contained in its own message spill. This is output as a NOTICE logging message. Regards, Doug Bailey I'm not sure I understand all that, but why does asterisk hang up? It means I can't receive any calls on that pstn line. AFAICS, only restarting asterisk allows calls to be received. A cron job to restart every 5 minutes? sean I hear Zaptel is pretty stable.. -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell) +12024369784 (Skype) -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell) +12024369784 (Skype) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
So Zap restart is a worse hack than restarting *? What DAHDI does that Zaptel doesn't - 1. Makes Digium lawyers happy 2. Gives Developers headaches 3. Makes Coffee and soft drink manufacturers happy since we need so much caffine. 4. Make priests happy since we have to go to confession about it. -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Steve Totaro Sent: Friday, January 16, 2009 3:54 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] pstn hangs up: MWI no message waiting ?? Sounds like an awful hack. What does DAHDI do that Zaptel does not? Sounds more like a post for the bugs list On Fri, Jan 16, 2009 at 4:48 PM, Danny Nicholas da...@debsinc.com wrote: Why not do a zap restart instead of restarting asterisk? You could write an AGI to do the ZR when the condition occurred and lines where empty. -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Steve Totaro Sent: Friday, January 16, 2009 3:39 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] pstn hangs up: MWI no message waiting ?? On Fri, Jan 16, 2009 at 4:10 PM, sean darcy seandar...@gmail.com wrote: Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! This message occurs when the pstn sends a FSK spill indicating the message waiting status of the FXO port in question. This may encoded in the caller ID indicator or may be contained in its own message spill. This is output as a NOTICE logging message. Regards, Doug Bailey I'm not sure I understand all that, but why does asterisk hang up? It means I can't receive any calls on that pstn line. AFAICS, only restarting asterisk allows calls to be received. A cron job to restart every 5 minutes? sean I hear Zaptel is pretty stable.. -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell) +12024369784 (Skype) -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell) +12024369784 (Skype) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
Both are hacks. Neither are good hacks. On Fri, Jan 16, 2009 at 5:04 PM, Danny Nicholas da...@debsinc.com wrote: So Zap restart is a worse hack than restarting *? What DAHDI does that Zaptel doesn't - 1. Makes Digium lawyers happy 2. Gives Developers headaches 3. Makes Coffee and soft drink manufacturers happy since we need so much caffine. 4. Make priests happy since we have to go to confession about it. -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Steve Totaro Sent: Friday, January 16, 2009 3:54 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] pstn hangs up: MWI no message waiting ?? Sounds like an awful hack. What does DAHDI do that Zaptel does not? Sounds more like a post for the bugs list On Fri, Jan 16, 2009 at 4:48 PM, Danny Nicholas da...@debsinc.com wrote: Why not do a zap restart instead of restarting asterisk? You could write an AGI to do the ZR when the condition occurred and lines where empty. -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Steve Totaro Sent: Friday, January 16, 2009 3:39 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] pstn hangs up: MWI no message waiting ?? On Fri, Jan 16, 2009 at 4:10 PM, sean darcy seandar...@gmail.com wrote: Doug Bailey wrote: - sean darcy seandar...@gmail.com wrote: pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4 no message waiting! This message occurs when the pstn sends a FSK spill indicating the message waiting status of the FXO port in question. This may encoded in the caller ID indicator or may be contained in its own message spill. This is output as a NOTICE logging message. Regards, Doug Bailey I'm not sure I understand all that, but why does asterisk hang up? It means I can't receive any calls on that pstn line. AFAICS, only restarting asterisk allows calls to be received. A cron job to restart every 5 minutes? sean I hear Zaptel is pretty stable.. -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell) +12024369784 (Skype) -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell) +12024369784 (Skype) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell) +12024369784 (Skype) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
Danny Nicholas wrote: Why not do a zap restart instead of restarting asterisk? You could write an AGI to do the ZR when the condition occurred and lines where empty. Yes, a cron job to restart zaptel would cut off any call then existing. But how would I test for it? I can imagine: exten=s,n,ExecIf(some damn thing, System(service dahdi restart)) It's the some damn thing I can't imagine. How do you test if dahdi is acting up? sean ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
On Friday 16 January 2009 17:43:21 sean darcy wrote: Danny Nicholas wrote: Why not do a zap restart instead of restarting asterisk? You could write an AGI to do the ZR when the condition occurred and lines where empty. Yes, a cron job to restart zaptel would cut off any call then existing. But how would I test for it? I can imagine: exten=s,n,ExecIf(some damn thing, System(service dahdi restart)) It's the some damn thing I can't imagine. How do you test if dahdi is acting up? Not a service restart, but a dahdi restart. You can't restart the dahdi service without first stopping Asterisk, anyway. if [ `../asterisk-trunk/contrib/scripts/astcli core show channels | wc -l` = 3 ]; then asterisk -rx 'dahdi restart'; fi -- Tilghman ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] pstn hangs up: MWI no message waiting ??
Tilghman Lesher wrote: On Friday 16 January 2009 17:43:21 sean darcy wrote: Danny Nicholas wrote: Why not do a zap restart instead of restarting asterisk? You could write an AGI to do the ZR when the condition occurred and lines where empty. Yes, a cron job to restart zaptel would cut off any call then existing. But how would I test for it? I can imagine: exten=s,n,ExecIf(some damn thing, System(service dahdi restart)) It's the some damn thing I can't imagine. How do you test if dahdi is acting up? Not a service restart, but a dahdi restart. You can't restart the dahdi service without first stopping Asterisk, anyway. if [ `../asterisk-trunk/contrib/scripts/astcli core show channels | wc -l` = 3 ]; then asterisk -rx 'dahdi restart'; fi Wow. I'll try that tomorrow. Put it as the cmd right after answer(), right? Or maybe, h,1 ? Well anyway, at least I'll be able to receive calls over pstn with dahdi. Thanks. sean ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
