[asterisk-bugs] [Asterisk 0017779]: tcptls.c:350 Unable to connect SIP socket Connection refused

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17779 
====================================================================== 
Reported By:                smallet
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17779
Category:                   Channels/chan_sip/TCP-TLS
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.10 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-08-02 14:06 CDT
Last Modified:              2010-08-05 14:03 CDT
====================================================================== 
Summary:                    tcptls.c:350 Unable to connect SIP socket Connection
refused
Description: 
Steps to reproduce:
1- Add a peer information as shown in graph 1 below in sip.conf.
2- do asterisk -r, then sip reload.
3- That server has connection refused so the asterisk debug will start
complaining it can't connect to the server.
4- Do sip show peers, you will see the peer with a status of UNREACHABLE.
So far so good...
5- Remove The whole graph 1 from your sip.conf file.
6- Do a sip reload again. the sip show peers will not show the peer
anymore.
7- The connection refused will keep going on and on forever unless you
actually restart asterisk completely.

Is there a way to bypass this or is this a bug?

[Aug  2 14:53:56] ERROR[13926]: tcptls.c:350 ast_tcptls_client_start:
Unable to connect SIP socket to 192.168.0.228:5060: Connection refused
[Aug  2 14:54:10] ERROR[13997]: tcptls.c:350 ast_tcptls_client_start:
Unable to connect SIP socket to 192.168.0.228:5060: Connection refused
[Aug  2 14:54:24] ERROR[14002]: tcptls.c:350 ast_tcptls_client_start:
Unable to connect SIP socket to 192.168.0.228:5060: Connection refused
[Aug  2 14:54:38] ERROR[14011]: tcptls.c:350 ast_tcptls_client_start:
Unable to connect SIP socket to 192.168.0.228:5060: Connection refused
[Aug  2 14:54:52] ERROR[14016]: tcptls.c:350 ast_tcptls_client_start:
Unable to connect SIP socket to 192.168.0.228:5060: Connection refused
[Aug  2 14:55:06] ERROR[14089]: tcptls.c:350 ast_tcptls_client_start:
Unable to connect SIP socket to 192.168.0.228:5060: Connection refused
[Aug  2 14:55:20] ERROR[14099]: tcptls.c:350 ast_tcptls_client_start:
Unable to connect SIP socket to 192.168.0.228:5060: Connection refused
====================================================================== 

---------------------------------------------------------------------- 
 (0125584) smallet (reporter) - 2010-08-05 14:03
 https://issues.asterisk.org/view.php?id=17779#c125584 
---------------------------------------------------------------------- 
Now my question is this:
Does this mean any TCP connection always hang and is never closed properly
for all calls? Or does this affect only SIP options?

You can see that if you change your IP address multiple times that it will
try every 15 seconds to connect to each IP address forever.. It's kind of
ugly :/.

I read there was a fix for TCP connections (memory leak) in 1.6.1.x branch
but sadly it did not fix this error.

Also when do you think there will be a patch available to fix this?
Thanks. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-05 14:03 smallet        Note Added: 0125584                          
======================================================================