[asterisk-bugs] [JIRA] (ASTERISK-21447) Asterisk crashes while connecting to TCP peers

[Zohair Raza (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205419#comment-205419 ] 

Zohair Raza commented on ASTERISK-21447:
----------------------------------------

Hi, 

I tried to simulate on another system (clone of the first) but asterisk didn't crash, maybe because it only has two phones. 

but I still see those messages 
2013-04-18 12:11:27] ERROR[28932]: tcptls.c:446 ast_tcptls_client_start: Unable to connect SIP socket to 190.103.142.199:5062: Connection refused

Later I installed asterisk 11 current release but having same messages. When I disable qualify and restart asterisk then these messages dont come every minute(qualifyfreq) but only a restart do the trick and reload does not.

However when it starts up, in the logs I see asterisk tries to connect on the previous ports which phone was connected from 
[2013-04-18 12:34:47] ERROR[29566]: tcptls.c:446 ast_tcptls_client_start: Unable to connect SIP socket to 190.103.140.168:5075: Connection refused
[2013-04-18 12:34:47] ERROR[29567]: tcptls.c:446 ast_tcptls_client_start: Unable to connect SIP socket to 190.103.142.199:5066: Connection refused

Is it obvious? I think it should forget about the peer in some time lets say 2 minutes?

                
> Asterisk crashes while connecting to TCP peers
> ----------------------------------------------
>
>                 Key: ASTERISK-21447
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21447
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 1.8.14.0
>         Environment: CentOS linux 2.6.32-279.19.1.el6.x86_64
>            Reporter: Zohair Raza
>            Assignee: Zohair Raza
>         Attachments: astlogs.txt, astsipsett.txt, backtrace3.txt, backtrace-threads3.txt, core-show-locks3.txt, gdb.txt
>
>
> Hi, 
> I ran in to this problem a couple of times, I have asterisk running in both TCP and UDP modes but the peers are configured as TCP. For some reason (maybe packet loss in the network) asterisk gets out of sync with phones and tries to make a connection with a port at which phone is not registered anymore. 
> The strange behavior is, after some time asterisk gets killed. I am not sure how to overcome this. What I am thinking is to somehow force asterisk to not connect with that peer if for eg X number of tries fail. I tried disabling qualify and originating session timers by asterisk but the connections were not being stopped.
> I am attaching backtraces and asterisk log before the time of restarts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira