FreeSWITCH
After twenty-one months of silence, FreeSWITCH 1.11 deleted thirty legacy modules and moved on
A side-by-side editorial comparison of Element Call and FusionPBX — release velocity, themes, recent moves, and the top alternatives to consider.
Matrix's calling app stopped negotiating which server hosts a call and let federation do it
Element Call spent June switching its default to a multi-SFU model: every participant connects to the media server attached to their own homeserver, and streams from other homeservers are pulled in subscribe-only. That removes the negotiation step that used to decide which single SFU a whole call would run on. July since then has been surface work — a default gradient background, retiring the last colors from the old design system, and mobile layout fixes for landscape one-on-one and grid modes.
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.
Element Call spent June switching its default to a multi-SFU model: every participant connects to the media server attached to their own homeserver, and streams from other homeservers are pulled in subscribe-only. That removes the negotiation step that used to decide which single SFU a whole call would run on. July since then has been surface work — a default gradient background, retiring the last colors from the old design system, and mobile layout fixes for landscape one-on-one and grid modes.
The multi-SFU switch is the project finishing what federated calling implies: no participant's call quality should depend on which homeserver happened to win a negotiation. It was compatible for six months before becoming the default, and legacy single-SFU mode is still reachable in developer settings, which is how infrastructure changes get made in an ecosystem of independent operators. With that settled, attention has visibly moved to mobile presentation and design-system consolidation.
Expect the legacy single-SFU path to be retired once operators have migrated, and the mobile layout work to continue through the 0.23 line. Note that every entry here is a release candidate, so these tags mark what is being tested rather than what operators are running.
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 Element Call 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 Element Call 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. Element Call 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. Element Call 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 Element Call alternatives in Meetings are ranked by recent ship velocity. Browse the "Element Call alternatives" section above for the current picks, or visit /alternatives/element-call 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.