I have an agent that I've provided a URL to send the POST request of end-of-call-report but it doesn't show to be sending any request or executing the tool at the end of the call. (I've selected end-of-call-report under Server Messages options too). My assistant ID is: 6ddabe85-2d09-464a-94a3-f85946fddcee Even after reviewing the messages on the call logs at the very end is not showing the execution of the end-of-call-report. I'm not sure if its becuase I'm triggering the call through an initial HTTP request (https://api.vapi.ai/call/phone) with some JSON parameters. Or because of the model I'm using. Any help would be greatly appreciate it, thanks!

@luisson I'm here to help! It sounds like you've set up everything correctly by selecting the end-of-call-report under Server Messages options and providing a URL for the POST request. Since you're not seeing the expected POST request, let's go through a checklist to troubleshoot the issue: 1. **URL Validity**: Ensure that the URL provided is correct and accessible from the server where the assistant is hosted. 2. **Server Configuration**: Verify that your server is configured to receive POST requests and there are no firewalls or security settings that might be blocking the incoming requests. 3. **Call Logs**: Review the call logs to confirm that the call is reaching the 'ended' status, which triggers the end-of-call-report. 4. **Assistant Configuration**: Double-check that the assistant ID is correct and that the assistant is configured to send the end-of-call-report. 5. **JSON Parameters**: Make sure that the JSON parameters you're using to trigger the call are correctly formatted and include all necessary information. 6. **Model Compatibility**: Confirm that the model you're using supports the end-of-call-report functionality. If after going through this checklist everything seems to be in order, and you're still not seeing the POST request, it might be an issue that requires further investigation from the support team. Please provide any additional details that you think might be relevant, such as the exact JSON parameters you're using to trigger the call, or any error messages you might be receiving. If there's no sensitive information, you can share the JSON parameters here, and I can help you review them. If the issue persists, I would recommend reaching out to the support team for more in-depth assistance.

@Vapi - So I've tested the URL, and it works totally fine. (https://201.151.150.189:5678/webhook/vapi-callback) - I've configured my server to receive POST request with a response code 200 as suggested - Reviewing the Call logs I see a "[ERROR] end-of-call-report Server URL Error: self-signed certificate". What type of certificate must be used in order to receive the request?

@luisson The error message you're seeing, "self-signed certificate," indicates that the SSL certificate used by your server is not trusted by the client making the request, in this case, the VAPI service. To resolve this issue, you should use a certificate issued by a trusted Certificate Authority (CA). Here's what you can do: 1. **Obtain a Trusted SSL Certificate**: You can get a trusted certificate from a well-known CA or use a free service like Let's Encrypt to generate a certificate for your domain. 2. **Install the Certificate**: Once you have the certificate, install it on your server following the instructions provided by your server's documentation or the CA. 3. **Ensure Proper Configuration**: Make sure that the certificate is correctly installed and that your server is configured to present the full certificate chain if required. 4. **Test the Certificate**: You can use online tools like SSL Labs' SSL Server Test to verify that your server is correctly configured and that the certificate is recognized as valid. After you've installed a trusted SSL certificate, try sending the end-of-call-report again. The VAPI service should now be able to communicate with your server without encountering the self-signed certificate error. If you continue to experience issues, please reach out to support for further assistance.

share call id.

3b660a6b-554c-4a38-bc93-b80c78b7b50c