What a dialer server does in a VICIdial cluster
A dialer is the phone server of a VICIdial cluster: calls, agent phones and conference rooms. What it does, where its processor goes, and what breaks on a busy one.

A cluster quote lists two, three or five "dialers", and it's fair to ask what each one does for the money. A dialer is a phone server: almost everything your customers and agents hear passes through one.
Here's its job, where its processor goes, and what goes wrong on a busy one.
The four jobs of a dialer
- Placing and answering calls. Each dialer runs Asterisk, the phone engine under VICIdial, and your carriers' SIP trunk connections land on it.
- Hosting the agents' phones. Whether an agent uses a Webphone in the browser or a softphone app, the phone side connects to a dialer.
- Running the conference rooms where calls are joined, including every Three-way call that brings a third person onto the line.
- Asking the database. A dialer queries it many times a second: which leads to dial, which agent is free, and what happened on each call.
What a dialer doesn't keep is the records. Leads, campaigns and call history live on the database and web server, which also serves the agent screens. The dialer is where the live calls are.
flowchart LR
C[Your carriers] -->|SIP trunks| D[Dialer running Asterisk]
P[Agent phones] --> D
D --> R[Conference rooms]
D -->|queries many times a second| DB[(Database + web)]
D2[Second dialer] -->|queries| DB
B[Agent browsers] -->|screen| DBWhere its processor goes
Asterisk does most of the work on a VICIdial floor. On one full shift we measured, it used 4.3 cores to the database's 1.3, more than three times as much, to carry 166 calls and 365 channels (the separate call legs Asterisk keeps open).
So we size dialers by calls and agents: one per 300 concurrent calls or 25 agents, whichever needs more, and never fewer than two. How many dialers a cluster needs walks through the count.
Our dialers are Intel Core i5-13500 machines with 14 cores (6P + 8E), 64 GB of memory and two 512 GB NVMe drives.
Four things that go wrong on a busy dialer
Voice packets get thrown away
Linux's default network buffers are sized for a desktop. On a busy dialer they overflow in bursts, and voice packets are discarded. One 60-agent server dropped 458,000 of them in four days, which agents and customers hear as choppy audio. Every server we build gets buffers sized for hundreds of calls.
Conference rooms run out
VICIdial frees conference rooms with a background process that is often left switched off. Without it, every room used for a 3-way call stays taken until the dialer has none left, and Leave 3-way starts failing. It runs on every dialer we build.
Customers reach a line nobody hears
When an agent's browser phone drops (a closed tab, a sleeping laptop, a new IP address), Asterisk keeps its side of the call up. VICIdial still sees a ready agent and keeps sending customers to silence. Every agent phone and carrier trunk we set up hangs up after two minutes without audio.
The manager interface fills up
Asterisk 21 and 22 leak a subscription on the AMI (Asterisk Manager Interface), Asterisk's manager interface, on every dialplan reload while the old users.conf file is present. After days of reloads, that can trip Asterisk's overload protection, which turns away new calls and phone registrations. Our post on when to reload Asterisk covers reloads in general.
When a dialer fails
If a dialer stops, the calls on it drop and the other dialers keep the floor working. That's the reason for the two-dialer minimum: with only one, a single failure silences every line.
On our cluster page each dialer gets its own row: free conference rooms, calls per second against its limit, how the last 15 minutes of calls ended at the carrier, and whether its background processes are running. The VICIdial cluster guide shows how the dialers fit with the rest of the layout.
Frequently asked
- The calls on that dialer drop. The other dialers keep working, which is why we never build a cluster with fewer than two.
- On one server, Asterisk and MariaDB share the same cores, so a busy report or a list load slows the calls. A cluster gives each its own machine.
› What happens to live calls if a dialer fails?
› Why not run the dialer and the database on one machine?
If one server still carries your floor, a single-server plan is the simpler choice. When it doesn't, book a sizing call and see today's cluster prices.
Related from VICIfast
- How we build VICIdial clustersA database, dialers and a standby, sized from load we measured on a live floor.
- Bare metal VICIdial serversEvery core yours, mirrored NVMe, delivered in minutes to days. Priced from live stock.
- For floors above 400 agentsCustom regions, procurement paperwork, and volume terms.
About VICIfast
We run VICIdial servers for call centres, so you don’t have to. You get the dialer set up, secured and kept running — we handle the server, the updates and the backups. Bring your own phone carrier at no markup, or use VICIfast Voice, our own US calling and numbers, from $0.0085 a minute. From $49 a month per server.
Questions? Call +1 636 556 0022 and talk to someone who runs dialers.
Citing this article
VICIfast Engineering. “What a dialer server does in a VICIdial cluster”. VICIfast LLC, November 21, 2026. Retrieved from https://vicifast.com/blog/vicidial-cluster-dialer-role
Have questions?
Related posts

Guides & tutorials
How many dialer servers does a VICIdial cluster need?

Guides & tutorials
Why a VICIdial cluster should never run on one dialer

Guides & tutorials
Installing audio codecs (g729 and friends) for VICIdial

Guides & tutorials
VICIdial clusters: how they work, when you need one, and how to size one
You might be interested in
Guides & tutorials
When a CRM polls VICIdial once per agent: the load you don't see
Guides & tutorials
Idle campaigns left active: the hidden database load in VICIdial
Guides & tutorials
Why searching a lead by phone number freezes VICIdial, and the missing index

Guides & tutorials
Keep the call log small: log archiving on a busy VICIdial database
VICIfast newsletter
Liked this? Get the next one in your inbox.
We ship the kind of stuff you just read - concrete, numbers-first, no drip. One email when a new post goes live. Unsubscribe in one click.
Comments
No comments yet - be the first.