Installing VICIdial from Scratch on Debian

Debian and Ubuntu are close cousins, so a from-scratch VICIdial build on Debian follows almost the same path. Ubuntu is built on Debian, which is why most of the steps carry over. The differences are in package names, default versions, and a few defaults that lean more conservative on Debian. If you have built on Ubuntu before, this will feel familiar.

The same overall flow

The arc is identical: clean OS, install dependencies and Perl modules, fetch a matched Asterisk source, compile and install Asterisk, fetch VICIdial, run the install script, load the database, and enable the keepalive crontab. The compile is still the longest step, and matching the Asterisk version to the VICIdial release still matters more than chasing the newest build.

flowchart TD
  A[Clean Debian install] --> B[Install deps and Perl modules]
  B --> C[Compile and install Asterisk]
  C --> D[Run VICIdial install script]
  D --> E[Write conf files and dialplan]
  E --> F[Add server trunk]
  F --> G[Enable keepalive crontab]

Where Debian differs

The most visible difference is package names. Some packages Ubuntu provides under one name are split, renamed, or live in a different component on Debian, so a dependency list copied straight from an Ubuntu walkthrough will leave gaps. Expect to look up a handful of names. Debian also tends to ship older stable versions of web and database packages, which is usually fine for VICIdial and sometimes helpful, since the older versions are well tested against it.

Sudo is not installed by default on a minimal Debian, and the default account setup differs, so plan to work as root or set sudo up first. Firewall defaults are minimal too, which means you open ports deliberately rather than fighting a preconfigured filter.

There is an upside to Debian being conservative. The packages it ships tend to have been in stable for a while, so you hit fewer surprises from a library that changed behavior last month. The flip side is that if you need a newer version of something, you may end up pulling it from backports or building it yourself, which adds a step. For the core VICIdial dependencies this rarely comes up, but it is worth knowing why a package looks a version or two behind what an Ubuntu walkthrough mentions.

Wiring up calls

Once the install script finishes and the Conf file set is written, you connect a carrier. You add a Server trunk so Asterisk knows how to reach your provider, then supply credentials. Most providers use SIP (Session Initiation Protocol) for this, though some still offer IAX2, an older Asterisk-native protocol that can be simpler across some firewalls because it uses a single port. Pick whichever your provider supports and your network allows.

Before you call it done

As on Ubuntu, the box can look installed yet place no calls until the Keepalive crontab is active. Confirm those jobs are running, place a test call, and check the agent screen connects before you onboard a team. A short test cycle here saves a lot of confusion later.

For the bigger picture, see our complete VICIdial install guide. Since the steps mirror the Ubuntu route so closely, it is worth reading installing from scratch on Ubuntu alongside this for the parts they share.

If hunting down package names and compiling Asterisk is not your idea of a good day, VICIfast provisions a secured dialer for you in under 40 seconds. See VICIfast pricing.