The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Signal-Calling-Service Alternatives
Similar projects and alternatives to Signal-Calling-Service
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
pyrite
Discontinued Pyrite is a web(RTC) client & management interface for Galène SFU
-
Jitsi Video Bridge
Jitsi Videobridge is a WebRTC compatible video router or SFU that lets build highly scalable video conferencing infrastructure (i.e., up to hundreds of conferences per server).
-
-
azure-ubuntu-jitsi
A private Jitsi videoconferencing set up on Azure
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
glommio
Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.
-
nntp-rs
NNTP server implementation in Rust. Diablo dhistory / spool compatible. WORK IN PROGRESS.
Signal-Calling-Service reviews and mentions
-
Is async runtime (Tokio) overhead significant for a "real-time" video stream server?
I am npt sure if this is related but Signal built Signal Calling Service and according to them it worked great.
-
Pyrite – open-source video conferencing
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.
-
An Introduction to WebRTC Simulcast
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...
-
A note from our sponsor - WorkOS
workos.com | 28 Mar 2024
Stats
signalapp/Signal-Calling-Service is an open source project licensed under GNU Affero General Public License v3.0 which is an OSI approved license.
The primary programming language of Signal-Calling-Service is Rust.