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


How to – Fix “Unable to lookup ‘SERVER_EXTERNAL_IP'”

SERVER_EXTERNAL_IP

How to – Fix “Unable to lookup ‘SERVER_EXTERNAL_IP'”

SERVER_EXTERNAL_IP

This error is the newer SVN versions and technically, won’t cause any issues, however here is the fix for it. Type the following command in your Linux Command Line:

sudo sed -i 's/SERVER_EXTERNAL_IP/0.0.0.0/' /etc/asterisk/pjsip.conf

That’s all there is to it.

Here is a video for those of you who prefer videos from HBTutorials

Chris aka carpenox

How to – Upgrade any Leap ViciBox install to Leap 15.6

Leap 15.6

How to – Upgrade any Leap ViciBox install to Leap 15.6

A lot of people seem to be keeping their systems on older Vicibox installs such as v9 which is on Leap 15.1, v10 which is on Leap 15.3 or v11 which is on Leap 15.5 which are all end of life. The reasoning behind this, is you are thinking that you are safe with whitelist only IP access to the server, however, you are mistaken. As software reaches its end of life, it no longer receives updates. This means it also stops receiving security patches. Even with IP access only, your firewall can be hit with a denial of service attack, taking it offline. All your software, including MySQL, Apache, OpenSSH, and the Linux kernels themselves, can then be hacked using exploits to gain full root to your servers. This article will teach you how to upgrade any of these to the latest and only supported version of Leap, 15.6, so let’s get started.

ViciBox 10
468x60 Seamless Conversations and Collaboration

Step 1 – Upgrade Repo URL’s

In this example, I am upgrading from ViciBox 10 from Leap 15.3 up to 15.6. You will notice the first line of code has s/15.3/15.6/g which you would need to replace the first part with whatever you are upgrading from, such as ViciBox 9 would be 15.1.

