But the VoIP/audio chat is using WebRTC, so Matrix is only the signalling server and the audio is p2p between the participants. As such the strain on the hosting server should be minimal
But the VoIP/audio chat is using WebRTC, so Matrix is only the signalling server and the audio is p2p between the participants. As such the strain on the hosting server should be minimal
Element (and some other clients, but I don't think it is part of the standard) also supports multi-user voice and video using Jitsi which works very well but you loose e2e encryption (although IIUC Jitsi has some experiments for this) and need to run it separately.
Setting up STUN and TURN is a real pain, though, if you run into any issues.
Actually, I'd suggest reading the entire document when you have time. For now, though, at least have a read of that section (it's short and sweet).
[0]: http://www.catb.org/~esr/faqs/smart-questions.html#beprecise
You won't be the first (nor the last, though if I can have the chance to improve that at some point I would love to) person to have struggled with it.