Fourwaves
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
A side-by-side editorial comparison of HOMER and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.
HOMER 11.0.369 fixes S3 auth on Ceph-based storage and stops compaction memory growth.
HOMER's 11.0 line is still hardening its DuckDB tiered-storage layer. 11.0.368 retries incomplete tier moves and fixes tiered queries that missed lake tables. The 11.0.369 pre-release stops sending the AWS session token with static S3 keys, which broke Vultr/Ceph RGW, and keeps DuckDB's file cache off on write paths so compaction memory plateaus. Security fixes (bound tiered lookup parameters, hono bump) ride alongside.
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.
HOMER's 11.0 line is still hardening its DuckDB tiered-storage layer. 11.0.368 retries incomplete tier moves and fixes tiered queries that missed lake tables. The 11.0.369 pre-release stops sending the AWS session token with static S3 keys, which broke Vultr/Ceph RGW, and keeps DuckDB's file cache off on write paths so compaction memory plateaus. Security fixes (bound tiered lookup parameters, hono bump) ride alongside.
Almost every release since early October fixes the parquet lake: compaction, cache behaviour, tiering and S3 compatibility. The storage rewrite is being shaken out in production on more varied object stores. Feature work, such as OTLP log events on the call ladder, has paused while this stabilises.
Expect 11.0.369 to be promoted from pre-release, followed by more storage fixes for non-AWS object stores before feature work picks up 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 HOMER or rtpengine.
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
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.
Kamailio's feed shows quiet, migration-free upkeep across two stable branches.
See all HOMER 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. HOMER 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. HOMER 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 HOMER alternatives in Meetings are ranked by recent ship velocity. Browse the "HOMER alternatives" section above for the current picks, or visit /alternatives/homer-voip 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.