Rafal Kwiatkowski
06/05/2024, 8:48 AMVapi Support
06/05/2024, 8:48 AMVapi Support
06/05/2024, 8:48 AMsilenceTimeoutSeconds
setting in your assistant's configuration. This setting determines how many seconds of silence the system will tolerate before ending the call. By default, this is set to 30 seconds, but if there are pauses in the conversation that exceed this limit, it could cause the call to end prematurely [(1)]() .
Additionally, ensure there are no endCallPhrases
inadvertently set in a way that might be causing the call to end when specific phrases are spoken by the assistant.
You might want to check and adjust these settings in your assistant's configuration through the Vapi dashboard or directly via API. Here’s how you might typically update these settings in your assistant configuration to handle this issue better:
json
{
"silenceTimeoutSeconds": 60, // Increasing the timeout to 60 seconds
"endCallPhrases": [] // Ensuring no unintended phrases are triggering a call end
}
If adjustments to these settings do not resolve the issue, it could be related to other factors such as network interruptions or configuration errors not covered directly in the provided documentation. In such cases, reviewing logs available in your dashboard might provide more insights into what is occurring at those termination moments [(2)]() .
For detailed steps on how to adjust these settings, you may refer to the creation and update assistant endpoints documentation [(1)]() .Vapi Support
06/05/2024, 9:15 AMVapi Support
06/05/2024, 10:00 AM