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

[Jean Aunis - Prescom (JIRA)]

Jean Aunis - Prescom created ASTERISK-28765:
-----------------------------------------------

             Summary: 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)