coturn
coturn ships three minor versions in six weeks, packaged as Docker images on three registries.
A side-by-side editorial comparison of OpenSIPS and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.
OpenSIPS 4.0 is in release-candidate testing, with two RCs a month apart.
OpenSIPS, the open-source SIP proxy and server, has two tracked entries: 4.0.0-rc1 in May and 4.0.0-rc2 in June 2026. Both release notes are one-line announcements, so the specific 4.0 changes are not visible in the feed.
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.
OpenSIPS, the open-source SIP proxy and server, has two tracked entries: 4.0.0-rc1 in May and 4.0.0-rc2 in June 2026. Both release notes are one-line announcements, so the specific 4.0 changes are not visible in the feed.
The product is moving toward a 4.0 major release through a standard RC cycle. A second RC a month after the first suggests stabilization work rather than new scope, but the entries do not say what 4.0 changes.
A 4.0.0 general release is the next expected step; what it contains cannot be read from these announcements.
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.
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.
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.
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 OpenSIPS or rtpengine.
coturn ships three minor versions in six weeks, packaged as Docker images on three registries.
Kamailio's tracked feed shows one thing: a quiet, schema-stable 5.8 maintenance release.
JW Player is rebuilding its VOD pipeline around CMAF, one workflow fix at a time
Restream's webinars get a registration page and a CSV of leads, turning broadcasts into a pipeline
BigBlueButton 4.0 rc.4 is a security-only release as the LiveKit stack hardens.
Fourwaves is polishing participant messaging after a pricing reset.
See all OpenSIPS alternatives → · See all rtpengine alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — sip, voip — within Meetings. rtpengine is currently shipping more aggressively (velocity 5.0 vs 0.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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rtpengine is currently shipping more aggressively (velocity 5.0 vs 0.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.
Top OpenSIPS alternatives in Meetings are ranked by recent ship velocity. Browse the "OpenSIPS alternatives" section above for the current picks, or visit /alternatives/opensips 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.