[asterisk-users] pstn hangs up: MWI no message waiting ??

Tilghman Lesher tilghman at mail.jeffandtilghman.com
Sat Jan 17 11:41:25 CST 2009


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



More information about the asterisk-users mailing list