Hello good day I keep noticing that the voicemail detector for calls is still not detected or activated anywhere! I have to put:

"machineDetectionTimeout": 4

, To obligatorily hang up the calls that go to voicemail or are not answered because the system does not detect them, it takes them as a call and charges them I even have the tools

"model": {
    "tools": [{ type: "voicemail" }]
  }

I have a tool to hang up the call I have the `"voicemailDetection`" configuration with its respective validations I have the following problems that I want to solve Hang up unanswered calls or those that go to voicemail so that vapi does not take it as a real call and ends up charging for the call. To solve that I have the validation` {"machineDetectionTimeout": 4`} for which I have the following problem The call hangs up very quickly so some clients do not have time to speak, some even speak and the AI ​​manages to answer but it hangs up. Call Los ids: > call rejects or voicemail: >

5ea133cf-1ee2-48cf-b05e-bc3c0b1e081d
> 5ea133cf-1ee2-48cf-b05e-bc3c0b1e081d
> 35e3ccb3-c5d4-456f-90f1-e990fb81a4bf

> Call cut off: >

40564fea-077c-4cb9-89d5-8274e90dd2e6
> 4b453cf3-0e31-4ad2-9098-527c0e0c4474
> 4d2ecb8f-8b5d-4037-9c1a-0c681cf4d4a7

For calls that hang up in between, it is because Twilio identifies them as customer calls did not answer. For voicemail failures, it is because Twilio AMD are not functioning properly for non-English languages, as per my interpretation. Please give me some time to look for other call IDs that might have similar issues.

Let me explain better, the calls that are hanging by themselves are because it is not possible to detect that they are talking and by having the "machineDetectionTimeout" property it hangs after reaching second 4, of course I have this validation so that all unanswered calls that go to voicemail are hung up.

Your current issue stems from setting a very low `machineDetectionTimeout`: 4, which causes two problems: \- Legitimate calls are being cut off because 4 seconds is too short for proper detection \-The system doesn't have enough time to properly distinguish between voicemail and human answers I recommend the following configuration: { "voicemailDetection": { "provider": "twilio", "enabled": true, "machineDetectionTimeout": 30, "machineDetectionSpeechThreshold": 2400, "machineDetectionSpeechEndThreshold": 1200, "machineDetectionSilenceTimeout": 5000, "voicemailDetectionTypes": \[ "machine_end_beep", "machine_end_silence", "machine_end_other" \] }, "model": { "tools": \[ { "type": "voicemail" } \] } } This configuration: \- Uses Twilio's default 30-second timeout which is more reliable \- Includes both AMD and model-based detection \- Properly handles different types of voicemail detection signals

I understand you, I want to clarify that I use "machineDetectionTimeout" precisely because of the problem that it doesn't detect or hang up the call! If I remove it, all the calls I make will be charged, I don't think it's a good thing that they last more than 5 seconds just to "detect" that they didn't answer and still have a cost for each call! Even so, I will try the implementation you tell me! I hope I don't have the problem of costs for calls that don't answer or go to voicemail.

@NicolasBcortes let me know how it goes for you.

Yes, I've been trying it, but I have the same problem! Still nothing, the call hangs up when it is rejected or goes to voicemail and even so I have a cost for these calls when I shouldn't have because the call was never answered How can you help me? I've already tried everything you've told me and I still have the same problems! The problems I have and want to solve are: -It doesn't detect rejected calls or voicemail -I'm having costs for each call because it doesn't identify the previous problem! \

@NicolasBcortes You will have the minimal cost for voicemail detection you know spinning up call workers and voice mail detection stuff consume resources.

Hi, I really understand the costs of voicemail detection, the problem is that it is not working and it is not being activated, that is why I have higher costs than I should. The main problem is that it cannot be identified in any way that it goes to voicemail or it is not answered!

@NicolasBcortes Try Google Voice Mail. I've heard it works well. Let me know how it goes for you. https://cdn.discordapp.com/attachments/1342555558984814653/1348962789686902845/Screenshot_2025-03-11_at_8.09.51_AM.png?ex=67d15eff&is=67d00d7f&hm=7e1eb61f496789542fd6f8e7925f58ed8d360a4c3e121426421684785e57da81&

Great! I hadn't seen that voicemail menu! I'll try it out and let you know how it goes with the tests.