[asterisk-bugs] [JIRA] Commented: (ASTERISK-20122) 1.8.14.0 seg faulted 10 times supposedly in ast_ssl_teardown while a TCP TLS node was re-regestering after the Asterisk reload

[Vladimir Mikhelson (JIRA)]

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

Vladimir Mikhelson commented on ASTERISK-20122:
-----------------------------------------------

Michael,

I saw the "Enter Feedback" but thought it would be misuse to utilize it to enter regular comments.  BTW, now the "Comment" button is available.

Mantis was so much more convenient, user friendlier, and 1000 times more efficient.

Thank you,
Vladimir


> 1.8.14.0 seg faulted 10 times supposedly in ast_ssl_teardown while a TCP TLS node was re-regestering after the Asterisk reload
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20122
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20122
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/TCP-TLS
>    Affects Versions: 1.8.14.0
>         Environment: CentOS 5.8, kernel 2.6.18-308.11.1.el5
> FreePBX 2.10.1.1
>            Reporter: Vladimir Mikhelson
>         Attachments: backtrace.txt, gdb.txt
>
>
> After Asterisk 1.8.14.0 was built from sources (upgraded from 1.8.13.0), and loaded normally, it experienced segmentation fault ten (10) times.
> The suspect is Cisco 7906 which re-registered on a previously used port 51844 where Asterisk would refuse the connection until Cisco tried to use 51063. See a successful sequence below. When the Asterisk seg. faulted we only observed a couple of "Unable to connect SIP socket to 172.17.137.70:51844: Connection refused" messages.
> [2012-07-11 22:51:13] NOTICE[4586] chan_sip.c: Peer '470' is now UNREACHABLE!  Last qualify: 0
> [2012-07-11 22:51:23] ERROR[4624] tcptls.c: Unable to connect SIP socket to 172.17.137.70:51844: Connection refused
> [2012-07-11 22:51:37] ERROR[4643] tcptls.c: Unable to connect SIP socket to 172.17.137.70:51844: Connection refused
> [2012-07-11 22:51:47] VERBOSE[4537] asterisk.c:     -- Remote UNIX connection
> [2012-07-11 22:51:51] ERROR[4716] tcptls.c: Unable to connect SIP socket to 172.17.137.70:51844: Connection refused
> [2012-07-11 22:52:05] ERROR[4736] tcptls.c: Unable to connect SIP socket to 172.17.137.70:51844: Connection refused
> [2012-07-11 22:52:19] ERROR[4753] tcptls.c: Unable to connect SIP socket to 172.17.137.70:51844: Connection refused
> [2012-07-11 22:52:33] ERROR[4768] tcptls.c: Unable to connect SIP socket to 172.17.137.70:51844: Connection refused
> [2012-07-11 22:52:47] ERROR[4783] tcptls.c: Unable to connect SIP socket to 172.17.137.70:51844: Connection refused
> [2012-07-11 22:53:01] ERROR[4809] tcptls.c: Unable to connect SIP socket to 172.17.137.70:51844: Connection refused
> [2012-07-11 22:53:15] ERROR[4828] tcptls.c: Unable to connect SIP socket to 172.17.137.70:51844: Connection refused
> [2012-07-11 22:53:29] ERROR[4848] tcptls.c: Unable to connect SIP socket to 172.17.137.70:51844: Connection refused
> [2012-07-11 22:53:38] VERBOSE[4862] chan_sip.c:     -- Registered SIP '470' at 172.17.137.70:51063
> [2012-07-11 22:53:38] NOTICE[4862] chan_sip.c: Peer '470' is now Reachable. (421ms / 2000ms)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira