Archives 2026

CVE-2026-98432: Critical Linux Kernel Use-After-Free in IPv4 TCP — What It Is and How to Fix It

Futuristic server room network diagram showing a red failure spreading through blue system connections

CVE-2026-98432: Critical Linux Kernel Use-After-Free in IPv4 TCP — What It Is and How to Fix It

A critical vulnerability in the Linux kernel (CVE-2026-98432) has drawn significant attention. Rated 9.8 (Critical) by the Linux kernel CVE team and marked High priority by Ubuntu, it involves a use-after-free race condition in IPv4 TCP option handling.

As of late October 2026, fixed packages are available on several distributions including Debian, Oracle Linux, parts of Amazon Linux, openSUSE Leap 16.0, and SUSE Linux Micro 6.2. Ubuntu still lists supported releases as vulnerable with fixes in progress, while Red Hat has deferred its fix. A research demonstration (involving Anthropic’s Claude) reportedly produced a laboratory remote-root exploit under specific conditions, underscoring the need for prompt action once patches arrive.

What Is CVE-2026-98432?

The bug lives in the IPv4 TCP handshake code. When the kernel creates a new child socket from a request socket (tcp_v4_syn_recv_sock()), it transfers ownership of the IP options (ireq->ireq_opt → newinet->inet_opt) without copying them.

A concurrent CPU can process a retransmitted SYN for the same request socket and build a SYNACK (tcp_v4_send_synack() → ip_options_build()). Because the options are freed with a plain kfree() (no RCU grace period) when the child socket is destroyed, this creates a classic use-after-free. A related path exists with TCP request-socket migration (net.ipv4.tcp_migrate_req=1 or certain BPF programs).

IPv6 is largely unaffected by the primary issue (options are duplicated), though a similar migration problem exists for CALIPSO and is addressed separately.

The flaw has been present since roughly Linux 4.4. Upstream fixed it by switching to kfree_rcu() in the relevant destructors (commit e3f33b0a1d89...). Stable kernels that include the fix include 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10, and mainline 7.3+.

Impact and Exploitability

  • Remote, unauthenticated network attack surface (TCP connections).
  • Potential outcomes: kernel crash / denial of service, memory corruption, or (in advanced cases) privilege escalation to root.
  • Winning the race is non-trivial, which is why some vendors score it lower (e.g., SUSE and Oracle 8.1, Red Hat ~5.9–8.1, Amazon 7.0). Ubuntu and the kernel CNA use the 9.8 score.
  • No confirmed widespread in-the-wild exploitation has been reported as of this writing, and it is not listed in CISA’s KEV catalog. However, a public research demonstration of a zero-click remote-root chain (particularly effective against multipath TCP listeners) raises the urgency.

Any system accepting TCP connections on a vulnerable kernel is potentially exposed—servers, cloud instances, containers sharing the host kernel, etc.

Current Status (as of 29 October 2026)

DistributionStatusNotes / Fixed Version
Ubuntu 22.04 / 24.04 / 26.04 / 26.10Vulnerable – fix in progressTarget versions exist but not yet released
Ubuntu 16.04 / 18.04 / 20.04VulnerableNo fix date announced
Debian 12 (bookworm) / 13 (trixie)Fixed6.1.190-1 / 6.12.113-1
Oracle Linux (UEK)FixedMultiple ELSA advisories
Amazon Linux 2023 (some kernels)Partially fixedkernel 6.18 and 6.12 fixed; others pending
openSUSE Leap 16.0Fixedkernel 6.12.0-160000.40.1 or later
SUSE Linux Micro 6.2Fixedkernel 6.12.0-160000.40.1 or later
SLES 15 SP4–SP6 LTSS / SLES 16.0Fixed or in progressSee SUSE advisories (e.g. SUSE-SU-2026:24386-1)
RHEL 8/9/10 + OpenShiftFix deferredNo released packages yet

Always check the official trackers (Ubuntu CVE page, SUSE CVE page, etc.) for the latest package status, as this changes quickly.

