Re: [asterisk-users] Asterisk 13.15.0, webrtc, Google chrome 58 beta and "bad media description"

Hello, Yes. When I today understood to set rtcp_mux=yes, at least Chrome (60.0 beta) worked (quickly tested) as expected. I'm sure that some day dtls_rekey can be set to the other value than 0 as well with Chrome. Best regards, Teijo 10.4.2017, 16.57, Matt Fredrickson kirjoitti: On

Re: [asterisk-users] Asterisk 13.15.0, webrtc, Google chrome 58 beta and "bad media description"

On Sat, Apr 8, 2017 at 7:23 AM, Dan Jenkins wrote: > > On Fri, Apr 7, 2017 at 9:44 PM, Teijo wrote: > >> Hello, >> >> I've been using webrtc (Jscommunicator) with Asterisk occasionally. Only >> problem until now which remained was that if dtls_rekey

Re: [asterisk-users] Asterisk 13.15.0, webrtc, Google chrome 58 beta and "bad media description"

Thank you Dan for this information. Best regards, Teijo 8.4.2017, 15:23, Dan Jenkins kirjoitti: On Fri, Apr 7, 2017 at 9:44 PM, Teijo wrote: Hello, I've been using webrtc (Jscommunicator) with Asterisk occasionally. Only problem until now which remained was that if

Re: [asterisk-users] Asterisk 13.15.0, webrtc, Google chrome 58 beta and "bad media description"

On Fri, Apr 7, 2017 at 9:44 PM, Teijo wrote: > Hello, > > 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

[asterisk-users] Asterisk 13.15.0, webrtc, Google chrome 58 beta and "bad media description"

Hello, 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