So I use make to make certain calls outbound and when I do the data from the call doesn’t send to the url in the messaging - server url it used to work but no longer. So I use an https request in make to use vapi to make a call but after a call I never see the webhook or server irk sending the data. Also in the webhook section of vapi it gives me one day and the screen is t scrollable, how can I test when your system won’t give me data anymore, if I make a manual outbound call in your system or on your website it works and the webhook fires and goes but done via https://api.vapi.ai/call/phone and after the call the end of call report doesn’t send to my server url

This is a known intermittent issue with Vapi outbound API calls where webhooks (like end-of-call-report) sometimes do not fire. Actionable step: Please review any recent changes to your SIP trunk or webhook configurations, as these are common causes. If the issue persists, consider reaching out to Vapi support with your callId for further investigation. Reference: [Vapi Discord support thread](https://discord.com/channels/1211482211119796234/1372358449761091584) Source: - [Vapi Discord support thread](https://discord.com/channels/1211482211119796234/1372358449761091584)

Hi Garret (eWebify), To troubleshoot the issue where the end-of-call-report webhooks are not being sent when using the Vapi API for outbound calls, here are a few steps you can take: 1. Review SIP Trunk Configuration: - Ensure there have been no recent changes in your SIP trunk configuration that could interfere with the webhook triggering process. 2. Verify Webhook Configuration: - Double-check the webhook settings in your Vapi dashboard. Ensure your server URL is correctly configured to receive the

end-of-call-report

and that server messages include this webhook type. 3. Test with Webhook.site: - Use [webhook.site](https://webhook.site) to test if the webhook events are being sent. This can help determine if the problem lies with Vapi or your server reception. 4. Check for Authentication Requirements: - Ensure your endpoint does not require additional authentication or headers that might be preventing Vapi from sending the webhooks successfully. 5. Manual Call Testing: - Since manual calls from the Vapi dashboard successfully trigger the webhook, compare the settings used there with those in your API call setup. 6. Check Vapi Dashboard Logs: - Verify if there are any error logs or messages in the Vapi dashboard under the Webhooks section that could indicate what might be going wrong. If the issue persists and none of these steps resolve it, you might want to consider reaching out to Vapi support directly with the relevant

callId

for further investigation, ensuring to include details of your attempts and any error logs available.