Fourwaves
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
A side-by-side editorial comparison of Asterisk and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.
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.
rtpengine opens the mr26.3 branch with a rollback message and leaner call state.
Sipwise's rtpengine media proxy opened a new mr26.3 branch on October 19. Its first build, mr26.3.1.1, carries everything from mr26.2.1.5 plus a rollback NG control message, relaxed loop detection for duplicate packets arriving over a second apart or from endpoints no longer local, ICE agent teardown when a peer drops ICE, inject-audio mixing fixes, and a long run of "lightweight string" refactors across call IDs, tags, SDP and recording fields. Three days earlier, a hardening batch went to four branches, followed by compile-fix releases.
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.
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.
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.
Sipwise's rtpengine media proxy opened a new mr26.3 branch on October 19. Its first build, mr26.3.1.1, carries everything from mr26.2.1.5 plus a rollback NG control message, relaxed loop detection for duplicate packets arriving over a second apart or from endpoints no longer local, ICE agent teardown when a peer drops ICE, inject-audio mixing fixes, and a long run of "lightweight string" refactors across call IDs, tags, SDP and recording fields. Three days earlier, a hardening batch went to four branches, followed by compile-fix releases.
Development continues on two levels: correctness fixes backported across every supported branch, and newer work, such as the rollback message and memory-lighter call state, landing on the newest line. Opening mr26.3 adds a fifth maintained branch, so the backport load grows.
Expect mr26.3.1.x point builds and continued synchronized backports to mr12.5 through mr26.2. The entries don't show when older branches stop receiving fixes.
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 rtpengine.
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
HOMER 11.0.369 fixes S3 auth on Ceph-based storage and stops compaction memory growth.
Element Call starts moving to new LiveKit transports and falls back to remote SFUs when needed.
JW Player moves CMAF VOD into the dashboard, adds AV1, and opens Broadcast Live to audio-only feeds.
Nextcloud Talk Desktop 2.3.3 adds accessibility options and bundles Talk v25.0.6.
Nextcloud Talk patches v22 and v23 while v25 stable sits five weeks past its last RC.
See all Asterisk alternatives → · See all rtpengine alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Asterisk and rtpengine are shipping at a similar cadence (velocity 5.0 vs 5.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. Asterisk and rtpengine are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
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.
Top rtpengine alternatives in Meetings are ranked by recent ship velocity. Browse the "rtpengine alternatives" section above for the current picks, or visit /alternatives/rtpengine for the full list with editorial commentary on each.