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

Michael L. Young (JIRA) noreply at issues.asterisk.org
Thu Apr 18 12:20:01 CDT 2013


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

Michael L. Young commented on ASTERISK-21447:
---------------------------------------------

Zohair,  not crashing is a good thing.  There have been memory leak fixes and buffer overflow fixes put into the latest code.  There have also been bug fixes in the TCP/TLS code as well.  Checkout the changelog and the upgrade files for potential configuration changes.  To me, it sounds like a configuration issue.  The message is stating that whatever is at 190.103.140.168, 190.103.142.199 and 190.103.142.199 is refusing the connection.  You need to find out why it is refusing the connection.  Check that firewalls are not blocking the connections.
                
> 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



More information about the asterisk-bugs mailing list