AMDY.IO

AMDY Troubleshooting — Start Here

updated 2026-05-20

AMDY Troubleshooting

Something not working as expected? Find your symptom below and follow the matching guide. Almost every issue falls into one of four areas.

Find your symptom

What you're seeing Guide
Installed AMDY but it's not running, module errors, no log entries, or every call routes to an agent Setup & installation
AMD works on some of your servers, but one server gets no AMD or no calls through AMD One server not getting AMD
connection error, processing error, NO AUDIO, status=403, or "AMDY can't reach our server" Connection problems
Voicemails reaching agents, false positives, accuracy dropped, machine rate too high Detection accuracy
Agents report early hangups, "scam call" caller ID, or silent prospects Agent & call experience
Agents sit idle, live answers dropped suddenly, "the dialer went bad" Agents not getting calls

Not sure which? Run the first-pass checks below — they tell you which guide you need.

First-pass checks (5 minutes)

When something seems wrong but you can't pin it down, run these three checks in order on your VICIdial telephony server.

1. Watch the live AMD log

Place a few test calls while watching the color-coded live log (green = HUMAN, red = AUDIO, yellow = MACHINE):

curl -sL https://download.amdy.io/amd-tail.sh | bash

2. Run the connection check

curl -sk https://download.amdy.io/proxy_check.py | python3 - --runs 10

Anything other than status=200 on every run → Connection problems.

3. Check your VICIdial settings

The most common silent problem: your AMD agent-options container — named AMD_AGENT_OPT_ followed by your campaign name — must have its entry set to exactly HUMAN,HUMAN. Full checklist in Setup & installation.

Install AMDY

More help