Re: [asterisk-users] Webrtc and iOS devices

Hello, I upgraded to 16.9.0 and then 16.10.0. I feel that there is something in iOS webrtc implementation which cause issues. If womebody has succeeded with combination iOS, browser (like Safari) and webrtc (conference call), it would be nice to hear. Best regards, Teijo Dan Jenkins

Re: [asterisk-users] Webrtc and iOS devices

Hello, Currently audio conference. Should upgrading Asterisk from 13 to newer version resolve webrtc/iOS problem? Best regards, Teijo Dan Jenkins kirjoitti 28.4.2020 klo 12.18: First things first, upgrade from 13 - WebRTC has moved a long a lot since then. If you can't up

[asterisk-users] Webrtc and iOS devices

from Windows seem to work. Best regards, Teijo -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Check out the new Asterisk community forum at: https://community.asterisk.org/ New to Asterisk? Start

[asterisk-users] Webrtc and iOS 11

more exact information? Best regards, Teijo -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Check out the new Asterisk community forum at: https://community.asterisk.org/ New to Asterisk?

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: O

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 dtls_rekey was s

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

ion" 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

[asterisk-users] dtls_rekey

_cipher=HIGH:!SSLv3 If I do not set dtls_rekey which afaik means no rekeying, the problem does not occur. I have also tested with Firefox 50 A2 32-bit, and setting dtls_rekey=60 is not a problem with it. Both browsers were Windows versions. Has somebody encountered th

Re: [asterisk-users] Asterisk 13.10.0 Now Available

ipher=ALL:!SSLv3 or dtls_cipher=HIGH:!SSLv3 Thank you! Best, Teijo -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs:

Re: [asterisk-users] dtls_cipher

Hello, After updating OpenSSL packages from version 1.0.1f to 1.0.2h I can get audio also with Chrome when setting dtls_cipher=ALL. Why dtls_cipher=ALL:!SSLv3 does not work? Best, Teijo 9.7.2016, 18:37, Teijo kirjoitti: Hello, I'm using Asterisk 13.9.1 (compiled from sourc

[asterisk-users] dtls_cipher

the moment I have no idea what to try next. Best, Teijo -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://ww