Request for Investigation: Failed Voicemail Detect...
# support
k
Hi Team, Could you please provide detailed information regarding the failed voicemail detection for the following call ID: 019d8b82-195f-7000-8c02-95bdf311606e? Specifically, we would like to understand: > The reason for the failure > Any error codes or logs associated with this call > A brief explanation of what caused the issue
c
hey, looked into call
019d8b82-195f-7000-8c02-95bdf311606e
— here's exactly what happened and how to fix it. what happened your assistant is configured to detect voicemail using vapi's audio-based detection. when the call connected, vapi started listening to the audio and passed it to the voicemail classifier at two points: • ~7 seconds into the call: classifier ran, did not detect voicemail • ~12 seconds into the call: classifier ran again, still did not detect voicemail because neither check came back as "voicemail", the
voicemailMessage
was never played and the call was never handed off to voicemail handling. the assistant just kept waiting. at ~27 seconds, the call hit your silence timeout and ended with
silence-timed-out
. no voicemail was left. how to fix it you need to tune your
voicemailDetection
config to sample earlier and more frequently so the classifier gets more chances to catch the greeting. here's your current config and a recommended update: current:
Copy code
"voicemailDetection": {
  "provider": "vapi",
  "type": "audio",
  "backoffPlan": {
    "startAtSeconds": 5,
    "frequencySeconds": 5
  },
  "beepMaxAwaitSeconds": 30
}
recommended:
Copy code
"voicemailDetection": {
  "provider": "vapi",
  "type": "audio",
  "backoffPlan": {
    "startAtSeconds": 2,
    "frequencySeconds": 2
  },
  "beepMaxAwaitSeconds": 30
}
if you're still seeing
silence-timed-out
after the config update, let me know and we can look at whether the specific carrier/number has unusual voicemail behavior.
k
The SIP provider logs confirm that a voicemail message was left by the user. The call should have been marked as "voicemail" rather than "silenced timeout". Please help troubleshoot why this is being incorrectly classified. https://cdn.discordapp.com/attachments/1493562838294462545/1493835339498917918/9ce311f8-f6c3-4280-9273-dd6df5995205.wav?ex=69e06a13&is=69df1893&hm=c49eb9859edf8b1ee14927e532f6681eebf4b66855f7c21b8edc359ad1b71643&
Any update on this?
c
Hi, How often this issue is occurring? If its happening a lot can you share more call Ids