Skip to content

Guide

What Server Is Required for VICIdial? Sizing Factors Explained

How to size a VICIdial server — concurrent calls, recording, CPU, RAM, disk, network, and when to move to a clustered setup with separate database and telephony servers.

Author
JH Dialer Engineering Team
Published
Reading time
2 min read
On this page
  1. What determines server size?
  2. Which resources matter most?
  3. When should you move to a cluster?
  4. What else should the server have?
  5. How do we size a server for you?

What determines server size?

Agent count alone is a poor guide. What actually loads a VICIdial server is:

  • Concurrent calls — a predictive campaign at 3:1 with 30 agents can have far more live channels than 30.
  • Recording — every recorded call writes audio to disk and later compresses it.
  • Codecs and transcoding — converting between codecs costs CPU.
  • Database activity — real-time reports, large lead lists and long log tables.
  • Features in use — AMD, conferences and IVR all add load.

Which resources matter most?

Resource Why it matters
CPU Asterisk audio processing, AMD and transcoding. Consistent single-core speed matters.
RAM Database caching and many concurrent processes.
Disk Database writes and recordings — fast SSD/NVMe storage avoids audio and reporting issues.
Network Low latency to carriers and agents; enough bandwidth for peak calls.

When should you move to a cluster?

Split roles when a single server starts showing strain — audio glitches at peak, slow real-time screens, or long maintenance on large tables. A typical progression:

  1. Single server — all roles on one machine.
  2. Separate database — database on its own server; telephony and web on another.
  3. Multiple telephony servers — calls distributed across several Asterisk servers.
  4. Separate web and archive servers — agent web traffic and recording storage moved off the telephony nodes.

What else should the server have?

  • A supported Linux OS (ViciBox is the common choice).
  • Accurate time synchronisation — call-time rules depend on it.
  • Firewall allow-listing for admin and SIP access.
  • Off-server backups.
  • Monitoring for disk space — full disks are a common cause of outages.

How do we size a server for you?

We start from your peak concurrent calls, recording policy and reporting needs, then recommend a single server or a cluster layout with room to grow. See dedicated servers or cloud hosting.

Frequently asked questions

Can VICIdial run on a shared virtual server?

It can for testing, but production dialers are sensitive to CPU contention and timing. Use a dedicated instance with guaranteed resources, or dedicated hardware for larger volumes.

Does VICIdial need a public IP address?

Usually yes, for carrier connectivity and remote agents — which is why firewall allow-listing and SIP hardening are essential.

Tell us how your call center runs. We’ll design the dialer around it.

Share your agent count, campaigns and CRM. You’ll get a technical recommendation and a written quotation — no obligation.