[asterisk-bugs] [Asterisk 0017544]: [patch] TCP connection will not be closed, if device do a reregister

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17544 
====================================================================== 
Reported By:                marcelloceschia
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   17544
Category:                   Channels/chan_sip/TCP-TLS
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Target Version:             1.4/1.6.2 Issues (Final Release)
Asterisk Version:           SVN 
JIRA:                       SWP-1753 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2 
SVN Revision (number only!): 271688 
Request Review:              
====================================================================== 
Date Submitted:             2010-06-22 07:12 CDT
Last Modified:              2011-05-05 12:49 CDT
====================================================================== 
Summary:                    [patch] TCP connection will not be closed, if device
do a reregister
Description: 
If I use a mobile device that switches between 3G an WLAN, several tcp
ports stay open.
Only a unregister from the client does close the ports, "sip unregister
<peer>" does not.


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

---------------------------------------------------------------------- 
 (0134514) mnicholson (administrator) - 2011-05-05 12:49
 https://issues.asterisk.org/view.php?id=17544#c134514 
---------------------------------------------------------------------- 
I am going to commit a modified version the TCP KEEPALIVE fix for this
issue.  I am not sure closing the existing session for that peer is the
right way to handle this. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-05 12:49 mnicholson     Note Added: 0134514                          
======================================================================