[Asterisk-bsd] Panic on dahdi restart

Ian FREISLICH ianf at clue.co.za
Thu Aug 26 08:25:27 CDT 2010


Max Khon wrote:
> Ian,
> 
> On Thu, Aug 26, 2010 at 4:57 PM, Ian FREISLICH <ianf at clue.co.za> wrote:
> 
> > Only thing is, I've now got RED alarms that won't clear:
> > >
> > > [Aug 26 10:59:24] WARNING[10527] chan_dahdi.c: Detected alarm on channel
> > 1: R
> > ed Alarm
> > > [Aug 26 10:59:24] WARNING[10527] chan_dahdi.c: Detected alarm on channel
> > 2: R
> > ed Alarm
> > >
> > > It worked for a little bit, but on removing the PSTN connection and
> > > restarting asterisk and dahdi a few times trying to get asterisk
> > > to not run as root (which fails because the devfs file permissions
> > > can't be set at load time).
> > >
> > > The RED alarm only clears on reboot.
> >
> > Ok.  This problem was the RJ11 connector - corrected.
> >
> > My other internal/inbound call issues were resolved by upgrading
> > asterisk to 1.6.
> >
> > Seems like echo cancellation is better than on zaptel+asterisk1.4
> > (freebsd-6) when I last had this work.  Now I can remove the linux
> > pbx, which is Great News.
> 
> Great! Which echo cancellation driver do you use?

Currently MG2, but I prefer OSLEC.  MG2 works better, not better
than OSLEC, if you can use fxotune to set the echocan coefficients,
which is why it's better now compared to old zaptel.  I'm not even
sure if while it was reporting MG2 on zaptel (1.4.7 an that time)
it was actually using it.

You've done a great job porting this to FreeBSD.

Thanks
Ian

-- 
Ian Freislich



More information about the Asterisk-BSD mailing list