Where agents connect in a VICIdial cluster: screen from one machine, phone from another
On a VICIdial cluster an agent's screen comes from the database and web server, while their phone connects to a dialer. Here is what each connection carries and what breaks.

Your agents log in on a cluster exactly the way they did on one server, so it's natural to think they connect to one place. They don't. The screen they click comes from one machine and the voice in their headset comes from another, and that split decides where you look first when a shift goes wrong.
Two connections, two machines
In our layout, the database and web server does two jobs. It holds every lead, campaign and call record in MariaDB, and it serves the agent screens, the admin pages and the reports. When an Agent types the login address into their browser, this is the machine that answers.
The phone goes somewhere else. A Webphone (a phone inside the browser tab) or a Softphone (a phone app on the computer) signs in to a dialer server, a step called Phone registration. Dialers run Asterisk, the phone engine that places and answers calls, and host the conference rooms for 3-way calls. Your carriers' trunks land there too.
flowchart LR
B[Agent browser] -->|screen, every second| W[(Database + web server)]
P[Agent phone] -->|voice| D1[Dialer 1]
C[Your carriers] --> D1
C --> D2[Dialer 2]
D1 -->|queries| W
D2 -->|queries| W
W -.->|live copy| S[(Standby database)]So one agent is two links: browser to the database and web server, phone to a dialer. The dialers, in turn, query the database many times a second.
What the screen connection carries
The agent screen doesn't load once and sit still. It asks the server for news every second. On one floor we measured, that polling made up 87.5% of every web request the server answered.
Each of those requests needs the database to reply. When the database is held up, for example by a long report reading the call log, the requests pile up and the screen stops moving. The same happens when Asterisk's manager interface (AMI (Asterisk Manager Interface)), the channel VICIdial uses to give the phone engine its orders, backs up.
Saving a Disposition, the result an agent picks when a call ends, travels this link too. So a frozen screen or a slow save points at the database and web server first, not the headset. For the checks to run on one stuck screen, see what to check when an agent screen freezes.
What the phone connection carries
The phone link carries the voice. When an agent logs in, VICIdial rings their phone on its dialer and keeps that line open for the whole Agent session. Every customer the dialer reaches is connected into that open line.
Which dialer a phone uses is set on the phone itself: each phone entry has a Server IP field that picks the server it's active on. We plan one dialer per 25 agents or 300 concurrent calls, whichever needs more, so a 50-agent floor puts about 25 phones on each of two dialers.
This is also where audio trouble lives. Choppy sound and dropped phone connections come from the path between the agent's computer and the dialer, or from the dialer itself. The screen can be perfectly healthy while the voice breaks up.
Where the distance matters
Agents can work from anywhere with a decent connection, because their browser and phone reach the cluster the same way they'd reach a single server. The distance that hurts is between the machines. A round trip between Germany and Finland is over 20 ms, enough to stall VICIdial's constant database questions, which is why every server in the cluster sits in one datacenter.
For your firewall, it means each agent has to reach two places: the web server for the screen and their dialer for the phone. Open only one and you get a screen with no voice, or a phone that never receives a call. If the phone side refuses to sign in, work through the webphone registration checklist.
Reading a problem by its connection
- Every screen stalls at once, statuses save slowly: the database and web server. Something is holding it, often a report or a lead search.
- Bad audio for everyone on one dialer: that dialer, its load or its network buffers.
- Bad audio for one agent only: that agent's own connection or computer.
- Customers reach silence: a browser phone that dropped while the screen stayed ready.
Our cluster page checks every server every 10 seconds and names the machine that needs a person, so you don't have to work this out by hand mid-shift. For how the rest of the layout fits together, read our guide to VICIdial clusters.
Frequently asked
- No. They log in and work their campaigns the same way they did on one server. The split only matters when you are working out what broke.
- Not in where it goes. Both sign in to a dialer for the voice, and the screen still comes from the database and web server.
› Do agents notice they are on a cluster?
› Does a softphone connect differently from a webphone?
Most floors begin on one server, and if yours still fits, pick a plan and grow later. When the screens and the phones need machines of their own, book a sizing call for your cluster and we'll lay it out around your agents.
Related from VICIfast
- VICIdial cluster sizing, with real numbersA database, dialers and a standby, sized from load we measured on a live floor.
- A whole machine for your dialerEvery core yours, mirrored NVMe, delivered in minutes to days. Priced from live stock.
- A white-label webphone in your brandA WebRTC phone inside the agent screen on every server, in your colours.
- 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. “Where agents connect in a VICIdial cluster: screen from one machine, phone from another”. VICIfast LLC, November 21, 2026. Retrieved from https://vicifast.com/blog/where-agents-connect-in-vicidial-cluster
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.



