Install AMDY — Standard AMD

This is the regular AMDY install — AI-powered Answering Machine Detection that returns HUMAN / MACHINE / FAS / etc. on each call, with no audio prompt played to the caller.

Want a greeting / "hello" prompt played to the caller while AMDY detects? That's the playback variant — see Playback audio (insert.wav) instead.

Need the full PDF reference? Installation & Configuration Guide (PDF)

1. Pick the installer for your system

Run the one-liner that matches your VICIdial telephony server, as root:

Each installer: - Installs the Python dependencies (pyst2, websocket-client, mysql-connector-python, configparser) - Downloads and unpacks the AGI script to /var/lib/asterisk/agi-bin/amd.py - Makes it executable - Inserts the AMDY dialplan block into /etc/asterisk/extensions.conf (extension 8370, or 8371 for Press-1) - Reloads Asterisk

Press-1 note: Press-1 campaigns require prospects to press 1 to be connected to an agent. The 8371 extension handles that workflow. After installation, set your campaign's Routing Extension to 8371 instead of 8370.

2. Verify the install

The fastest check — confirms AGI, modules, and AMDY reachability in one command:

curl -s https://download.amdy.io/check-aiamd.sh | bash

If everything reports OK, install is good. If anything fails, see What each check-aiamd.sh failure means.

Or step through manually:

Step 1 — AMD script runs

/var/lib/asterisk/agi-bin/amd.py

The script should start and wait silently for input (this is normal AGI behaviour). No Python import errors, no missing-module messages. Press Ctrl+C to exit.

Step 2 — Python modules load

python3 -c "import websocket, mysql.connector, asterisk.agi; print('All modules loaded successfully')"

You should see:

All modules loaded successfully

If you see ImportError, re-run the installer for your OS (table above) or install manually:

pip3 install pyst2 websocket-client mysql-connector-python

3. Configure VICIdial

3.1 Enable AMD Agent Routing on the campaign

Admin → Campaigns → (your campaign) — set:

3.2 Configure the AMD Agent Route Options container

This controls which AMDY classifications are routed to an agent. Without this, machines and dead air will reach your agents.

Admin → System Settings → Container Settings — find or create the container:

PDF note: The official PDF example shows AMD_AGENT_OPT_VAC because VAC was a sample campaign. The container is named after your specific campaign, not the literal string VAC. You need one container per active campaign — check-aiamd.sh lists them and flags any that are missing or misconfigured.

The HUMAN,HUMAN entry tells AMDY: only route calls classified as live humans to agents. Every other status (MACHINE, FAS, etc.) is dispositioned automatically and never wakes an agent.

3.3 Set the Routing Extension

Admin → Campaigns → (your campaign) → Dial Settings → Routing Extension:

3.4 Rebuild telephony config

This step is mandatory. Without it, your changes don't apply and no AMDY routing happens — you'll see zero entries in the log file.

Admin → Servers → (your telephony server) → Rebuild Config (or "Generate Config"). Wait for completion.

4. First test calls

Place a few real calls (or use a click-to-call dialer test).

Watch the live log

On the telephony server:

tail -f /var/log/astguiclient/AMD_log$(date +%Y%m%d).txt

You should see one line per answered call with its classification — HUMAN lines route to agents, anything else is dispositioned.

For color-coded monitoring:

tail -f /var/log/astguiclient/AMD_log$(date +%Y%m%d).txt | sed -u \
  -e '/AUDIO/s/.*/\o033[31m&\o033[m/' \
  -e '/HUMAN/s/.*/\o033[32m&\o033[m/'

Red = audio/machine, green = human.

Log format

Each line is pipe-delimited: - Timestamp — when the detection happened - Unique ID — call identifier (use this to pull the recording later) - Detection result — HUMAN / MACHINE / FAS / etc., with confidence scores - Campaign info — which campaign + dial config produced the call - Phone number — destination number (partially masked for privacy)

5. If something doesn't work

Run the one-shot check first — it tells you exactly which subsystem is broken:

curl -s https://download.amdy.io/check-aiamd.sh | bash

Then jump to the right page:

6. Quick reference — what got installed

See also

• Installation & Configuration Guide (PDF) — official document
• Cheat sheet — scripts & commands — all install / verify / connectivity one-liners in one page
• Playback audio (insert.wav) — install the variant that plays a greeting during detection
• Setup & installation problems — what to do when something goes wrong
• Understanding AMD statuses & timing — what HUMAN / MACHINE / FAS / etc. mean