for compliance reasons we have use cases where we cannot send audio/video through JVB. Problem is that somewhat simplified it seems like JITSI has 3 levels of defense to get video working (when configured for p2p)?
1: p2p directly
2: if network conditions are not working for p2p directly use TURN
3: When devices don’t support 1&2 (all ios browsers, firefox, etc) + other cases we have yet to fully understand use JVB.
In order to be compliant we simply turned off JVB which makes 1&2 work in most cases. For some VPN:s video does not work though. Is turning off JVB a pragmatic way to ensure video/audio is only using 1&2 (like it works in cases X,Y but have known issues with Z)? Is there another way of achieving it (config, code) that does not force us to turn off JVB?
If you are not going to use the JVB then I think Jitsi is not the right tool for you.
Jitsi Meet requires the JVB to function. The only case in which you can get away without it is with 2 participants in p2p mode. The moment a 3rd one joins, or one of the participants disconnects and tries to reconnect (there will be 3 participants momentarily) you need the JVB.
Thanks for the info. Our use case when JVB is disabled is only 1 to 1 calls. Could you please clarify if JITSI without JVB would also get away with 1 to 1 calls via turn?
Yes and no. Yes, you can get away without using it, proven a TURN server is provisioned, but a JVB must be there or you’ll get an error saying there are no bridges available.
That said, using Jitsi Meet just for 1-1 calls like that is overkill IMHO. You could build something much simpler than this.
Also, as I said, your experience will be bad if one of the participants drops and re-connects, since you’ll have > 2 participants for a bit.