VICIdial AMD: 8 values inline, 2 left to amd.conf
VICIdial's dialplan passes eight of AMD()'s ten values inline, leaving maximum_word_length and playback_file to amd.conf. Where each value lives.

To the point
On ViciBox 12 (our test server, Asterisk 18.26.1-vici, read 11 Sep 2026), AMD campaigns run Asterisk's AMD() with eight values typed into the dialplan, the same line as VICIdial's own sample. Those eight override /etc/asterisk/amd.conf. In stock Asterisk the settings it does not pass, maximum_word_length and playback_file, come from amd.conf.
- The eight values are in
extensions.conf:AMD(2000,2000,1000,5000,120,50,4,256). - Stock Asterisk's AMD module reads amd.conf when it loads, and does not load without it.
- Average decision time per outcome was 2.9 to 4.8 seconds across 22,954 decisions.
This does not repeat the accuracy numbers from how accurate AMD is.
Where the arguments live
Three dialplan lines call the detector for the AMD-enabled extensions 8369, 8373 and 8375. In the manual's numbering, 8369 is AMD then normal routing, 8373 is AMD then a survey, and 8375 is AMD then a text-to-speech survey. The same line is in VICIdial's own sample dialplan.

totalAnalysisTime caps how long the detector listens before it decides. maximumNumberOfWords is behind the MAXWORDS cause in the logs.
To change behavior, back up extensions.conf, edit the lines, run asterisk -rx "dialplan reload", and confirm with dialplan show 8369@default.
What amd.conf still sets
Stock Asterisk's AMD module (we read 18.26.1 and 22.5.1) reads amd.conf when it loads, as defaults that AMD() arguments overwrite. The dialplan passes eight values, so the settings it does not pass keep their amd.conf values:
maximum_word_length: a longer word ends detection as MACHINE, causeMAXWORDLENGTH. The built-in 5000 ms is set large so it is not used. None of our 22,954 decisions had that cause.playback_file: audio the caller hears during detection. Asterisk's sample amd.conf leaves it unset.
ViciBox runs its own Asterisk build, 18.26.1-vici. We read stock Asterisk's module, not that build's.
The module will not load without a valid amd.conf. asterisk -rx "dialplan reload" reloads only extensions.conf; use asterisk -rx "module reload app_amd.so".
What waitforsilence_options is for
The campaign field waitforsilence_options is used by VD_amd.agi only when leaving a message after a machine is identified. It waits for silence before the message plays. The manual's voicemail-drop recipe uses 2000,2,30. It plays no part in deciding human or machine.
Set it up, step by step
In VICIdial's admin

- Answering Machine Message (
am_message_exten): the message played to a machine. - AMD Type (
amd_type):AMDis the only engine present on the image we read. - AMD send to Action (
amd_send_to_vmx):Yplays the message, otherwise it hangs up. - AMD Agent Route Options (
amd_agent_route_options):DISABLED,ENABLED, orPENDING(edit the container without applying it). - AMD Status Map (
amd_status_map): the disposition for calls that never reach an agent.
In the Trustane console

- Detect answering machines: switches detection on for the campaign.
- When it is a machine: hang up, or leave the message below.
- Message left on machines: the audio played.
These change campaign fields. The same tab's Detector sensitivity rewrites the AMD() line on 8369, 8373 and 8375 for every AMD campaign on the server, and keeps a backup of extensions.conf.
What the AGI does with the verdict
After AMD() returns, VD_amd.agi logs the AMDSTATUS, the AMDCAUSE, the run time in milliseconds and the raw stats to vicidial_amd_log. Then it routes.
By default, with amd_agent_route_options at DISABLED, HUMAN and NOTSURE go to an agent. MACHINE does not. With amd_send_to_vmx=Y the machine path waits for silence (when waitforsilence_options is set) and plays am_message_exten, limited by vmm_daily_limit per lead per day. Otherwise it hangs up.
With ENABLED, a settings container named AMD_AGENT_OPT_<campaign_id> decides. Only exactly matching lines such as NOTSURE,TOOLONG reach an agent. There is no wildcard, and flags such as FAX-Hangup-ENABLED hang up at once.
Which engine
amd_type accepts other values. CPD is Sangoma's licensed detector, which Sangoma no longer sells, and KHOMP needs KHOMP's SIP gateway. The server we read had viciamd_enabled at 0 and no binaries, and admin offers ViciAMD only when that setting is on.
What it costs in time
The manual warns that detection delays every call and suggests a dial timeout of 22 to 26 seconds as an alternative. The slowest group was NOTSURE at 4.8 seconds, and those calls reached an agent every time, so the customer waited that long in silence. Cutting totalAnalysisTime shortens the wait for more NOTSURE verdicts.
A call under analysis is not available to an agent. VICIdial's drop timer starts only after the analysis, so that wait does not count toward drop_call_seconds. See the abandon rate and the dial level.
How to tune it
- Baseline a week of
vicidial_amd_log: counts per status and cause, and average run time. - Change one argument. Back up, reload, verify with
dialplan show. - Measure the same week again.
- Join
vicidial_amd_logtovicidial_logonuniqueidand read agent dispositions against the verdict. This shows false humans: calls the detector passed that agents marked as machines.
What we did not test
Changing the arguments on a live campaign and measuring the effect, VICIdial installs other than ViciBox 12, ViciBox's own build of the AMD module, any alternative to the stock values, and editing amd.conf. What it still sets, we read in Asterisk's source.
Questions people ask
Does amd.conf do anything at all?
Yes, in stock Asterisk. It supplies maximum_word_length and playback_file, and the AMD module will not load without it. Only that module reads the file.
Which setting shortens the silent wait?
totalAnalysisTime, the fourth argument, 5000 ms here.
Next steps
Search your extensions.conf for AMD( and confirm the values. Pull a week of vicidial_amd_log. Under Dedicated, our pricing page lists "Carrier setup, LCR and AMD tuning". See also VICIdial hosting.
VICIdial is a trademark of its owner. Trustane is an independent hosting provider.
Sources
- Trustane notes on AMD and caller ID, read from VD_amd.agi and extensions.conf
- Trustane notes on the VICIdial 2.14 manager manual
- Asterisk 18.26.1 app_amd.c, how AMD() reads amd.conf
- Asterisk 18.26.1 sample amd.conf
- Cover photo by Pixabay on Pexels
Managed VICIdial hosting


