[asterisk-bugs] [Asterisk 0014727]: lock or crash after changing sip 'transport'

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
http://bugs.digium.com/view.php?id=14727 
====================================================================== 
Reported By:                pj
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   14727
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 183057 
Request Review:              
====================================================================== 
Date Submitted:             2009-03-23 16:59 CDT
Last Modified:              2009-04-16 10:05 CDT
====================================================================== 
Summary:                    lock or crash after changing sip 'transport'
Description: 
When I change sip transport protocol order, eg. udp,tcp -> tcp,udp and do
'sip reload' asterisk locks or crash


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013117 [patch] multiple 'transport' on peer do...
====================================================================== 

---------------------------------------------------------------------- 
 (0103314) dvossel (administrator) - 2009-04-16 10:05
 http://bugs.digium.com/view.php?id=14727#c103314 
---------------------------------------------------------------------- 
I've taken a brief look at this issue but have not been able to reproduce
the deadlock.  I've got a few more ways I'd like to test it, but it would
be helpful to have more information as to what the system is doing before
the deadlock.  What kind of environment does it need to be in for this to
happen?  Also, is this something that happens %100 of the time or just
occasionally? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-16 10:05 dvossel        Note Added: 0103314                          
2009-04-16 10:05 dvossel        Status                   assigned => feedback
======================================================================