This opens the firewall for that IP address and hands you a one-line command to run on the dialer. About a minute of work — or send someone the setup guide and let them do it.
Recent decisions —
Time
Verdict
Why
Decided by
Took
Calls as they come in
Time
Dialer
Verdict
Why
Decided by
Listened for
Took
Campaign
Who is allowed to reach this server
IP address
Dialer
Rule
You never edit these by hand. Adding a dialer opens the door for its IP address, removing it closes it again, and changing its IP moves the rule across. Any other machine on the internet is simply refused.
The firewall's own words
—
Your account
Who can sign in
Username
Created
Password changed
How the detection is tuned these are set on the server and shown here so you know what is running
Setting
Currently
What it does
Change it with
Connecting your own scripts
Anything you can do on these pages, a script can do too — GET /api/clients to list dialers, POST /api/clients to add one, DELETE /api/clients/<name> to remove one, GET /api/fw for the firewall. Scripts identify themselves with the admin token in an X-Admin-Token header instead of signing in, so the token never has to leave your server.
Client created — set up the dialer
Run this once on that dialer, as root. It installs the AMD client and this key, and changes no call behaviour until you switch a campaign over.
This is the only time the key is shown — the engine stores only its hash.
If you install by hand instead, this is /etc/amdai/amdai.conf:
Run it as root on the ViciDial server (the box, not your laptop). It installs the client, writes the 8370 AI-AMD extension into extensions.conf next to 8369 (with automatic fallback to stock AMD if the engine is ever unreachable), registers this dialer's IP, reloads the dialplan and runs a live self-test — about a minute. Then set the campaign's AMD routing extension to 8370; dial 8371 from an agent phone to hear the verdict.
Not doing it yourself? Send them the setup guide — it walks a non-technical person through the whole thing.