[asterisk-bugs] [Asterisk 0012799]: fresh reboot of asterisk server, TCP sip peers get invite via UDP

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12799 
====================================================================== 
Reported By:                pabelanger
Assigned To:                bbryant
====================================================================== 
Project:                    Asterisk
Issue ID:                   12799
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0-beta9 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             06-05-2008 11:41 CDT
Last Modified:              06-26-2008 13:00 CDT
====================================================================== 
Summary:                    fresh reboot of asterisk server, TCP sip peers get
invite via UDP
Description: 
Weird issue, 

If we reboot our asterisk server (# sudo reboot), then let everything boot
back up.  SIP peers configured for TCP seem to default to UDP clients.  But
if we issue 'reload' from the asterisk cli or init.d script, the SIP peers
will be setup back to TCP.
====================================================================== 

---------------------------------------------------------------------- 
 bbryant - 06-26-08 13:00  
---------------------------------------------------------------------- 
Only registrations that are udp should have been stored in the db.

I can't seem to replicate this problem locally, but I have a theory on
what is happening. What the problem could be is that asterisk doesn't know
what to do if a peer that should be using a tcp session sends a response
via udp, stores the connection information in astdb, and continues using
udp for any further communication with that peer.

With the exception of not saving this switch in the astdb, not changing
the peer's transport for new dialogs, and throwing a warning for when
switching from tcp or an error and failure case for when switching from tls
i believe this is the correct fix for that problem.

I'll have a patch up soon.

pabelanger, are your peers running on the same machine, i.e. softphones or
other asterisk installations in a virtual machine? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-26-08 13:00  bbryant        Note Added: 0089302                          
======================================================================