[Home]

Summary:ASTERISK-24929: WebRTC Client No Audio after 60 seconds on Windows Only
Reporter:JoshE (n8ideas)Labels:
Date Opened:2015-04-01 02:27:19Date Closed:2015-04-02 19:10:08
Priority:CriticalRegression?
Status:Closed/CompleteComponents:
Versions:11.16.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Seen a strange set of behaviors with Chrome WebRTC clients on Windows OS only.  ChromeOS and OS X are unaffected.

After exactly one minute, Asterisk throws a:

[2015-03-31 23:25:47] WARNING[30439][C-00000002]: res_srtp.c:407 ast_srtp_unprotect: SRTP unprotect failed with: authentication failure 110

This is generally preceded by a handful of authentication failure 10s, but the call continues to pass audio normally:

[2015-03-31 23:25:45] WARNING[30439][C-00000002]: res_srtp.c:407 ast_srtp_unprotect: SRTP unprotect failed with: authentication failure 10

At the 60 second mark, when the 110 error occurs, all audio is lost.  I've tried this with 1.4.2 version of libsrtp, as well as the latest github code.  All produce exactly the same behavior.

Anyone else experienced this?
Comments:By: Rusty Newton (rnewton) 2015-04-02 09:55:31.524-0500

{quote}
Anyone else experienced this?
{quote}

This isn't a support forum. You should be asking this question on the forums or mailing lists...

In regards to this issue, please post steps to reproduce the issue and Asterisk debug logs along with SIP traces demonstrating the issue as usual.

By: JoshE (n8ideas) 2015-04-02 17:40:55.883-0500

Yeah Rusty-

Sorry about that.  Probably a bit inelegant in phrasing.  There is a larger bug here that we worked around, but it more appropriately belongs in another ticket.  We'll get that submitted separately.

In the meantime, for anyone experiencing that flow, an upgrade to Chrome 42, in beta as of today, will resolve this failure to decrypt audio.  It's quite likely a libsrtp 1.5 upgrade is required.

I would recommend closing this ticket out.