How to Check If You Are Affected

  1. Identify your running kernel: uname -r
  2. On Ubuntu: dpkg -l | grep linux-imageThen match against https://ubuntu.com/security/CVE-2026-98432.
  3. On openSUSE / SUSE: rpm -q kernel-default # or zypper se -s kernel-defaultCompare against the fixed version (e.g. 6.12.0-160000.40.1+).
  4. Monitor for available updates on your distribution.

Steps to Fix the Vulnerability

Primary fix: Install the patched kernel and reboot.

On Ubuntu (once packages are published)

sudo apt update
sudo apt full-upgrade
sudo reboot

On Debian

sudo apt update
sudo apt full-upgrade
sudo reboot

On openSUSE Leap / SUSE Linux Enterprise / SUSE Linux Micro

sudo zypper refresh
sudo zypper update
# or more specifically:
sudo zypper in -t patch openSUSE-...   # follow the exact patch name from the advisory
# or
sudo zypper up kernel-default
sudo reboot

For openSUSE Leap 16.0 and SUSE Linux Micro 6.2 the fixed kernel is 6.12.0-160000.40.1 (or later). After updating, confirm with uname -r.

On RHEL / AlmaLinux / Rocky / Oracle (when available)

sudo dnf update kernel
sudo reboot

Important: The vulnerability is fixed only after the system is running the patched kernel. Simply installing the package is not enough—reboot is mandatory.

Temporary Mitigations (While Waiting for Patches)

These reduce attack surface but do not fully eliminate the primary race:

  • Disable TCP request-socket migration: sudo sysctl -w net.ipv4.tcp_migrate_req=0Make it persistent by adding the line to /etc/sysctl.d/99-tcp-migrate.conf (or similar) and running sysctl --system.
  • Limit exposure of TCP services to untrusted networks (firewall rules, security groups, reverse proxies).
  • Prefer IPv6-only listeners where feasible (the primary path is IPv4-specific).
  • Avoid enabling multipath TCP (MPTCP) on publicly reachable services if not required.

These are stop-gaps only. The real solution is the kernel update.

Best Practices Going Forward

  • Subscribe to your distribution’s security notices (Ubuntu USN, SUSE Security Advisories, etc.).
  • Enable automatic security updates where appropriate, but treat kernel updates carefully (test first in non-production).
  • Maintain an inventory of kernel versions across your fleet (especially cloud instances and containers).
  • For high-security environments, consider live-patching solutions once they support this CVE, though a full reboot remains the cleanest approach for kernel fixes of this type.

Conclusion

CVE-2026-98432 is a serious race-condition use-after-free in a core networking path. While reliable remote exploitation is non-trivial, the combination of a 9.8 CVSS score, network reachability without authentication, and demonstrated research exploits makes it high priority.

Monitor the official trackers closely. As soon as fixed kernel packages appear for your release (already available for openSUSE Leap 16.0, SUSE Linux Micro 6.2, Debian, and Oracle), install them and reboot. Until then, apply the temporary mitigations and restrict network exposure.

Stay patched, stay safe.

PHP2Shell: Critical PHP Remote Code Execution Vulnerabilities Require Immediate Action

phpshell

PHP2Shell: Critical PHP Remote Code Execution Vulnerabilities Require Immediate Action

phpshell

The PHP community has released emergency security updates to address two critical remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619, collectively being referred to as PHP2Shell. Both vulnerabilities can allow an unauthenticated attacker to execute code on affected web servers through specially crafted HTTP requests. PHP has rated both vulnerabilities as 9.2 (Critical) and administrators should patch immediately. [almalinux.org], [almalinux.org]

The vulnerabilities affect multiple PHP versions and deployment methods, including PHP-FPM, Apache mod_php, CGI, LiteSpeed, and FrankenPHP installations. PHP released fixed versions on October 21, 2026, with updates available in:

  • PHP 8.2.35
  • PHP 8.3.36
  • PHP 8.4.27
  • PHP 8.5.12

[almalinux.org], [phpvulnera…lities.app]

ViciBox 11 and ViciBox 12

The ViciDial team has already published fixes for supported ViciBox releases.

