- Ya
- 26 Aprili 2026, 20:39 UTC
- Mwandishi
- kamo
- Ahadi ya
- 6fd7d5c
The browser-side SDK init failure is currently invisible — the popup just says "Phone SDK failed to initialize" with no message, the WebSocket never opens, and we have no DevTools output. Add a /api/softphone-debug beacon endpoint that logs whatever the browser POSTs, then have SipJsPhoneSdk emit a step-by-step trail of phase events (precheck, new-UserAgent-failed, ua-start-call, ua-start-failed, register-call, register-rejected/threw, etc.). Each phase carries any underlying error message. This lets us read kamo-internal pod logs to see exactly where init dies without round-tripping through the browser console.