to reproduce issue: create new assistant from dashboard select 'vapi' in model' save & start call talk to it and assistant does not respond

I've found that other users have reported similar "deafness bug" issues where the assistant doesn't hear them. This could be related to network issues, configuration errors, or problems with the specific assistant. To help troubleshoot your issue, could you share what browser you're using and whether you see any error messages in the browser console when attempting to speak to the assistant? (You can open the console by pressing F12 or right-clicking and selecting "Inspect" then navigating to the Console tab) Sources: - [Discord Channel](https://discord.com/channels/1211482211119796234/1343612796717371393) - [Discord Channel](https://discord.com/channels/1211482211119796234/1296435541952303124)

works fine when another model other than 'vapi' is selected

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!

can you follow the reproduction steps outlined in this post

🟡 01:41:23:518 Couldn't create completion request for provider: vapi @jentic\_ can you try again by creating an new assistant, most likely its one of the chances its failing for you. let me know how it goes for you.

Have you created a new assistant with vapi and tested workflow? @User @Shubham Bajaj

Hey, can you share three call IDs: 1. For which assistant is invalid 2. For which attaching to that workflow the voice is different 3. For which I can compare the voices (the unexpected vs. the expected one)