update

Author: bryantanderson

fern/calls/call-ended-reason.mdx

@@ -4,7 +4,6 @@ subtitle: A guide to understanding all call "Ended Reason" types & errors.
 slug: calls/call-ended-reason
 ---
 
-
 This guide will discuss all possible `endedReason`s for a call.
 
 You can find these under the **"Ended Reason"** section of your [call
@@ -31,6 +30,7 @@ Object](/api-reference/calls/get-call)).
 These relate to issues within the AI processing pipeline or the Large Language Models (LLMs) used for understanding and generating text:
 
 - **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.
+- **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.
 - **pipeline-error-\***: Similar to **call.in-progress.error-vapifault-\***. However, these error codes are surfaced when you are using your own provider keys.
 - **pipeline-no-available-llm-model**: No suitable LLM was available to process the request.
 
@@ -45,6 +45,7 @@ These relate to issues within the AI processing pipeline or the Large Language M
 - **vonage-disconnected**: The call was disconnected by Vonage, another call management service.
 - **vonage-failed-to-connect-call**: Vonage failed to establish the call connection.
 - **vonage-rejected**: The call was rejected by Vonage due to an issue or configuration problem.
+- **sip-telephony-provider-failed-to-connect-call**: The SIP telephony provider failed to establish the call connection.
 
 #### **Other Reasons**