Test log: Provider "vapi", "openia", and "Google" "voicemailDetection": { "provider": "vapi", "beepMaxAwaitSeconds": 8 } My number provider is Twilio. Do you think it's necessary to change it? It's identified that only on iPhones is it capable of not answering the call so it knows it's a voicemail. On Android, however, it takes 1 to 3 seconds to identify and end the call. The logs show that on Android, all calls that last that length of time have the "Ended Reason" result of "Customer Ended Call," when it is and should be "Customer Did Not Answer." Additionally, they are counted as "Successful" calls, which makes no sense. Call iD iPhone: db06996a-6f0a-41d2-b4b8-60d8628727f9 1b3c7f45-1d4a-4c16-833a-765be9e7e856 1bda66be-5d9e-4789-acfb-f887c5d9dcbd Call iD Android: 9ec5df68-533d-4a59-abe9-50fba9af718b df6bbc99-ba82-4bfa-81eb-557022224d5b 0acb9671-0973-4f3e-a109-7827a7b9f7bb It's not possible that you need to answer a call to identify it, especially when you're already doing it. configuration, taking into account that each second is charged by both Vapi and the number provider, Twilio. These costs can be significant for bulk calls. I don't think the service is cost-effective, charging for each call attempt, given that Twilio also charges per second. Why is there a difference in detection behavior between calls to iPhone and Android under the same configuration? Is it a signaling/early media issue that doesn't work the same way for Android? Why are Android calls that end in 1-3 seconds due to machine detection incorrectly logged as Customer Ended Call and Successful? How can this be corrected? Is there any alternative configuration or recommendation to minimize/eliminate connection time on Android, or at least ensure that the termination reason and status are correctly logged?

Try adjusting your voicemail detection configuration to use Twilio as the provider with optimized parameters:

json
"voicemailDetection": {
  "provider": "twilio",
  "enabled": true,
  "machineDetectionTimeout": 5,
  "machineDetectionSpeechThreshold": 2400,
  "machineDetectionSpeechEndThreshold": 1000,
  "machineDetectionSilenceTimeout": 3000
}

This configuration reduces detection time while maintaining accuracy, which should help minimize connection costs and improve logging accuracy for Android calls. Sources: - [Discord discussion on voicemail detection](https://discord.com/channels/1211482211119796234/1334597630235512956) - [Vapi documentation on voice mail detection](https://docs.vapi.ai/phone-calling/voice-mail-detection)

I'm sorry, but I've been using that setup for the past month and have experienced very high charges for calls that aren't identified as voicemail. Additionally, the calls aren't detected and are cut off before the user can.

Hey Nicolas Bcortes, I completely understand your frustration and pain here. Allow me some time to go through the complete calls logs and our past developments or discussions in other threads, and get back to you with some resolutions and hopefully more information.