[asterisk-dev] Final call for changes to Asterisk 1.4 and 1.6.2

[Russell Bryant]

----- Original Message -----
> On Apr 26, 2011, at 9:33 AM, Nic Colledge wrote:
> 
> >> I have the same comment here. Can you please point me to the
> >> specific bug reports that have affected you? I know 1.8 isn't
> >> perfect (or any other version of Asterisk), but it's useful to have
> >> additional feedback on issues that have prevented migration.
> >
> > I have been experiecing the issues reported in 0018511 and 0017521
> > (possibly related) causing serious problems with IAX and daily
> > crashes on 1.8. We have managed to move most of our calls away from
> > IAX but the problems still remain (where users cant use SIP).
> > Transcoding seems to make things worse (crash more frequent). One
> > current theory (which I hope to test later this week) is that 118511
> > is timing related and the probelms go away when you switch over to
> > Dahdi for timing.
> 
> 
> 18511 - Yes, I agree that this looks timing related. It looks like
> res_timing_pthread is just consuming so much CPU that it appears that
> Asterisk is locking up. Switching to res_timing_dahdi or
> res_timing_timerfd should resolve this. I think we should probably
> just disable res_timing_pthread completely. It causes too many bug
> reports like this. It's useful for a lightly loaded system, but that's
> about it. A more modern Linux install should get res_timing_timerfd by
> default, though.
> 
> 17521 - Are you using Mac OS X? From my last quick browse of this
> issue, this one also looked like it had to do with the use of
> res_timing_pthread, and the reporter didn't have any other timing
> module option since he's using OS X. A different timing module might
> resolve this for you, as well.

Also, as far as I can tell, neither of these are specific to 1.8.  Did you only start experiencing problems when you migrated to 1.8?  What were you migrating from?  If you were going from 1.4, and it does turn out that res_timing_pthread is the issue here, then that would make sense.  The timing API was introduced in 1.6.1.

You also mentioned you were having crashes with 1.8.  Do you have bug reports for those?

-- 
Russell Bryant
Digium, Inc.   |   Engineering Manager, Open Source Software
445 Jan Davis Drive NW    -     Huntsville, AL 35806  -  USA
www.digium.com  -=-  www.asterisk.org -=- blogs.asterisk.org