Fourwaves
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
A side-by-side editorial comparison of Element Call and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.
Element Call starts moving to new LiveKit transports and falls back to remote SFUs when needed.
Element Call ships a release candidate roughly every two to three weeks. v0.28.1-rc.1 adds a breaking change that falls back to publishing media on a remote SFU when possible, supports migrating to new LiveKit transport types and endpoints, and fixes room v12 power-level compatibility. It also brings in a MatrixRTC SDK and patches several dependency security advisories. The previous rc added a quick audio menu and redacted analytics IDs from rageshakes.
rtpengine opens the mr26.3 branch with a rollback message and leaner call state.
Sipwise's rtpengine media proxy opened a new mr26.3 branch on October 19. Its first build, mr26.3.1.1, carries everything from mr26.2.1.5 plus a rollback NG control message, relaxed loop detection for duplicate packets arriving over a second apart or from endpoints no longer local, ICE agent teardown when a peer drops ICE, inject-audio mixing fixes, and a long run of "lightweight string" refactors across call IDs, tags, SDP and recording fields. Three days earlier, a hardening batch went to four branches, followed by compile-fix releases.
Element Call ships a release candidate roughly every two to three weeks. v0.28.1-rc.1 adds a breaking change that falls back to publishing media on a remote SFU when possible, supports migrating to new LiveKit transport types and endpoints, and fixes room v12 power-level compatibility. It also brings in a MatrixRTC SDK and patches several dependency security advisories. The previous rc added a quick audio menu and redacted analytics IDs from rageshakes.
With the MatrixRTC protocol cutover finished in August, the team is now working on the media transport layer itself: how calls find and publish to SFUs and how LiveKit endpoints change underneath them. Packaging the RTC logic as an SDK suggests it is meant to be reused beyond the Element Call app.
Expect a 0.28.1 final and follow-ups to the LiveKit transport migration; whether the MatrixRTC SDK gets its own release isn't clear from the entries.
Sipwise's rtpengine media proxy opened a new mr26.3 branch on October 19. Its first build, mr26.3.1.1, carries everything from mr26.2.1.5 plus a rollback NG control message, relaxed loop detection for duplicate packets arriving over a second apart or from endpoints no longer local, ICE agent teardown when a peer drops ICE, inject-audio mixing fixes, and a long run of "lightweight string" refactors across call IDs, tags, SDP and recording fields. Three days earlier, a hardening batch went to four branches, followed by compile-fix releases.
Development continues on two levels: correctness fixes backported across every supported branch, and newer work, such as the rollback message and memory-lighter call state, landing on the newest line. Opening mr26.3 adds a fifth maintained branch, so the backport load grows.
Expect mr26.3.1.x point builds and continued synchronized backports to mr12.5 through mr26.2. The entries don't show when older branches stop receiving fixes.
Other Meetings products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Element Call or rtpengine.
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
HOMER 11.0.369 fixes S3 auth on Ceph-based storage and stops compaction memory growth.
JW Player moves CMAF VOD into the dashboard, adds AV1, and opens Broadcast Live to audio-only feeds.
Nextcloud Talk Desktop 2.3.3 adds accessibility options and bundles Talk v25.0.6.
Nextcloud Talk patches v22 and v23 while v25 stable sits five weeks past its last RC.
Kamailio's feed shows quiet, migration-free upkeep across two stable branches.
See all Element Call alternatives → · See all rtpengine alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — webrtc — within Meetings. Element Call and rtpengine are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Element Call and rtpengine are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
Top Element Call alternatives in Meetings are ranked by recent ship velocity. Browse the "Element Call alternatives" section above for the current picks, or visit /alternatives/element-call for the full list with editorial commentary on each.
Top rtpengine alternatives in Meetings are ranked by recent ship velocity. Browse the "rtpengine alternatives" section above for the current picks, or visit /alternatives/rtpengine for the full list with editorial commentary on each.