[asterisk-bugs] [JIRA] (ASTERISK-28543) When Asterisk cannot connect to SIP socket it starts to flood with "Bad descriptor" errors and hangs

Kevin Harwell (JIRA) noreply at issues.asterisk.org
Wed Sep 18 13:59:47 CDT 2019


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

Kevin Harwell commented on ASTERISK-28543:
------------------------------------------

The chan_sip channel driver is in 'extended' support status and is supported only by community members.  Your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available.

Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1]

If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way.

[1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process
[2]: http://www.asterisk.org/community/discuss
[3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties



>     When Asterisk cannot connect to SIP socket it starts to flood with "Bad descriptor" errors and hangs
> --------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28543
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28543
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 16.3.0, 16.5.1
>         Environment:     CentOS Linux release 7.6.1810 (Core) x64
>            Reporter: John Smith
>         Attachments: 2019-09-18_10-4303.png, MobaXterm_Personal_11.1_2019-09-16_21-2648.png
>
>
>     When some endpoint goes offline the following messages appear in the console:
>  ERROR[2889]: tcptls.c:553 ast_tcptls_client_start: Unable to connect SIP socket to IP:5060: Connection refused 
> followed by 
> ERROR[2751]: iostream.c:569 ast_iostream_close: close() failed: Bad file descriptor
> Error occurs only for endpoints with protocol=tcp in sip.conf (and probably tls) after some time calls started to drop with "Bad file descriptor" errors and finally after some time Asterisk becomes unresponsible: all endpoints lose their registrations, no calls can be made/received. 
> Service restart does not help. 
> Server restart can help for a short time. 
> Workaround is to remove offline endpoint from sip.conf
> sip.conf example:
> [phone1] 
> type=friend 
> host=10.10.8.8 
> port=5060 
> dtmfmode=rfc2833
> context=office
> directmedia=no
> qualify=yes 
> transport=tcp 
> allow=!all,alaw,ulaw,g722 
> checked versions:
> 16.3.0
> 16.5.1



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list