updated ended-reason doc

Author: sahilsuman933

fern/calls/call-ended-reason.mdx

@@ -16,16 +16,19 @@ You can find these under the **"Ended Reason"** section of your [call logs](http
 
 - `assistant-ended-call`: The assistant intentionally ended the call based on the user's response.
 - `assistant-ended-call-after-message-spoken`: The assistant intentionally ended the call after speaking a pre-defined message.
+- `assistant-ended-call-with-hangup-task`: The assistant ended the call using a hangup task.
 - `assistant-error`: This general error occurs within the assistant's logic or processing due to bugs, misconfigurations, or unexpected inputs.
 - `assistant-forwarded-call`: The assistant successfully transferred the call to another number or service.
 - `assistant-join-timed-out`: The assistant failed to join the call within the expected timeframe.
 - `assistant-not-found`: The specified assistant cannot be located or accessed, possibly due to an incorrect assistant ID or configuration issue.
-- `assistant-not-invalid`: The assistant ID provided is not valid or recognized by the system.
+- `assistant-not-valid`: The assistant ID provided is not valid or recognized by the system.
 - `assistant-not-provided`: No assistant ID was specified in the request, causing the system to fail.
+- `assistant-request-failed`: The request to the assistant failed to complete successfully.
 - `assistant-request-returned-error`: Communicating with the assistant resulted in an error, possibly due to network issues or problems with the assistant itself.
 - `assistant-request-returned-forwarding-phone-number`: The assistant triggered a call forwarding action, ending the current call.
 - `assistant-request-returned-invalid-assistant`: The assistant returned an invalid response or failed to fulfill the request properly.
 - `assistant-request-returned-no-assistant`: The assistant didn't provide any response or action to the request.
+- `assistant-request-returned-unspeakable-error`: The assistant returned an error that cannot be spoken to the user.
 - `assistant-said-end-call-phrase`: The assistant recognized a phrase or keyword triggering call termination.
 
 #### Pipeline and LLM
@@ -36,27 +39,52 @@ These relate to issues within the AI processing pipeline or the Large Language M
 - `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. Previously `pipeline-no-available-model`.
+- `call.in-progress.error-pipeline-no-available-llm-model`: No suitable LLM was available to process the request during the call.
 
 #### Phone Calls and Connectivity
 
 - `customer-busy`: The customer's line was busy.
 - `customer-ended-call`: The customer (end human user) ended the call for both inbound and outbound calls.
 - `customer-did-not-answer`: The customer didn't answer the call. If you're looking to build a use case where you need the bot to talk to automated IVRs, set `assistant.voicemailDetectionEnabled=false`.
 - `customer-did-not-give-microphone-permission`: The user didn't grant the necessary microphone access for the call.
-- `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.
+- `call.in-progress.error-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.
 - `phone-call-provider-closed-websocket`: The connection with the call provider was unexpectedly closed.
+- `phone-call-provider-bypass-enabled-but-no-call-received`: The phone call provider bypass was enabled but no call was received.
 - `twilio-failed-to-connect-call`: The Twilio service, responsible for managing calls, failed to establish a connection.
 - `twilio-reported-customer-misdialed`: Twilio reported that the customer dialed an invalid or incomplete number.
 - `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. Previously `sip-gateway-failed-to-connect-call`.
+- `vonage-completed`: The call was completed successfully by Vonage.
+- `call.in-progress.error-sip-telephony-provider-failed-to-connect-call`: The SIP telephony provider failed to establish the call connection.
+
+#### Call Start Errors
+
+- `call-start-error-neither-assistant-nor-server-set`: Neither an assistant nor server was configured for the call.
+- `call.start.error-get-org`: Error retrieving organization information during call start.
+- `call.start.error-get-subscription`: Error retrieving subscription information during call start.
+- `call.start.error-get-assistant`: Error retrieving assistant information during call start.
+- `call.start.error-get-phone-number`: Error retrieving phone number information during call start.
+- `call.start.error-get-customer`: Error retrieving customer information during call start.
+- `call.start.error-get-resources-validation`: Error validating resources during call start.
+- `call.start.error-vapi-number-international`: Error with international Vapi number during call start.
+- `call.start.error-vapi-number-outbound-daily-limit`: Outbound daily limit reached for Vapi number.
+- `call.start.error-get-transport`: Error retrieving transport information during call start.
+
+#### Call Forwarding and Hooks
+
+- `call.forwarding.operator-busy`: The operator was busy during call forwarding.
+- `call.ringing.hook-executed-say`: A say hook was executed during the ringing phase.
+- `call.ringing.hook-executed-transfer`: A transfer hook was executed during the ringing phase.
 
 #### Other Reasons
 
+- `database-error`: A database error occurred during the call.
 - `exceeded-max-duration`: The call reached its maximum allowed duration and was automatically terminated.
+- `manually-canceled`: The call was manually canceled.
 - `silence-timed-out`: The call was ended due to prolonged silence, indicating inactivity.
 - `voicemail`: The call was diverted to voicemail.
+- `worker-shutdown`: The worker handling the call was shut down.
 
 #### Unknown