What is a VICIdial cluster? The parts in plain words
A VICIdial cluster is one dialer system spread over several machines. Here is what each part does, followed through the life of a single call.
Someone has quoted you a "VICIdial cluster" and listed machines you never had to think about on one server. What does each one actually do, and which one do your agents touch?
The short version: a cluster is still one VICIdial system. It just runs on several machines instead of one, and each machine has a clear job.
What stays the same for your floor
Your agents log in the way they always have. Each Campaign (a set of leads and dialing rules) runs the way it did before. Reports, lists and statuses all live in one place.
What changes is underneath. On one server, the phone engine and the database share the same cores, so a heavy report can slow the calls. In a cluster each gets its own machine.
Both jobs are real work. On one 166-call floor we measured, Asterisk, the phone engine underneath VICIdial, used 4.3 cores and the MariaDB database 1.3, on the same machine. Asterisk does most of the work, but the database grows with every call too.
Follow one call through the parts
The easiest way to see the parts is to follow a single outbound call from dial to disposition.
1. A dialer places the call. Dialer servers run Asterisk. They place and answer calls, and your carriers' SIP trunk connections land here. We run one dialer per 300 concurrent calls or 25 agents, whichever needs more, and never fewer than two.
2. The customer answers, and the database picks the agent. VICIdial hands each answered call to a free agent through the database. That database lives on its own machine, the database and web server, which holds every lead, campaign and call record in MariaDB.
3. The agent hears the customer through the dialer. The agent's phone is connected to a dialer too. Dialers host the agents' phones and the conferences, including every Three-way call that brings a third person onto the line.
4. The agent's screen comes from the database machine. In our layout the database machine also serves the admin pages, the reports and the agent screens. The agent's browser loads its screen from there, while their phone talks to a dialer.
5. The agent saves a disposition. When the agent picks a Disposition, the result of the call, it is written to the database.
flowchart LR
T[Your SIP trunks] --> D[Dialer]
D -- who is free? --> DB[(Database + web)]
DB -- this agent --> D
D --> P[Agent phone]
DB --> S[Agent screen]
S -- disposition --> DB
DB -. live copy .-> SB[(Standby database)]The part your agents never see: the standby
The standby database copies the main database as it changes, so it is always a live copy. If the database machine fails, the standby is promoted and takes over.
That matters because the database is the one machine every dialer depends on. Lose a dialer and the calls on it drop, but the other dialers keep the floor working. Lose the database with no standby and everything stops.
Why the parts sit side by side
Every machine sits in the same datacenter, joined by a private network. Dialers query the database many times a second; on that same 166-call floor, the database answered 2,230 queries a second.
At that rate, distance hurts. A round trip between Germany and Finland is over 20 ms, which is enough to stall VICIdial. So a cluster is never split across two sites to look safer; the safety comes from the second dialer and the standby instead.
For how many machines your floor needs and what they cost, see our complete guide to VICIdial clusters. If you want the database split on its own first, running the VICIdial database on its own server covers that step.
Frequently asked
- No. Agents log in and work the same way they did on one server. Their phone is set up on a dialer for them, and their screen loads from the database machine.
- It is a live copy that replicates as the database changes, so it can be promoted to take over if the database machine fails.
› Do agents need to know which dialer they are on?
› Is the standby database a backup?
If one server still covers your floor, start on a plan. When it doesn't, book a sizing call and see today's prices.
Related from VICIfast
- How we build VICIdial clustersA 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.
- Hosted VICIdial servers, live in 40 secondsYour own VICIdial server, patched and monitored, billed per server.
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 is a VICIdial cluster? The parts in plain words”. VICIfast LLC, November 18, 2026. Retrieved from https://vicifast.com/blog/what-is-a-vicidial-cluster
Have questions?
Related posts
You might be interested in
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.


