Re: Off-topic: making WebRTC work in practice (Re: a brief pondering)

[Philipp Hancke <[e-mail]>]

hey Carsten,

Am 01.04.20 um 13:53 schrieb Carsten Bormann:
> In the university, a lot of WebRTC is using Jitsi as a tool.
> This works mostly well, with occasional surprises.
> What we could use now is a better way to diagnose these surprises.

https://test.webrtc.org/ (opensource but mostly abandoned) might help or 
https://network-test.testrtc.com/ (commercial)
chrome://webrtc-internals or firefox about:webrtc are useful but require 
you to be an expert.

> This requires WebRTC knowledge that our IT people don’t have.
> A WebRTC troubleshooting guide that I could point them to would be most helpful

https://support.google.com/a/users/answer/7380413
is pretty good. Some of it is specific to Google meet but there is quite 
some general advice.

> (Debugging and fixing Jitsi so it works reliably with both Firefox and Chrome would also help.)
> Grüße, Carsten
> 
> 
>> On 2020-03-22, at 06:45, Carsten Bormann <[e-mail]> wrote:
>>
>> On 2020-03-21, at 16:54, Livingood, Jason <[e-mail]> wrote:
>>>
>>> what can this community (and similar/adjacent ones) do productively together to help
>>
>> The one thing that would be most useful for me right now would be a document with operational considerations for keeping WebRTC running (e.g., How not to mess it up with your firewall).
>>
>> Grüße, Carsten
>>
>