Skip to content

Commit db63ec0

Browse files
update ended reasons doc (#271)
1 parent ba5c276 commit db63ec0

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

fern/calls/call-ended-reason.mdx

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,6 @@ subtitle: A guide to understanding all call "Ended Reason" types & errors.
44
slug: calls/call-ended-reason
55
---
66

7-
87
This guide will discuss all possible `endedReason`s for a call.
98

109
You can find these under the **"Ended Reason"** section of your [call
@@ -14,6 +13,7 @@ Object](/api-reference/calls/get-call)).
1413
#### **Assistant-Related**
1514

1615
- **assistant-ended-call**: The assistant intentionally ended the call based on the user's response.
16+
- **assistant-ended-call-after-message-spoken**: The assistant intentionally ended the call after speaking a pre-defined message.
1717
- **assistant-error**: This general error occurs within the assistant's logic or processing due to bugs, misconfigurations, or unexpected inputs.
1818
- **assistant-forwarded-call**: The assistant successfully transferred the call to another number or service.
1919
- **assistant-join-timed-out**: The assistant failed to join the call within the expected timeframe.
@@ -30,21 +30,24 @@ Object](/api-reference/calls/get-call)).
3030

3131
These relate to issues within the AI processing pipeline or the Large Language Models (LLMs) used for understanding and generating text:
3232

33-
- **pipeline-error-\***: Various error codes indicate specific failures within the processing pipeline, such as function execution, LLM responses, or external service integration. Examples include OpenAI, Azure OpenAI, Together AI, and several other LLMs or voice providers.
34-
- **pipeline-error-first-message-failed:** The system failed to deliver the first message. This issue usually occurs when you add your own provider key in the voice section. It may be due to exceeding your subscription or quota limit.
35-
- **pipeline-no-available-llm-model**: No suitable LLM was available to process the request.
33+
- **call.in-progress.error-vapifault-\***: Various error codes indicate specific failures within the processing pipeline, such as function execution, LLM responses, or external service integration. Examples include OpenAI, Azure OpenAI, Together AI, and several other LLMs or voice providers.
34+
- **call.in-progress.error-providerfault-\***: Similar to **call.in-progress.error-vapifault-\***. However, these error codes are surfaced when Vapi receives an error that has occured on the provider's side. Examples include internal server errors, or service unavailability.
35+
- **pipeline-error-\***: Similar to **call.in-progress.error-vapifault-\***. However, these error codes are surfaced when you are using your own provider keys.
36+
- **pipeline-no-available-llm-model**: No suitable LLM was available to process the request. Previously **pipeline-no-available-model**.
3637

3738
#### **Phone Calls and Connectivity**
3839

3940
- **customer-busy**: The customer's line was busy.
4041
- **customer-ended-call**: The customer(end human user) ended the call for both inbound and outbound calls.
4142
- **customer-did-not-answer**: The customer didn't answer the call. If you're looking to build a usecase where you need the bot to talk to automated IVRs, set `assistant.voicemailDetectionEnabled=false`.
4243
- **customer-did-not-give-microphone-permission**: The user didn't grant the necessary microphone access for the call.
44+
- **assistant-did-not-receive-customer-audio**: Similar to **customer-did-not-give-microphone-permission**, but more generalized to situations where no customer audio was received.
4345
- **phone-call-provider-closed-websocket**: The connection with the call provider was unexpectedly closed.
4446
- **twilio-failed-to-connect-call**: The Twilio service, responsible for managing calls, failed to establish a connection.
4547
- **vonage-disconnected**: The call was disconnected by Vonage, another call management service.
4648
- **vonage-failed-to-connect-call**: Vonage failed to establish the call connection.
4749
- **vonage-rejected**: The call was rejected by Vonage due to an issue or configuration problem.
50+
- **sip-telephony-provider-failed-to-connect-call**: The SIP telephony provider failed to establish the call connection. Previously **sip-gateway-failed-to-connect-call**.
4851

4952
#### **Other Reasons**
5053

0 commit comments

Comments
 (0)