https://vapi.ai/ logo
Join Discord
Powered by
SILENCE TIMED OUT nonsense error !
# support
j
callid: 3aca342d-7cf6-4463-ae72-d8bd, callid: 3aca342d-7cf6-4463-ae72-d8bd, 56a82b9d-8417-425d-91e1-5c2b5df5514e. AssistantdID: d1a997a7-2d81-4988-b2c8-2d2c986124d9 https://cdn.discordapp.com/attachments/1357671691412836432/1357671691584798932/image.png?ex=67f10dcb&is=67efbc4b&hm=8c128b31e1c8505166170eb8318472c3fe7285fe0dc7f0ec2b3cef481e750bd5&
@Shubham Bajaj @Vapi @Support.Voice-Agent @Vapi Support Bot I was talking and agent hanged up several times on me
v
Hi there! I see you're experiencing "SILENCE TIMED OUT" errors with your Gcollect outbound assistant calls 🔍 I can help explain what this error means and provide some troubleshooting steps, though I can't determine the exact cause for your specific calls without access to the detailed logs. ## What "SILENCE TIMED OUT" means This error occurs when the system detects silence for longer than the configured timeout period. According to the [information I found](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334948523816259604), this typically happens when the agent is waiting for audio input but doesn't receive any for an extended period. ## Possible causes Several factors could be triggering this error: 1. **Network issues**: Network latency or connectivity problems between your system and Vapi's endpoints 2. **Configuration settings**: Your 
silenceTimeoutSeconds
parameter might need adjustment (default is 15 seconds) 3. **Voicemail detection**: If using voicemail detection, the 
machineDetectionSilenceTimeout
might need adjustment (default is 6000ms/6 seconds) 4. **Third-party services**: Issues with transcription services like Deepgram or voice generation services like 11labs 5. **Microphone access**: The system might not be receiving proper microphone input ## Troubleshooting steps ### 1. Check your VAPI configuration Review your VAPI settings, especially those related to timeouts: - Consider increasing the 
silenceTimeoutSeconds
(default is 15 seconds) to 30 seconds, which [helped resolve this issue for another user](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1338586561662419055) - If using voicemail detection, check the 
machineDetectionSilenceTimeout
setting ### 2. Check network connectivity Ensure there are no network issues causing timeouts between your system and Vapi's endpoints. ### 3. Use the call IDs for debugging You can use the call IDs you provided to investigate further:
1. Go to the Vapi Dashboard > Logs > Calls to find detailed information about these calls 2. Check the logs associated with these call IDs to understand what happened during the calls 3. If needed, contact Vapi support and provide these call IDs for them to investigate further ### 4. Verify Assistant ID configuration Ensure the Assistant ID (d1a997a7-2d81-4988-b2c8-2d2c986124d9) is correctly set on your phone number. ### 5. Review Gcollect outbound assistant The Gcollect outbound assistant is designed to [collect user information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344363789184798760) such as full name, email, and phone number. Make sure it's properly configured for your use case. Would you like me to explain any of these troubleshooting steps in more detail? Sources: - [What does the SILENCE TIMED OUT error mean in Vapi?](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334948523816259604) - [What are the possible causes of the SILENCE TIMED OUT error in Vapi?](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1338586561662419055) - [How to troubleshoot the SILENCE TIMED OUT error in Vapi?](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1338586561662419055) - [What is the purpose of the Gcollect outbound assistant in Vapi?](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344363789184798760) - [How to use call details like callid and AssistantdID to debug call issues in Vapi?](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339467226381684789)
Hi there! 👋 I see you're experiencing an issue where your voice agent is hanging up on you multiple times with a "SILENCE TIMED OUT" error, even though you were actively talking. That's definitely frustrating! Based on the information I have, I can help explain what's happening and suggest some solutions to fix this issue. ## What's causing this problem? "SILENCE TIMED OUT" indicates that the call ended because the system detected silence for longer than a configured timeout period. According to the [documentation](https://docs.vapi.ai/calls/call-ended-reason), this can happen for several reasons, even when you're actually speaking: 1. The agent might go silent after a tool call, eventually leading to a timeout 2. There could be issues with voicemail detection settings 3. There might be a handshake problem between your telephony provider and Vapi 4. The silence detection settings might be too sensitive ## How to fix it: Here are some solutions you can try: ### 1. Adjust Silence Timeout Settings Modify the 
silenceTimeoutSeconds
parameter and related settings:
Copy code
json
{
  "silenceTimeoutSeconds": 10 // Increase this value
}
### 2. Check Voicemail Detection Configuration Ensure your voicemail detection settings aren't conflicting with silence timeout:
Copy code
json
{
  "voicemailDetection": {
    "provider": "twilio",
    "enabled": true,
    "machineDetectionTimeout": 30, // Increase this value
    "machineDetectionSilenceTimeout": 5000 // Make sure this is appropriate
  }
}
### 3. Adjust Agent's Speaking Plan According to [user discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336875140990111796), try these recommended settings:
Copy code
json
{
  "startSpeakingPlan": {
    "waitSeconds": 0.8 // Reduce this value
  },
  "transcriber": {
    "endpointing": 300 // Adjust this for Deepgram
  }
}
### 4. Check for Tool Call Issues
The agent may go silent after tool calls. You can suppress tool call messages or improve prompt engineering to ensure the agent continues the conversation. ### 5. Investigate Telephony Provider Issues There might be a handshake issue between your telephony provider and Vapi. Consider contacting your provider to investigate further. Would you like me to provide more specific guidance on any of these solutions? I'd be happy to help you troubleshoot further! Sources: - [Vapi Documentation Call Ended Reason](https://docs.vapi.ai/calls/call-ended-reason) - [Discord Thread Silence Timeout Issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1296852804631265392) - [Discord Thread Agent Speaking Plan](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336875140990111796) - [Discord Thread Tool Call Issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1327662627882795059) - [Discord Thread Voicemail Detection](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344633027925377064)
p
s
it seems like the assistants dont get anything from what is said... i think its related to the transcriber issues
j
the silence timed out is at 113 sec. Whether I give a VONAGE or TWILIO phone nb to this agent, it keeps repeating the first message on and on and doesn't understand ANYTHING I say 🙂
s
same
j
@Sven it's an BUG with VAPI, I keep saving fr language and after page refresh, I keep seeing eng
p
Yes, language dont save atm
s
@Jetsoccer Game yes it is. @Pigeon helped already to #1293690685781839933 over this along others. Emergency alert is already triggered to the dev team ... i think we have to wait for the solution
j
so it's a general bug preventing users from saving agents ? @Sven @Pigeon
s
correct
message has been deleted
p
Its 2 part bug, theres issue with saving, but you can bruteforce it, except for transcriber language
1. Frontend sends old values often, so changes dont save, but you can still save it after pressing publish multiple times, refreshinh, etc 2. Frontend never sends language value, so its never saved, people also could not save thorugh API
j
@Sven @Pigeon I'm guessing it'll take a few hours ?
p
few of something 🙂
minutes, hours, days
Maybe not days 😄
s
hope not
p
j
any news @Sahil @Sven @Pigeon ? 🙂
s
nope ... unfortunately 😭
s
Frontend team are in PST timezone. They should be online any minute now then they will fix it. Sorry for the inconvenience.
s
Thanks for the update @Sahil
s
Fixed, can you check?
s
not working yet
@Arvind @Sahil Still not fixed unfortunately... Are you on it? Any update? Thanks in advance
try change to google or openai ... save and then change back to deepgram... that worked for me ... kinda ... the agents responses are whacky still but the language remains changed
@Arvind Agents working reliably again ... thanks for your effort
j
@Sahil @Pigeon @Sven so it's completely fixed, no need to choose google as voicemail detection ?
s
that i dont know ... i fixed it via the provider change to google and back (nothing to do with voicemail detection IMHO)
try it and let us know plz
p
Marking this ticket as Solved ✅
2 Views
PreviousNext
Powered by