← Back to home
Comparison · Meetings

Asterisk vs Element Call

A side-by-side editorial comparison of Asterisk and Element Call — release velocity, themes, recent moves, and the top alternatives to consider.

Asterisk vs Element Call: at a glance

FeatureAsteriskElement Call
SectorMeetingsMeetings
Velocity score5.06.3
Sparks · 30d01
Top themesbackport discipline, multi-branch releases, maintenance cycle, telephony corefederated-calling, matrix-rtc, multi-sfu, architecture-cleanup
Last editorial update16d ago3d ago
WebsiteVisit →Visit →

What is Asterisk?

The three-branch cycle closes: 20, 22 and 23 all promote to final with the same 28-issue set.

The release round that opened on August 7 has finished. Asterisk 20.21.0, 22.11.0 and 23.5.0 all tagged within a minute of each other, each carrying 39 commits from 16 authors, 28 resolved issues and zero security advisories. The counts are identical across all three branches, which is the same backport-in-lockstep pattern the certified track and the June security round both followed.

Read the full Asterisk trajectory →

What is Element Call?

Element Call is removing its legacy architecture — the federated multi-SFU model is now the only option.

Element Call has spent the last two months removing compatibility scaffolding: MatrixRTC legacy mode (v0.25.0) and .well-known transport discovery (v0.24.0) are both gone. Every participant now connects to their homeserver's SFU with no fallback to the old negotiated single-SFU model. React Compiler is enabled for rendering performance, and media quality settings got a dedicated UI in v0.24.0. The RC release cadence is high while stable releases remain patch-focused.

Read the full Element Call trajectory →

Asterisk vs Element Call: editorial side-by-side

A
Asterisk
MEETINGS
5.0

The three-branch cycle closes: 20, 22 and 23 all promote to final with the same 28-issue set.

◆ Current state

The release round that opened on August 7 has finished. Asterisk 20.21.0, 22.11.0 and 23.5.0 all tagged within a minute of each other, each carrying 39 commits from 16 authors, 28 resolved issues and zero security advisories. The counts are identical across all three branches, which is the same backport-in-lockstep pattern the certified track and the June security round both followed.

◆ Where it's heading

Nothing about the shape has changed: three mainline branches plus a certified track, one fix set, promoted together. The rc1-to-rc2-to-final progression narrowed from 27 issues to a single websocket segfault fix and then closed, which is a cycle converging on schedule. Release bodies still publish counts and links rather than user-facing notes, so the feed measures release discipline rather than product direction.

◆ Prediction

Expect the certified track to pick up this same fix set in its next cert release, following the lag it showed after the June round. The next mainline round should open with rc1 tags on all three branches again.

E
Element Call
MEETINGS
6.3

Element Call is removing its legacy architecture — the federated multi-SFU model is now the only option.

◆ Current state

Element Call has spent the last two months removing compatibility scaffolding: MatrixRTC legacy mode (v0.25.0) and .well-known transport discovery (v0.24.0) are both gone. Every participant now connects to their homeserver's SFU with no fallback to the old negotiated single-SFU model. React Compiler is enabled for rendering performance, and media quality settings got a dedicated UI in v0.24.0. The RC release cadence is high while stable releases remain patch-focused.

◆ Where it's heading

The architecture is settled: federated multi-SFU, homeserver-anchored, no legacy bridges. The breaking changes are pruning maintenance surface rather than adding capability. The next period is likely refinement — call quality controls, edge-case stability, and mobile experience polish — within the established architecture. Element Call's trajectory is now governed by the Matrix ecosystem roadmap more than its own feature backlog.

◆ Prediction

Stable releases catching up to the RC channel, with polish on the media quality controls from v0.24.0 and mobile layout improvements. Homeserver-level call routing policies are a plausible next capability now that the SFU model is uniform across all deployments.

Alternatives to Asterisk and Element Call

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 Asterisk or Element Call.

See all Asterisk alternatives → · See all Element Call alternatives →

Recent activity from Asterisk and Element Call

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4d agoElement Callv0.26.0-rc.2
  2. 6d agoElement Callv0.26.0-rc.1
  3. 16d agoElement CallElement Call v0.25.0 removes MatrixRTC legacy mode, requiring full multi-SFU migration
  4. 17d agoAsterisk22.11.0 promotes to final with 28 issues resolved
  5. 17d agoAsterisk23.5.0 closes the cycle on the newest mainline branch
  6. 17d agoAsterisk20.21.0 carries the same fix set back to the LTS line
  7. 24d agoAsterisk23.5.0-rc2: single fix for a websocket PONG segfault
  8. 24d agoAsterisk20.21.0-rc2 takes the same one-commit websocket fix
  9. 24d agoAsterisk22.11.0-rc2 mirrors the websocket PONG crash fix
  10. 1mo agoElement CallElement Call v0.24.0: React Compiler enabled, media quality UI, legacy transport removed
  11. 1mo agoElement Callv0.23.0-rc.1
  12. 2mo agoElement CallElement Call v0.22.0: Mobile call UI overhaul with gradient backgrounds as default

Frequently asked questions

What is the difference between Asterisk and Element Call?

They serve adjacent needs but don't currently overlap on shipped themes. Element Call is currently shipping more aggressively (velocity 6.3 vs 5.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.

Is Asterisk better than Element Call?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Element Call is currently shipping more aggressively (velocity 6.3 vs 5.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.

What are the best alternatives to Asterisk?

Top Asterisk alternatives in Meetings are ranked by recent ship velocity. Browse the "Asterisk alternatives" section above for the current picks, or visit /alternatives/asterisk for the full list with editorial commentary on each.

What are the best alternatives to Element Call?

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.