@Omogen I'm sorry to hear that you're experiencing issues with the Answering Machine Detection (AMD) requests resulting in 404 responses. This typically indicates that the resource you're trying to access is not found on the server. There could be several reasons for this, such as an incorrect URL, the resource being removed, or an issue with the server configuration. To help resolve this issue, please ensure that: 1. The URL you're using is correct and corresponds to the API's endpoint for AMD. 2. The

call_id

and

org_id

parameters are accurate and correspond to valid entities in the system. 3. There are no service outages or known issues with the VAPI platform that could be affecting the AMD feature. If you've verified all of the above and the issue persists, it would be best to contact support with detailed information about the requests and any error messages you're receiving. They will be able to provide more specific assistance and investigate the issue further. If you need me to do anything else for you, please let me know!

You can continue this conversation by mentioning me in the message.

Got another one : 870d521b-4d16-45f7-8d42-7de6b2bbb0eb

(Can't see any twilio message in the logs)

Hi again ! Have you found an explanation ? Should I change sth in the config ? I also have a more general question : do you process refunds for calls with Vapi-related errors ? e.g. 4-minute calls with voicemail

@Omogen If failed to detect voicemails because of Vapi API or outage then yeah can help you on this.

> Hi again ! Have you found an explanation ? Should I change sth in the config ? There was an outage yesterday, so I suggest try making few calls and defenatiely it will work!!