In our installation, we saw sometimes prosody considered some of the long gone clients still in the room. This is causing different issues. One of them being the room will never be freed, because some ghost clients are still considered in the room. As a result, if later another meeting is held in the same room, all the history text messages will be dumped to the newly joined participants.
Not sure if we config anything wrong. We were basically following the jitsi instructions. The only related setting we can think of is the bosh_max_inactivity, where we changed the default value 60 to 30. (Testing with the default value now, will report back.)
We’ve not found a reliable way to reproduce this. Seems like happening randomly. We tried to force kill a client or cut off network etc, and we do see the participant timeout after 30 seconds as we set.
We are using jitsi-meet 3548 on a Ubuntu 18.04 server. Prosody was installed together with jitsi-meet. The version is 0.10.0-1.
We have an old setup where we have jitsi-meet 3383 together with prosody 0.9.10-1. We don’t recall seeing similar issue on that server.
Any suggestion how can we solve this or how to nail down the issue? Thanks in advance!