ViciBox 11

Documentation:

Update commands:

zypper ref
zypper dup --from openSUSE-Leap-15.5-ViciDial-ViciBox --allow-vendor-change
systemctl restart apache2

After updating, verify PHP:

php -v

You should see:

PHP 7.4.34-dev

ViciBox 12

Documentation:

Update commands:

zypper ar https://download.opensuse.org/repositories/devel:/languages:/php:/php82/openSUSE_Leap_15.6/devel:languages:php:php82.repo
zypper mr -f devel_languages_php_php82
zypper --gpg-auto-import-keys ref
zypper dup --from devel_languages_php_php82 --allow-vendor-change
systemctl restart apache2

After updating, verify PHP:

php -v

You should see:

PHP 8.2.35 or later.

Important Note for ViciBox 11 Users

The ViciDial team has indicated that it is becoming increasingly difficult to maintain and build packages for the aging ViciBox 11 platform. Administrators still running ViciBox 11 or older should begin planning an upgrade path, as older openSUSE repositories may eventually be removed from public mirrors.


AlmaLinux Fix

AlmaLinux has released patched PHP packages for all supported PHP streams across AlmaLinux 8, 9, and 10. The AlmaLinux project confirmed that patched packages are now available in the production repositories. [almalinux.org]

To update:

sudo dnf clean metadata
sudo dnf upgrade 'php*'

Restart PHP-FPM:

sudo systemctl restart php-fpm

If you are using Apache with mod_php:

sudo systemctl restart httpd

Verify the installed version:

php -v

For systems running PHP 8.2, the patched version should be:

PHP 8.2.35

or newer. AlmaLinux has also backported protections for some older, end-of-life streams where possible. [almalinux.org], [computingf…rgeeks.com]


Rocky Linux Fix

Rocky Linux administrators can patch affected systems using the standard AppStream update process. Updated packages have been synchronized from Red Hat’s security advisories for supported PHP streams. [computingf…rgeeks.com]

Update PHP:

sudo dnf upgrade 'php*'

Restart services:

sudo systemctl restart php-fpm
sudo systemctl restart httpd

Verify:

php -v

Supported streams should be updated to patched package releases, including PHP 8.2.35 and PHP 8.3.36 where applicable. [computingf…rgeeks.com], [php2shell.app]


Special Notice for VICIdial Servers Running PHP 7.4

Many older VICIdial deployments on AlmaLinux 8, Rocky Linux 8, and ViciBox 11 continue to use PHP 7.4. While the upstream PHP project no longer maintains the 7.4 branch, several distributions have backported security fixes to their packaged versions. The PHP2Shell vulnerabilities have been patched in supported vendor repositories even though the version number may still report as PHP 7.4.x. Administrators should not assume they are protected simply because they are running PHP 7.4 and should verify that all available operating system updates have been installed. [computingf…rgeeks.com], [php2shell.app]

AlmaLinux PHP 7.4

Update all PHP packages:

sudo dnf clean all
sudo dnf upgrade 'php*'
sudo systemctl restart httpd

Verify installed packages:

rpm -q php-common
php -v

AlmaLinux has released patched packages for PHP 7.4 in its repositories, including backported fixes for the PHP2Shell vulnerabilities. [computingf…rgeeks.com], [almalinux.org]

Rocky Linux PHP 7.4

Update all PHP packages:

sudo dnf clean all
sudo dnf upgrade 'php*'
sudo systemctl restart httpd

Verify package versions:

rpm -q php-common
php -v

Rocky Linux has synchronized the corresponding security updates from Red Hat for supported PHP 7.4 streams. Because Red Hat backports security fixes, the displayed version number may not change significantly even though the vulnerability has been patched. Administrators should review package changelogs and installed RPM versions rather than relying solely on php -v. [computingf…rgeeks.com], [php2shell.app]

Verify Your System Is Patched

After updating, verify your installed PHP packages:

rpm -q php-common

Or review the package changelog:

rpm -q --changelog php-common | grep CVE

