- Shipped
- August 5, 2026 at 7:24 AM UTC
- Author
- kamo
- Commit
- 4530902
Three confirmed findings from the review of 08cecc6d. Outbound Teams calls showed the wrong remote party. TeamsAcsSession derived remoteNumber/remoteName from call.callerInfo, which describes whoever PLACED the call — us, on an outbound one — and wireSession then overwrote the correct number dial() had just set. Every outbound call card showed our own identity or "Unknown", and the CRM lead lookup keyed off it, so it matched nothing. The dialled target is now carried into the session explicitly. Audio device changes never reached a live Teams call. ACS renders audio itself, so there is no #rc-remote-audio element for the app's live AV-sync effect to act on and it early-returns for Teams — meaning preferences applied once at registration and never again. The adapter now listens for the settings event and re-selects the ACS speaker/microphone. An unconnected Teams member was told to "Connect your RingCentral account" — the normal first-run state for every Teams user, naming a product their org may not even have. The backend already returns the provider discriminator; the hook now uses it. Verified: npm test — 41 files, 413 tests, 0 failures; tsc --noEmit clean.