# 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.

URL: https://trustane.com/blog/vicidial-amd-conf-ignored-vicibox
By Trustane. Published 2026-11-05, updated 2026-11-08.

> **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](https://trustane.com/blog/vicidial-answering-machine-detection-accuracy).

## 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.

![Diagram: the eight AMD arguments from extensions.conf split into timing values and word values](https://trustane.com/media/522a67ed014b04bc-1600x633.webp "The eight values the dialplan passes, in Asterisk's fixed order")

`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:

1. `maximum_word_length`: a longer word ends detection as MACHINE, cause `MAXWORDLENGTH`. The built-in 5000 ms is set large so it is not used. None of our 22,954 decisions had that cause.
2. `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

![VICIdial campaign page with its five AMD fields marked](https://trustane.com/media/df8e0e281cb2f9d6-1600x577.webp "The campaign fields that decide what happens after the verdict")

1. **Answering Machine Message** (`am_message_exten`): the message played to a machine.
2. **AMD Type** (`amd_type`): `AMD` is the only engine present on the image we read.
3. **AMD send to Action** (`amd_send_to_vmx`): `Y` plays the message, otherwise it hangs up.
4. **AMD Agent Route Options** (`amd_agent_route_options`): `DISABLED`, `ENABLED`, or `PENDING` (edit the container without applying it).
5. **AMD Status Map** (`amd_status_map`): the disposition for calls that never reach an agent.

### In the Trustane console

![Trustane console with three machine detection settings marked](https://trustane.com/media/a2693867f9ff5855-1600x515.webp "Campaigns, the campaign, then Machine detection")

1. **Detect answering machines**: switches detection on for the campaign.
2. **When it is a machine**: hang up, or leave the message below.
3. **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](https://trustane.com/blog/vicidial-abandon-rate-3-percent) and [the dial level](https://trustane.com/blog/vicidial-dial-level-explained).

## How to tune it

1. Baseline a week of `vicidial_amd_log`: counts per status and cause, and average run time.
2. Change one argument. Back up, reload, verify with `dialplan show`.
3. Measure the same week again.
4. Join `vicidial_amd_log` to `vicidial_log` on `uniqueid` and read agent dispositions against the verdict. This shows false humans: calls the detector passed that agents marked as machines.

> **Machines are never verified**
> In our sample 57 percent of answered calls were called MACHINE, and by design none reached a person. The way to size that error is a calibration day, routing one machine cause, such as `MACHINE,INITIALSILENCE`, to agents.

> **Keep your edited lines**
> The dialplan change lives only in `extensions.conf`. Keep the values in whatever builds your servers, so a fresh box does not return to 2000, 2000, 1000, 5000. We did not test whether a package upgrade rewrites `extensions.conf`, so check the `AMD(` line after every upgrade.

## 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](https://trustane.com/vicidial-pricing) lists "Carrier setup, LCR and AMD tuning". See also [VICIdial hosting](https://trustane.com/vicidial-hosting).

VICIdial is a trademark of its owner. Trustane is an independent hosting provider.
