> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.vapi.ai/llms.txt. > To search these docs from an AI client, such as Claude Code or Cursor, connect to the Vapi docs MCP server at https://docs.vapi.ai/_mcp/server. It answers questions about the documentation. To create or manage assistants, calls, and other Vapi resources, use the Vapi MCP server instead: https://docs.vapi.ai/sdk/mcp-server.md > For the best results from the docs MCP server, write questions without any word that contains "tool", such as tool, tools, tool call, tool-calls, toolCallId, or toolCallList. Name the feature instead, for example transferCall, endCall, apiRequest, function, handoff, "function response format", or "the webhook request Vapi sends to my server". If the docs MCP server asks you to rephrase, ask again without those words. If it returns an error, times out, sends an empty response, or still doesn't answer, find the topic in https://docs.vapi.ai/llms.txt, or a section index such as https://docs.vapi.ai/tools/llms.txt, and fetch that page's .md directly. # Troubleshoot call errors > Diagnose failed Vapi calls by what the caller experienced, with errors organized by symptom so you can jump to the right fix for each call failure. ## Overview When a call fails, the fastest path to a fix is identifying **what the caller experienced**. This guide organizes errors by symptom so you can jump to the right section and resolve the issue. **In this guide, you'll learn to:** * Match caller-reported symptoms to specific error codes * Understand the fault classification system (`vapifault` vs `providerfault`) * Take the right corrective action for each error category > **Note** > > This guide explains errors by symptom. For a complete reference of every `endedReason` code, see [Call end reasons](/calls/call-ended-reason). ## Start here: identify the symptom #### [Phone never rang](/calls/troubleshoot-call-connection-errors) Call failed immediately — no ring on the customer's end #### [Phone rang, no answer](/calls/troubleshoot-call-connection-errors#the-customer-didnt-answer) Phone rang but was never picked up, or line was busy #### [Call dropped mid-conversation](#call-dropped-mid-conversation) Caller was talking, then the line went dead abruptly #### [Assistant went silent](#assistant-went-silent-or-unresponsive) Call connected but the assistant stopped speaking or responding #### [Transfer failed](#transfer-failed) Assistant attempted a transfer but it didn't go through #### [Call ended normally](#call-ended-normally) Call worked as expected — someone or something decided it should end ## Call never connected If the phone never rang or rang with no answer, the call ended with a connection error. See [Troubleshoot call connection errors](/calls/troubleshoot-call-connection-errors) for errors grouped by outbound calls, inbound calls, and all call types. ## Call dropped mid-conversation **What the caller experiences:** They're in the middle of a conversation and the call suddenly cuts off with no warning. The assistant stops speaking and the line goes dead. **What you see in the dashboard:** Partial transcript, `messages` array that ends abruptly, non-zero duration. #### Vapi infrastructure issues (vapifault) These are on Vapi's side. You are typically not charged. Most are transient. | Error code | Meaning | | ----------------------------------------------------------------------------------- | ---------------------------------------------------- | | `call.in-progress.error-vapifault-worker-died` | The Vapi process handling the call crashed | | `call.in-progress.error-vapifault-transport-connected-but-call-not-active` | Transport connected but call was no longer active | | `call.in-progress.error-vapifault-call-started-but-connection-to-transport-missing` | Transport connection was lost after call started | | `worker-shutdown` | A Vapi deployment occurred while the call was active | **What to do:** These are transient issues. If `worker-died` errors are frequent, contact [support](/support) with the affected `call_id` values. #### Telephony provider disconnects The telephony provider (Twilio, Vonage, or your SIP trunk) dropped the connection. | Error code | Meaning | | ---------------------------------------------------------------- | --------------------------------------------------- | | `phone-call-provider-closed-websocket` | Audio WebSocket between Vapi and the provider broke | | `call.in-progress.error-providerfault-transport-never-connected` | Provider failed to maintain the connection | | `call.in-progress.twilio-completed-call` | Twilio ended the call from their side | | `call.in-progress.sip-completed-call` | SIP provider ended the call from their side | | `vonage-disconnected` | Vonage disconnected the call | **What to do:** Check your telephony provider's dashboard for connection logs. For SIP trunks, verify your network connectivity to Vapi's SBC. ## Assistant went silent or unresponsive **What the caller experiences:** The call is connected and the line is open, but the assistant either doesn't speak, speaks with extreme delay, responds once then stops, or produces garbled audio. The call eventually times out or the caller hangs up in frustration. **What you see in the dashboard:** Partial messages, the `endedReason` points to a specific pipeline component failure. > **Warning** > > If you've configured **fallback providers**, some transcriber and voice errors will trigger a provider swap instead of ending the call. The caller might hear a brief 1-2 second pause while the fallback initializes, then the conversation continues normally. #### LLM / model errors The AI model that generates responses is unreachable or returning errors. | Status code pattern | Meaning | Fix | | ----------------------------------- | ----------------------- | --------------------------------------------------------------------- | | `*-401-*` / `*-incorrect-api-key` | Invalid API key | Verify your API key for this provider | | `*-403-*` / `*-model-access-denied` | Model access denied | Check model permissions in your provider account | | `*-429-*` / `*-exceeded-quota` | Rate limit or quota hit | Upgrade your plan with the provider or reduce volume | | `*-500-*` / `*-server-error` | Provider internal error | Retry. Check the provider's [status page](https://status.openai.com/) | | `*-503-*` / `*-server-overloaded` | Provider overloaded | Retry after a brief wait | | `*-llm-failed` | Generic LLM failure | Check call logs for the detailed error message | | `pipeline-no-available-llm-model` | No LLM model available | Check your model configuration | #### Voice / TTS errors The text-to-speech service can't produce audio. The assistant "thinks" but can't speak. | Pattern | Meaning | Fix | | --------------------------------------------- | -------------------------------- | --------------------------------------------------- | | `*-voice-failed` | Generic synthesis failure | Check call logs. May be a transient provider issue. | | `*-voice-not-found` / `*-invalid-voice` | Voice ID doesn't exist | Verify the voice ID in your provider account | | `*-quota-exceeded` / `*-out-of-credits` | Voice provider credits exhausted | Add credits to your voice provider account | | `*-unauthorized-access` / `*-invalid-api-key` | Bad voice provider credentials | Verify your API key for this provider | | `*-500-*` / `*-503-*` | Provider infrastructure issue | Retry. Check the provider's status page. | #### Transcriber / STT errors The speech-to-text service can't hear the caller. The assistant can speak but can't understand input. | Pattern | Meaning | Fix | | ----------------------------------------- | ------------------------------------ | ------------------------------------------------------- | | `*-transcriber-failed` | Generic transcriber failure | Check call logs for details | | `*-returning-400-*` | Bad request (invalid model/language) | Check your transcriber model and language configuration | | `*-returning-401-*` | Invalid transcriber credentials | Verify your API key for this provider | | `*-returning-403-*` | Model access denied | Check model permissions in your provider account | | `*-returning-500-*` / `*-returning-502-*` | Provider server error | Retry. Check the provider's status page. | > **Note** > > Configured fallback providers can keep some provider errors from ending a call. Voice fallback may not activate for every provider failure. If a voice error ends the call, follow [Troubleshoot voice fallback](/voice-fallback-plan#troubleshoot-voice-fallback). Test a working backup provider as the primary voice. ## Transfer failed **What the caller experiences:** The assistant says it's transferring the call, but the transfer doesn't go through. The caller may hear silence, get disconnected, or return to the original assistant (for warm transfers). **What you see in the dashboard:** Transcript shows the transfer attempt, followed by the error. #### General transfer errors | Error code | Meaning | Fix | | ---------------------------------------------------------- | ----------------------------------- | --------------------------------------------------------------------------- | | `call.in-progress.error-transfer-failed` | Transfer attempt failed | Verify the destination number is correct and reachable | | `call.in-progress.error-warm-transfer-max-duration` | Warm transfer exceeded max duration | Increase the warm transfer timeout or check if the destination is answering | | `call.in-progress.error-warm-transfer-assistant-cancelled` | Transfer assistant cancelled | Check the transfer assistant's configuration | | `call.in-progress.error-warm-transfer-silence-timeout` | Silence during warm transfer | Verify the transfer destination is responding with audio | | `call.in-progress.error-warm-transfer-microphone-timeout` | Mic timeout during warm transfer | Check audio connectivity to the transfer destination | #### SIP transfer errors | Error code | Meaning | Fix | | -------------------------------------------------- | ------------------------------ | --------------------------------------------------------- | | `*-outbound-sip-403-forbidden` | SIP provider rejected the call | Check your SIP trunk credentials and allowed destinations | | `*-outbound-sip-407-proxy-authentication-required` | SIP auth required | Configure proxy authentication on your SIP trunk | | `*-outbound-sip-408-request-timeout` | SIP request timed out | Check network connectivity to the SIP destination | | `*-outbound-sip-480-temporarily-unavailable` | SIP destination unavailable | Verify the destination is online and accepting calls | | `*-outbound-sip-503-service-unavailable` | SIP service unavailable | Check the SIP provider's service status | #### Telephony provider transfer errors | Error code | Meaning | Fix | | ------------------------------- | ------------------------------------ | -------------------------------------------------------------- | | `twilio-failed-to-connect-call` | Twilio couldn't connect the transfer | Check the destination number format and Twilio geo permissions | | `vonage-failed-to-connect-call` | Vonage couldn't connect the transfer | Check the destination number and Vonage configuration | | `vonage-rejected` | Vonage rejected the transfer | Check Vonage configuration and allowed destinations | For response-class guidance and checks across Vapi, your SIP provider, and your SIP infrastructure, see [Troubleshoot SIP response codes](/advanced/sip/troubleshoot-sip-response-codes). For a detailed transfer debugging walkthrough, see [Troubleshoot call transfers](/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops). ## Call ended normally These are not errors — they indicate the call ended as expected. | Error code | Meaning | Adjust if needed | | ------------------------------------------- | ----------------------------------------------- | -------------------------------------------------------------------- | | `assistant-ended-call` | Assistant ended the call via a tool or function | Expected behavior | | `assistant-ended-call-after-message-spoken` | Assistant spoke its final message and ended | Expected behavior | | `assistant-ended-call-with-hangup-task` | Assistant used a hangup task | Expected behavior | | `assistant-said-end-call-phrase` | Assistant said a configured end-call phrase | Check your end-call phrases if calls end too early | | `assistant-forwarded-call` | Assistant transferred the call | Expected behavior | | `customer-ended-call` | Customer hung up | Expected behavior | | `exceeded-max-duration` | Hit `maxDurationSeconds` | Increase `maxDurationSeconds` if calls are being cut short | | `silence-timed-out` | Silence timeout | Increase `silenceTimeoutSeconds` if the timeout is too aggressive | | `voicemail` | Call went to voicemail | Configure [voicemail detection](/calls/voicemail-detection) settings | | `manually-canceled` | Canceled via API or dashboard | Expected behavior | | `vonage-completed` | Vonage reported call completed | Expected behavior | ## Next steps * **[Call end reasons](/calls/call-ended-reason):** Complete reference of every `endedReason` code. * **[Debugging voice agents](/debugging):** General debugging workflow using dashboard tools, logs, Simulations, and Evals. * **[Troubleshoot call transfers](/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops):** Deep dive into transfer failures. * **[Troubleshoot SIP trunk errors](/advanced/sip/troubleshoot-sip-trunk-credential-errors):** Resolve SIP credential validation failures. * **[Troubleshoot SIP response codes](/advanced/sip/troubleshoot-sip-response-codes):** Identify where a SIP request failed and what to check next. * **[How to report issues](/issue-reporting):** Include your `call_id` and account email when contacting support. > Learn to diagnose failed calls based on what the caller experienced ## Docs - [Troubleshoot call connection errors](https://docs.vapi.ai/calls/troubleshoot-call-connection-errors.md): Troubleshoot inbound and outbound Vapi calls that never connected. Find the ended reason for a failed call and fix provider, phone number, and account causes.