[asterisk-bugs] [JIRA] (ASTERISK-24132) Remote TLS server close connection. Dialstatus = CANCEL

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-24132:
----------------------------------------

While "CANCEL" is the wrong status for your scenario, I don't think {{app_dial}} itself is wrong. From its perspective, it went to read a frame from the channel and didn't get one back. That's an indication that the calling channel hung up. The best it can infer from that is that the caller gave up, and so it cancels the dial.

If we need to have a different status in this situation, then something should queue a hangup on the destination channel with the appropriate status code. It sounds like that didn't happen here; if it had, I would expect that we would have hung up the calling channel appropriately long before it got to this place.

> Remote TLS server close connection. Dialstatus = CANCEL
> -------------------------------------------------------
>
>                 Key: ASTERISK-24132
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24132
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/TCP-TLS
>    Affects Versions: 1.8.29.0
>         Environment: Linux Centos 6, Microsoft Lync
>            Reporter: Olle Johansson
>            Severity: Minor
>
> Call is set up, TLS connection opened. Microsoft Lync requires TLS client cert, Asterisk sends cert (automatically in OpenSSL I guess) and MS Lync doesn't approve. 
> Lync close TCP connection, Asterisk sends SSL finish, then connection closes.
> TLS read now generates a read error on the socket, the TCP thread shuts down and app_dial can't read a frame during call setup, the call fails with CANCEL as dialstatus.
> I think it has to be CONGESTION. But can't figure out where to set that status in this chain of events. CANCEL is very wrong.



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