VICIfast
ENES
Guides & tutorials

The database and web server: the machine every dialer depends on

In a VICIdial cluster one machine holds every record, hands every answered call to an agent and serves every screen. What it does all shift, and how to protect it.

VICIfast Support
··3 min read
Servers in a data centre — illustration for: The database and web server: the machine every dialer depends on
Photo by Christina Morillo on Pexels

Your dialers look healthy, yet dispositions hang after an agent picks a status and the agent screens stop updating. In a VICIdial cluster, that often points at one machine: the database and web server.

Every dialer and every agent depends on it. Here's what it does all shift, what happens when it slows, and why it's the machine to protect first.

Two jobs on one machine

The first job is the database. MariaDB on this machine holds every Lead (a person or business you plan to call), every Campaign and every call record. The dialers don't hold that data; they ask this machine for it.

The second job is the web side. In our layout the same machine serves the VICIdial admin pages, the reports and the agent screens. When an agent opens their screen, the browser loads it from here, while their phone connects to a dialer.

What it answers all day

  • Dialers asking which leads to dial next, and recording every call they place.
  • The hand-off. VICIdial gives each answered call to a free agent through the database, so a customer who just said hello is waiting on this machine.
  • Agents saving a Disposition, the result of the call, which is written to the database.
  • Agent screens asking for news every second. On one floor we measured, that polling was 87.5% of all web requests.
  • Managers running reports and searching for leads, against the same tables.

Add it up and it's a busy machine. On one 166-call floor, the database answered 2,230 queries a second.

flowchart LR
  D1[Dialer 1] -->|leads, hand-offs, call records| DB[(Database + web)]
  D2[Dialer 2] -->|leads, hand-offs, call records| DB
  A[Agent screens] -->|ask for news every second| DB
  M[Managers] -->|admin and reports| DB
  DB -. live copy .-> SB[(Standby database)]

Why a slow database stops everything at once

VICIdial keeps its call records in MyISAM tables, which lock the whole table while a read runs. One report that reads the call log for a few seconds makes every disposition wait behind it. On a 60-agent floor, a single day-long count held up to 334 statements for as long as 4 seconds.

The wait spreads outward. Agent screens queue their every-second requests and freeze. The hand-off stalls while the drop timer keeps counting, so calls drop with agents ready. The dialers show the symptom, while the cause sits here.

Before you blame a dialer, look at what is reading the call log. A report, stats tool or lead search that runs for a few seconds mid-shift is enough to make every disposition wait behind it.

Size it for locks, protect it with a standby

This machine rarely runs out of processor. When we replayed a live floor's database traffic at seven times its real speed, about 1,260 calls, the database never needed more than 3.1 of its cores. The slow moments came from table locks on the call log, and the fix was keeping that table small with VICIdial's log archiving.

We still build it on an AMD Ryzen 9 7950X3D with 16 cores, 128 GB and mirrored NVMe, because the agent screens and reports share it with MariaDB. What hardware a VICIdial database server really needs explains the choice.

Protection matters more than size. Lose a dialer and the calls on it drop while the others keep going. Lose this machine with nothing behind it and every agent stops. Our clusters run a standby database that replicates every change and is promoted if the main machine fails, a switch called Failover. Why a cluster needs a standby database covers how it works.

For how this machine fits with the dialers and the network between them, see our complete guide to VICIdial clusters.

Frequently asked

› Do agents' phones connect to the database and web server?
No. The agent's browser loads the screen from it, but the phone connects to a dialer.
› Will a bigger database machine fix slow dispositions?
Usually not. In our replay the database never needed more than 3.1 cores; the waits came from table locks on the call log. Keeping that table small and moving long reads off the shift is what helps.

Running one server today? A plan may still cover you. When you need the database on its own machine with a standby behind it, size your cluster and see today's prices.

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. “The database and web server: the machine every dialer depends on”. VICIfast LLC, November 21, 2026. Retrieved from https://vicifast.com/blog/vicidial-cluster-database-web-role

Have questions?

Related posts

You might be interested in

Comments

Comments are reviewed before they appear. We never publish your email.

No comments yet - be the first.