Hi, Carsten,
On Wed, Apr 1, 2020 at 6:54 AM Carsten Bormann <cabo@xxxxxxx> wrote:
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.
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.
(Debugging and fixing Jitsi so it works reliably with both Firefox and Chrome would also help.)
Just so I understand, are you talking about
- something that needs to happen in RTCWeb, or
- something that needs to happen in network operations, or
- something that needs to happen in the Jitsi implementation itself?
If the answer is two or more of these, that's also good to know.
Best,
Spencer
Grüße, Carsten
> On 2020-03-22, at 06:45, Carsten Bormann <cabo@xxxxxxx> wrote:
>
> On 2020-03-21, at 16:54, Livingood, Jason <Jason_Livingood@xxxxxxxxxxx> 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
>
