We have had a recurring issue where our ai has talked with a user and the user claims the ai hung up, in the vapi logs it looks like the AI keeps listening for a while and then times out with "Silence timed out" since this is a recurring issue is this a known bug? call id: ee163a9d-6f44-4ca2-8953-e3722089444a

Hi there! 👋 I don't have specific information about the particular call ID you shared, but I can definitely help with the "Silence timed out" issue you're experiencing. Based on the information I've found, "Silence timed out" is indeed a recurring issue that many Vapi users have reported. While it's not explicitly labeled as a "known bug" in the documentation, Vapi support is aware of the issue and is actively investigating it. [Multiple users have reported experiencing this problem](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1296852804631265392), and support teams have been collecting information to diagnose it. The reason users experience this as a "hangup" is because when the "Silence timed out" error occurs, the call ends abruptly from the user's perspective. This can happen for several reasons: 1. The AI might go silent after a tool call, leading to a timeout that users perceive as a hangup 2. There might be microphone access issues where the Vapi code is waiting for an audio stream that isn't initiating 3. Delays from external services like 11labs can cause timeouts 4. The AI might not be hearing the user due to what some users call a "deafness bug" Some potential causes for this recurring issue include: - Conflicts with voicemail detection settings and other timeout parameters - Issues with transcription services (especially Deepgram) - Network connectivity problems - Incorrect VAPI configuration (particularly the

silenceTimeoutSeconds

parameter) - Problems with third-party services that Vapi relies on To troubleshoot this issue, I'd recommend checking your Vapi logs for error messages, verifying your VAPI settings (especially

silenceTimeoutSeconds

and

machineDetectionSilenceTimeout

), and ensuring there are no network connectivity issues. Is there anything specific about this issue you'd like me to elaborate on? Sources:

looking into it.