Comments on: WebRTC FAQ: The 2018 Version https://bloggeek.me/webrtc-faq-2018/ The leading authority on WebRTC Wed, 05 Feb 2020 13:07:38 +0000 hourly 1 By: Tsahi Levent-Levi https://bloggeek.me/webrtc-faq-2018/#comment-119257 Tue, 25 Sep 2018 17:55:04 +0000 https://bloggeek.me/?p=12677#comment-119257 In reply to Bob.

Bob, I don’t know one directly, but I don’t think there’s technical issue in adding it.

]]> By: Tsahi Levent-Levi https://bloggeek.me/webrtc-faq-2018/#comment-119256 Tue, 25 Sep 2018 17:54:29 +0000 https://bloggeek.me/?p=12677#comment-119256 In reply to Michael Graves.

Thanks for sharing this Michael

]]> By: Michael Graves https://bloggeek.me/webrtc-faq-2018/#comment-119255 Tue, 25 Sep 2018 15:55:28 +0000 https://bloggeek.me/?p=12677#comment-119255 As a practical matter, the G.722 audio codec is supported in Chrome and Firefox. This provides a happy middle ground for integration of IP telephony and WebRTC without resorting to (ugh!) G.711.

We make use of this every day, allowing WebRTC interaction with ZipDX, which was the world’s first HDVoice conference service.

]]> By: Bob https://bloggeek.me/webrtc-faq-2018/#comment-119254 Mon, 24 Sep 2018 21:35:06 +0000 https://bloggeek.me/?p=12677#comment-119254 Do you know of any way to use webrtc through an ionic ios app? I haven’t found any solution and assume it isn’t possible without using a 3rd party provider.

]]> By: Tsahi Levent-Levi https://bloggeek.me/webrtc-faq-2018/#comment-119253 Sun, 23 Sep 2018 18:31:24 +0000 https://bloggeek.me/?p=12677#comment-119253 In reply to Ed Unverricht.

Peer to peer connections with Safari works well. Not easy, but doable. Video will need to be H.264 with Safari.

And broadcasting to Safari from Chrome (directly, or via a media server) is possible as well.

]]> By: Ed Unverricht https://bloggeek.me/webrtc-faq-2018/#comment-119252 Sun, 23 Sep 2018 17:13:54 +0000 https://bloggeek.me/?p=12677#comment-119252 I understand that peer to peer connection does not work with Safari, but if I have Chrome on my end, can I setup a one-way connection? To clarify, the person with Chrome would be in effect broadcasting and the person with Safari would not even be asked to use his audio or video.

]]> By: Tsahi Levent-Levi https://bloggeek.me/webrtc-faq-2018/#comment-119251 Mon, 17 Sep 2018 14:34:27 +0000 https://bloggeek.me/?p=12677#comment-119251 I’d say that is a reply that is suitable for 100% of all services running on the web inside browsers. If the developers who put up the service you use didn’t secure it, then it isn’t secure.

Now sure how what you’re saying is any different than a man in the middle attack in front of a bank website, airline service or any text chat service.

]]> By: Lennart Grahl https://bloggeek.me/webrtc-faq-2018/#comment-119250 Mon, 17 Sep 2018 13:35:06 +0000 https://bloggeek.me/?p=12677#comment-119250 “Is WebRTC posing a security threat for me?”

Yes, if your signalling solution is not end-to-end encrypted, man in the middle attacks are easily doable. IMHO an underrated attack surface.

]]>