ViciBox 12 install guide: ISO, setup and default logins
How to install ViciBox 12.0.2 - which ISO to download, Phase 1 to Phase 2, the default logins to change, the known 12.0 bugs and the openSUSE 15.6 problem.
ViciBox 12 is the official VICIdial installation image, and the current release is 12.0.2. It installs in two phases: Phase 1 puts the operating system on the disk, and Phase 2 installs VICIdial, either as an all-in-one Express box or as one role in a cluster. This guide follows the ViciBox 12.0 documentation at docs.vicibox.com and the files on the official download server, both read on 16 October 2026. Where we add advice the docs do not give, we say so.
Read this first. ViciBox 12 is built on openSUSE Leap 15.6, and the openSUSE project said in April 2026 that Leap 15.6 would reach end of life at the close of that month and "no longer receive maintenance or security updates". The download server also holds two ViciBox 13 beta images, but no stable 13 release when we checked. ViciBox 12 still installs and runs. It just means a new install today starts on an operating system that no longer gets security patches.
What is ViciBox 12?
ViciBox 12 is an installation ISO that sets up openSUSE Leap and VICIdial together; its documentation calls it "the official installation image for the ViciDial Call Center Suite". It covers the server only: users, leads and campaigns are left to the VICIdial manuals.
What hardware does ViciBox 12 need?
For a single all-in-one server, the ViciBox 12 docs say to use their Recommended spec at a minimum, and rate it at around 10-15 agents.
| Spec in the docs | CPU | RAM | Storage | What the docs say it suits |
|---|---|---|---|---|
| Minimum | 4 cores, 2.0 GHz or faster | 8 GB | 160 GB | A telephony server with no call recording |
| Recommended | 4 cores, 2.0 GHz or faster | 16 GB | 500 GB | An Express box for around 10-15 agents |
| Dedicated Database for 150 Agents | 8 cores, 2.0 GHz or faster | 32 GB | 500 GB | A more future-proof Express box, fine to about 20 agents |
The same section asks for SATA SSD at a minimum, RAID1 where you can, any CPU newer than AMD Zen 1 or Intel Sandy Bridge, and a 2 TB drive on an all-in-one server that keeps recordings. For the network it wants a static IP, wired connections, and checks of packet loss, jitter and latency to your SIP carrier rather than a speed test.
Which ViciBox 12 ISO should you download?
Download ViciBox_V12.x86_64-12.0.2.iso (standard) or ViciBox_V12.x86_64-12.0.2-md.iso (software RAID1) from the official folder at download.vicidial.com/iso/vicibox/server/. Each is about 2 GB, and each has an .md5 file beside it; compare the checksum before you write the image.
| ISO | Use it when |
|---|---|
| Standard | One drive, a hardware RAID card, a SAN boot, or a virtual machine |
| MD (MultiDevice) | Two plain drives you want mirrored in software RAID1 |
Older 12.0.0 and 12.0.1 images sit in the same folder; use 12.0.2. To write a USB stick, the docs suggest Rufus or imageUSB on Windows and balenaEtcher on a Mac. On a rented VPS you need a provider that lets you boot your own ISO; if yours does not, ViciBox is not an option there.
How do you install ViciBox 12 (Phase 1)?
Boot the ISO, choose Install ViciBox, pick the disk and confirm, then finish the first-login wizard as root.
- Boot from the USB stick or ISO and select Install ViciBox. The installer erases the target disk.
- Pick the installation disk and confirm the data-destruction prompt.
- When the
login:prompt appears, log in asroot. The first login starts a configuration wizard. - Choose the locale, keyboard layout and time zone, and accept the license.
- Set a new root password. The image ships with a known default root password and the wizard lets you keep it; do not. The docs suggest 14 or more characters mixing cases, numbers and symbols, without "vici" or "pass" anywhere in it.
- Let it install updates if the server is online.
- On the MD image, pick the second drive for the RAID mirror.
- At the
vicibox12:~ #prompt, remove the install media and typereboot.
What should you do before installing VICIdial (Phase 1.5)?
Give the server a static IP and a unique hostname, then install updates, because once VICIdial is installed its configuration is tied to the server's IP addresses.
- Static IP and hostname. Run
yast lanand set a static IPv4 address (the docs say VICIdial has not been extensively tested with IPv6), one default gateway, DNS servers and a hostname of 16 characters or fewer, such as DB1, web1 or dialer1 in a cluster. Log out and back in, then test withping -4 google.com. - Updates. Run
zypper up, answerY, then reboot. This also updates the ViciBox installer used in Phase 2, and the docs warn it can be up to 300 MB. Updating first also avoids the 12.0.0 RAID-tool bug, though some of the bugs below are caused by later openSUSE updates, so re-check them after each one. - RAID, MD image only. If you did not add the second drive in Phase 1, run
vicibox-mdraid1, then check the arrays withcat /proc/mdstat.
How do you install VICIdial with vicibox-express (Phase 2)?
Run vicibox-express, answer Y, reboot, then check that VICIdial's processes and Asterisk are up before you open the admin page.
- As root, type
vicibox-expressand answerY. - When the prompt returns, type
reboot. - Log back in and run
screen -ls. Per the docs it can take upwards of 5 minutes, but it should end up showing 11 sockets in/run/screens/S-root. - Run
asterisk -r. You should see processes such as sendcron logging on and off. Typequitto leave. - Browse to the server's IP address, click Administration and log in.
The docs say Express suits fewer than 20 agents or a proof of concept, and its roles can be split off later. For a cluster, run vicibox-install in expert mode on each server, in order: database, then web, then telephony. A cluster built that way scales to 500 agents, according to the same pages.
What is the ViciBox 12 default login?
There are two default logins, and both are public knowledge, so change both on day one.
- Root, for the operating system. The Phase 1 wizard asks for a new root password and accepts the old default if you type it. Set your own, and change it later with
passwd. - The VICIdial admin. The docs log in to Administration as user
6666, with a default password printed in the same step. They recommend giving6666all Admin permissions after the initial setup. We would also change its password straight away and create named admin users, so every change can be traced to a person.
What should you check after installing ViciBox 12?
Check the firewall first, then the certificate, then the time zone.
- Firewall. ViciBox uses firewalld. On 12.0.0 images the docs say firewalld does not start by default; turn it on with
systemctl enable firewalld.serviceand reboot. The default mode loads the VoIP Black List of known SIP abusers. For remote agents,vicibox-firewallswitches to the ViciDial White List, which works with the dynamic portal on port 446. - Ports. Per the docs: SIP on UDP 5060, limited to your carriers and agents; RTP on UDP 10000-20000, open; HTTPS on TCP 443; and secure WebSockets for the web phone on TCP 8089.
- SSL. Point a domain name at the server and run
vicibox-ssl, which requests a Let's Encrypt certificate, sets up renewal and configures Apache and Asterisk. Check it withasterisk -rx "http show status"and over HTTPS in a browser. The web phone needs it. - Time zone.
vicibox-timezonesets the operating system's zone; you still have to set the server's GMT offset under Admin, Servers. - Then VICIdial itself. Work through our VICIdial post-install checklist.
What are the known ViciBox 12 bugs?
Most of the docs' bug-fix page applies to every 12.x server, because several problems come from openSUSE 15.6 updates, not one ViciBox release.
| Problem | Affects | What the docs say to do |
|---|---|---|
| Huge Apache error logs, a slow web server | All 12.x, after openSUSE PHP updates overwrite php.ini | Restore the ViciBox php.ini settings listed on the bug-fix page, then restart Apache |
firewalld fails, yast firewall errors | All 12.x, after firewalld updates | Reinstall it with zypper in --force firewalld, then reboot |
| Dynamic portal unreachable | All 12.x, after an Apache update overwrites listen.conf | Add back the Listen lines for ports 81 and 446 |
| VICIdial misbehaves on a new database | New 12.0 databases | Turn off MariaDB's explicit timestamp defaults (below) |
yast firewall hangs | 12.0.1 | Remove the duplicate ssh service from the external zone |
| Swap array set up wrong | 12.0.0 MD image | Rebuild the swap array as the page shows |
The database fix, as the docs give it:
echo "explicit_defaults_for_timestamp = Off" >> /etc/my.cnf.d/general.cnf
systemctl restart mariadb.service
The docs also warn that the large VoIP Black List can push firewalld into a race condition after changes in yast lan: stop firewalld, make the change, then reboot.
How long does a ViciBox 12 install really take?
The documentation gives no total, and the honest answer depends on whether the hardware, the static IP and the domain name are ready before you start. The docs name two waits: up to 300 MB of updates, and upwards of 5 minutes after the Express reboot before VICIdial's processes are all running. The steps themselves are mostly menus.
The time goes on the static IP, DNS for the certificate, a firewall mode for remote agents, the bug-fix list and a test call through your carrier. Then comes the ongoing part, which on 12.x now includes an operating system with no security updates until a stable ViciBox 13 ships and you move to it. Why VICIdial installs are hard covers those running costs.
Should you install ViciBox 12 in 2026?
Install it if you need VICIdial on your own hardware now and accept the operating-system gap; otherwise wait for a stable ViciBox 13 or choose another base. Our AlmaLinux 9 guide covers the community route on a distribution with security updates until 2032, and installing VICIdial, step by step compares the routes. ViciBox vs managed hosting weighs owning the box against renting one; moving off ViciBox explains a migration.
Or skip all of this
Or skip all of this: a VICIfast server arrives with VICIdial installed in under 40 seconds, with patching, the firewall, SSL and 24/7 monitoring handled, and full root access when you want it. See the VICIdial installation service or every plan on pricing.
Sources
- ViciBox 12.0 documentation (PDF build dated 29 September 2025) - Introduction, Installation, Networking, Maintenance and Bug Fixes.
- The official ViciBox ISO folder - file names, sizes, dates and .md5 files.
- openSUSE News, "Closing Out a Roughly 8-Year Era" (1 April 2026), on the Leap 15.6 end of life.