Why does my agent keeps hanging up at 30seconds?
# support
v
Hi there! 👋 I see you're having an issue with your agent hanging up after about 30 seconds. I don't have specific information about recent changes to your "Alex - Dementia Assistant" agent, but I can definitely help explain why your calls are ending with "Silence Timed Out" and how to fix it. Based on the call logs you shared, your agent is hanging up due to the silence timeout feature. This is actually working as designed - by default, Vapi agents have a
silenceTimeoutSeconds
parameter set to 30 seconds, which means the call automatically ends if there's no speech detected for that duration. This matches perfectly with your calls ending at around 30-31 seconds. To fix this issue, you'll need to increase the
silenceTimeoutSeconds
parameter. According to the [Vapi documentation](https://docs.vapi.ai/api-reference/assistants/create-assistant), you can set this value between 10 and 3600 seconds. For example, you could configure it to 60 or 120 seconds to give more time for conversation pauses. Here's how you can adjust this setting:
Copy code
javascript
const assistant = {
  // other configurations
  silenceTimeoutSeconds: 120, // Increase to 120 seconds or your preferred duration
  // other configurations
};
You can also set a custom message to be played when silence is detected using
messagePlan.silenceTimeoutMessage
if you prefer to prompt the user rather than ending the call. Is there anything else you'd like to know about configuring your agent's timeout settings? Source: - [Vapi documentation](https://docs.vapi.ai/api-reference/assistants/create-assistant)
e
No, the agents starts talking and answering, then just hangs up suddenly, repeatedly.
I really need help with this! Please.
n
Are you using Custom SIP or a phone number from VAPI or Twilio ?
n
Interesting.... you got me guessing
s
Hey @Elastic, checking if this was resolved for you.
After discord office hours.
e
@Shubham Bajaj No. It is still not resolved. The call still drops at 30secs. I have evn tried copying/cloning it as another project, same thing. Still not working as before.
s
Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!
e
@User Original call ID: 1) 5b9c8f42-3e46-4368-967a-09c59c230026 2) 89b14349-5254-4523-ad0b-5f3d0436b83a Copy of original: 3) c80b41b9-4a69-4d9e-be35-83b6a7da0c38 4) b7ce26f9-768a-4578-8b22-5fd067b34f14 I even tried making another copy to see if that would make a difference, but same thing for both. Would these 'failures' have anything to do with the Files/Knowledgebase documents? (just puzzled) My previous previous project is working fine though: e94158ed-ce21-47e0-83b4-fda91d6c1da3
s
Hey Lost Seed, you are set your silence timeout seconds to 10. With just a mere silence, the call got ended. Set it to a higher value, then it will work as expected. Let me know how it goes for you. https://cdn.discordapp.com/attachments/1354618487603073109/1355880197861150810/Screenshot_2025-03-30_at_5.53.31_PM.png?ex=67ea8956&is=67e937d6&hm=82dc651acbc5aef82187e2c76308a53c658fda677f900b39cd59a17c609cc414&
e
Upped it to 30 seconds. Will do some more testing and let you know.
@Shubham Bajaj BTW - It would be better if we could "type in the numbers" rather than use the sliders. It's very difficult to get the sliders to a specific number, at least for the Silence Timer setting, but should be able to type in numbers for all of them. Thanks!
@User Guys. I have a demo/pitch for this with a potential buyer on Friday, and it's been over a week now since I've been having this problem. Can someone please help me resolve this!? Thanks!
s
Hi, checking if this is resolved/solved for you?
e
I basically had to create a new one from scratch.
s
Hey, Elastic for call dropping even after setting the silence time to 30 seconds. Could you share the call ID?
e
I don't even know where to find that anymore. I changed the name of the assistant, so everything (even historical) is now showing the new name in the logs. However, I restarted it a few minutes ago and here are the details: Call ID: fa5eead9-9565-4327-a8f9-2acdae6a2fe6 Message: Model sent end token Let me know if this helps. https://cdn.discordapp.com/attachments/1354618487603073109/1358799948518260827/Screen_Shot_2025-04-07_at_9.44.01_AM.png?ex=67f52891&is=67f3d711&hm=ce988a05d81d896a1d165d6231283b1e462a56a82298960ecb33d3ac1253d0fc&
s
Copy code
"silenceTimeoutSeconds": 10
e
ok
s
Ignore my last message.
e
np
s
I am checking with the team why the call ended with a silence timeout as it shouldn't be ending with it.
e
I gave up on that one and create a brand new agent from scratch, then just moved my prompts. The cutoffs were happening for over a week, so had to do something.
The old one is still there tho, the one that kept cutting off.
s
The issue is on our end, and the team is working on it. Sorry for your experience. I've informed the team, and they're working on it.
**update**: team's was on vacation, so they'll make progress by Monday US time.