Fourwaves
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
A side-by-side editorial comparison of Pexip and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.
Pexip Infinity v40 lands as a maintenance-grade release.
The recent feed is dominated by the Pexip Infinity v40 release notes — upgrade procedure, changelog, resolved issues, known limitations — alongside the prior v39.1 release. The v40 release itself notes 'no significant changes' in functionality, suggesting this is a stability/security cut rather than a feature push.
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 recent feed is dominated by the Pexip Infinity v40 release notes — upgrade procedure, changelog, resolved issues, known limitations — alongside the prior v39.1 release. The v40 release itself notes 'no significant changes' in functionality, suggesting this is a stability/security cut rather than a feature push.
Pexip is operating in classic enterprise-on-prem mode: regular versioned releases with multi-step upgrade paths, security bulletins, and detailed end-of-life announcements. There is no visible AI or cloud-native pivot in the current notes. The product is being maintained for the install base it already has, not reshaped for a new buyer.
Expect a v40.x point release within 4–6 weeks addressing v40 known limitations, and continued biannual major versions. The next directional signal would be either an AI-meeting feature inside the web app or a cloud-managed deployment option — neither is hinted at in this batch.
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 Pexip 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 Pexip 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. Pexip 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. Pexip 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 Pexip alternatives in Meetings are ranked by recent ship velocity. Browse the "Pexip alternatives" section above for the current picks, or visit /alternatives/pexip 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.