Elastic
03/27/2025, 12:50 AMVapi Support Bot
03/27/2025, 12:52 AMsilenceTimeoutSeconds 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:
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)Elastic
03/27/2025, 1:01 AMElastic
03/27/2025, 1:23 AMElastic
03/27/2025, 1:26 AMNir Simionovich (CEO@Cloudonix)
03/27/2025, 11:35 AMElastic
03/27/2025, 1:15 PMNir Simionovich (CEO@Cloudonix)
03/27/2025, 9:46 PMVapi
03/27/2025, 11:39 PMVapi
03/27/2025, 11:39 PMElastic
03/28/2025, 11:44 AMVapi
03/29/2025, 2:44 PMElastic
03/29/2025, 6:03 PMVapi
03/30/2025, 12:23 PMElastic
04/02/2025, 10:18 AMElastic
04/02/2025, 11:53 AMElastic
04/02/2025, 12:11 PMElastic
04/02/2025, 11:06 PMVapi
04/06/2025, 12:39 PMElastic
04/06/2025, 12:59 PMVapi
04/07/2025, 1:21 PMElastic
04/07/2025, 1:45 PMVapi
04/09/2025, 12:43 AM"silenceTimeoutSeconds": 10Elastic
04/09/2025, 12:48 AMShubham Bajaj
04/09/2025, 12:48 AMElastic
04/09/2025, 12:48 AMVapi
04/09/2025, 12:54 AMElastic
04/09/2025, 12:55 AMElastic
04/09/2025, 12:56 AMVapi
04/10/2025, 11:14 PMVapi
04/14/2025, 1:40 AM