How to configure GoAutoDial v4 for low-latency answering machine detection

The limits of native GoAutoDial detection

GoAutoDial v4 provides a web interface on top of ViciDial, Asterisk, and Kamailio. Under the hood, outbound campaign routing defaults to standard Asterisk silence detection modules. This legacy approach measures initial silence, greeting length, and noise spikes. It makes a binary guess based on sound duration rather than speech structure.

When a prospect answers with a quiet hello or pauses before speaking, legacy silence detection routinely misclassifies the call as a machine. The dialer hangs up or sends the call to an automated message. You lose live leads, generate ghost calls, and burn through numbers as prospects flag silent calls as spam. Modern call screening features on smartphones compound this issue, as explored in our guide on how call screening broke legacy dialer AMD.

Replacing standard silence detection with stream audio analysis fixes these drops. AMDY begins audio processing within 1/8 of a second, evaluating acoustic fingerprints rather than waiting for multi-second pauses. The service achieves 99% accuracy in separating humans from automated systems while catching carrier false answer supervision (FAS) before billing timers start.

Step 1: Account setup and API keys

Integrating AMDY with GoAutoDial does not require rebuilding your server kernel or replacing Kamailio. Sign up at amdy.io to claim 50,000 free detections for initial testing. Once registered, grab your deployment key from the account dashboard.

AMDY supports native one-line installation scripts for Asterisk and ViciDial bases, as well as a direct WebSocket API for custom dialer flows. For a standard GoAutoDial v4 deployment, the native installer places the audio socket daemon directly alongside Asterisk.

Step 2: Modifying the Asterisk dialplan in GoAutoDial

In GoAutoDial v4, campaign settings route calls through specific dialplan contexts inside the Asterisk configuration files or through the administration interface under Telephony Settings. You must replace the call to standard silence detection with the AMDY audio socket routine.

Open your dialplan configuration or use the GoAutoDial admin console to update your outbound routing context. Locate the extension block handling outbound campaign routing and insert the AMDY execution call immediately after the channel answers. Instead of passing control to internal Asterisk functions, stream the live channel audio directly into the analysis socket. The engine evaluates incoming PCM audio streams in real time. If you have previously followed our walkthrough on how to replace stock ViciDial AMD with stream audio detection, the GoAutoDial setup follows a similar underlying logic due to shared Asterisk components.

Step 3: Setting response handling and flags

Once the audio stream opens, AMDY returns an instant classification signal back to the Asterisk dialplan variable space within 1/8 of a second. The evaluation sets channel variables that control where GoAutoDial sends the call:

• HUMAN: The dialer instantly connects the channel to a live agent in the GoAutoDial agent screen without measurable delay or dead air.
• MACHINE: The dialer executes your campaign machine handling rule, such as dropping an automated audio message or terminating the leg.
• FAS: Carrier false answer supervision occurs when the carrier sends an answer signal before the remote party picks up. AMDY flags this condition so your routing logic registers the false connection and prevents wasted carrier spend.

Ensure your GoAutoDial campaign configuration under Campaign Settings has answering machine detection enabled, but configured to custom routing so Asterisk does not run legacy background filters simultaneously.

Step 4: Tuning low-latency audio pipelines

Sub-second accuracy depends on immediate audio delivery. Configure your GoAutoDial SIP trunks to negotiate uncompressed audio codecs like G.711u or G.711a first. Transcoding compressed formats like G.729 adds CPU overhead and introduces 20 to 40 milliseconds of latency before the audio socket receives frames.

Verify that your firewall allows outbound WebSocket connections if you opt for external API integration rather than the local native agent. Local socket installations pass raw PCM audio over local sockets directly to the machine learning engine, keeping network overhead minimal.

Step 5: Campaign verification and metrics

Run a test campaign with a small lead list using live test numbers and voicemail targets. Monitor your GoAutoDial real-time report screen alongside the console log output in Asterisk.

Check the timing between the answer signal and the agent connection timestamp. Standard silence detection typically introduces long silent delays while waiting for greeting pauses. With AMDY configured, agent bridges occur almost instantly upon answer, eliminating the ghost call signature that causes prospects to hang up or report caller ID numbers.

Review the AMDY dashboard to inspect detection accuracy metrics, carrier FAS flags, and total detection counts. With 50,000 free detections included upon sign-up, you can fully validate accuracy across live outbound calls before committing to production scale.