If your repository updates are current and the CVE references appear in the changelog, the PHP2Shell fixes have been applied even if the PHP version string still shows 7.4. [php2shell.app]


IMPORTANT: PHP 7.4 is officially end-of-life upstream. While AlmaLinux, Rocky Linux, and ViciBox may provide backported security fixes, organizations should develop a migration plan to PHP 8.2 or newer as soon as practical for long-term security and support. [computingf…rgeeks.com], [almalinux.org]


What Administrators Should Do Right Now

  1. Identify all servers running PHP.
  2. Update PHP packages immediately.
  3. Restart PHP-FPM and/or Apache after patching.
  4. Verify the running version.
  5. Review logs for suspicious requests dating back to October 2026.
  6. Prioritize systems using Apache mod_php, as PHP developers have identified them as the highest-risk deployment model. [hackread.com], [notebookcheck.net]

Final Thoughts

Unlike vulnerabilities that affect a specific CMS or plugin, PHP2Shell targets the PHP runtime itself. This means WordPress, Laravel, Drupal, Joomla, VICIdial, custom applications, and virtually any PHP-powered application may be exposed if the underlying PHP installation remains unpatched. The safest course of action is simple: update PHP immediately and verify that your services have restarted successfully. [almalinux.org], [phpvulnera…lities.app]

Chris aka carpenox

VICIdial Development Roundup: Key Changes From Late November 2025 to Early 2026

2FA Agent

Allow Stero Recordings

VICIdial Development Roundup: Key Changes From Late November 2025 to Early 2026

By Carpenox — VICIdial Architect, Troubleshooter, and Eternal Code Archaeologist

Every few months I like to step back, sift through the commit logs, and take stock of how VICIdial continues to evolve. Since late November 2025, the project has seen a surprisingly dense wave of improvements — from AGI-level call‑flow logic to backend archival tooling, adaptive dialing enhancements, PHP8 compatibility, and even new experimental VCA components.

This cycle wasn’t about flashy UI changes. It was about tightening the engine, fixing long‑standing edge cases, and expanding the adaptive dialer’s intelligence. Below is my curated breakdown of what matters, why it matters, and how these updates impact real‑world call center operations.


AGI & Call‑Flow Enhancements

agi-DID_route.agi — 251112-1517

Alter CID Name

Added alter_cid_name option
A small but meaningful upgrade. This gives inbound routing more flexibility when manipulating Caller ID Name data — especially useful for branded routing, DID‑based identity masking, and carrier‑specific CNAM quirks.


VD_amd.agi — 260129-1443

Reinserts missing vicidial_auto_calls records
This is a big reliability win. In rare race conditions, AMD could lose track of an auto‑call record. This patch ensures the system self‑heals instead of leaving orphaned calls or broken agent states.


agi-VDAD_ALL_outbound.agi — 251020-0835

Allow Recording DTMF Detection
Allow recording DTMF Muting

Added recording_dtmf_muting + stereo recording fix
DTMF muting is essential for PCI‑sensitive environments. Stereo recording fixes help anyone using dual‑channel compliance recording or advanced QA analytics.


cm_areacode.agi — 260108-0052

cm_postal.agi — 260107-2119

Both now update vicidial_list records with optional field variables
These scripts finally behave like first‑class data‑enrichment tools. If the lead exists, they can now push enriched metadata directly into custom fields — a huge win for automated lead hygiene.


agi/piper_generate.pl — 251014-1211

piper_generate_names.pl — 251104-0908

First build — part of the growing TTS/voice asset ecosystem.

First build; TTS caching added
Based on cepstral_generate.pl, this new generator caches TTS files for reuse. That means faster IVR prompts, fewer CPU spikes, and smoother high‑volume inbound flows.


Admin & Backend Maintenance Tools

ADMIN_archive_log_tables.pl — 260111-2138

Added --agent-log-only flag
Perfect for shops that want to archive agent logs without touching other datasets.


ADMIN_cold_storage_log_tables.pl — 251230-0853

Added --vl-year flag
Lets you target year‑specific vicidial_log_archive_YYYY tables. Cleaner, safer archival workflows for long‑running systems.


