One Server Not Getting AMD
Use this guide when AMD works on some of your dialers but one server gets no AMD results, or calls on it never reach agents through AMD. Run the four steps below on that server, as root, in this order, and keep the output of each.
The most common cause: the IP you added in the portal is not the address the server actually uses to reach the internet (a typo, a second network card, or a NAT address). AMDY only accepts connections from the IPs on your account, so traffic from the real address is refused.
Step 1: Find the server's public IP and run the proxy check
curl -s https://api.ipify.org; echo
curl -sk https://download.amdy.io/proxy_check.py | python3 - --runs 10
The first line prints the address this server uses to reach the internet. Compare it with the IPs under IP management at app.amdy.io: if it is not there, that is your problem, and step 2 fixes it.
The proxy check then tests a connection from this server to every AMDY server on port 2700. Healthy output ends with All IPs healthy. Refused or timed-out connections mean either the IP is not on your account yet, or your firewall blocks outbound port 2700 (see Connection problems).
If you get dig: command not found, install it first: zypper in -y bind-utils (ViciBox / openSUSE) or yum install -y bind-utils (CentOS).
Step 2: Install (or re-install) AMD
curl -fsSL https://download.amdy.io/installamd-v2.sh | bash -s -- --api-key YOUR_API_KEY
Use the key from API keys at app.amdy.io. The installer sets up AMD on this server and registers the server's real public IP on your account automatically, so you do not have to type it. Running it again on a server that already has AMD is safe: it replaces the AMD extension instead of duplicating it. It works on ViciBox 7 and newer, including the default Python of each version.
Our firewalls pick up a newly registered IP within a few minutes.
Step 3: Run the install check
curl -s https://download.amdy.io/check-aiamd.sh | bash
This checks the AMD script, the Python modules it needs (using the same Python that AMD runs under), the connection to our servers, and your ViciDial campaign settings. Every red line comes with the exact command or setting that fixes it. The usual ones:
- Python module missing: run the fix command it prints, or re-run step 2.
- Campaign AMD route disabled: Admin → Campaigns → your campaign → set AMD Agent Route Options to
ENABLED. - Container missing: Admin → System Settings → Containers → add
AMD_AGENT_OPT_<campaign>, typeAMD_AGENT_OPTIONS, entry exactlyHUMAN,HUMAN. - After any ViciDial change: Admin → Servers → Rebuild Config.
Step 4: Watch the live AMD log
curl -sL https://download.amdy.io/amd-tail.sh | bash
Leave it running and place a few test calls. Each detection appears in color as it happens:
| Color | Meaning |
|---|---|
| Green | HUMAN: a live person, sent to an agent |
| Yellow | MACHINE: voicemail, IVR and similar |
| Cyan | FAS / HONEYPOT: carrier false answer or spam trap |
| Red | Audio being streamed to AMDY (normal while a call is analysed) |
| Magenta | PROCESSING_ERROR / SERVER_TIMEOUT: see Connection problems |
No lines at all while calls are being placed means the calls are not going through the AMD extension (8370): re-check the campaign settings from step 3.
If it still does not work
Send AMDY support the output of all four steps: the public IP from step 1, the proxy check, the installer output, the install check, and a few lines of the live log. See Contacting support.
Want us to do it for you? Work on your own servers is not included in the plan. For $99 we install and test AMD on your server for you (we need SSH access). Order it from Install help in the portal: app.amdy.io/integration-help.