VAPI•2y ago

Call getting cut randomly in the end due to pipeline-error-openai-llm-failed.

Call id - 30910160-ca7b-4057-bf99-eee61de32ed8, 75f80da6-eeb0-4c87-84ec-dab66c9f42ec
My call works normally until the end where the call just randomly ends due to the error mentioned above. It was working fine until today.

Vapi•7/28/24, 6:08 PM

@anishkasi
I'm sorry to hear that you're experiencing issues with your calls ending unexpectedly. Based on the errors you've mentioned, it seems there could be multiple factors at play. Let's address each one:

Customer did not give microphone permission: Please ensure that you have granted the necessary microphone permissions in your browser or app settings. This is crucial for the call to function properly.
Phone call provider closed websocket: This could be due to network issues or an unexpected error with the call provider's service. Please check your internet connection and try again. If the problem persists, there might be an issue with the call provider that needs to be resolved on their end.
Twilio failed to connect call: If you're using Twilio and it failed to establish a connection, this could be due to a service disruption or a misconfiguration in your Twilio setup. Please check Twilio's status page for any ongoing issues and verify your Twilio configuration.

If you've checked all the above and the problem still occurs, it might be best to reach out to the support team for further assistance. Would you like me to help you with anything else at this moment?

Vapi•7/28/24, 6:08 PM

You can continue this conversation by mentioning me in the message.

VVapi You can continue this conversation by mentioning me in the message.

VapiAPP•7/28/24, 6:08 PM

Got it. Tagging @Vapi Team for additional help.

safe-amethyst•7/29/24, 11:03 AM

We are also experiencing this kind of errors in almost every calls: b7927aab-fe97-410c-b171-efef0f95a1f0, f563b52c-366f-4659-9a46-9a5e791aa0c7, f7764c7b-2e74-43c3-b9bb-95a1ccb62899, 2d8339b5-bc9a-4b84-aab2-dfb0c3fc8f84, etc

safe-amethyst•7/29/24, 11:10 AM

It seems related to a function call we trigger at the beginning of the call. Maybe this is a race condition

endless-jadeOP•7/29/24, 4:41 PM

How did you resolve it?

living-lavender•7/29/24, 4:49 PM

Fix would be deployed in 45 minutes.

@anishkasi

endless-jadeOP•7/29/24, 4:53 PM

Awesome thanks!

Call getting cut randomly in the end due to pipeline-error-openai-llm-failed.

Similar Threads

Similar Threads

Similar Threads