ADMIN_keepalive_ALL.pl — 260126-1334

Now checks reserved_extensions against dialplan numbers
This prevents accidental collisions when generating conf files — a subtle but important safeguard for multi‑tenant or heavily customized dialplans.


Adaptive Dialer Intelligence Upgrades

adapt percent-max

AST_VDadapt.pl — 251205-0949

Added adaptive_percentmax_percentage + new ADAPT_PERCENTMAX dial method
This is one of the most meaningful dialing upgrades in years. It gives admins tighter control over max pacing behavior and reduces the risk of over‑dialing during volatile traffic periods.


AST_VDauto_dial.pl — 251205-1455

Added SHARED_ADAPT_PERCENTMAX
This allows multiple campaigns to share adaptive pacing logic — ideal for blended or load‑balanced environments.


AST_list_export.pl

  • 251128-1536 — Added --basic-export
  • 251130-0006 — Added --custom-export=XXX

These options make exports far more flexible, especially for CRMs that expect specific field layouts.


AST_update_AMI2.pl — 251203-2218

Added server_live_partitions inserts/updates
Improves AMI‑driven monitoring and partition‑aware reporting.


New & Experimental VCA Components


experimental/VCA/AST_VCA_log_report.php — 190329-1852

Legacy first build, but still relevant as the VCA suite expands.


experimental/VCA/VCA_client_settings.pl — 260112-1114

Initial build — foundational for client‑side VCA customization.


experimental/VCA/VCA_log_manage.pl — 260112-1455

First version — derived from the archive log tools.


extras/CRM_log_manage.pl — 260117-0756

First version — CRM‑focused log management built on the VCA framework.


Web Interface & PHP8 Compatibility

www/agc/functions.php — 251205-1742

Fix for undefined variable issues — small but necessary cleanup.


www/agc/vdc_db_query.php — 251124-0935

Added lead status display for callback list output
A quality‑of‑life improvement for agents and supervisors.


www/agc/vicidial.php

  • 251124-0936 — Lead status display for callbacks
  • 260106-1418 — PHP8 fixes

The PHP8 transition continues, and these patches keep the AGC stable.


www/vicidial/AST_hangup_cause_report.php — 260103-1900

Fix for missing variables in links — improves report reliability.


performance report update

www/vicidial/AST_server_performance.php — 251001-1700

Switched from Ploticus to Graph.js
This is a modernizing move. Graph.js is lighter, more flexible, and plays better with responsive layouts.


www/vicidial/AST_timeonVDADallSUMMARY.php — 251205-1931

Added ADAPT_PERCENTMAX support — keeping reporting aligned with the new dialer logic.


www/vicidial/admin.php

alter CID name
  • 251112-2201 — Added alter_cid_name DID option
  • 251204-0757 — Added SERVER DRIVE PARTITIONS display
partition sizes
crashed tables
  • 251211-1134 — Added ADAPT_PERCENTMAX + adaptive_percentmax_percentage
  • 260106-1438 — PHP8 fixes + 2026 date change
  • 260126-1335 — Added reserved_extensions vs dialplan number check

This file saw the most action — reflecting how central the admin panel is to daily operations.


API Improvements

non_agent_api.php

  • 251205-1456 — Added ADAPT_PERCENTMAX dial method
  • 260123-1020 — Fixed pause_sec in agent_stats_export

API parity with new dial methods is essential for third‑party integrations, and the pause_sec fix resolves a long‑standing annoyance for analytics tools.



Additional System & Campaign Enhancements (UI, Compliance, Dialing Logic, and Security)



While the core AGI and backend updates defined this development cycle, VICIdial also introduced a wide range of UI‑level, compliance‑focused, and workflow‑refining features across System Settings, Campaigns, In‑Groups, and DIDs. These changes may look subtle at first glance, but they significantly improve agent experience, dialing accuracy, security posture, and administrative control.

Below is my breakdown of the most impactful additions.


Agent Experience & Workflow Controls

Hide Agent Failed Dial Codes

