zlacker

Do you happen to know of others by any chance. For self-hosted video call solutions, looks like Jitsi and BigBlueButton (BBB) are the only decent options out there.

>>samspe+(OP)
There's now also https://github.com/vector-im/element-call.

They have SFU support as of recently, so it should scale similarly to Jitsi et al.

>>samspe+(OP)
QOS (Quality-of-Service) rules might starve your traffic of bandwidth. Are you sure you have perfect "Net Neutrality" on your side?

You would be well advised to use services where the traffic travels through https on port 443 on the server (because it's been my experience that it tends to get pretty good QOS favorability). My own little rule of thumb: "you can connect to any port you want, so long as it's port 443 https." ;)

>>esbeeb+oy
On the other hand, tls/443 is pretty undesirable for media delivery in videoconferencing because a) it's tcp-based and the required ACKs mean a big reduction in throughput and increase in latency, especially in the presence of packet loss, and b) most video services these days (and open source servers) use webrtc which encrypts the data in transit already--so the tls encryption is a waste of resources

Though tls/443 is usually still supported because it's most often allowed by even restrictive firewalls and networks

>>samspe+(OP)
> Do you happen to know of others by any chance.

There's Galene, <https://galene.org>. It's easy to deploy, uses minimal server resources, and the server is pretty solid. The client interface is still a little awkward, though. (Full disclosure, I'm the main author.)