Vapi is the Voice AI platform for developers.

Vapi AI

Details:

Call ID: 4e8eec39-03dd-4192-9c96-5bec816a9292
When: From 1:36 to the end of the call due to silence timeout.
Expected Behavior: The voice agent should continue to pick up user input and proceed with the conversation.
Actual Behavior: The agent became unresponsive, and the logs showed repeated "User speech possibly stopping" and "User speech possibly starting" entries.

Please help us investigate and provide a resolution.

<@1159451189524570226>
I'm sorry to hear that you experienced an issue with the voice agent becoming unresponsive. It seems like there might have been a problem with the voice activity detection which led to the agent not properly recognizing when the user was speaking.

To assist you further, I would need to check the system logs and settings related to voice activity detection and speech recognition for the call ID you've provided. However, as a support bot, I don't have direct access to system logs or settings.

Please reach out to the technical support team with the call ID and the details you've provided here. They will be able to investigate the issue by reviewing the logs and the system's configuration to determine why the voice agent was unresponsive and how to prevent this from happening in the future.

If there's anything else I can help you with, please let me know!

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

<@1159451189524570226> The issue arose due to a conflict between the endpointing and idle timeout detection pipeline, which I believe was triggered before the bot ceased speaking, ultimately resulting in idle messages. Can you try, attempt another call and inform me of the outcome. I am quite certain this is one of the possibilities that may have occurred.

<@865531204849500190> so far the problem has not been reproduced, but I will report if it happens again

Hey! Thanks for the update! If the issue pops up again or if you have any more questions, just let me know!