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

Asterisk Bug Tracker noreply at bugs.digium.com
Tue May 5 03:56:01 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:                     assigned
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-05-05 03:56 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0104190) pj (reporter) - 2009-05-05 03:56
 http://bugs.digium.com/view.php?id=14727#c104190 
---------------------------------------------------------------------- 
side note, asterisk is trying to send 'options' request to phone using TCP,
but it's wrong, because phone is registered using UDP.
Asterisk should use transport protocol, that phone actualy uses in
registration request and not rely on transport order specified by
"transport=tcp,udp" in this case. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-05 03:56 pj             Note Added: 0104190                          
======================================================================




More information about the asterisk-bugs mailing list