Signal-Calling-Service VS azure-ubuntu-jitsi

I am npt sure if this is related but Signal built Signal Calling Service and according to them it worked great.

I was curious and looked through the code of Galene briefly and found the following, which may answer your question. For context, I am familiar with the Jitsi code and have written my own calling server (and written about it: https://signal.org/blog/how-to-build-encrypted-group-calls/).

Galene appears to be less mature than Jitsi. For example, it uses REMB feedback messages from the client to calculate allowable bitrates rather than calculating the bitrates itself (as Jitsi and Signal's SFU do). Worse, it appears that what it does with that information is erroneous. I could be wrong, but it looks like the bitrate allocation code (see https://github.com/jech/galene/blob/e8fbfcb9ba532f733405b1c5...) only allocates the bitrate for one of the video streams, not all of them. Perhaps the author did not realize that there is one REMB sent back for all the video streams by WebRTC rather than one per stream (see, for example, here: https://source.chromium.org/chromium/chromium/src/+/main:thi...). Further, I find the spatial layer switching code to be strange. For examples, it doesn't go down a layer unless it's 150% over the estimated allowable bitrate, which gives a lot of opportunity for inducing latency.

In short, I think Galene has a ways to go before it works as well as Jitsi (Videobridge), and thus Pyrite group calls are unlikely to work as well as Jitsi group calls (for 1:1 calls, I don't know; I didn't look into that).

Oh, and just a reminder, the SFU we use for Signal group calls is also open source: https://github.com/signalapp/Signal-Calling-Service.

And yeah, it uses Signal-Calling-Service written on Rust.

That's a well written article covering the basics of simulcast.

If you're interested in seeing an implementation of an SFU doing simulcast forwarding written in Rust, we (at Signal) recently open sourced our SFU:

https://github.com/signalapp/Signal-Calling-Service/blob/mai...

Yep. Ran one during most of the pandemic: https://github.com/rcarmo/azure-ubuntu-jitsi

I have been running Jitsi Meet (https://meet.jit.si/) for a little over a year[1] for a group of friends to do their monthly meetings during the COVID times, and tried this out a little while ago.

I liked it, but there is still a fair amount of assemby required, and I hope they get it to the point where (like Jitsi) everything is a docker-compose away.

[1]: https://github.com/rcarmo/azure-ubuntu-jitsi - all my tweaks, ready to deploy

The most interesting thing for me is actually the galene server, but playing around with the demo server and looking at the documentation it seems to be a fair bit behind Jitsi in ease of use and deployment.

(I built a one-shot template to deploy and run Jitsi on Azure - https://github.com/rcarmo/azure-ubuntu-jitsi - and it's been trivial to maintain over the past two years, for a small group of friends and monthly "open sessions")

I'm not enamored of the Pyrite UI (again, Jitsi seems simpler), but I'll keep an eye on both.