I’m not expert either, but the fact that it works for 2 people, makes me think it utilises the a P2P connection; the clients stream their audio and video directly to each other. This is a feature of Jitsi Meet to minimise the load of the server (I guess).
Read more about TURN (p2p):
I’m not sure what goes wrong for you, just wanted to point out the P2P feature.
Update: I found a possible place for the two lines, changed their values to the public url and the local ip of my jitsi server, and it worked with three people yesterday (plus a second connection from another browser tab on one machine).
@all: The correct place is $HOME/.jitsi-meet-cfg/jvb/sip-communicator.properties
Unfortunately, the problem still exits partially. After running for a couple of hours, the problem returns that with 3+ people, all remote video+audio goes black.
Restarting the server solves the problem until it returns after some time. Any ideas?
edit: 3+ people, not 2+ people
edit 2: Ah, it happens after I get a new IP from my ISP. So a workaround would be to restart the Jitsi server after that happens. But it is still an annoying effekt. So, any help with this would be appreciated.
Hi Windsurfer, thanks for your reply. The problem is directly connected to a changed WAN IP of my internet connection (see edit #2 in my last post) It doesn’t depend on the uptime of the server. If I start the server, it works. If I change my public IP right away by reconnecting my internet connection, the problem appears until I restart the server again. It doesn’t look like a memory problem to me, as it is directly connected to the IP change.
If I’m missing something, please feel free to elaborate.
I only found it in /etc/jitsi/videobridge/sip-communicator.properties and tried tinkering on this with no luck, so when I saw your reply I thought there was another sip-communicator.properties in a different directory.
Anyway, is it recommended to use the Docker version instead of the regular one?
I don’t know the exact differences, the Docker version was easier to install and worked from the start. I also tried the normal installation, but it required too many new packages to install for my taste, and didn’t even work on my Ubuntu Server 18.04 after that, so I removed it again and stayed with the Docker one.