Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
A side-by-side editorial comparison of 3CX and PJSIP — release velocity, themes, recent moves, and the top alternatives to consider.
3CX is rebuilding around an AI Server, and it just handed the channel the AI edition to sell.
Recent releases split between the AI Server — sizing guidance, deployment updates, MCP and admin control in the V20 Update 10 alpha — and steady client work, most recently the V5.8 softphone beta with one-click SSO and outbound number choice. Packaging moved too: partner and distributor NFR subscriptions were replaced with the AI Edition.
A mature SIP stack turns its attention to concurrency correctness and AI voice endpoints
PJSIP remains the reference open-source SIP and media stack for embedded and mobile softphones, shipping roughly one feature release a year. Version 2.17 pairs asynchronous client authentication with a documented real-time AI speech connectivity path, alongside ten separate deadlock fixes. The cadence is slow, but each drop carries a backward-incompatibility section integrators have to read before upgrading.
Recent releases split between the AI Server — sizing guidance, deployment updates, MCP and admin control in the V20 Update 10 alpha — and steady client work, most recently the V5.8 softphone beta with one-click SSO and outbound number choice. Packaging moved too: partner and distributor NFR subscriptions were replaced with the AI Edition.
The AI Server is being treated as infrastructure customers deploy themselves rather than a hosted add-on, with hardware guidance, dedicated deployment tooling and an MCP endpoint for connecting assistants. Putting the AI Edition into partner hands and easing self-managed subscription changes both point at pushing that stack out through the channel rather than upselling it centrally.
Expect V20 Update 10 to move from alpha toward release with the AI Server management changes already previewed, and the V5.8 softphone beta to reach general availability.
PJSIP remains the reference open-source SIP and media stack for embedded and mobile softphones, shipping roughly one feature release a year. Version 2.17 pairs asynchronous client authentication with a documented real-time AI speech connectivity path, alongside ten separate deadlock fixes. The cadence is slow, but each drop carries a backward-incompatibility section integrators have to read before upgrading.
The arc from 2.14 to 2.17 moves away from platform and codec breadth — IPv6 dual stack, a Metal renderer, Lyra, a Schannel TLS backend — and toward the harder problem of concurrency inside the media core: async conference bridge operations, then parallel bridging, then async authentication and systematic deadlock elimination. AI speech connectivity in 2.17 is the first indication the project treats voice agents, not only human callers, as a target workload. The growing list of API breaks suggests the maintainers will trade source compatibility for cleaner threading semantics.
Expect the next release to widen the AI speech path with more transport and codec options while continuing to convert blocking media-core calls to asynchronous ones.
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 PJSIP.
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Homer's storage churn pauses long enough to ship a catalog backup CLI.
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Wowza keeps arguing its case for detection inside the streaming pipeline
Vimeo ships another batched product post: six changes to embeds and the player
Switcher Studio's feed is a livestreaming how-to blog, not a changelog
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 6.3 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. 3CX is currently shipping more aggressively (velocity 6.3 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 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 PJSIP alternatives in Meetings are ranked by recent ship velocity. Browse the "PJSIP alternatives" section above for the current picks, or visit /alternatives/pjsip for the full list with editorial commentary on each.