[asterisk-bugs] [Asterisk 0014727]: lock or crash after changing sip 'transport'
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Apr 21 15:34:41 CDT 2009
A NOTE has been added to this issue.
======================================================================
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: closed
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 183057
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2009-03-23 16:59 CDT
Last Modified: 2009-04-21 15:34 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...
======================================================================
----------------------------------------------------------------------
(0103560) svnbot (reporter) - 2009-04-21 15:34
http://bugs.digium.com/view.php?id=14727#c103560
----------------------------------------------------------------------
Repository: asterisk
Revision: 189771
U trunk/channels/chan_sip.c
------------------------------------------------------------------------
r189771 | dvossel | 2009-04-21 15:28:37 -0500 (Tue, 21 Apr 2009) | 11
lines
Fixes segfault when switching UDP to TCP in sip.conf after reload.
If transport in sip.conf is switched from upd to tcp, Asterisk segfaults
right after issuing a sip reload. The problem is the socket type is
changed to TCP but the fd may still be present for UDP. Later, when the
tcp session should be created or set using an existing one, it isn't
because the old file descriptor is still present. Now every time transport
is changed during a sip.conf reload, the file descriptor is set to -1,
signifying it must be created or found.
(closes issue http://bugs.digium.com/view.php?id=14727)
Reported by: pj
Tested by: dvossel
Review: http://reviewboard.digium.com/r/229/
------------------------------------------------------------------------
http://svn.digium.com/view/asterisk?view=rev&revision=189771
Issue History
Date Modified Username Field Change
======================================================================
2009-04-21 15:34 svnbot Checkin
2009-04-21 15:34 svnbot Note Added: 0103560
======================================================================
More information about the asterisk-bugs
mailing list