What broke
A valid connection carried an invalid configuration.
The provider accepted the WebSocket, then rejected an unsupported nested setting before useful output began.
DentSignal repair · Cloud integration
The socket opened. The session still failed.
Azure-hosted telemetry moved the investigation past infrastructure and onto the first provider settings message.
What changed
The payload was reduced to supported values.
The rejected object was removed, valid values were constrained, and the exact message shape received regression coverage.
What it fixed
The provider acknowledged the session settings.
A controlled no-audio handshake reached SettingsApplied without rebuilding unrelated cloud infrastructure.
Before / after
Send only the accepted settings.
Broken
settings = {"threshold": 0.8,
"nested": unsupported}
socket.send(settings)Fixed
settings = {"threshold": valid_threshold}
socket.send(settings)
assert event == "SettingsApplied"Evidence
Telemetry narrowed the failure to one settings boundary.
The connection opened, the original settings payload was rejected, and the narrowed payload reached the provider's accepted-settings state in the controlled path. The evidence is historical and does not claim a current live-call result.
Stack and capabilities
Narrow integration repair from hosted evidence.
- Python
- WebSockets
- Azure telemetry
- Provider events
- Payload validation
- Regression tests
Next