sed -i 's/15.3/15.6/g' /etc/zypp/repos.d/*.repo
zypper --releasever=15.6 lr -u
zypper lr
zypper

You can see in the picture above, these first steps will replace the repo URL’s, however, some have been changed even more than just the 15.6 portion and we will need to replace those. Below, I will show you how to find which ones to remove by the errors you receive that will be in red.

zypper --releasever=15.6 ref
zypper lr
zypper rr 2
zypper rr 3 
Screenshot 2025 02 12 121712

In this picture above, you can see repo #’s 2 and 4 are broken which is Perl and Ast-13 so I removed it with the code above by typing “zypper rr 2” and then “zypper rr 3” (its 3 here and not 4 because when we deleted #2, it moved up one). Now on the next step, we will add all the repo’s we need and replace the ones we deleted.

https://download.opensuse.org/repositories/devel:/languages:/python/15.6/devel:languages:python.repo
zypper ar http://download.opensuse.org/repositories/server:/php:/applications/15.6/server:php:applications.repo
zypper ar https://mirrorcache-us.opensuse.org/repositories/devel:/languages:/perl/15.6/devel:languages:perl.repo
zypper ar https://download.opensuse.org/repositories/home:/vicidial:/vicibox/openSUSE_Leap_15.6/home:vicidial:vicibox.repo
zypper ar https://download.opensuse.org/repositories/home:/vicidial:/asterisk-16/openSUSE_Leap_15.5/home:vicidial:asterisk-16.repo
zypper ar https://download.opensuse.org/update/leap/15.6/oss/openSUSE:Leap:15.6:Update.repo
zypper ar https://download.opensuse.org/update/leap/15.6/backports/openSUSE:Backports:SLE-15-SP6:Update.repo
Screenshot 2025 02 12 121259
250x300 Business Communications

Now the hard part is done, lets run the updates.

Step 2 – Upgrade the OS

zypper --releasever=15.6 ref
zypper --releasever=15.6 dup

When you run these two commands, you will get errors, you want to make sure you are installing asterisk 16 so pressing 1 most of the way down, and then “breaking vicibox-install” towards the end which I believe was 4.

Screenshot 2025 02 12 121957

You will then reach the portion to say “y” like in the picture below:

Screenshot 2025 02 12 121928

Once everything downloads and installs, you can reboot and you will see the new OS will be labeled as Leap 15.6 when you type “cat /etc/os-release” as you see below even though it is still labeled as ViciBox 10:

Screenshot 2025 02 12 124404

Step 3 – Confirm everything that ViciDial needs is installed

zypper install ppp ppp-devel autoconf automake kernel-default-devel kernel-devel gcc make libtool libedit-devel libedit kernel-default dahdi* libopenssl-devel

zypper install php screen php-mcrypt subversion php-cli php-gd php-curl php-mysql php-ldap php-zip php-fileinfo php-opcache

zypper in wget unzip make patch gcc gcc-c++ subversion php php-devel php-gd gd-devel readline-devel php-mbstring php-mcrypt

zypper in php-imap php-ldap php-mysqli php-odbc php-pear php-xml php-xmlrpc curl curl-devel perl-libwww-perl ImageMagick 

zypper in newt-devel libxml2-devel kernel-devel sqlite-devel libuuid-devel sox sendmail lame-devel htop iftop perl-File-Which

zypper in php-opcache libss7 mariadb-devel libss7* libopen*

zypper install sqlite-devel httpd mod_ssl nano chkconfig libedit-devel uuid* libxml2*

Step 4 – Enable services

We need to reactive the asterisk and dahdi services by typing the following commands:

systemctl enable asterisk
systelctm enable dahdi

Reboot and verify everything is running correctly, check your sockets with “screen -ls” (make sure “send” and “listen” are there. Check dahdi with “dahdi_cfg -v” and if it errors, run “modprobe dahdi” and you should be good to go, but if you have any issues, join our discord at the bottom of any page for more help.

250x300 Business Communications

Chris aka carpenox

How to – Debug Webphones for ViciDial

web socket url

How to – Debug Webphones for ViciDial

webphones

I get asked several times a day in the Discord and Skype group chats about how to fix peoples webphones. So this article will be the typical steps I take in order to debug these type of issues.

image 101361115 15836239

Step 1- Is Dahdi running?

The first thing I check is is dahdi running? I do this by typing “dahdi_cfg -v” and the output should look like it does below:

dahdi

You do not want it to say “1 error(s) detected” as shown below:

dahdi

If it does respond like above, you need to run the command “modprobe dahdi” which will bring it into a state like the first picture which is good, retest to verify with “dahdi_cfg -v”. It could also need to be recompiled if it wasnt installed properly. I will create a separate article for this later this week.

Step 2 – Are the ports running?

if the above is functioning correctly, the next step is to make sure you see the ports that are needed for websockets to be running. You can do this by typing “ss -ltnu” and you should see ports 8088 and 8089 running like in the picture below:

image 10

If the ports are showing correctly here, move on to step 3, if not it means your configuration file for web sockets is not setup correctly. To fix this you need to edit your /etc/asterisk/http.conf file and make sure it looks like below or you can copy this file from my github:

[general]
enabled=yes
bindaddr=0.0.0.0
bindport=8088
enablestatic=yes
tlsenable=yes
tlsbindaddr=0.0.0.0:8089
tlscertfile=/etc/letsencrypt/live/DOMAINNAME/fullchain.pem
tlsprivatekey=/etc/letsencrypt/live/DOMAINNAME/privkey.pem

One you update this file, restart Asterisk and check its status for web sockets by typing the follow commands:

asterisk -rx 'core restart now'
/usr/share/astguiclient/ADMIN_keepalive_ALL.pl
asterisk -rx 'http show status'

It should output as shown below:

websocket

You can also verify the ports are running like we did in step 2 above.

image 101361114 15836241

Step 3 – Is the webrtc template setup correctly?

Now let’s login to the ViciDial admin GUI and make sure the webrtc template is setup with the proper settings. You can copy the template below and refer to the picture to verify yours is done correctly.

type=friend 
host=dynamic 
context=default 
host=dynamic 
trustrpid=yes 
sendrpid=no 
qualify=yes 
qualifyfreq=600 
transport=ws,wss,udp
encryption=yes
avpf=yes
icesupport=yes
rtcp_mux=yes
directmedia=no
disallow=all
allow=ulaw,opus,vp8,h264
nat=yes
directmedia=no 
dtlsenable=yes
dtlsverify=no
dtlscertfile=/etc/letsencrypt/live/DOMAIN/cert.pem
dtlsprivatekey=/etc/letsencrypt/live/DOMAIN/privkey.pem
dtlssetup=actpass
webrtc template

You can get to this area by going down to “Admin” then clicking “templates”

templates

Step 4 – Is the web socket server setup?

On this last step, go into admin once again and click on “servers” and make sure you have the websocket set in the “Web Socket URL” as shown below in the following format:

wss://DOMAIN:8089/ws
websocket server

If everything here is setup correctly, your webphones should be working. However there is a couple other possible causes, such as not allowing the mic to access the agents webpage, broken headsets, expired or bad SSL certificates. You can acceess our support channels in the Discord and Skype links at the top of the page for more help, its free. Hopefully this helps solve some of the more common issues.

Chris aka carpenox

How to – Set Up Load Balanced Phones and Calling for ViciDial

bulk phone insert

How to – Set Up Load Balanced Phones and Calling for ViciDial

Step 1: Ensure Prerequisites

Before you start, make sure you have:

webrtc template

Step 2: Access the Bulk Phone Insert Page in the Admin Utilities on the Reports Page

  1. Log in to your VICIdial web interface.
  2. Navigate to the “Bulk Phone Insert Page” in the Admin utilities by clicking on the appropriate menu option in admin utilities on the reports page as shown below:
admin untilities
bulk Phone Insert
bulk Phone Insert
image 101361114 14092462

Step 3: Prepare Phone extensions and server IP’s

  1. Create a column in Excel or Google Sheets with your list of phone extensions as shown below
  2. Do the same for the server IP’s for all your telephony/asterisk servers
extensions

Step 4: Configure the Phone Alias and Phone info

  1. On the Bulk Phone Insert Page, you’ll see all the options to set with an example below
  2. Copy your extensions and servers to the appropriate pages
  3. Configure the servers, phones, registration password(anything you want), Login Password(anything), Create Alias Entries = YES, Suffix you can leave blank, Context=default, Set as Webphone=Y, Template ID to your webrtc template and hit Submit.
image 6 png

That’s it, you have now properly load balanced your webphones across all your telephony servers. now we can move on to properly load balancing the calls on each.


Step 5: Enable Balance Dialing on all servers

  1. Go into Admin > Servers and then into each telephony server and make sure “Balance Dialing” is set to Y
  2. You can give the servers higher ranks for harder calling on the ones with higher ranks where it says “Balance Rank”
Balance Dialing
Balance RankThis is the way the ranking works
This field allows you to set the order in which this server is to be used for balance dialing, if balance dialing is enabled. The server with the highest rank will be used first in placing Balance fill calls. Default is 0.
image 101361114 15620149

That is all there is to it, you have now properly load balanced your cluster with both the phones and the calls. This will help keep the dialing load equally spread out over your cluster, therefore not overwhelming one or two servers more than others. As always if you have any questions feel free to join our discord: https://discord.gg/ymGZJvF6hK

Chrris aka carpenox

How to – Renew your certbot SSL cert when it fails

Screenshot 2025 02 07 180422 png

How to – Renew your certbot SSL cert when it fails

enewing a Let’s Encrypt SSL certificate can sometimes result in an “unauthorized” error. This error typically indicates that the certificate authority (CA) couldn’t verify your domain ownership2. Here’s a step-by-step guide to help you troubleshoot and resolve this issue:

Step 1 – Turn the firewall off and remove old files

So for some reason sometimes the certbot certificates renewal process will not go through and you will see an error like this saying “unauthorized”:

Screenshot 2025 02 07 180305 2

You need to remove the cert folders for archive and live in cd /etc/letsencrypt/ as shown above as well as the .conf file and rename the viciportal.conf file:

cd /etc/letsencrypt/live/
rm -rf dvdial.dialer.com/
cd /etc/letsencrypt/archive/
rm -rf dvdial.dialer.com/
rm -rf /etc/httpd/conf.d/dvdial.dialer.com-le-ssl.conf
mv /etc/httpd/conf.d/viciportal-ssl.conf /etc/httpd/conf.d/viciportal-ssl.conf.off

Replace “dvdial.dialer.one” with your domain

Step 2 – Rerun the certbot command

After step 1 is complete, you can rerun “certbot” which will recreate the .conf file we deleted and recreate the SSL cert, but with -0001 added to the new directories so we need to copy these new folders to the old locations for the viciportal.conf to work without changes.

Screenshot 2025 02 07 180422

First rename the viciportal conf back to the correct name as shown below then copy the directories:

mv /etc/httpd/conf.d/viciportal-ssl.conf.off /etc/httpd/conf.d/viciportal-ssl.conf
cd /etc/letsencrypt/live/
cp -r dvdial.dialer.com-0001/ dvdial.dialer.com/

Step 3 – Restart Apache and Turn the firewall back on

Screenshot 2025 02 07 180447
service httpd restart
service firewalld start

This will work on any certs you have issued from my auto installers, its a bug I haven’t quite worked out yet. If you have any input to fix the renewals please comment here or join the Discord: https://discord.gg/ymGZJvF6hK

Chris aka carpenox

CyburDial’s New Merchandise Store

Merch shop

Welcome to CyburDial’s New Merchandise Store

Guy Fawkes mask with the inside part looking like fire transparent background removebg preview Copy png

We are beyond excited to announce that CyburDial has officially launched its brand-new merchandise store! Now, you can show your love for CyburDial with our exclusive range of products, designed to cater to every fan’s needs. From stylish clothing to practical everyday items, our merchandise collection has something for everyone. Visit our store at CyburDial Shop today and explore what’s in store!

Fashion Forward: Stylish Clothing Collection

Our clothing line features an array of options that reflect the CyburDial spirit. Whether you’re looking for a comfortable t-shirt for casual wear, a cozy hoodie for those chilly days, or a sleek sweater that makes a bold statement, we’ve got you covered.

  • T-Shirts: Show off your CyburDial pride with our stylish t-shirts. Made from high-quality materials, these shirts are not only comfortable but also durable, ensuring that you can wear them for any occasion.
  • Hoodies & Sweaters: Perfect for keeping you warm while representing your favorite brand. Our hoodies and sweaters come in various designs and colors, making them a versatile addition to your wardrobe.
a realistic image of a phoenix with a transparent background removebg Copy png

Everyday Essentials: Mugs, Mousepads, and More

We understand that our fans want to incorporate their love for CyburDial into their daily lives, which is why we’ve expanded our merchandise collection to include essential items for your home and workspace.

  • Mugs: Start your morning with a cup of coffee in our exclusive CyburDial mugs. Each mug features a unique design that captures the essence of our brand, making it the perfect addition to any kitchen or office.
  • Mousepads: Upgrade your desk with our premium mousepads, designed for both style and functionality. With smooth surfaces that provide excellent tracking for your mouse, these mousepads will enhance your productivity while showing off your CyburDial pride.

Unique Collectibles: Glasses and Other Accessories

a high dpi image of 600 x 600 of a phoenix fighting a dragon with a transparent background removebg preview Copy png

For those who appreciate the finer things in life, our merchandise store includes unique collectibles and accessories that add a touch of CyburDial to your everyday routine.

  • Glasses: Enjoy your favorite beverages in style with our CyburDial glasses. These high-quality glasses are perfect for any occasion, whether you’re hosting a party or enjoying a quiet evening at home.
  • Accessories & More: From keychains to phone cases, our store offers a variety of accessories that allow you to carry a piece of CyburDial with you wherever you go.

Shop Now and Show Your Support

Ready to dive into the world of CyburDial merchandise? Head over to CyburDial Shop and start browsing our collection today. By purchasing our merchandise, not only are you getting high-quality products, but you’re also supporting the CyburDial community and helping us continue to bring you the content and experiences you love.

Thank you for being a part of the CyburDial family. We can’t wait to see you rockin’ your new gear! Don’t forget to share your merch photos with us on social media using the hashtag #CyburDialMerch. Happy shopping!

Click here to check out the merch store now!