Why a VICIdial cluster should never run on one dialer
One database plus one dialer gives you two machines that can each stop the whole floor. A second dialer is what turns a failure into a partial outage.

A cluster with one database server and one dialer looks like the cheapest way off a single box. Two machines, the database off the phones' cores, done. It's also the layout with the least protection, because now there are two machines and either one can stop your whole floor.
What lives on a dialer
A dialer server runs Asterisk, the phone engine. It places and answers the calls, hosts your agents' phones and runs the conference rooms behind every 3-way call. Your carriers' SIP trunk lines and your agents' Softphone apps (phone software on their computer) all connect to it.
The database and web server holds the leads and serves the agent screens. The calls themselves only exist on a dialer. With one dialer, every live call on your floor sits on one machine.
One dialer, two ways to stop the floor
On a single server there is one machine that can stop everything. Split it into a database and one dialer and you've doubled that: if either machine fails, every agent stops. You've paid for a second machine and kept the single point of failure.
A second dialer changes the picture. If a dialer fails, the calls on it drop and the other dialers keep the floor working. Add the standby database, a live copy promoted if the main database machine fails, and losing any one machine costs you part of the floor instead of all of it.
flowchart LR
T[Your carriers] --> D1[Dialer 1]
T --> D2[Dialer 2 - failed]
A1[Agents on dialer 1] --> D1
A2[Agents on dialer 2] -.-> D2
D1 --> DB[(Database + web)]
D2 -.-> DB
DB -. replicates .-> SB[(Standby database)]What about the agents who were on the failed dialer? With phone aliases, each agent's login is tied to a phone on more than one dialer, and at login VICIdial picks the active dialer with the lowest load. They log out, log back in, and carry on with the same login details. Our post on keeping agents online when a dialer fails walks through it.
Dialers fail quietly, too
A dialer doesn't have to crash to stop serving your floor. These are three ways we've seen a dialer that looks up still let agents down:
- It turns calls away. Asterisk 21 and 22 leak a subscription on the AMI (Asterisk Manager Interface) (the manager interface VICIdial uses to drive Asterisk) on every dialplan reload while the old users.conf file is present. After days of reloads, Asterisk's overload protection can start refusing new calls and phone registrations.
- It runs out of conference rooms. VICIdial frees 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.
- It throws voice away. Linux's default network buffers are sized for a desktop. On a busy dialer they overflow in bursts, and one 60-agent server dropped 458,000 voice packets in four days.
With one dialer, each of these hits every agent at once. With two or more, it hits that dialer's share while someone fixes it. We fix all three on every dialer we build, and our cluster page shows each dialer's free conference rooms and calls per second against its limit, so a struggling dialer stands out.
How many dialers, then?
Our rule is one dialer per 300 Concurrent calls (calls up at the same moment) or 25 agents, whichever needs more, and never fewer than two. A floor that fits on one dialer by the numbers still gets two. Our post on how many dialers a cluster needs works through the count.
If your floor is small enough that one dialer would sit half empty, ask whether you need a cluster yet. A single server is one machine to look after, and our plans start there. When the floor outgrows it, the cluster guide shows the full layout.
Ready to plan one? Book a sizing call and we'll work out the layout and the monthly price for your floor with you.
Frequently asked
- No. The calls on that dialer drop. The other dialers keep the floor working, and agents set up with phone aliases can log back in on a dialer that is still up.
- No. Even a floor that fits on one dialer gets two in our clusters, because the second one is what stops a single failure from halting every agent.
› If a dialer fails, do its live calls move to the other dialer?
› Does a second dialer only matter on big floors?
Related from VICIfast
- VICIdial cluster sizing, with real numbersA database, dialers and a standby, sized from load we measured on a live floor.
- Dedicated VICIdial hardware, live pricesEvery core yours, mirrored NVMe, delivered in minutes to days. Priced from live stock.
- Add-ons and one-time servicesHands-on setup, migrations and extras, priced per job rather than per month.
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. “Why a VICIdial cluster should never run on one dialer”. VICIfast LLC, November 20, 2026. Retrieved from https://vicifast.com/blog/why-vicidial-cluster-needs-two-dialers
Have questions?
Related posts
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.



