|Summary:||ASTERISK-16524: Segmentation fault in scheduled event|
|Date Opened:||2010-08-08 07:16:47||Date Closed:||2010-08-09 07:56:15|
|Environment:||Attachments:||( 0) sched.fix|
|Description:||This is continuation of https://issues.asterisk.org/view.php?id=17497, closed by dvossel.|
It looks to me that fix by dvossel was incorrect, because actual fix is backport from 1.6.2 or trunk. This is verified on production server with 500 real simultaneous calls on which this issue reproduced up to several times a day, and stopped reproducing after attached patch.
What dvossel did is completely new functionality that is introduced in asterisk and can cause regressions.
|Comments:||By: under (under) 2010-08-08 07:21:50|
Attached patch fixes issues with segfaults in sip_t38_abort() and transmit_provisional_keepalive().
Actually this patch is a backport from trunk.
I backported only relevant to t38 and provisional keepelive pieces of code, because we didn't experience problems in other parts of similar code and I don't want to put regressions there.
Patch is verified on production server with 500 calls (operation during 1 week without failures)
By: Paul Belanger (pabelanger) 2010-08-09 07:56:04
You will need to maintain the patch yourself, we have placed 1.6.0 / 1.6.1 into security mode.
Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.6.0 and 1.6.1 branches has ended. For continued maintenance support please move to the 1.6.2 branch.
More information on this change can be found in the release announcement: http://www.asterisk.org/node/49924