coturn
coturn ships three minor versions in six weeks, packaged as Docker images on three registries.
A side-by-side editorial comparison of 3CX and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.
3CX is opening the PBX to agents while its feed fills with awards and academy news
3CX is a self-hosted business phone system, and its feed mixes real releases with marketing. The releases have been solid and specific: an MCP server for managing the PBX from an AI client, a choice of SendGrid or Zoho for system email, department-level music on hold. Around them sit a G2 badge announcement, an academy launch and a walkthrough for adding a customer service AI agent to an existing setup.
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.
3CX is a self-hosted business phone system, and its feed mixes real releases with marketing. The releases have been solid and specific: an MCP server for managing the PBX from an AI client, a choice of SendGrid or Zoho for system email, department-level music on hold. Around them sit a G2 badge announcement, an academy launch and a walkthrough for adding a customer service AI agent to an existing setup.
The AI thread is the one with direction. An MCP server for the PBX makes administration something an assistant performs rather than a console task, and the customer-service agent guide extends the same idea to the call path itself. The rest is steady administrative polish — email provider choice, per-department hold music — which is what a self-hosted product ships between larger moves. The award and academy posts carry no product content and should not be read as cadence.
With an MCP server for administration and a documented path for a customer service agent, the obvious gap is the two meeting — call handling driven by the same MCP surface rather than a separately configured agent.
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 3CX or rtpengine.
coturn ships three minor versions in six weeks, packaged as Docker images on three registries.
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.
See all 3CX alternatives → · See all rtpengine alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — voip — within Meetings. 3CX is currently shipping more aggressively (velocity 7.5 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. 3CX is currently shipping more aggressively (velocity 7.5 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.
Top 3CX alternatives in Meetings are ranked by recent ship velocity. Browse the "3CX alternatives" section above for the current picks, or visit /alternatives/3cx 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.