[asterisk-bugs] [JIRA] (ASTERISK-16279) [patch] TCP connection will not be closed, if device do a reregister
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Thu Jan 22 08:16:37 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224608#comment-224608 ]
Matt Jordan commented on ASTERISK-16279:
----------------------------------------
This issue is closed.
If you feel this is still a problem, you will need to open a new issue. Please provide:
* Your {{sip.conf}}
* A debug log with 'sip set debug on' illustrating the problem. Indicate in the issue report where the problem occurs in the log. Instructions can be found on the Asterisk wiki on how to properly generate a debug log: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information
* Evidence showing the persistent TCP connection.
> [patch] TCP connection will not be closed, if device do a reregister
> --------------------------------------------------------------------
>
> Key: ASTERISK-16279
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-16279
> Project: Asterisk
> Issue Type: Bug
> Components: Channels/chan_sip/TCP-TLS
> Reporter: Marcello Ceschia
> Severity: Minor
> Attachments: chan_sip-close-tcp-connection.patch, chan_sip-tcp-close_branch162.patch, chan_sip-tcp-close_branch18.patch, tcptls.patch
>
>
> 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.
> ****** ADDITIONAL INFORMATION ******
> E.g.:
> *CLI> sip show tcp
> Host Port Transport Type
> 172.17.1.50 40039 TCP Server
> 172.17.1.50 59966 TCP Server
> # netstat -n | grep "5060"
> tcp 0 0 172.17.3.1:5060 172.17.1.50:59966 VERBUNDEN
> tcp 0 0 172.17.3.1:5060 172.17.1.50:40039 VERBUNDEN
> tcp 0 0 172.17.3.1:5060 172.17.1.50:50794 VERBUNDEN
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list