I want to monitor (and keep open) several Jitsi rooms on our self-hosted server. To this end, I wrote a small website which joins some rooms (username Big Brother ) in separate iframes using the Jitsi Meet API. I can then poll the list of participants etc. using the API JS objects.
It works fine for 1 to 3 or 4 sessions. If I try to join more sessions at once, the browser drops out of one or more of them more or less regularly (trying to reconnect…, ping timeouts, …). When I open more than 6 sessions in Google Chrome, I see „Waiting for websocket“ – probably because Chrome is limited to 6 active connections at once (WTF Google???), so I switched to Firefox now. But here, the same problem occurs, even when I distribute the rooms over multiple tabs (didn’t try multiple firefoxes with different profiles yet).
I also want to switch off video receiving, but this should not be the problem, because the connection loss also happens when no one else is in the room, i.e. there is no video or audio stream transmitted.
To put it in a nutshell:
- Why is it so horribly unstable even if I join multiple empty meetings?
- Is there some way to use the API “headless”, i.e. join the meeting without receiving any data streams or rendering anything? (Btw.: Would it help to hide – display: none; – the iframes?)
- Is there a better way to extract participant information for certain rooms?