VICIdial Error: AMD Timeout — Cause & Fix

Error Summary

Error Message

AMD Timeout

Severity

Warning

Component

Asterisk

What Causes This Error

The Asterisk AMD application is taking too long to make a human/machine determination and timing out before a decision is reached. The call may be dropped or incorrectly routed as a result. Caused by wait_for_silence set too high, noisy carrier audio preventing silence detection, or AMD analysis window set too wide.

How to Fix It

  1. 1
    Check AMD configuration: grep AMD /etc/asterisk/extensions.conf
  2. 2
    Review AMD timeout values in VICIdial: Admin > Campaigns > AMD settings
  3. 3
    Reduce wait_for_silence value (try 1500ms if currently higher)
  4. 4
    Check for carrier audio issues: enable verbose logging and listen to AMD failures
  5. 5
    Adjust Asterisk AMD application parameters in dialplan: AMD(initialSilence, greeting, afterGreetingSilence, totalAnalysisTime)
  6. 6
    Test AMD with recordings of known humans and machines to calibrate
  7. 7
    Consider ViciStack AMD module for AI-powered AMD that handles edge cases better

How to Prevent It

Tune AMD parameters specifically for your carrier's audio profile. Monitor AMD false positive and false negative rates weekly. Test AMD performance after carrier changes. Maintain AMD benchmark recordings for calibration testing.

Critical Phone Login Not Active Web Critical Asterisk Not Running Asterisk Critical Audio One Way Network

Still Stuck?

ViciStack's free 30-day support plan includes unlimited live VICIdial troubleshooting. If you can't resolve this error with the steps above, our engineers will connect to your system and fix it directly — no support tickets, no hourly billing.

Get Free VICIdial Support →

Frequently Asked Questions

What causes the VICIdial "AMD Timeout" error?
The Asterisk AMD application is taking too long to make a human/machine determination and timing out before a decision is reached. The call may be dropped or incorrectly routed as a result. Caused by wait_for_silence set too high, noisy carrier audio preventing silence detection, or AMD analysis window set too wide.
How do I fix the VICIdial "AMD Timeout" error?
Check AMD configuration: grep AMD /etc/asterisk/extensions.conf Then: Review AMD timeout values in VICIdial: Admin > Campaigns > AMD settings Then: Reduce wait_for_silence value (try 1500ms if currently higher) Then: Check for carrier audio issues: enable verbose logging and listen to AMD failures Then: Adjust Asterisk AMD application parameters in dialplan: AMD(initialSilence, greeting, afterGreetingSilence, totalAnalysisTime) Then: Test AMD with recordings of known humans and machines to calibrate Then: Consider ViciStack AMD module for AI-powered AMD that handles edge cases better
How can I prevent the "AMD Timeout" error in VICIdial?
Tune AMD parameters specifically for your carrier's audio profile. Monitor AMD false positive and false negative rates weekly. Test AMD performance after carrier changes. Maintain AMD benchmark recordings for calibration testing.