VoIP Quality Daily Standup · Sprint 24

Changes over the past day (2026-06-21, Sunday) · grouped by owner · action items

Sprint 24 (11–24 Jun) · Risk 🔴 High / 🟡 Med / 🟢 Low — by severity/blocker/dependency/process, not schedule · 🐛 Bug 📋 Task

29 tickets in sprint· Changed yesterday 1· Sunday was a UAE weekend — only one China-TZ commit landed

🚩 Action summary (by priority)

🟢 Zhao — VPQ-116: ML-VQC low-MOS (ty=9) quality-event reporting implemented & committed across iOS + Android (whatrtc_ios/jni, botim-ios/android); all builds green → continue in-testing, no blockers

Changed yesterday (by owner)

Owner	Work item	Owner / status Δ	Activity (📦commit / 💬comment)	🚩 Action
Zhao ·1	📋 VPQ-116 ML-VQC SDK integration — real-time quality detectionML-VQC 模型集成进 VoIP SDK · 实时质量检测	— no Δ (In Testing)	📦 whatrtc_ios + whatrtc_jni `feat/4.10.0/VPQ-116` (774e2949 · 514c8560) + botim-ios/android binaries refreshed (39525206e · 8ba08a5de); builds ✅ iOS xcframework + Android arm64/arm32 (Jun 21 22:07–22:08) 💬 Zhao: added ty=9 low-MOS event to V4 glitches[] — fires when ML-VQC CalMOS < 3.0, enter/exit window model like freeze/bad-QP; records mosAvg / vmafAvg / qpAvg, passive-close on session end; 6 files synced iOS+Android	🟢 in testing

Everything else — unchanged yesterday

No status / owner / comment changes on 2026-06-21 for the other 28 sprint tickets (UAE weekend).
In flight from Fri/Sat, awaiting the next working day: VPQ-359 V4 grayscale 50/50 A/B (In Testing) · VPQ-367 Android reconnect / low-res after answer (Submit for Review) · VPQ-357 V4/V3 freeze-detection divergence (Pending Confirmation) · VPQ-360 iOS BOTRTCV4 crash logs (Pending Confirmation) · VPQ-340 / VPQ-356 / VPQ-314 BUGFIXED → verify & close · VPQ-351 Voice Bot Phase 1 (In Dev).