Comments on: What’s up with WebRTC Video as a Service in 2017 https://bloggeek.me/webrtc-vaas-2017/ The leading authority on WebRTC Sat, 28 Dec 2019 15:14:29 +0000 hourly 1 By: Tsahi Levent-Levi https://bloggeek.me/webrtc-vaas-2017/#comment-118752 Tue, 14 Mar 2017 04:47:52 +0000 https://bloggeek.me/?p=11262#comment-118752 In reply to A.

Thanks for the shoutout.

Do notice that this article is about video as a service. The mention in the end is of frameworks you can use to build and deploy your own and it is by no means exhaustive – even the list of CPaaS vendors supporting video isn’t exhaustive.

]]>
By: A https://bloggeek.me/webrtc-vaas-2017/#comment-118751 Tue, 14 Mar 2017 04:41:57 +0000 https://bloggeek.me/?p=11262#comment-118751 You forgot Janus.
https://janus.conf.meetecho.com

]]>
By: Tsahi Levent-Levi https://bloggeek.me/webrtc-vaas-2017/#comment-118750 Mon, 13 Mar 2017 20:08:45 +0000 https://bloggeek.me/?p=11262#comment-118750 In reply to Anton Venema.

Anton, thanks for sharing.

]]>
By: Tsahi Levent-Levi https://bloggeek.me/webrtc-vaas-2017/#comment-118749 Mon, 13 Mar 2017 20:07:50 +0000 https://bloggeek.me/?p=11262#comment-118749 In reply to Lawrence Byrd.

Lawrence – thanks for the clarification. SIP interconnect is probably the next-best-thing to real PSTN connectivity with all of its “richness”. Most vendors I’ve seen who end up using TokBox, do so for its video capabilities and not for its PSTN connectivity.

Oftentimes, I’ve noticed vendors who would look elsewhere because “they need to connect a phone into a video conference”. That being the case, I suggest beefing up the documentation in that specific area.

]]>
By: Anton Venema https://bloggeek.me/webrtc-vaas-2017/#comment-118748 Mon, 13 Mar 2017 18:32:54 +0000 https://bloggeek.me/?p=11262#comment-118748 Thanks for the mention, Tsahi. LiveSwitch is currently slated for release in June, so there will be a lot more information coming in the next few months. It is a bit unique in that it operates as a licensed SFU/MCU hybrid product, where clients can connect in as either forwarded or mixed participants. The server manages the bridging/scaling internally, so you can simply connect as whatever makes sense for the endpoint capabilities. The connections are all client-driven, so a participant can switch their mode at any time. True to WebRTC spirit, it is also signalling agnostic, so the included gateway can be extended to support third-party signalling systems as well as VoIP, PSTN, and CDN. Anyone looking for more information as it becomes available can simply sign up to our newsletter at http://www.frozenmountain.com.

]]>
By: Lawrence Byrd https://bloggeek.me/webrtc-vaas-2017/#comment-118747 Mon, 13 Mar 2017 15:35:35 +0000 https://bloggeek.me/?p=11262#comment-118747 Thanks for your comments, Tsahi. To integrate with legacy environments, TokBox provides SIP Interconnect from WebRTC-based video sessions in the TokBox cloud to traditional telephony and unified communications systems. Read more on our website. But you are right that TokBox is completely focused on Internet video (backed up by good audio, messaging, screen sharing, broadcasting, distributed SFU, cloud-level control etc etc) and not on selling PTSN functionality that can be found elsewhere. Focus is good :).

]]>