Cross-Cluster Communication

Cross-Cluster Communication (CCC) is a VICIdial capability that enables multiple independent VICIdial clusters to communicate and share resources — including agents, calls, and real-time data — across separate server installations. CCC allows geographically distributed or organizationally separate VICIdial deployments to function as a coordinated operation, routing calls between clusters and sharing agent availability information.

How It Works in VICIdial

CCC operates by establishing communication channels between separate VICIdial cluster databases and telephony servers. Each cluster maintains its own database, web servers, and Asterisk telephony servers, but CCC enables them to exchange real-time status information about agent availability, call queues, and campaign activity.

When a call needs to be routed to an agent on a different cluster, CCC coordinates the transfer through IAX2 or SIP trunks connecting the Asterisk servers between clusters. The call audio is bridged across the inter-cluster trunk while the signaling and lead data are synchronized between the databases. This allows an inbound call arriving at Cluster A to be handled by an agent logged into Cluster B, with full lead data and disposition capabilities.

Database synchronization between clusters uses replication or API-based data exchange to keep lead records, callback schedules, and DNC lists consistent across all clusters. Real-time status updates ensure that each cluster has accurate information about agent counts and queue depths on the other clusters, enabling intelligent cross-cluster routing decisions.

Why It Matters

CCC is essential for large-scale VICIdial operations that have outgrown a single cluster or need geographic distribution for redundancy and latency optimization. Common use cases include: multi-site call centers that need unified routing across locations, disaster recovery configurations where a secondary cluster takes over if the primary fails, and large operations that need to segregate workloads while maintaining the ability to share overflow capacity.

Without CCC, each VICIdial cluster operates as an isolated island — agents on one cluster cannot receive calls from another, and there is no way to balance workloads across installations. CCC transforms multiple clusters into a coordinated system, enabling operations to scale beyond the limits of a single cluster while maintaining routing flexibility. The complexity of CCC configuration requires careful planning of network connectivity, database replication topology, and inter-cluster trunk capacity.