VICIdial Clustering: What Breaks at Scale and How to Fix It

Your single-server VICIdial box just hit a wall. Agents get "time synchronization" errors, the hopper empties faster than it fills, and your real-time report loads like it's 2003. You've Googled "VICIdial cluster setup" and found a 15-year-old PDF, some AI-generated marketing content, and fragmented forum threads. The core problem: Asterisk doesn't scale vertically. A 64-core server chokes at the same agent count as a quad-core. A single all-in-one VICIdial server maxes out around 20-25 agents for predictive outbound. That's not hardware — it's architecture. The solution is more servers, each doing one job well. The Four Server Roles Database server. The brain. Every agent login, disposition, hopper query, and real-time report flows through one MySQL instance. VICIdial uses MyISAM exclusively — not InnoDB. The VICIdial creator has been clear about this: "We do not recommend using InnoDB under any circumstances." Use SSDs at minimum, NVMe for 200+ agents, and an LSI Logic MegaRAID contr