Installing VICIdial on AlmaLinux 9 or Rocky Linux 9

A platform decision, not a step-by-step

Fast answer: this publication has not run, checked, or pinned a VICIdial install on AlmaLinux 9 or Rocky Linux 9, so this article does not hand you a command sequence for either one. What it gives you instead is what genuinely differs on the Red Hat Enterprise Linux (RHEL) family versus the Debian family for VICIdial specifically, how Security-Enhanced Linux (SELinux) policies and PHP compatibility need to be evaluated, where to find community-maintained installers, and a straight decision rule for choosing between AlmaLinux 9 or Rocky Linux 9, this publication's ViciBox appliance path, and the scratch-install instructions posted on the VICIdial forum for the Debian family.

None of the platform choice below changes what words like agent, campaign, carrier, trunk, channel or DID mean — see VICIdial terminology for complete beginners: users, phones, campaigns and leads if any of those are new. This article only changes how much of the road to get there is already paved.

AlmaLinux 9 and Rocky Linux 9 are both free, binary-compatible rebuilds of Red Hat Enterprise Linux 9, and both are the current RHEL-family targets teams reach for when standardizing on that lineage. Everything below applies equally to either one; nothing in VICIdial's own requirements favors one rebuild over the other.

• No install command sequence for AlmaLinux 9 or Rocky Linux 9 appears anywhere below.
• This publication's most detailed install path is the ViciBox appliance (lab-only, not a from-scratch build) — see Install ViciBox 12 in a lab and reach a secure first login.
• Everything below is read-only checks, real platform differences and a decision rule.

What actually differs on the RHEL family versus the Debian family

Compare actual candidate hosts rather than assuming identical packages. SELinux policy and enforcement vary by installation; Debian also offers SELinux packages. RHEL-family and Debian-family repositories and package names differ. Inspect the enabled repositories, PHP version and module streams on the exact candidate release, then verify compatibility with the chosen VICIdial build before installing anything. RHEL 9 documentation lists PHP 8.0 as the initial AppStream version and 8.2 as an additional stream; neither establishes the default on every related distribution.

None of these differences are exotic to VICIdial. They are exactly the differences anyone moving any Apache/PHP/database-driven application between the two families runs into. What makes VICIdial specifically painful is that its own install tooling, community documentation and forum knowledge base grew up almost entirely on the Debian family and older CentOS releases, so RHEL-family package names, SELinux contexts and firewalld zones get worked out by individual community authors project by project, rather than shipped as VICIdial's own tested default.

SELinux                      | Inspect installed policy and mode on the candidate hostPackage source                | RHEL-family: EPEL plus third-party repos | Debian-family: Debian archive plus third-party reposFirewall tool                 | Inspect the active backend and rules on either familyPHP version handling          | RHEL-family: dnf module streams or Remi  | Debian-family: apt with a pinned package name Detailed, step-by-step guide on this site: ViciBox only (openSUSE-based appliance, lab-only) -- neither a from-scratch RHEL-family nor Debian-family build is currently pinned here.

• SELinux, package source, firewall tool and PHP version handling all differ from the Debian-family path.
• None of these differences are unique to VICIdial; they apply to any similar application moved to the RHEL family.
• The real gap is community tooling maturity, not Linux capability itself.

Assess SELinux policy for the target build

SELinux is a kernel-level access-control layer that enforces which process can read, write or execute which file, socket or port, on top of ordinary Linux permissions. AlmaLinux 9 and Rocky Linux 9 ship it enabled and set to `enforcing`. The cited community guides disable SELinux, but they do not establish that disabling it is universally necessary. Evaluate the security impact and a tested policy for the exact build before choosing a deployment path.

The reason is not that SELinux is bad practice in general; it is that VICIdial was never written with it in mind. Its Perl scripts write and rewrite configuration files, spawn processes and open sockets in ways that assume unrestricted file access. Asterisk, the open-source telephony engine underneath VICIdial that actually places and receives calls, writes recordings, generates PJSIP (a SIP channel implementation) configuration, and reads and writes voicemail and spool directories in places SELinux's default policy was never taught to allow for that binary. Apache's own configuration, and the paths VICIdial's web screens read and write under it, assume the same freedom.

Writing a correct custom SELinux policy for all of that is possible in principle. The reviewed community guides describe permissive or disabled SELinux; this publication has not verified a suitable enforcing policy. Permissive and disabled are different states. Confirm which state a candidate server is actually in before you plan around it; do not assume from the distribution name alone.

cat /etc/os-releasegetenforcesestatus 2>/dev/null | head -n 5php -v

• SELinux ships enforcing by default on AlmaLinux 9 and Rocky Linux 9.
• VICIdial's Perl scripts, Asterisk's file operations and Apache's configuration all assume it is off.
• The cited community guides disable SELinux; this publication has not verified an alternative policy.

The PHP 8.2 reality: old VICIdial code was not written for it

PHP (PHP: Hypertext Preprocessor) is the scripting language behind VICIdial's admin and agent web screens, and the installed version depends on the release and package sources. Older VICIdial revisions may warn or fail under newer PHP versions; check the exact revision and test the target stack.