A new option that replaces raw SIP failure codes with a custom message.
This prevents agents from being overwhelmed by technical alerts and keeps the manual dial workflow clean.

Dialstring Filtering

Manual & 3‑Way Dialstring Filters

A major upgrade for dialing hygiene.
You can now enforce rules like:

  • Digits only
  • Digits + plus sign
  • Digits + letters
  • Remove leading 1 or 0
  • Right‑trim to 10 digits

These filters prevent malformed numbers from hitting the dialplan and reduce carrier rejections.


Recording Enhancements & PCI‑Focused Features

Stereo Recordings

Enables dual‑channel recordings (agent left, customer right).
Critical for QA, analytics, and compliance.

Stereo Parallel Recordings

Allows multiple simultaneous stereo recordings per call.
This is VICIdial’s most advanced recording capability to date.

Recording DTMF Detection

Flags recordings where DTMF tones occur — essential for PCI audits.

Recording DTMF Muting

A powerful privacy tool with multiple modes:

  • Campaign‑level control
  • Cluster‑wide override
  • Forced muting for a defined number of seconds

This is VICIdial’s strongest PCI‑protection feature ever shipped.


Authentication, Passwords & Security

Two‑Factor Admin & Agent Auth Hours

Defines how long a 2FA session remains valid.
A major step forward for enterprise security.

Two‑Factor Auth Config Container

Centralizes all 2FA configuration.
If misconfigured, the system warns you to prevent accidental lockouts.

A subtle but important security refinement.


Reporting, Infrastructure & Diagnostics

Server Drive Partitions Display

Admin → Servers now shows drive partitions directly in the UI.
Great for catching low‑disk or misconfigured mounts.

Database Crash Table Detection

A new diagnostic page that alerts you if any MySQL tables are in a crashed state.
This is one of those “finally” features that every admin appreciates.


Inbound DID Enhancements

Alter CID Name

A flexible new tool for manipulating Caller ID Name on inbound calls.
Modes include:

  • ALLCALLS — alter every call
  • OTHSYS — alter only calls from other systems
  • CIDNUM — set CNAM to the caller’s number
  • CLEAN — replace CNAM with “CLEANED”

This is extremely useful for multi‑system routing and carrier normalization.


Final Thoughts From the Field

This development window wasn’t about massive feature drops — it was about refinement, stability, and future‑proofing. The adaptive dialer got smarter. The admin tools got safer. The AGI layer got more reliable. And the PHP8 transition continues to harden the web interface for the next decade.

If you’re running a production cluster, these updates are absolutely worth pulling in. They reduce edge‑case failures, improve compliance recording, and give you more control over pacing and data hygiene.

-Chris aka carpenox

How to – Install ViciDial on Alma Linux 10

Alma 10

How to – Install ViciDial on Alma Linux 10

image

How to Install VICIdial on AlmaLinux 10 Using My Updated Auto‑Installer

VICIdial admins have been waiting for this one. AlmaLinux 10 is here with a modernized kernel, updated libraries, and a cleaner security model — but it also breaks a lot of legacy telephony components, especially DAHDI. After weeks of patching, testing, and rebuilding, I’ve updated my VICIdial auto‑installer to work smoothly on AlmaLinux 10, complete with the dynamic portal and CyburPhone support.

If you’ve been struggling with DAHDI, PHP, or dependency mismatches on AL10, this guide walks you through the cleanest, most reliable installation path. The updated installer handles the heavy lifting for you.

The code is available here:
https://github.com/carpenox/vicidial-install-scripts


Why AlmaLinux 10?

AlmaLinux 10 brings:

  • A hardened 6.x kernel
  • Updated OpenSSL and system libraries
  • Better performance and security
  • Long‑term stability for production call centers

The downside?
Legacy DAHDI does not compile on kernel 6.x without patching. My installer handles this by applying compatibility fixes and disabling obsolete hardware modules that no longer work on modern kernels.

If you need full DAHDI hardware support, AlmaLinux 9 is still the recommended environment. But for most cloud‑based or SIP‑only VICIdial deployments, AlmaLinux 10 is now a solid choice.


