I have this configuration! "voicemailDetection": { "provider": "twilio", "voicemailDetectionTypes": [ "machine_start", "machine_end_beep", "machine_end_silence", "unknown", "machine_end_other" ], "enabled": true, "machineDetectionTimeout": 4, "machineDetectionSpeechThreshold": 2000, "machineDetectionSpeechEndThreshold": 1000, "machineDetectionSilenceTimeout": 3000 } It is not detecting the voicemail and the call continues and then ends up charging only for the silence space The user speaks or answers and still hangs up the call after reaching 4 seconds It does not detect the rejected call, the voicemail or the voice of the answering machine The idea is that it detects these types of things so as not to have additional costs for silence spaces and not to hang up when it has answers. Help! - Here is the example of the voicemail, it does not hang up and they charge for the call: Call ID : 5bb693ac-73a5-4bb0-8a83-c07c4279f85a - Here is the example of the user answering, it hangs up and they charge for the call Call ID : 7410eb00-21ac-4379-8084-673163a4da9f Call ID : 4e1a9237-f85b-4eb9-95f7-23666f518741

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

@NicolasBcortes It sounds like you're experiencing some issues with the voicemail detection configuration. Let's address each point to ensure that your system works as intended and avoids unnecessary costs: 1. **Voicemail Detection Configuration**: The

machineDetectionTimeout

is currently set to 4 seconds, which might be too short to accurately detect voicemail or machine answers. This could be why the system is not detecting voicemail and is hanging up prematurely when the user speaks. 2. **Detection Types**: You've listed several detection types, including

machine_start

, which is not part of the standard configuration provided in the context. If

machine_start

is not supported by the provider, it should be removed from the configuration. 3. **Speech Thresholds**: The

machineDetectionSpeechThreshold

and

machineDetectionSpeechEndThreshold

values seem to be set quite low. If the system is not detecting speech correctly, you might want to adjust these thresholds to better match the characteristics of the speech you're trying to detect. 4. **Silence Timeout**: The

machineDetectionSilenceTimeout

is set to 3000 milliseconds (3 seconds). If this is shorter than the typical silence period in the voicemails you're dealing with, you may want to increase it. Here's what I suggest: - Increase the

machineDetectionTimeout

to give the system more time to detect voicemail or machine answers. - Ensure that all

voicemailDetectionTypes

are supported by your provider. - Adjust the

machineDetectionSpeechThreshold

and

machineDetectionSpeechEndThreshold

to better match the speech patterns of your calls. - Consider increasing the

machineDetectionSilenceTimeout

if the current setting is too short. Would you like me to assist you with updating these settings? If so, please provide the new values you'd like to set for each parameter.

All calls that exceed 4 seconds, whether they answer, do not answer or go to voicemail, they are charged!

@NicolasBcortes For your information, only the first call ID is relevant in comparison to the other two call IDs. Regarding voicemail detection, it is essential to configure your first message mode so that the assistant waits for the user to speak. If necessary, consider extending the assistant's speaking time. I encourage you to experiment with setting the first message mode to wait for user input and share your feedback on the outcome. Additionally, to gain further insights into voicemail, please refer to this document: https://docs.vapi.ai/documentation/advanced-concepts/calls/voice-mail-detection

My new configuration: "voicemailDetection": { "provider": "twilio", "voicemailDetectionTypes": [ "machine_start", "machine_end_beep", "machine_end_silence", "unknown", "machine_end_other" ], "enabled": true, "machineDetectionTimeout": 4, "machineDetectionSpeechThreshold": 2400, "machineDetectionSpeechEndThreshold": 1000, "machineDetectionSilenceTimeout": 2000 } Call ID : 020c985b-2ff6-4634-a449-35ab786b0938 Call ID : bf4839b4-42ab-4e3c-945b-5de2b1a26161 Even so, it still doesn't detect the beep or the voicemail voice! Additionally, the call lasts 3 seconds and they charge me 0.01 for each type of calls like these, which are rejected or not answered! How can I solve it?

json
 "startSpeakingPlan": {"smartEndpointingEnabled": true},

@NicolasBcortes You need to set the first message mode to 'assistant waits for the user' and set smartEndpointingEnabled to false, as it only works for English transcriptions. Also, set startSpeakingPlan.waitSeconds to 0.8 to give the assistant enough time to speak. After making these changes, the assistant will wait for the user to speak. Meanwhile, Twilio voicemail will activate, allowing it to detect if it's voicemail. After that, it should work as expected. You might need to tweak a few parameters, but it's not 100% perfect. https://cdn.discordapp.com/attachments/1334385998423130174/1335868600153669685/Screenshot_2025-02-03_at_12.34.41_PM.png?ex=67a1bc15&is=67a06a95&hm=d9c2f30eaf8c30200f5ff387a3829167db8d716c10828ae23c4b02214ad63536&

Perfect, I'm going to test this new configuration and tell you how to find the solution!

@NicolasBcortes I'm closing this ticket for now, If this comes up again we can continue on this and if something new comes up then please create a new ticket.

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 1. 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 2. 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

@NicolasBcortes Sorry for asking you to do some extra work, can you please create a new #1211483291191083018 ticket to get your ticket under SLA?

Let me know your thoughts on this.