VoIP Quality Daily Standup · Sprint 24

Changes on Mon 2026-06-22 · grouped by owner · action items

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

30 tickets in sprint· Changed in window 6· 1 bug fixed · 1 new bug · 1 new analysis · 1 → In Testing

🚩 Action summary (by priority)

🔴 Fahed Saghir — VPQ-360 iOS BOTRTCV4 crash reopened in the morning (crash recurred on a 4.12 build) and bounced through several owners; Ankit Kumar Gupta root-caused it as a Firebase version incompatibility with the Ads SDKs (not the earlier Pangle-SDK hypothesis) and rolled Firebase back to 12.7; Fahed retested on the new 4.12 build (202606221219) — no crash → BUGFIXED. Monitor in the 4.12 release.
🟡 Zhao — VPQ-116 ML-VQC: blocked on backend — mlvqc_enabled is not pushed by any config channel (client CC or server signaling), so the SDK defaults to Strategy A (false); backend must set mlvqc_enabled in CC/signaling to validate Strategy B in the test env.
🟡 Zhao — VPQ-364 new bug: iOS OpenH264 software-encode / Android software-decode — switching resolution to 360p distorts the color space; filed Submit for Review → triage & schedule dev.
🟢 Chao Tian — VPQ-359 V4 grayscale PK 50/50 A/B moved To Do → In Development → In Testing; server uses uid-hash for cohort split.
🟢 Abhishek Manoharan — VPQ-270 SDK old-vs-new comparison dashboard: committed /voip/quality-compare V4 (patch-level filter, Hive↔Kibana toggle, ETL hardening).

Changed in window (by owner)

Owner	Work item	Owner / status Δ	Activity (📦commit / 💬comment)	🚩 Action
Fahed Saghir ·1	🐛 VPQ-360 iOS BOTRTCV4 crash logs (4.12.0)iOS BOTRTCV4 崩溃(4.12.0)	🔄 Pending Confirm→Reopened→…→BUGFIXED (Fixed) (by Fahed Saghir); reassigned Fahed→Abhishek→Ankit→Fahed through the day	💬 morning: crash recurred on 4.12 build — reopened with crash logs + video 💬 first hypothesis Pangle ad-SDK use-after-free (Abhishek), then corrected — Ankit: a bumped Firebase version was incompatible with the Ads SDKs; rolled back to 12.7 💬 Fahed retested on build `202606221219` — no crash	🔴 monitor in 4.12 release (regressed once today)
Zhao ·2	📋 VPQ-116 ML-VQC SDK Integration — real-time quality detectionML-VQC 模型集成进 VoIP SDK	— no status Δ (In Testing); Fix Version 4.13	💬 06-22: verified config channels via `UpdateWithJson` logs — `mlvqc_enabled` not sent by client CC or server signaling, SDK falls back to Strategy A (default `false`); iOS/Android signaling params identical 📦 06-21 (carried): low-MOS ty=9 quality event implemented & committed (whatrtc iOS `774e2949` / JNI `514c8560`); final ML-VQC evaluation doc attached	🟡 backend to set `mlvqc_enabled` for Strategy B test
Zhao ·2	🐛 VPQ-364 360p switch distorts color space (iOS OpenH264 sw-encode / Android sw-decode)切到 360p 时色彩空间失真(OpenH264 软编/软解)	🆕 pulled into Sprint 24 (06-22); status Submit for Review	💬 new bug; devices iPhone 14 Plus + iPhone 17 Pro Max; distortion appears on the 360p resolution switch	🟡 triage & schedule dev
Chao Tian ·2	📋 VPQ-359 VoIP SDK V4 Grayscale Rollout — PK 50/50 A/B plan & progressV4 灰度发布 — 巴基斯坦 50/50 A/B 计划与进展	🔄 To Do→In Development→In Testing (by Chao Tian)	💬 server uses the hash of the uid to control the 50/50 grouping	🟢 in testing
Chao Tian ·2	📋 VPQ-368 [Analysis] Lighthouse — FPM Drop Funnel AnalysisLighthouse — FPM 漏斗掉落分析	🆕 pulled into Sprint 24 (06-22); status To Do	💬 new analysis task; mock dashboard linked (Call→Ring signal — VoIPSignal + Messenger)	🟢 not started — scope & pick up
Abhishek Manoharan ·1	📋 VPQ-270 BOTIM SDK Old vs New Version Comparison DashboardBOTIM SDK 新旧版本对比看板	— no status Δ (In Development)	📦 voip-lighthouse `197710b7`: feat `/voip/quality-compare` V4 — patch-level filter, Hive↔Kibana toggle, ETL hardening, briefings skill	🟢 in progress

Everything else — unchanged in window

No status / owner / comment changes on 2026-06-22 for the other ~24 sprint tickets.
Carried from earlier standups: VPQ-351 (Voice Bot, Chao Tian) · the Fri 06-19 bug-clearing batch (VPQ-340 / 356 / 314 / 357) already cleared. Today's signal is dominated by the VPQ-360 reopen → Firebase-rollback → BUGFIXED cycle, plus two newly-filed sprint items (VPQ-364 bug, VPQ-368 analysis).