[asterisk-bugs] [Asterisk 0017813]: Segmentation fault in scheduled event

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17813 
====================================================================== 
Reported By:                under
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17813
Category:                   Channels/chan_sip/General
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0 - SECURITY ONLY! Test 1.6.2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-08-08 07:16 CDT
Last Modified:              2010-08-09 07:56 CDT
====================================================================== 
Summary:                    Segmentation fault in scheduled event
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.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-09 07:56 pabelanger     Status                   new => closed       
2010-08-09 07:56 pabelanger     Resolution               open => won't fix   
======================================================================