coturn
coturn ships three minor versions in six weeks, packaged as Docker images on three registries.
Comparison · Meetings
Element Call vs rtpengine
A side-by-side editorial comparison of Element Call and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:webrtc
Element Call vs rtpengine: at a glance
What is Element Call?
Element Call drops MatrixRTC legacy mode entirely, betting the entire call stack on the multi-SFU protocol.
Element Call is deep into a protocol transition: MatrixRTC legacy mode was removed in v0.25.0-rc.1, and .well-known transport discovery was removed in v0.24.0-rc.1. Both had been optional for months before the forced cutover. The current v0.26.x RC cycle is stabilizing the post-legacy stack with bug fixes to audio output selection, memberId handling in MatrixRTC mode, and leave timing adjustments when SFU delegation is active. The product ships exclusively as release candidates at this stage, signaling it's in final pre-release hardening.
What is rtpengine?
rtpengine backports the same DTLS and socket fixes across four maintenance branches at once.
Sipwise's rtpengine media proxy is maintaining several release lines in parallel (mr13.5, mr14.1, mr26.0, mr26.1, mr26.2), and most recent entries are coordinated backports. The September 16 batch fixes hash-table updates, nested string lookups and stop_forwarding mixups across four branches, and adds DTLS negotiation corrections (setup=actpass logic, ignoring incorrect DTLS=passive, keeping TLS IDs on answer role changes) to the mr26.0 and mr26.1 lines.
Element Call vs rtpengine: editorial side-by-side
Element Call
6.3MEETINGS
Element Call drops MatrixRTC legacy mode entirely, betting the entire call stack on the multi-SFU protocol.
◆ Current state
Element Call is deep into a protocol transition: MatrixRTC legacy mode was removed in v0.25.0-rc.1, and .well-known transport discovery was removed in v0.24.0-rc.1. Both had been optional for months before the forced cutover. The current v0.26.x RC cycle is stabilizing the post-legacy stack with bug fixes to audio output selection, memberId handling in MatrixRTC mode, and leave timing adjustments when SFU delegation is active. The product ships exclusively as release candidates at this stage, signaling it's in final pre-release hardening.
◆ Where it's heading
Having removed both legacy transport paths, Element Call is fully committed to a multi-SFU architecture where each homeserver operator runs their own SFU and participants connect to whichever SFUs host the streams they need. The ongoing RC cycle and the LiveKit logging improvements in v0.26.0-rc.1 point to a push for call-quality diagnostics before a stable release. Mobile performance has been a consistent focus across v0.22–v0.26 — landscape layouts, PiP mode, voice-only call handling — pointing to mobile as a priority segment.
◆ Prediction
A stable v0.26.0 release is imminent given the RC cadence. The delegated leave timing breaking change in v0.26.0-rc.2 is unfinished infrastructure for SFU delegation — that work will likely define the next development cycle.
rtpengine
5.0MEETINGS
rtpengine backports the same DTLS and socket fixes across four maintenance branches at once.
◆ Current state
Sipwise's rtpengine media proxy is maintaining several release lines in parallel (mr13.5, mr14.1, mr26.0, mr26.1, mr26.2), and most recent entries are coordinated backports. The September 16 batch fixes hash-table updates, nested string lookups and stop_forwarding mixups across four branches, and adds DTLS negotiation corrections (setup=actpass logic, ignoring incorrect DTLS=passive, keeping TLS IDs on answer role changes) to the mr26.0 and mr26.1 lines.
◆ Where it's heading
The work is focused on correctness in media negotiation, especially DTLS role handling and ICE on closed sockets, rather than new features. The newest branch, mr26.2, also brought AMR fmtp defaults, mirroring of generated RTCP sender reports to Homer, and recording cleanup hardening, which points to better interop and observability for carrier deployments.
◆ Prediction
More synchronized backport releases across the mr13.5 through mr26.2 lines are the clear pattern; feature work will most likely keep landing on mr26.2 first.
Alternatives to Element Call and rtpengine
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.
OpenSIPS
OpenSIPS 4.0 is in release-candidate testing, with two RCs a month apart.
Kamailio
Kamailio's tracked feed shows one thing: a quiet, schema-stable 5.8 maintenance release.
JW Player
JW Player is rebuilding its VOD pipeline around CMAF, one workflow fix at a time
Restream
Restream's webinars get a registration page and a CSV of leads, turning broadcasts into a pipeline
BigBlueButton
BigBlueButton 4.0 rc.4 is a security-only release as the LiveKit stack hardens.
See all Element Call alternatives → · See all rtpengine alternatives →
Recent activity from Element Call and rtpengine
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoElement Callv0.26.1-rc.1
- 16d agortpenginertpengine mr13.5.1.27: mux-offer fix when required
- 17d agortpenginertpengine mr26.0.1.23: DTLS negotiation and forwarding fixes
- 17d agortpenginertpengine mr13.5.1.26: forwarding and socket bug fixes
- 17d agortpenginertpengine mr26.2.1.2: core lookup and forwarding fixes
- 17d agortpenginertpengine mr26.1.1.11: DTLS negotiation and forwarding fixes
- 24d agoElement Callv0.26.0-rc.2
- 26d agoElement Callv0.26.0-rc.1
- 1mo agoElement CallMatrixRTC legacy mode removed — all calls now run on the new protocol ⚡
- 1mo agortpenginertpengine mr26.2.1.1: Homer RTCP mirroring, AMR defaults, recording fixes
- 1mo agoElement Callv0.24.0-rc.1
- 2mo agoElement Callv0.23.0-rc.1
Frequently asked questions
What is the difference between Element Call and rtpengine?
Both compete on the same themes — webrtc — within Meetings. Element Call is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Element Call better than rtpengine?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Element Call is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
What are the best alternatives to Element Call?
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.
What are the best alternatives to rtpengine?
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.