Live answers marked AA
Quiet or hesitant greetings are dropped as machines.
GoAutoDial runs on the same Asterisk AMD as ViciDial — and inherits the same mistakes. AMDY slots in alongside it with the same extension-based install.
detection starts after answer
calls lost when AMDY is unreachable
free detections to evaluate
GoAutoDial’s detection is Asterisk’s timing-based AMD, so it struggles with the same real-world answers.
Quiet or hesitant greetings are dropped as machines.
Short voicemails slip through as live answers.
Long analysis windows leave people waiting in silence.
Add the AMDY step to a copy of your AMD extension and point the campaign at it. Native AMD() stays in place as the fallback.
Read the API docsexten => 8370,n,EAGI(amdy.agi,KEY)
exten => 8370,n,GotoIf($["${AMDSTATUS}" = "FALLBACK"]?native)
exten => 8370,n(vdamd),AGI(VD_amd.agi,${EXTEN})
exten => 8370,n,Hangup()
exten => 8370,n(native),AMD()
exten => 8370,n,Goto(vdamd)The dialer still dials and your carrier still carries the call. The decision just gets better.
Keep GoAutoDial, your campaigns and your carriers.
Detection starts about 125 ms after answer.
Test one campaign, compare, then switch the rest.
50,000 free detections. Point one campaign at it and compare.