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

[Nic Colledge]

> 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?
What version I was using is a hard question to answer, we were using a old pre-1.8 trunk release for ages that was pretty stable (don't have the revision number - over a year old) we were only using it rather than 1.6 because it included CEL. I'm pretty sure this was from before the timing API though which would make sense.
When we moved to 1.8 we started seeing problems with IAX similar to those reported above (and others), I was not the original reporter of the issues above but have been monitoring them with interest rather than posting my own duplicates.
We are currently using timerfd and Ubuntu. My experiences with 17521 were very similar to the original posters, using G729 transcoding (using the Digium software codec) made the problem much more frequent. We are currently using a work-around of minimising our use of IAX and transcoding since doing this two weeks ago we have had a much more stable setup. I'll try Dahdi for timing and re-enable G729 and report my findings on issues.asterisk.org.
I feel like I'm hijacking this thread now which was not my intention, I just wanted to draw your attention to the IAX related issues on the tracker which may be preventing others from migrating.
Thanks,
Nic.