Examples: CallID bb87aa68-de49-49a6-9356-406e7f501714 CallID 697df4b2-88e3-468e-83e5-d08eee1bf08c VAPI dials numbers, waits for speaker to stop speaking, but does not answer. Other calls (such as ca433994-2691-4607-8b6c-92999c558308) seem to work correctly. Any idea what's going on? Same parameters on calls with slightly different prompts (one asks for business hours, one asks for list of services). Thanks!

@Brian @ Testbot.app LemurLabs.ai It sounds like you're experiencing inconsistent behavior with the VAPI calls. Since the issue is not consistent across all calls, it could be related to the specific prompts or the phoneCallProviderBypassEnabled setting. If the bypass is enabled, VAPI won't initiate calls directly, and any issues might be related to the external call handling setup. To assist you better, I would need to check the configuration for each CallID you've mentioned, especially the phoneCallProviderBypassEnabled setting and the phoneCallProviderDetails. Unfortunately, I don't have direct access to call logs or configurations, but I can guide you on what to check: 1. Verify if

phoneCallProviderBypassEnabled

is set to true for the calls that are not working, and compare it with the ones that are working. 2. Check the

phoneCallProviderDetails

for any discrepancies between the calls that might be causing the issue. 3. Review the prompts used in the calls to ensure they are correctly formatted and do not contain any elements that might cause the VAPI to wait indefinitely. If you've already checked these settings and everything seems to be in order, it might be best to reach out to support with the specific CallIDs and details of your configuration for further investigation. Please ask support for more info on this.

I ran another 2 test calls, one failed again ca433994-2691-4607-8b6c-92999c558308 and one worked 873f4c39-f187-4aab-9091-b18fff0520ee

@Brian @ Testbot.app LemurLabs.ai can you be more clear here what exactly is not working for you for this call id ca433994-2691-4607-8b6c-92999c558308?

We place the outbound call with VAPI. The call is answered and the initial greeting is spoken. After that, the VAPI agent never responds and the call ends up timing out. It does not always happen, sometimes it works correctly. The example call ids show the one-sided call.

@Brian @ Testbot.app LemurLabs.ai the model is hallucinating sometimes, it is better to change the model to openai gpt-4o-mini/gpt-4o.

I already changed it to 4o and same thing

can you share the call id for it?

@Brian @ Testbot.app LemurLabs.ai it's probably your mic

There is no mix, it’s one bot calling another. I missed a place where the model was still the old version and that seems to have resolved that issue, but I’m seeing issues where it looks like that analysis doesn’t run and returns n/a… does that mean a true false test failed or it was unable to determine the state? Example: call ID 1bd82ec3-91e3-4b9f-9e96-30fa09f773bf.

@Brian @ Testbot.app LemurLabs.ai can you please use new startSpeakingPlan and stopSpeakingPLan endpointing model because of old endpointing model used in your assistant user was considered speaking continuously.

logs

🔵 20:05:22:559 [user CHECKPOINT] User speech possibly stopping 🔵 20:05:13:967 Talkscriber

user

Still Pushing Chunks...