This becomes a RHEL-specific decision because of how each family lets you manage that mismatch. On the Debian family, pinning an older PHP version alongside 8.2, or holding a package at a known-working version, is a well-worn `apt` pattern with mature third-party repositories behind it. On the RHEL family, the equivalent tools are `dnf module` streams, which switch the whole system's default PHP stream, or the Remi repository, which offers multiple PHP versions side by side with its own naming and configuration conventions. Community guides for VICIdial on AlmaLinux 9 lean on Remi specifically, because `dnf module` alone often cannot reach far enough back for an older VICIdial revision's actual PHP requirement.

Before deciding anything, find out which PHP version the VICIdial revision you intend to run actually needs, and which PHP version the candidate server already has. A brand-new revision on 8.2 may need nothing at all; an older one will need a specific, deliberately chosen PHP version, not whatever the distribution happened to install.

php -vphp -m | grep -i mysqlirpm -q php 2>/dev/null || echo 'no rpm package named php: this may not be a RHEL-family host'

• Check the installed PHP version and the compatibility of the exact VICIdial revision.
• Older VICIdial revisions may warn or fail under newer PHP versions; test the specific revision.
• Pinning an older PHP version uses dnf module streams or the Remi repository on the RHEL family, versus a pinned apt package on the Debian family.

Where to get a procedure you can actually trust

This publication is not the place to get a step-by-step AlmaLinux 9 or Rocky Linux 9 install sequence, because it has not run one and will not invent one to fill the shape of a how-to. Two kinds of source are worth naming instead, and they are not the same kind of authority.

The VICIdial project's own scratch-install instructions are the first stop, and the closest thing to vendor guidance that exists for building VICIdial from individual packages on any Linux distribution, RHEL-family included. Read them in full before running anything; they describe the components VICIdial needs, Asterisk, a database server, Apache, Perl and PHP among them, and the order they go in, without assuming any one distribution's package names.

The actively maintained community auto-installer for AlmaLinux 9 and Rocky Linux 9 with Asterisk 18 is the script maintained by carpenox at dialer.one, the CyburDial project. It specifically addresses the DAHDI (Digium/Asterisk Hardware Device Interface) and PHP 7 packaging problems that used to block a clean AlmaLinux 9 build, and it is the installer named consistently across independent community sources as the current, working option for this platform. KingAsterisk and ViciStack each publish their own separate manual walkthroughs covering the same ground. All three of these are community-maintained: written, tested and updated by individuals and small teams outside the VICIdial project, not by VICIdial itself and not verified by this publication.

• VICIdial's own scratch-install instructions describe components and order for any distribution, RHEL-family included.
• The carpenox / CyburDial auto-installer at dialer.one is the actively maintained community installer for AlmaLinux 9 and Rocky Linux 9 with Asterisk 18.
• KingAsterisk and ViciStack publish separate community walkthroughs; read any of these in full, including their own caveats, before running anything.

What this publication has verified, and what it has not

Say the gap plainly, once: this publication has not verified a from-scratch install on AlmaLinux 9 or Rocky Linux 9. It has never been run, checked or pinned here, and nothing in this article should be read as changing that.

This publication's most detailed, vendor-doc-backed install path is Install ViciBox 12 in a lab and reach a secure first login — a prebuilt appliance, not a from-scratch build, and currently lab-only. See ViciBox version status: why ViciBox 12 and ViciBox 13 are lab-only lessons for why (openSUSE Leap 15.6 has been end-of-life since April 30, 2026).

Whichever family you land on, hardening the server is a separate job from installing it, and this publication already covers that ground without repeating firewall specifics here: see Secure your VICIdial server: SSH, firewall and access control for SSH lockdown, fail2ban and the exact port list VICIdial needs open, then apply it through whichever firewall tool your server actually runs — firewalld on the RHEL family and on ViciBox, UFW on the Debian family.

Decide: ViciBox, RHEL-family, or Debian-family from scratch

Three situations cover most real decisions here. If you have a genuinely free choice of distribution and a prebuilt appliance is acceptable rather than a from-scratch build, pick Install ViciBox 12 in a lab and reach a secure first login — the most detailed, vendor-doc-backed path on this site, though it is currently lab-only (see ViciBox version status: why ViciBox 12 and ViciBox 13 are lab-only lessons).

If you need a from-scratch build and your organization has already standardized on the RHEL family, or a support contract or compliance auditor names Red Hat Enterprise Linux or one of its rebuilds specifically, pick AlmaLinux 9 or Rocky Linux 9 and use the scratch-install instructions posted on the VICIdial forum or the carpenox / CyburDial installer, read in full first — that requirement is not something an install guide can argue you out of.

If you need a from-scratch build on the Debian family specifically, go straight to the scratch-install instructions posted on the VICIdial forum; this publication no longer maintains its own pinned installer for that path.

If you are still unsure which situation you are in, the read-only checks earlier in this article, distribution, SELinux state and installed PHP version, tell you what you are actually starting from. Run them on the candidate server before you commit to any path, so the decision rests on the server in front of you rather than on a distribution's reputation.

• Free choice of distribution, appliance model acceptable: choose Install ViciBox 12 in a lab and reach a secure first login — lab-only, not yet a production path.
• From-scratch build, standardized or compliance-bound to the RHEL family: choose AlmaLinux 9 or Rocky Linux 9, using the scratch-install instructions posted on the VICIdial forum or the carpenox / CyburDial installer, read in full first.
• From-scratch build on the Debian family: use the scratch-install instructions posted on the VICIdial forum directly — this publication does not maintain a pinned installer for that path.
• Either way, confirm SELinux state, PHP version and distribution on the real candidate server before deciding, not from memory or a guess.