[asterisk-users] Asterisk 13.15.0, webrtc, Google chrome 58 beta and "bad media description"
creslin at digium.com
Mon Apr 10 08:57:51 CDT 2017
On Sat, Apr 8, 2017 at 7:23 AM, Dan Jenkins <dan.jenkins88 at gmail.com> wrote:
> On Fri, Apr 7, 2017 at 9:44 PM, Teijo <g.aloitus at gmail.com> wrote:
>> I've been using webrtc (Jscommunicator) with Asterisk occasionally. Only
>> problem until now which remained was that if dtls_rekey was set to the
>> value other than 0, call hanged up when using chrome after the time where
>> dtls_rekey was set.
>> I suppose that "bad media description" shown in Chrome's window which
>> causes call to fail, has appeared with Chromes newer versions (currently 58
>> beta installed) or with Asterisk 13.15.0. Audio codec I'm using is Opus.
>> Has somebody else encountered this problem, or more better resolved it?
>> Best regards,
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>> Check out the new Asterisk community forum at:
>> New to Asterisk? Start here:
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
> Hi Teijo
> Take a read of https://nimblea.pe/monkey-business/2017/01/19/webrtc-
> asterisk-and-chrome-57/ :)
13.15.0 should address rtcp-mux issues.
If there are still issues outstanding, it might be worth reporting a bug on
Best wishes :-)
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asterisk-users