[asterisk-bugs] [JIRA] (ASTERISK-28765) tcptls API: bad file descriptor when connection fails

Asterisk Team (JIRA) noreply at issues.asterisk.org
Tue Mar 3 05:19:25 CST 2020


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

Asterisk Team commented on ASTERISK-28765:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> tcptls API: bad file descriptor when connection fails
> -----------------------------------------------------
>
>                 Key: ASTERISK-28765
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28765
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_externalivr, Channels/chan_sip/TCP-TLS
>    Affects Versions: 16.3.0
>            Reporter: Jean Aunis - Prescom
>
> When trying to connect to an ExternalIVR() which is not started, a "Bad file descriptor" error is reported.
> Excerpt from the logs:
> {code}
>  -- Executing [2000 at default:1] ExternalIVR("Local/2000 at default-00000000;2", "ivr://127.0.0.1") in new stack
>     -- Called 2000 at default
>        > ExternalIVR received application and arguments: ivr://127.0.0.1
>        > ExternalIVR received options: (null)
>        > Parsing options from: [(null)]
>     -- Answering channel and starting generator
>     -- Local/2000 at default-00000000;1 answered
>        > Launching Wait(1000) on Local/2000 at default-00000000;1
> [Mar  3 11:58:57] ERROR[16427][C-00000001]: tcptls.c:553 ast_tcptls_client_start: Unable to connect IVR to 127.0.0.1:2949: Connection refused
> [Mar  3 11:58:57] ERROR[16427][C-00000001]: iostream.c:569 ast_iostream_close: close() failed: Bad file descriptor
> [Mar  3 11:58:57] ERROR[16427][C-00000001]: app_externalivr.c:529 app_exec: Local/2000 at default-00000000;2: Could not connect to any host.  ExternalIVR failed.
> {code}
> A similar issue happens when using chan_sip with TCP transport.
> It seems that ast_tcptls_client_start closes twice the same file descriptor.
> It can randomly affect Asterisk stability if the same file descriptor is reused in the meantime.



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



More information about the asterisk-bugs mailing list