Recently, we enabled Jitsi Video conferencing option on RocketChat for private channels. The issue is the conference session is not timing out or the same session is using on future calls even after 5+ hours. Is there any way to set the Jitsi session timeout in RocketChat to avoid the same session being using for all calls? If yes, that would be much helpful.
I have started a video conference call on a private channel, and all online staff got alert about the call.
Closed the call session after 15 minutes of meeting
Later after 5+ hours, I started one more video call in the same channel but no alert came in users end and they had to click on the same old Join button to get into the conference call.
I then asked one of the other staff to start a conference call, and when he did no one get the alert and had to use the same old Join button to get into the conference he started.
This isn’t suitable for a production state. I guess the old conference session is not getting timeout even after closing off the call. I probably would be missing some thing, or it could be a bug.
Any help would be much appreciated!
- Version of Rocket.Chat Server: 2.4.0
- Operating System: CentOS 7
- Deployment Method: rocketchatctl
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled
- NodeJS Version: v8.17.0
- MongoDB Version: 4.0.17
- Proxy: No
- Firewalls involved: CSF, but no issues with it.