The call terminates from assistant side, without any reason. I've setup end call phrases, but it ends without the mention of any of these phrases. Happened multiple times now. Please let me know if there's any fix I can do on my side. Call Ids - 850c0e13-8311-47c4-bb2c-6c35a1eb45db, Mar 19, 2025, 21:00 e071d22d-edc2-46ef-b067-9a8f06f293dc, Mar 19, 2025, 07:07 Let me know if you need more details

Hi there! I understand you're experiencing unexpected call drops from the assistant side, which can be frustrating. I'm unable to provide a specific fix for your particular call drops without examining the exact logs for those call IDs. However, I can definitely help with potential causes and general troubleshooting steps that might resolve your issue. ## Potential Reasons for Unexpected Call Drops There are several reasons why calls might terminate unexpectedly from the assistant side: 1. **Network & Latency Issues**: According to [documentation I found](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341839048817246218), latency issues, network problems, or Twilio configuration issues can cause call drops. 2. **Assistant Errors**: An "assistant-error" can occur within the assistant's logic or processing due to bugs, misconfigurations, or unexpected inputs as mentioned in the [call ended reason documentation](https://docs.vapi.ai/calls/call-ended-reason). 3. **Silence Timeout**: Calls can be dropped if the user doesn't speak for a configured duration, even when the user is actively speaking (suggesting a problem with voice detection). 4. **Configuration Settings**: Incorrect endpointing settings can lead to delays in recognizing silence, and incorrect voicemail detection settings can conflict with

silenceTimeoutSeconds

. ## Troubleshooting Steps Here are some steps you can take to troubleshoot: 1. **Check Assistant Configuration**: - Ensure your assistant ID is correctly configured - Review voicemail detection settings to ensure they don't conflict with

silenceTimeoutSeconds

- Check endpointing settings, as incorrect configuration can lead to delays in recognizing silence 2. **Adjust Timing Parameters**: - Try setting

waitSeconds

to 0.8 in

startSpeakingPlan

- Set Deepgram's endpoint to 300 ms - Modify the transcriber settings to include

"endpointing": 300

3. **Network Checks**:

It is not an assistant error The assistant ends it with their end call message - as the reason for end call silence timeout is configured, but it ends before any silence @Shubham Bajaj can you take a look pls

Your calls ended because the assistant said the end call phrase. I will suggest you remove these phrases from your assistant, and after that, try to make 2-3 test calls, and then you can check if your assistant is working as you have expected. Below, I will drop the CURL request for removing the end call phrases.

```bash
curl -X PATCH "https://api.vapi.ai/assistant/{ASSISTANT_ID}" \
  -H "Authorization: Bearer {API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "endCallPhrases": null
  }'

``` \### Values to Replace: 1\. {ASSISTANT_ID} - Replace with your specific assistant/resistance ID (e.g., "12345678-1234-1234-1234-123456789abc") - This is the unique identifier for your assistant/resistance - You can find this in your VAPI dashboard under the Assistants section 2\. {API_KEY} - Replace with your VAPI API key - This is the authentication token needed to access your VAPI account - You can find or generate this in your VAPI dashboard under Settings > API Keys