Step 1 — Prepare the System

Start with a fresh AlmaLinux 10 installation.

Reboot before continuing copy the code below and paste into your Linux command line:

Set your timezone:

timedatectl set-timezone America/New_York

Update the system and install core dependencies:

yum check-update
yum update -y
yum -y install epel-release
yum update -y
yum install git -y
yum install kernel* --exclude=kernel-debug* -y

Disable SELinux (required for VICIdial’s web components):

sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config

Download the installer:

cd /usr/src
git clone https://github.com/carpenox/vicidial-install-scripts.git
cd vicidial-install-scripts
reboot

Step 2 — Run the VICIdial Auto‑Installer

Once the system comes back up, you’re ready to launch the installer.

Make sure your server has a valid FQDN (hostname + domain). VICIdial requires it for Apache, SSL, and SIP services.

Run the installer:

cd /usr/src/vicidial-install-scripts
chmod +x cyburdial-installer-alma10.sh
./cyburdial-installer-alma10.sh

This is an automated installer, but you’ll still need to:

  • Press Enter a few times
  • Provide the server’s IP address
  • Confirm a couple of prompts

Don’t walk away completely — but you won’t be typing commands manually.


What’s New in the AlmaLinux 10 Installer?

✔ Updated PHP handling

AL10 ships with newer PHP streams, so the installer automatically configures the correct version for VICIdial.

✔ DAHDI compatibility patches

Kernel 6.x breaks older DAHDI modules. The installer:

  • Removes obsolete hardware drivers
  • Applies compatibility patches
  • Ensures DAHDI tools install cleanly
  • Supports SIP‑only deployments out of the box

✔ Dynamic Portal + CyburPhone

Both components install automatically and are fully functional on AL10.

✔ Cleaner dependency management

No more repo conflicts or mismatched packages.


Absolutely — adding a section about the standard‑db option is a smart move, because a lot of admins don’t realize how close this gets them to a fully functional, production‑ready dialer. Here’s a polished, blog‑ready section you can drop straight into your AlmaLinux 10 article.


Using the standard-db Option for a Ready‑to‑Go VICIdial Deployment

One of the most powerful features of the installer is the standard-db option. Instead of starting with an empty VICIdial database, this option loads a fully pre‑configured baseline environment that mirrors a real‑world production dialer. It’s designed for people who want to get operational fast without spending hours clicking through the admin interface.

With standard-db enabled, your system comes online with:

  • Prebuilt campaigns
  • Default ingroups
  • Standard user groups
  • Sample users and agents
  • Basic system settings already optimized
  • Recording, logging, and reporting defaults in place

In other words, the dialer is 90% ready the moment installation finishes.

What You Still Need to Add

Once the standard database is loaded, the only things you must configure manually are:

  • Your inbound DIDs
  • Your carrier IP / trunk settings

That’s it. Everything else — campaigns, statuses, user groups, recording rules, routing defaults — is already in place and ready to use.

Why This Matters

For new deployments, labs, demos, or rapid‑launch call centers, the standard-db option eliminates the usual setup grind. Instead of spending an hour building the VICIdial structure from scratch, you can log in and immediately:

  • Create agents
  • Upload leads
  • Start dialing

It’s also perfect for multi‑server clusters, because every node starts with the same clean, consistent baseline.

Who Should Use It

The standard-db option is ideal for:

  • New call centers launching quickly
  • Developers testing integrations
  • Training environments
  • Anyone who wants a “turnkey” VICIdial setup

If you prefer a completely blank database for custom enterprise builds, you can skip it — but for most users, it’s the fastest path to a working dialer.


Additional Resources

Other installer versions:
https://github.com/carpenox/vicidial-install-scripts

Advanced usage guide:
How to – Use the full functionality of the ViciDial installer by carpenox


Final Thoughts

This installer represents a lot of work, testing, and late‑night debugging — but the result is a clean, modern VICIdial deployment on AlmaLinux 10 with minimal effort on your part.

If this project helps you, consider supporting the blog:
https://www.paypal.me/TheDialerOne