I have kept a running server and tried multiple times calling the phone number connected to vapi. With no other changes for a call start the webhook is called inconsistently, sometimes it never sends a post request at the start of the call and sometimes it does, is this a known issue?

Heyajobi882 Thank you for creating the ticket! A member of our team will reach out to you shortly.

This is for inbound calls fyi

message has been deleted

@Vapi that doesnt explain why given an identical setup the webhook sometimes gets called and sometimes doesnt, the server load is not an issue im the only caller and my network is stable

@ajobi882 I understand your concern. If the server setup and network conditions are consistent and stable, but you're still experiencing intermittent webhook calls, this could indicate an issue on the VAPI side or with the way the webhooks are being triggered. Here are a few additional steps you might consider: 1. **Check VAPI Service Status**: Ensure there are no reported outages or issues with the VAPI service that could affect webhook delivery. 2. **Webhook Delivery Logs**: If VAPI provides logs for webhook delivery attempts, review them to see if there are any failed attempts and what the reasons might be. 3. **Redundancy Checks**: Implement redundancy in your webhook handling by setting up a secondary server or endpoint to compare if both experience the same issue. 4. **Contact VAPI Support**: Since the issue seems to be inconsistent and not related to your setup, reaching out to VAPI support with specific details of the call attempts and timestamps can help them investigate the issue further. If you would like, I can guide you through the process of contacting VAPI support or provide further assistance. Would you like to proceed with contacting support, or is there anything else I can help you with?

@Vapi where does vapi provide webhook delivery logs

@ajobi882 VAPI typically provides webhook delivery logs through their dashboard or developer portal. To access these logs, you would normally follow these steps: 1. **Log in to the VAPI Dashboard**: Use your credentials to log into the VAPI dashboard where you manage your account and services. 2. **Navigate to Logs or Reporting Section**: Look for a section in the dashboard that is labeled "Logs", "Webhook Logs", "Reporting", or something similar. 3. **Filter Logs by Date/Time**: If available, use filters to narrow down the logs to the specific date and time range when you experienced the issue. 4. **Review Webhook Event Logs**: Check the logs for any webhook events related to inbound calls and note any errors or failed delivery attempts. If you are unable to find the logs or if VAPI does not provide this feature directly, please reach out to VAPI support for more information on how to access webhook delivery logs or for assistance in troubleshooting the inconsistent webhook calls. Would you like me to assist you with anything else at this moment?

I see the logs why is vapi sending end of call reports to https://hook.us2.make.com/vhvohhsxmo9sdylcdcojb1anrksnri3e whereas I have explicitly configured my server url as something different

@ajobi882 It seems there might be a misconfiguration in the webhook URL settings within your VAPI account. Here's what you can do to resolve this: 1. **Review Webhook Settings**: Go back to the section in the VAPI dashboard where you configure webhooks. Double-check that the URL for the start of call events is set to your server URL and not the

https://hook.us2.make.com/...

URL. 2. **Update Configuration**: If you find that the URL is incorrect, update it to the correct URL of your server where you expect to receive the webhook events. 3. **Save and Test**: After updating the configuration, save the changes and perform a test call to ensure that the webhook is now being sent to the correct URL. 4. **Contact Support**: If after making these changes you still encounter issues, or if the settings were correct but the wrong URL is being called, you should contact VAPI support for further assistance. They can help investigate why the wrong endpoint is being triggered. If you need further assistance with updating your webhook settings or if you'd like me to guide you through contacting support, please let me know.

@Vapi how many places are there for the webhook settings? or is it only vapi server URL? because i already set that

@ajobi882 In most cases, there should be only one primary place to set the webhook URL for VAPI, which is typically in the application or account settings where you configure your VAPI server URL. However, there could be multiple events that you can subscribe to, each potentially having its own URL configuration. Here's what to consider: 1. **Single Configuration Point**: Usually, there's a single configuration point where you set the server URL that VAPI will use for all webhook events related to your application. 2. **Event-Specific URLs**: Some platforms allow you to set different URLs for different events (e.g., call start, call end, etc.). Check if VAPI offers this and ensure that all event URLs are set correctly. 3. **Application-Level vs Account-Level Settings**: There might be settings at both the application level and the account level. Ensure that the correct URL is set in the right place. 4. **Multiple Applications**: If you have multiple applications within your VAPI account, each application might have its own webhook settings. Ensure you're updating the correct application. 5. **Documentation Review**: Review VAPI's documentation to understand how webhook URLs are managed and whether there are multiple places or levels where they need to be set. If you've confirmed that the server URL is set correctly in all the necessary places and you're still experiencing issues, it's best to reach out to VAPI support for a more in-depth investigation. Would you like any further assistance with this matter?

@Vapi so in summary the vapi webhook is sending webhook calls to the incorrect url, not the one specified in my server url configuration

@ajobi882 Yes, that's correct. If VAPI is sending webhook calls to a URL different from the one you have specified in your server URL configuration, it indicates a misconfiguration or an issue on the VAPI side. Here's what you should do: 1. **Double-Check Configuration**: Verify once more that the server URL is correctly set in the VAPI dashboard or configuration file. 2. **Contact VAPI Support**: Since the issue persists despite the correct configuration, it's important to contact VAPI support. Provide them with the details, including the URL you have set, the incorrect URL where the webhooks are being sent, and any relevant logs or timestamps. 3. **Investigation Request**: Ask the support team to investigate why the webhooks are not being sent to the configured URL and to provide a resolution. If you need guidance on how to contact VAPI support or require any additional assistance, please let me know.

@ajobi882 could you share your ORG_ID so I can take a look?

hey Shubham sorry meant to close this i replied in the other related thread and the issue is resolved