Comments on: How do you Upgrade Your WebRTC Media Servers?

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Mon, 21 Aug 2017 10:59:04 +0000

In reply to Warren McDonald. Yap. Every new browser that joins adds headaches until things settle down. Some time in 2018 we will be able to sit and analyze the current state of browsers and their WebRTC support, but at least until then things will stay dynamic and interesting.

By: Warren McDonald

Warren McDonald — Fri, 18 Aug 2017 23:36:29 +0000

I agree Tsahi, the movement in browser WebRTC behaviour impacts timing assumptions in the signalling stack, that can’t be taken for granted. This is amplified by high availability signalling architecture.

Interestingly, recent work on supporting Safari, shows how more browsers in the mix complicate the connection timing assumptions, leading to even more signalling upgrades.

By: Philipp Hancke

Philipp Hancke — Tue, 15 Aug 2017 14:07:19 +0000

In reply to Tsahi Levent-Levi.

signaling servers should be pass-through, unless you are a telco engineer… wait… brb 😉

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Tue, 15 Aug 2017 05:08:25 +0000

In reply to Silvia Pfeiffer.

Silvia,

You make a good point. That said, signaling is intertwined between what goes on in the signaling server and the client software running on the device (be it JS code or native on iOS or Android). What I’ve noticed is that any signaling server for WebRTC that hasn’t been updated in the last 12 months with either not work or malfunction in obvious scenarios – probably due to changes in browser behavior.

By: Silvia Pfeiffer

Silvia Pfeiffer — Tue, 15 Aug 2017 04:39:37 +0000

Hmm, browser upgrades and signaling should have nothing to do with each other, after all, signaling is not specified in WebRTC.