ViciBox vs generic openSUSE vs Ubuntu/Debian for VICIdial beginners

Start here

This curriculum's install path is ViciBox. Generic openSUSE is worth knowing for its own sake, and a from-scratch Ubuntu or Debian install is a legitimate approach elsewhere, but neither is what the rest of this library builds on top of. Do not layer one path's commands over another's host.

This lesson exists because the three choices look superficially similar — all three end with a Linux host you can SSH into — and it is genuinely easy to assume they are interchangeable starting points for VICIdial. They are not, and the difference shows up the first time you try to follow an install step written for one of the other two.

None of the three choices is objectively wrong in general. A from-scratch Ubuntu or Debian install is a legitimate way to run VICIdial in production, maintained by administrators who prefer full control over every package. This curriculum simply does not walk through that path — it walks through ViciBox, and says so plainly rather than leaving the gap unstated.

Generic openSUSE, similarly, is not a lesser choice than ViciBox — it is simply a different layer of the stack. Choosing it teaches you the operating system underneath what ViciBox eventually builds, which is valuable in its own right, but it stops well short of a working dialer, because none of the telephony-specific configuration ViciBox's own installer performs happens on a plain openSUSE host by itself.

If you find yourself wanting both — the deep operating-system fluency generic openSUSE teaches and a working VICIdial lab — the honest path is to do them as two separate exercises on two separate hosts, not to try to convert one into the other partway through.

The remaining lessons in this stage assume you have settled on ViciBox. If you have not, the checks below still work as a general diagnostic for any host, but the lessons that follow this one are written specifically for the appliance path.

The idea in plain language

An appliance ISO controls the base system and the application configuration together — that is what ViciBox is. A generic distribution gives you a starting operating system and nothing telephony-specific. A from-scratch installer starts from a known clean host and builds up, one package and one configuration file at a time. Each approach is internally consistent; problems start when their commands or assumptions get mixed on the same machine.

The most common mistake this lesson exists to prevent is running a ViciBox-specific script, or a from-scratch install guide's package commands, against a plain openSUSE host that was never taken through ViciBox's own Phase 1 and Phase 2 installers. The result is a host that resembles ViciBox in some ways and is missing critical pieces in others, which is far harder to diagnose than either a clean generic install or a clean ViciBox appliance.

Try one safe check

Record the operating system and kernel of the host in front of you before selecting which guide to follow. The output is evidence for your notes, not something to act on directly. Writing this down before you pick a guide, rather than after something goes wrong, is a small habit that pays off the first time a symptom turns out to be a distribution mismatch rather than a configuration mistake.

cat /etc/os-releaseuname -r

• The distribution ID and version, from the previous two lessons' checks
• The kernel version, which can matter for hardware or virtualization compatibility

Confirm whether this is actually stock ViciBox

ViciBox commonly includes its own firewall helper and packages. Their presence is useful evidence, but files can be copied or packages changed; it does not prove an installation is stock.

This check also doubles as a way to verify a lab you inherited from someone else, or a VM template you were handed, before trusting that it is what its name or description claims. Compare the tool and package results with the installation records and the vendor’s documentation before relying on appliance-specific instructions.

The captured file list is one lab observation. Packages, paths and helper names may differ by ViciBox version; use the candidate build’s records and vendor documentation to identify it.

ls -l /usr/bin/VB-*rpm -qa 'vicibox*'

• Whether /usr/bin/VB-firewall is present
• Which vicibox-prefixed packages the RPM database lists

Ready for the next lesson

This curriculum's install path is ViciBox. Continue to the version-status lesson next.