FreeSWITCH
After twenty-one months of silence, FreeSWITCH 1.11 deleted thirty legacy modules and moved on
A side-by-side editorial comparison of SRS and FusionPBX — release velocity, themes, recent moves, and the top alternatives to consider.
SRS 6.0 went stable by making H.265 work everywhere, not just in one protocol.
SRS shipped 6.0 release 0 in December 2025, promoting the 6.0 line to stable in place of 5.0 at roughly 170,000 lines of code. The headline is H.265/HEVC carried across RTMP, HTTP-FLV, HLS, HTTP-TS and SRT, with DVR recording to both MP4 and FLV. WebRTC gained WHEP for playback, stereo Opus over SDP and a configurable AAC-to-Opus bitrate; SRT moved to libsrt 1.5.3 with round-trip latency reported down to 200ms.
The release feed stops in 2018, so nothing here describes the current product
Every visible entry predates 2019. The newest is 4.4.1, a minor bug-fix release covering call centre login, device password propagation and call detail record naming. Below it sit 4.4.0 with user change logs, call recording management, QR-code provisioning and added translations, and two 4.2.x releases focused on bug fixes and SQL injection hardening in LUA scripts.
SRS shipped 6.0 release 0 in December 2025, promoting the 6.0 line to stable in place of 5.0 at roughly 170,000 lines of code. The headline is H.265/HEVC carried across RTMP, HTTP-FLV, HLS, HTTP-TS and SRT, with DVR recording to both MP4 and FLV. WebRTC gained WHEP for playback, stereo Opus over SDP and a configurable AAC-to-Opus bitrate; SRT moved to libsrt 1.5.3 with round-trip latency reported down to 200ms.
The eighteen months of alpha and beta tags before release 0 were overwhelmingly crash, leak and iterator fixes — smart-pointer conversions, use-after-free repairs in the HLS and bridge paths, RTC-to-RTMP stability. That is the signature of a project stabilizing an existing engine rather than extending it, with the codec work landing at the end. SRS is positioning as the self-hosted streaming server that speaks every ingest and egress protocol in one binary.
With 6.0 now the stable line, the pattern from the 5.0 era points to a run of 6.0 patch releases carrying fixes rather than features. The entries give no indication of what the next major line targets.
Every visible entry predates 2019. The newest is 4.4.1, a minor bug-fix release covering call centre login, device password propagation and call detail record naming. Below it sit 4.4.0 with user change logs, call recording management, QR-code provisioning and added translations, and two 4.2.x releases focused on bug fixes and SQL injection hardening in LUA scripts.
What the archive shows is a project that treated security hardening as release-worthy in its own right and steadily broadened administrative tooling around FreeSWITCH. What it cannot show is anything about the last several years — the feed has been silent since 2018, so no current direction is observable.
There is not enough recent data to predict a next move. Until this feed carries releases again, the product's current state is unreadable from here.
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 SRS or FusionPBX.
After twenty-one months of silence, FreeSWITCH 1.11 deleted thirty legacy modules and moved on
Six branches patched inside thirteen minutes — Asterisk's security process is the story here
PeerTube 8.2 spends its release candidates hardening instances against scrapers and locking down account data
Buried in Muvi's OTT explainer mill, Alie is quietly becoming the reason to buy.
mediasoup's Rust line is absorbing an outside security audit while finishing subchannels over pipe transport.
EventMobi's feed argues for onsite badge printing while saying nothing about what it shipped
See all SRS alternatives → · See all FusionPBX alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. SRS and FusionPBX are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. SRS and FusionPBX are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
Top SRS alternatives in Meetings are ranked by recent ship velocity. Browse the "SRS alternatives" section above for the current picks, or visit /alternatives/srs for the full list with editorial commentary on each.
Top FusionPBX alternatives in Meetings are ranked by recent ship velocity. Browse the "FusionPBX alternatives" section above for the current picks, or visit /alternatives/fusionpbx for the full list with editorial commentary on each.