Recent content by markjcrane

Impossible for FusionPBX its not the one communicating with the SIP protocol. The FusionPBX sends configuration information to FreeSWITCH and then FreeSWITCH handles the SIP messages. I would recommend using IP authentication for Gateways and if you have to use Registration on a Gateway use them...

Upgrade -> App Defaults would add groups if all groups were completely missing in v_groups table. Your version was likely a fairly old version of FusionPBX. Assigning users to a group use to be done in a table called v_group_users. Not sure how many years ago that was changed to v_user_groups.

There was a bug in a commit on Saturday and that problem was fixed on Monday December 5th. Here is the fix in case you need visual proof. The bug affected calls that were being recorded. https://github.com/fusionpbx/fusionpbx/commit/bccc736fea3d84b76e7c0d61d722d8f3caf8b393 The change on...

I have upgraded many people that have not had an issue with voicemail. Maybe you have an old local-extension and voicemail dialplans. You can delete them and run Upgrade -> App defaults to get new defaults.

Advanced -> Access Controls -> domains needs to always be set to default deny.

Run these commands from the command line. Make sure none of your Phone IP addresses or local network are in the domains ACL Use the domains ACL only for your VoIP providers.

I just updated the install and upgrade code so that if the config.php exists it will redirect to the install automatically. - From there if the config directory is writable it will make the config.conf automatically from the config.php - If the config directory isn't writable it will tell you...

Make sure the password to the database is correct in /etc/fusionpbx/config.conf you can look at the old /etc/fusionpbx/config.php file for the password.

This event guard high CPU issue should be fixed. It is working fine for me now in all tests. Tested the following scenarios. 1. FreeSWITCH stopped and event_guard service started (failed) - Result High CPU load (Fixed 20 Oct 2022) 2. event_guard service started when FreeSWITCH was running then...

Newest version sets FreeSWITCH to use its default database in /varlib/freeswitch/db directory so there is no password for that by default. Adjusted that for new upgrades yesterday. Did have some useful bug fixes yesterday that everyone should make sure they have.

Compare the password in config.php, config.lua and the new config.conf file. Also where did the message come from web browser or FreeSWITCH fs_cli or FreeSWITCH logs? Fixing something over text based means is not as effective as a phone call and remote desktop

Run this as root from on your server console or through ssh. I have mentioned this multiple time here in the forum and even the past 5 to 10 day. The web GUI upgrade can update the source but it can't always do everything as its a web application and there are valid limits to what it can do...

Run this as root on your server console or through ssh.

Remember this is a third party forum. If you want to submit bugs you might consider submitting the bug to https://www.fusionpbx.com