I have an existing installation of Jitsi/jicofo/prosody server on a ubuntu as stun integration with rocket.chat. It is pretty fresh (#pandemic). It is being used for team work from home.
Users in videoconferencing are experiencing problems:
What they see is - users get often kicked out from their video conference room, their presence remains visible as “ghost” guest window. As long as they were not the Owner of the conference - that is not a big problem, as the existing Owner can kick out those ghost guests. The real problem happens when the conference owner gets kicked-out and becomes a ghost-guest. He or she can rejoin, but after rejoining they have normal member status and cannot clean up the mess anymore.
Also let’s suppose that the conference finishes and the same bunch of people starts conference on the second day (team work scenario) they are given the same video conference room/session - with the same expired ghost-guests presences that noone is able to clean up . So after 3 days their conference experience is full of 2/3 of ghost guests.
I am trying to figure out how those vide conferencing sessions are governed, recycled and with use of only 3 logs:
/var/log/jitsi/jvb.log /var/log/jitsi/jicofo.log /var/log/prosody/prosody.log
There are no errors whatsoever, I see entries about “Owner has left the room” in the jicofo.log and the same room id being reused some time later. But how do I finetune this behaviour, what can I do here to help, is there any admin friendly documentation that I can lean upon?
I am nowhere near providing the solution. I am not a java developer. Can someone point me in the right direction ? How to reconfigure or debug the problem.