# A VICIdial glossary: hopper, dial level, trunks, lagged, AMD

> Plain definitions of the VICIdial terms that come up in every support ticket, with the table or field name for each and a link to the longer post.

URL: https://trustane.com/blog/vicidial-glossary
By Trustane. Published 2026-11-05.

> **To the point**
> These are the VICIdial terms we explain most often, each with the field or table name as typed and a link to the longer post. We read VICIdial 2.14 on a ViciBox 12 server.
>
> - Start with the **hopper** and the **trunk** limit when a campaign misbehaves.
> - A **drop** needs a person on the line. A no-answer does not.
> - `max_vicidial_trunks` is enforced by the dialer. `auto_dial_limit` is not.
> - `call_log`, not `vicidial_carrier_log`, names the carrier.

## Where these fields live

![Diagram: the hopper, dial level, max trunks, local GMT and system performance flags and where each is set](https://trustane.com/media/5e30a7d1d1c5f40b-1600x563.webp "Five terms and the screen where you set each one")

On our test server, campaign Sunline Solar Q4 callbacks (`SUNQ4`). Markers map to the numbered list below each picture.

### In VICIdial's admin

![VICIdial campaign page with Minimum Hopper Level, Dial Method, Auto Dial Level and Maximum Adapt Dial Level highlighted](https://trustane.com/media/03916cb6d5511d78-1600x827.webp "Hopper and pacing fields on the campaign page")

1. **Minimum Hopper Level**: how full the hopper tries to stay (`hopper_level`).
2. **Dial Method**: who sets the pace (`dial_method`).
3. **Auto Dial Level**: lines per agent counted (`auto_dial_level`).
4. **Maximum Adapt Dial Level**: the ceiling for adaptive methods (`adaptive_maximum_level`).

![VICIdial server record with Max Trunks, Max Calls per Second and Local GMT highlighted](https://trustane.com/media/b973fa17cb5548ca-1600x792.webp "Line limits and the clock live on the server record")

1. **Max Trunks**: `max_vicidial_trunks`, the box-wide line limit.
2. **Max Calls per Second**: how quickly new calls start.
3. **Local GMT**: the offset the hopper uses for local time.

## Dialing

- **Hopper.** The table `vicidial_hopper`, holding the next leads per campaign. The dialer takes leads only from it. A script refills it about once a minute. An empty hopper is the first thing to check when nothing dials. See [reading the hopper](https://trustane.com/guides/why-vicidial-is-not-dialing-hopper).
- **Dial method.** `dial_method`: `MANUAL`, `RATIO`, the `ADAPT_*` family, `INBOUND_MAN` and the `SHARED_*` variants. See [what a predictive dialer does](https://trustane.com/blog/what-is-a-predictive-dialer).
- **Dial level.** `auto_dial_level`, the lines aimed at per agent counted. Level 2.0 with ten agents is a goal of 20. `AST_VDadapt.pl` moves it, up to `adaptive_maximum_level`. Plan lines from that ceiling, not today's value. See [the dial level post](https://trustane.com/blog/vicidial-dial-level-explained).
- **Drop.** A call answered by a person when no agent is free. After `drop_call_seconds`, `drop_action` decides what they hear. The target is `adaptive_dropped_percentage`. The legal limit for your calls is yours to check. See [the abandon rate](https://trustane.com/blog/vicidial-abandon-rate-3-percent).
- **Available only tally.** `available_only_ratio_tally`. On `Y` the dialer counts only READY agents. On `N` it counts READY and INCALL.
- **Call time.** A named window such as `9am-9pm` set by `local_call_time`. The hopper tests each lead's local clock against it.
- **Lead filter.** Saved SQL (`lead_filter_id`) added to the hopper's selection. `NONE` means none.
- **Dial statuses.** `dial_statuses`, the lead statuses the hopper may pick, such as `NEW`.
- **Local GMT.** `servers.local_gmt`, such as -5.00. The hopper uses it, not the operating system, for local time. See [time zones and clock skew](https://trustane.com/blog/vicidial-local-gmt-time-zones).

## Capacity and lines

- **Trunk.** One outbound line. The box limit is `servers.max_vicidial_trunks`, 23 on a stock ViciBox 12. The excess is counted as `local_trunk_shortage`, shown as "trunk short" on the real-time screen. See [lines per agent](https://trustane.com/blog/vicidial-lines-per-agent-capacity).
- **Reserved trunks.** Rows in `vicidial_server_trunks` that set lines aside for a campaign (`OVERFLOW_ALLOWED`) or cap it (`MAXIMUM_LIMIT`).
- **Outbound calls per second.** `servers.outbound_calls_per_second`, 1 to 200.
- **Auto dial limit.** `system_settings.auto_dial_limit`, the top choice in the admin dial level menu. The dialer scripts do not read it.
- **sys_perf_log.** The flag that records load and channel counts in `server_performance`. Off by default. See [watching capacity when it is off](https://trustane.com/blog/vicidial-sys-perf-log-capacity).

## Agents

- **Live agents.** `vicidial_live_agents`, one row per logged-in agent.
- **READY, INCALL, PAUSED.** Waiting, on a call, not taking calls.
- **Lagged.** No check-in from the agent's browser for 30 seconds. It usually reflects the network between agent and server. See [lagged agents](https://trustane.com/guides/vicidial-lagged-agents-network).
- **Remote agent.** A fake agent line, such as for a broadcast. It counts toward the line goal like a person.
- **In-group.** A named inbound queue. A campaign must have it ticked as allowed to answer its calls.
- **Blended.** A campaign that dials out and takes inbound. It needs `campaign_allow_inbound=Y`, which the admin forces to N on `MANUAL`.

## Detection, caller ID and carriers

- **AMD.** Answering machine detection. On ViciBox 12 the arguments are inline in `extensions.conf`, so `amd.conf` is never read. Decisions go to `vicidial_amd_log`. See [why editing amd.conf changes nothing](https://trustane.com/blog/vicidial-amd-conf-ignored-vicibox).
- **NOTSURE.** The detector could not decide. By default these go to an agent, as does HUMAN.
- **CID group.** A named set of caller IDs chosen by `cid_group_id`. The dialer uses the number used least so far today. The off value is exactly `---DISABLED---`. See [caller ID and CID groups](https://trustane.com/blog/vicidial-caller-id-cid-groups).
- **Carrier.** A SIP or IAX trunk to a provider, in `vicidial_server_carriers`. See [which carrier carried that call](https://trustane.com/blog/vicidial-which-carrier-carried-call).
- **DID.** An inbound number routed to an in-group or agent, in `vicidial_inbound_dids`.
- **Disposition.** The code a lead gets after a call, such as `NA` or `DROP`. Status flags decide what counts as a contact, sale or do-not-call.

> **Three pairs that get confused**
> The trunk limit and the auto dial limit sound alike, but only the first is enforced. A drop and a no-answer differ, since a drop needs a person on the line. And `call_log` names the carrier, not `vicidial_carrier_log`.

## Questions people ask

### Why does the dialer ignore my auto dial limit?

`auto_dial_limit` only sets the top choice in the admin menu. The line cap that binds is `max_vicidial_trunks`.

### What does an empty hopper mean?

Nothing dials. The campaign takes leads only from `vicidial_hopper`, so check it first.

## Next steps

Look up each unfamiliar term in the right table before you change anything. To compare options, see [hosting](https://trustane.com/vicidial-hosting) and [pricing](https://trustane.com/vicidial-pricing), or [ask us a question](https://trustane.com/contact).

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