Matheus Borges
04/01/2025, 12:27 PMVapi Support Bot
04/01/2025, 12:29 PMassistant.server.url
2. phoneNumber.serverUrl
3. org.serverUrl
Make sure the correct URL is set at the appropriate level for phone number calls, as noted in the [Vapi API reference](https://docs.vapi.ai/api-reference/assistants/update).
### 3. Check Twilio Configuration (if applicable)
If you're using Twilio:
- Ensure that the webhook URL in Twilio for incoming calls correctly points to the Vapi endpoint
- Review Twilio number settings to make sure there are no forwarding rules causing issues
- Check Twilio logs for any errors related to the calls
### 4. Investigate Vapi Worker System
There might be an issue with Vapi's worker system that prevents the webhook event for call end status from triggering. This has been [reported previously](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333787835144343553) as a potential cause.
### 5. Review Server Logs
Check your server logs for any errors or intermittent downtime that could be affecting the webhook calls. Also verify that your firewall or security settings aren't blocking requests from Vapi.Vapi Support Bot
04/01/2025, 12:29 PMKings Big
04/01/2025, 8:29 PM