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

@mojodaxx It seems like you're experiencing timeouts with the GPT-3.5-turbo model. This could be due to a temporary issue with the model's availability in the specified regions or a network-related problem. Since switching to GPT-4o resolves the issue, it's less likely to be a problem with your script or knowledge base. To address this, you could: 1. Continue using GPT-4o if it's working well for your needs. 2. Retry the request with GPT-3.5-turbo after some time to see if the issue persists. 3. Check your network connection to ensure it's stable and fast enough, as timeouts can sometimes be related to network issues. 4. Review the VAPI documentation or status page for any known issues or maintenance that might be affecting the GPT-3.5-turbo model. If the problem continues and you're unable to determine the cause, please reach out to support for more detailed assistance. They can provide insights into whether the issue is with the model, VAPI, or something else in your setup.

Also, it says warn message which is not an issue

@Sahil - I have looked at the callbacks on my side and it looks like the assistant is triggering the endcall function immediately after the first user response on gpt 3.5