[asterisk-bugs] [JIRA] (ASTERISK-27826) res_rtp_asterisk: DTLS negotiation fails when it should succeed, causing SRTP failure

[Mikhail Ivanov (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-27826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Ivanov updated ASTERISK-27826:
--------------------------------------

    Attachment: bad_call.mp3
                good_call.mp3
                dump.pcap
                chrome-logs.txt

> res_rtp_asterisk: DTLS negotiation fails when it should succeed, causing SRTP failure
> -------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27826
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27826
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 15.3.0
>            Reporter: Mikhail Ivanov
>            Assignee: Abhay Gupta
>              Labels: fax, pjsip, webrtc
>         Attachments: 1205-5191-01.pcap, 1205-5191-02.pcap, app_install_list.txt, asterisk_config_log.txt, bad_call.mp3, chrome_bad_call_log.txt, chrome-logs.txt, config.log, dump, dump.pcap, fragment, good_call.mp3, installed.txt, res_srtp.txt, res_srtp.txt
>
>
> I have a problem with incoming (may be with outgoing too, not sure) calls to WebRTC clients (based on jssip.net library)
> Sometimes (2-5% of all incoming calls) I have no sound (on both sides) on incoming calls.
> RTP is going fine in both sides (local network)
> If I turn on mixMonitor on Asterisk, I can see only noise in call (looks like a problem with srtp keys, but not sure)
> https://www.dropbox.com/s/41nmwqhg0chcwl7/cf626000ac4601445d6cee3cd909188d.mp3?dl=1
> Asterisk 15.3.0, JsSIP 3.2.8, tested in Chrome, Chromium and Firefox
> If I turn off rtp encryption 
> webrtc = no 
> rtcp_mux = yes 
> use_avpf = yes 
> ice_support = yes 
> media_encryption = no
> and 
> --disable-webrtc-encryption in Chrome (Chromium)
> everything is fine, yes, it's workaround but not a solution



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