Use the symptom to choose a check. Keep the test destination, Environment and time so you can match the provider call, socket events and Transcript.
Symptom checks
| Symptom | Check first | Verify the correction |
|---|
| Wrong agent or version answers | Number/connection assignment, Draft versus Published, or saved socket session key. | Start a new session and check its resolved Environment. |
| No microphone input | Wait for asr.started; send binary frames in its acknowledged format, not MediaRecorder containers. | Confirm a committed asr.transcript for the spoken phrase. |
| Agent speaks but browser is silent | Base64 decoding, output encoding and playback queue. | Play a complete supported audio message, then acknowledge its action. |
| Old audio continues after interruption | Clear all queued and active audio on asr.barge-in. | Interrupt a reply and confirm it stops before the next reply. |
| Replies cut off customer pauses | Selected STT provider’s endpointing controls. | Repeat a date/order number with realistic pauses. |
| Replies wait after speech | Recognition end-of-turn timing, model/tool time and audio sync. | Compare recognition commitment and generation events before adjusting one setting. |
| Keypad never submits | Input step, enabled collection, delimiter and timeout. | Enter digits and submit with the configured key or wait. |
| Calls end unexpectedly | Call end reason, silence and maximum duration. | Reproduce each configured timeout independently. |
| Outbound request rejected | 400 configuration/destination, 402 credits, 429 production concurrency. | Resolve the specific cause, then place one test call. |
| Human transfer fails | Provider destination or SIP REFER acceptance. | Call the actual destination; a prototype does not validate transfer. |
| Recording missing | Recording was disabled, PII redaction, or nullable Transcript ID. | Enable the intended settings and make a new call. |
Choose the correct diagnostics
For phone-system routing and media problems, use SIP troubleshooting. For custom transport failures, use Errors and recovery. Managed-call Webhooks and raw socket events are different interfaces.
Isolate a slow response
- Record the test Environment, timestamp and connection type.
- Reproduce one symptom with a destination you control.
- Inspect recognition, generation, playback or provider events for that call.
- Change the setting at the failing layer and repeat the same test.
Retry and credential boundaries
Do not redial automatically after an unknown outbound HTTP outcome. Confirm the provider/call state first. Never put a private project key in browser code.