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 mediasoup and PJSIP — release velocity, themes, recent moves, and the top alternatives to consider.
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
The Rust line spent most of this window on single-PR point releases, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. That pattern broke with 0.26.0, a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when media was captured. 0.27.0 continues in the media path with a breaking change limiting simulcast and SVC to the preferred temporal layer. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison plus fixes for an OOB write and an SCTP integer overflow.
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.
The Rust line spent most of this window on single-PR point releases, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. That pattern broke with 0.26.0, a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when media was captured. 0.27.0 continues in the media path with a breaking change limiting simulcast and SVC to the preferred temporal layer. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison plus fixes for an OOB write and an SCTP integer overflow.
The subchannel thread that dominated July has gone quiet and the media path has taken over. First timing correctness — RemoteClockOffsetEstimator and RemoteCaptureTimeEstimator gave the worker a notion of remote capture instants it did not previously have — and now layer selection, with 0.27.0 constraining which temporal layer simulcast and SVC will actually deliver. Both are behavior changes in what an SFU sends downstream rather than additions to its API surface, and 0.27.0 is labelled breaking, so integrators are being asked to absorb them.
With two consecutive releases changing media-path behavior, the near-term releases are likely to be corrections shaking out the new timing and layer-selection paths across simulcast and pipe transports. The capture-time estimators remain unused beyond Sender Reports, which leaves them the obvious foundation for further synchronization work.
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 mediasoup 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.
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
Every manual control Mux ships now arrives with a Robots workflow that does it for you
See all mediasoup alternatives → · See all PJSIP alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mediasoup is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. mediasoup is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 mediasoup alternatives in Meetings are ranked by recent ship velocity. Browse the "mediasoup alternatives" section above for the current picks, or visit /alternatives/mediasoup 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.