OpenSIPS
OpenSIPS 4.0 is in release-candidate testing, with two RCs a month apart.
A side-by-side editorial comparison of coturn and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.
coturn ships three minor versions in six weeks, packaged as Docker images on three registries.
The tracked feed for coturn, the open-source TURN/STUN server, is Docker image releases: 4.16.0, 4.17.0, 4.17.1, 4.17.2 and 4.18.0 between late July and early September 2026. Each is published to Docker Hub, GitHub Container Registry and Quay.io, and the release notes here point to the upstream changelog without listing changes.
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.
The tracked feed for coturn, the open-source TURN/STUN server, is Docker image releases: 4.16.0, 4.17.0, 4.17.1, 4.17.2 and 4.18.0 between late July and early September 2026. Each is published to Docker Hub, GitHub Container Registry and Quay.io, and the release notes here point to the upstream changelog without listing changes.
The cadence picked up: three minor versions (4.16, 4.17, 4.18) landed in about six weeks, with two same-day patch images for 4.17. The project keeps container packaging in lockstep with upstream releases, which matters to operators running TURN for WebRTC in containers.
A 4.18.x patch image or a 4.19.0 release is the likely next entry, following the observed roughly two-to-four-week rhythm; the feature content is not visible from these entries.
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 coturn or rtpengine.
OpenSIPS 4.0 is in release-candidate testing, with two RCs a month apart.
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 coturn alternatives → · See all rtpengine alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — webrtc — within Meetings. rtpengine is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 2.5), 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 coturn alternatives in Meetings are ranked by recent ship velocity. Browse the "coturn alternatives" section above for the current picks, or visit /alternatives/coturn 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.