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

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Mar 23 17:08:41 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14727 
====================================================================== 
Reported By:                pj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14727
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
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-03-23 17:08 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


====================================================================== 

---------------------------------------------------------------------- 
 (0102109) pj (reporter) - 2009-03-23 17:08
 http://bugs.digium.com/view.php?id=14727#c102109 
---------------------------------------------------------------------- 
I think also, that current design, when asterisk doesn't use same transport
for outgoing request as peer is using for registration, is bad, because eg.
'qualify' always marks peer as unreachable, in case when peer registers eg.
with tcp, but asterisk has configured transport=udp,tcp
imho, better behaviour will be to use same transport, that peer is using
for registration, regardless of order of 'transport' protocol fields in
sip.conf 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-23 17:08 pj             Note Added: 0102109                          
======================================================================




More information about the asterisk-bugs mailing list