[asterisk-bugs] [Asterisk 0017779]: [patch] 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:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   17779
Category:                   Channels/chan_sip/TCP-TLS
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Target Version:             1.6.2.15
Asterisk Version:           SVN 
JIRA:                       SWP-1999 
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-10-13 09:48 CDT
====================================================================== 
Summary:                    [patch] tcptls.c:350 Unable to connect SIP socket
Connection refused
Description: 
Steps to reproduce:

<ol>
<li>Add a peer information as shown in graph 1 below in sip.conf.</li>
<li>do asterisk -r, then sip reload.</li>
<li>That server has connection refused so the asterisk debug will start
complaining it can't connect to the server.</li>
<li>Do sip show peers, you will see the peer with a status of
UNREACHABLE.</li>

So far so good...<br />

<li>Remove The whole graph 1 from your sip.conf file.</li>
<li>Do a sip reload again. the sip show peers will not show the peer
anymore.</li>
<li>The connection refused will keep going on and on forever unless you
actually restart asterisk completely.</li>
</ol>

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
====================================================================== 

---------------------------------------------------------------------- 
 (0127944) smallet (reporter) - 2010-10-13 09:48
 https://issues.asterisk.org/view.php?id=17779#c127944 
---------------------------------------------------------------------- 
Ok, so before applying the patch I could reproduce the issue. See how .13
and .14 both trigger errors but in my peer conf file I just have .14
defined.

[Oct 13 10:09:53] ERROR[4308]: tcptls.c:350 ast_tcptls_client_start:
Unable to connect SIP socket to 192.168.0.14:5060: No route to host
[Oct 13 10:09:54] NOTICE[3118]: chan_sip.c:23322 sip_poke_noanswer: Peer
'192.168.0.14' is now UNREACHABLE!  Last qualify: 0
[Oct 13 10:10:00] ERROR[4309]: tcptls.c:350 ast_tcptls_client_start:
Unable to connect SIP socket to 192.168.0.13:5060: Connection refused
[Oct 13 10:10:07] ERROR[4360]: tcptls.c:350 ast_tcptls_client_start:
Unable to connect SIP socket to 192.168.0.14:5060: No route to host
[Oct 13 10:10:14] ERROR[4365]: tcptls.c:350 ast_tcptls_client_start:
Unable to connect SIP socket to 192.168.0.13:5060: Connection refused

After applying the patch, I did the same steps, and now I see errors only
coming from the Peer that is defined in the conf file. The other warnings
have disappeared.

The patch works! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-13 09:48 smallet        Note Added: 0127944                          
======================================================================