This happens after updating your operating system for redhat distro’s such as Alma, Rocky or CentOS. Its an easy fix thats outlined below:
cd /usr/src/dahdi-linux-complete-3.4.0+3.4.0/make && make install && modprobe dahdiThat’s all there is to it.
CyburDial is excited to announce the release of the 2025 edition of its Full White Label Theme for ViciDial! This latest version brings a host of new features and improvements designed to enhance the user experience for call center agents and administrators alike.
The new theme introduces several key features on the agent screen, including:
Over the past year, CyburDial has diligently worked on addressing bugs and improving the overall interface of ViciDial. These enhancements include:
Recognizing the global reach of ViciDial, the 2025 edition now includes support for additional foreign languages. This makes it easier for call centers around the world to use ViciDial in their native languages, improving communication and efficiency.
To learn more about the new and improved Full White Label Theme for ViciDial 2025 edition, visit our website: https://dialer.one/index.php/product/white-label-cyburdial-theme-2025/.
We look forward to seeing how this new edition helps your call center achieve even greater success!
cd /etc/apache2/conf.d/
for file in *.conf.old; do mv "$file" "${file%.conf.old}.conf"; done
Answer y to all replace file questions
cd /usr/src/astguiclient/trunk
perl install.pl --copy_sample_conf_files --no-prompt
rm -rf /var/lib/asterisk/sounds
ln -s /usr/share/asterisk/firmware /var/lib/asterisk/firmware
ln -s /usr/share/asterisk/images /var/lib/asterisk/images
ln -s /usr/share/asterisk/moh /var/lib/asterisk/moh
ln -s /usr/share/asterisk/mohmp3 /var/lib/asterisk/moh
ln -s /usr/share/asterisk/sounds /var/lib/asterisk/sounds
ln -s /usr/share/asterisk/static-http /var/lib/asterisk/static-http
ln -s /usr/share/asterisk/phoneprov /var/lib/asterisk/phoneprovln -s /var/lib/asterisk/agi-bin /usr/share/asterisk/agi-bin
ln -s /var/lib/asterisk/phoneprov /usr/share/asterisk/phoneprov
zypper ref && zypper up
cp /etc/firewalld/zones/external.xml.rpmnew /etc/firewalld/zones/external.xml
Also apply this patch:
zypper in -t patch openSUSE-SLE-15.6-2024-4321=1 SUSE-2024-4321=1
The last issue I have received reports about is a time synchronization issue even when times match everywhere on the system, I am working on debugging this currently, check back here for solution.
The fix is below:
echo "explicit_defaults_for_timestamp = Off" >> /etc/my.cnf.d/general.cnf
systemctl restart mariadb.serviceHere is the documentation for it: https://docs.vicibox.com/en/latest/bugfix/bugfix1201-2.html
Here is also a link to the official docs from the ViciBox support website:
https://docs.vicibox.com/en/latest/bugfixerrata.html
You need to add port 446 to /etc/apache2/conf/listen.conf as shown below:
If you have any questions feel free to join our discord: https://discord.gg/ymGZJvF6hK
Chris aka carpenox
Hey there, fellow VICIdial enthusiasts!
I am thrilled to announce the launch of my latest GitHub repository, dedicated to creating custom reports for VICIdial. As a long-time user and developer in the VICIdial community, I understand the importance of having detailed and actionable data at your fingertips. This repository aims to enhance your call center’s efficiency and decision-making process by providing insightful reports tailored to your specific needs.
The first report available in this repository is the “Area Code Call Breakdown.” This report is designed to give you a comprehensive analysis of the number of calls made to each area code within a specified date range. Whether you are looking to optimize your outbound campaigns or ensure compliance with call regulations, this report will provide valuable insights into your call distribution patterns.
In light of recent changes to spam regulations, it is crucial to manage your Direct Inward Dial (DID) numbers effectively. According to the new guidelines for 2025, you should aim to keep the number of calls per DID below 50 calls per day. This report will help you achieve that by suggesting the optimal number of DIDs you should have for each area code based on the collected data and a six-day work week.
Here’s how the calculations work:
For example, if you made 3,000 calls to area code 305 over a six-day period:
To make the data even more accessible, this report includes the option to export your findings to a CSV file. This feature allows you to easily share the data with your team, analyze it in spreadsheet software, or integrate it with other systems for further processing.
Ready to enhance your VICIdial reporting capabilities? Head over to my GitHub repository here to get started. You’ll find detailed instructions on how to set up and run the reports, as well as ongoing updates and new features.
Go to your “vicidial” directory on your web server. For ViciBox type “cd /srv/www/htdocs/vicidial” and for Redhat(Alma/Rocky/CentOS) type “cd /var/www/html/vicidial” and then clone the repo by typing:
git clone https://github.com/carpenox/Reports.gitThen browse to your server – https://yourserver.com/vicidial/Reports/did_report.php
I have added a bunch more that are all described on the github, but the latest one looks like this:
Thats it, enjoy!
Stay tuned for more custom reports and features coming soon. If you have any suggestions or feedback, feel free to open an issue on GitHub or reach out to me directly on Discord: https://discord.gg/ymGZJvF6hK
Happy dialing!
Chris aka carpenox
There is a new issue with ViciBox 9, 10 or 11 where Apache will not start up after installations. The error message is calling for mod_deflate which seems to not be there. The easy fix for this is to delete the include for it.
nano /etc/apache2/vhosts.d/dynportal.conf - Then go to line 16 and delete "Include /etc/apache2/conf.d/mod_deflate.conf"
Do the same for dynportal-ssl.conf
This next set of instructions is from BVD in our Skype group:
1st step is only for apache error user’s
1st step
simple go to /etc/apache2/conf.d/ and rename all that files which is on .old like before /etc/apache2/conf.d/mod_deflate.conf.old
change into this mod_deflate.conf only and do same process on all files just remove .old or .bak some thing
2nd step
cd /usr/src/astguiclient/trunk
then run perl install.pl
install.pl will help you to create agi-bin missing files
3rd
rm -r /var/lib/asterisk/sounds
ln -s /usr/share/asterisk/firmware /var/lib/asterisk/firmware
ln -s /usr/share/asterisk/images /var/lib/asterisk/images
ln -s /usr/share/asterisk/moh /var/lib/asterisk/moh
ln -s /usr/share/asterisk/mohmp3 /var/lib/asterisk/moh
ln -s /usr/share/asterisk/sounds /var/lib/asterisk/sounds
ln -s /usr/share/asterisk/static-http /var/lib/asterisk/static-http
ln -s /usr/share/asterisk/phoneprov /var/lib/asterisk/phoneprov
ln -s /var/lib/asterisk/agi-bin /usr/share/asterisk/agi-bin
ln -s /var/lib/asterisk/phoneprov /usr/share/asterisk/phoneprov
You can also check out the video version from Innovate IT Lab
If you have any questions feel free to join our discord: https://discord.gg/ymGZJvF6hK
Chris aka carpenox
Vicidial administrators, take note: the Carpenox Auto Installer is about to change the game. This tool transforms the usually complex setup of Vicidial into a smooth, hassle-free experience. Let me go over some post installation steps and key things to take note of and changes I suggest you make after the fact of using the installer. I will give you a few steps to do first:
This assumes you have installed already through this article: How to – Install Vicidial on Alma Linux 9 with my new auto installer
After you reboot the server, which should only be done once you have attached the FQDN(Fully Qualified Domain Name) for the SSL cert in the very last step of the installation process. This step is important and I advise you don’t skip it if you plan to use webphones that are built into the installer. If you do skip this step, make sure you turn the firewall off before trying to run it post the initial install or certbot wont be able to get through to create the SSL. The command is “service firewalld stop” and then start it back again after you install the SSL. This being said, then login to that domain in your browser. For example: https://my.dialer.one (Use your domain this is NOT real)
The default login is 6666 and password 1234 – make sure you change this password and then go into users and give yourself all the permissions possible.
If you do decide to not use webphones and can not or will not be installing SSL, you will need to login still through the https port with https://192.168.1.1 (your IP) and change the password the same. You will need need to add the http port to your trusted zone as well as the dynamic portal non SSL port to public which is 81. You can do so with the following commands:
firewall-cmd --permanent --add-port=81/tcp
firewall-cmd --add-service=http --zone=trusted --permanent
firewall-cmd --reloadHackers these days are quick, like I mean I have had servers provisioned from well known hosting companies like Hetzner, Vultr, DigitalOcean, OVH Cloud, IONOS, Contabo and many others within 15 minutes. They scan these known IP ranges and go for known vulnerabilities very quick and will install rootkits, crypto miners, DDOS bots and other malware. The firewall rules I have set in place leave the needed ports to be open to use the dialer in the “trusted” zone, however I have left port 443(https) open to public zone so you can login and change the default password, because you can not use the dynamic portal to validate your IP until after the default password has been changed.
So, now that you’ve changed that password, lets remove the https port 443 from the public zone. To do so type the following commands: You can also see more use for the firewall here: How to – Use Firewalld via command line
firewall-cmd --permanent --remove-service=https
firewall-cmd --reload
You also need to update the dynamic portal redirect link with this command:
nano /var/www/vhosts/dynportal/inc/defaults.inc.php
Change the https://cyburdial.com/agc/cyburdial.php to https://yourdomain.com/agc/vicidial.php
You should not be able to get to your domain at this point, you will need to use the dynamic portal login to validate your IP. You can find the URL for this at https://my.dialer.one:446/valid8.php (Again, use your domain) or for those of you that are only using IP – http://192.168.1.1:81/valid8.php. When you go to that page you will see a login area that looks like the image below:
If you have followed the previous steps you should now be redirected to the ViciDial agent page to login with your username and password. Just browse to the admin area by removing the /agc/vicidial.php part. Some more advanced steps would be to change the Dynamic portal port off of 446 to something above the 50000 range as it takes more time for hackers to scan this high and they typically will not waste the time. Changing the name of the valid8.php file is also a good standard operating procedure to put in place, however this take some other changes in the template file as well, that I will not go over on this article. If you would like to see an article for that, post a comment below.
At this point, most of you should know how to setup your your Vicidial configurations and setup. If not make sure to check out a few of my friends YouTube pages with lots of content regarding this:
If you do decide to use the standard-db.sh file on my github, there is one thing that I messed up on the original design that needs to be fixed post import. Adding an “a” to the phone login on each user account. To run the standard-db file which comes pre-configured with everything ready to go other than adding DID’s and your VoIP carrier IP, simply run the commands below:
cd /usr/src/vicidial-install-scripts
chmod +x standard-db.sh
./standard-db.shOnce you use this file, your new password to get into the 6666 user will be “CyburDial2024”
After this go into each user account an add the letter “a” to the phone login area as shown below:
The first place you need to change the domain from mine to yours is in the server itself for the websocket location in admin > servers as shown below:
The second place is in the webrtc template labeled as “SIP_generic” in admin > templates as shown below:
The last place in in system settings for the audio store or “sounds web server” location as shown below:
cd /var/www/html
mkdir hgcjvmrjzqcngw47wf5zf4xjzd9n0k
chmod -R 755 hgcjvmrjzqcngw47wf5zf4xjzd9n0k
chown -R apache:apache hgcjvmrjzqcngw47wf5zf4xjzd9n0k
cp -R /var/lib/asterisk/sounds/* /var/www/html/hgcjvmrjzqcngw47wf5zf4xjzd9n0kThis next step is going on the thought of using the standard-db file on my github, but for those of you that do the config’s yourself, don’t forget the bulk tools area is a great way for adding your DID’s in bulk.
The next step is to add your DID’s, you can do so easily through the bulk tools in Admin > Reports > admin utilities
After this go Admin Bulk Tools
Click the highlighted area and the first area you see will be to copy DID’s, select the one I have there that says Copy this DID as shown below and paste your DID’s in the area available, then click submit.
Paste them in this box and click submit
The second part of this is to change the carrier IP in admin > carriers > carrier
That’s it, you can start dialing. Now lets go over a few tools I have added to help manage and debug your systems:
Hopefully this helps with some of the questions I have been asked and common issues people run into. If you have any other questions, feel free to join my discord channel: https://discord.gg/ymGZJvF6hK or comment below.
Chris aka carpenox
There is a new feature in ViciDial as of SVN 3878 that will allow you to increase the call handle time through the AMD system which would lower your Short Duration Percent(SDP) in your carrier stats. Doing so can typically save you hundreds if not thousands per month in VoIP fees for being below their SDP requirements. Adding one line to you carrier dialplan as show below will do this for you. Doing so will also save your DID’s (Caller ID’s).
This example will add 7 seconds to each call.
exten => _8567.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _8567.,n,Set(__AMDMINLEN=7)
exten => _8567.,n,Dial(SIP/carrier/${EXTEN:4},,tToR)
exten => _8567.,n,HangupI hope this helps
-Chris aka carpenox
Please read this carefully as it contains important information regarding the security of your VICIdial system.
The ViciDial Group recently conducted a security audit of VICIdial which resulted in the identification of severe vulnerabilities. We have patched these and submitted these changes to the code-base. Any system that is at SVN version 3848 or greater already has them. If your system is below that version, we strongly recommend that you upgrade to address these concerns. If you would like us to upgrade your system for you, please send a new email to support@cyburdial.com and put “Security Upgrade” in the subject. A typical upgrade takes about 15 to 30 minutes of support time. You can see the seriousness of these exploit here: https://packetstormsecurity.com/files/181461/VICIdial-2.14-917a-Remote-Code-Execution.html
https://packetstormsecurity.com/files/181460/VICIdial-2.14-917a-SQL-Injection.html
To find the SVN version of your VICIdial installation, log into your administator account and go to “Admin”, then click on “System Settings”. It will be the second line from the top, on the right, under “SVN Version”.
Please note, if your setup contains customizations done directly to VICIdial’s code, further review of your system will be needed as it may not be possible to upgrade you.
You can update your SVN by following this article: How to – Update your Vicidial version with subversion
Chris aka carpenox
A problem arises when people do a scratch install of ViciDial and you do not set the proper permissions for the directory that the recordings are stored. I will go over a couple of things to check and/or set to make sure they work properly.
The usual suspect is not setting proper permissions on the folder for the recordings, to fix this simply type the commands below:
Redhat(Alma, Rocky or CentOS):
chmod -R 755 /var/spool/asterisk/monitorDONE
chown -R apache:apache /var/spool/asterisk/monitorDONE
OpenSuSE(Tumpleweed, Leap ViciBox):
chmod -R 755 /var/spool/asterisk/monitorDONE
chown -R wwwrun:www /var/spool/asterisk/monitorDONE
The other issue could be not having a proper alias/vhost set for apache. To fix this simply paste the lines below at the bottom of your http.conf file
CustomLog /dev/null common
Alias /RECORDINGS/MP3 "/var/spool/asterisk/monitorDONE/MP3/"
<Directory "/var/spool/asterisk/monitorDONE/MP3/">
Options Indexes MultiViews
AllowOverride None
Require all granted
</Directory>For Redhat this goes in /etc/httpd/conf/httpd.conf
For OpenSuSE this goes in /etc/apache2/httpd.conf
I hope this helps, as always if you have any questions feel free to drop by our live chat support on Skype or discord through the links below.
Skype – https://join.skype.com/ujkQ7i5lV78O
Discord – https://discord.gg/FjpDQbUs
-Chris aka carpenox
This article is going to go over the steps I suggest to take in order to setup a ViciDial Cluster when using scratch install methods. I do things a little different when it comes to this to prepare for worst case scenario that a server may have problems and have to be taken offline, I install all services to each server, such as apache, mysql and asterisk this way if need be, they each can take on additional roles to cover for a server having to be taken out of production. Obviously this is going to assume you have ViciDial already installed on each server with all roles ready to go. To do so you can follow any one of my articles for scratch installs. I suggest using my auto installer for Alma Linux 9.
Install ViciDial with the auto installer on each server.
Repeat this process on each server and then move on to step 2.
Now we need to disable services not needed on each server to save on resources, but this way they are there if they are needed in the future.
We want to leave apache running on the asterisk servers so we can install webrtc for webphones
Now we want to link them all together by running the install.pl script located in the source directory for vicidial, follow the following commands to get to and run it:
cd /usr/src/astguiclient/trunk
perl install.plNow follow the prompt and answer them accordingly. The pictures below will show the choices needed for each server role except make sure you set the IP for the DB server on all the rest instead of localhost.
For the web server make sure you put the DB server IP instead of localhost
Make sure you only put 5 and 7 keepalives on one asterisk server, the rest you should only choose 123468.
Now we need to add them into the GUI for Vicidial by going to Admin then servers
Once you are here, click “Add a new server”
Fill out the fields accordingly and click submit
Now for the DB and web server turn the options to N(no) where you see highlighted below:
Add conferences for each asterisk server by following these instructions
Now reboot all servers and then check your reports page to make sure all servers are set to green like shown below
That’s all there is to it, not as hard as you thought it would be, right? If you have any questions feel free to join our live support on Skype:
I hope this helps!
Chris aka carpenox