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

Olle Johansson (JIRA) noreply at issues.asterisk.org
Tue Jul 29 07:33:56 CDT 2014


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

Olle Johansson commented on ASTERISK-24132:
-------------------------------------------

Congratulations! You've hit the exact spot where I'm confused. We don't issue a hangup on the sip_read and down in the TLS read we have no idea of a channel to issue a hangup to.  So maybe sip_read could check the state of the invite and say "oops - read error during call setup on tcp or tls propably means we failed setting up the call". If the call is in UP state (or hold) this is not the case, as a new TCP/TLS connection can be set up for that. Now if a connection dies in the middle of an in-dialog transaction, like MESSAGE or re-invite, we're in trouble. The transaction fails, but the call does not.

This propably affects pjsip as well btw.

/O

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



More information about the asterisk-bugs mailing list