Search results

FusionPBX install now has support for Debian 13 - https://www.pbxforums.com/threads/fusionpbx-install-debian-13.8872/

FusionPBX supports native PostgreSQL's native logical mult-master replication. Whether you're setting up a 2-node or 3-node cluster, or additional nodes for more redundancy. The FusionPBX project was an early adopter of BDR (Bi-Directional-Replication), and we taught many of you how to use it...

We are excited to announce that the latest FusionPBX install now supports Debian 13! Important Note This is a new version of Debian, it uses a new major version of regular expressions. Before deploying this update in a production environment, we recommend testing it in a test environment. This...

Here are some ideas that might help. - Are you installing this on bare metal or some kind of virtualization? - The answer matters because they can behave differently. - When installing Debian use a minimal install. Adding extras could cause conflicts. I mentioned this before in my first...

@WLR275 Did you try calling our support number during support hours? The FusionPBX support number is listed there. - https://www.fusionpbx.com/support The FusionPBX website download shows an install for Debian 12 or Ubuntu 24.04 LTS - https://www.fusionpbx.com/download Here are tests. I...

I've decided to put effort into improving app/sms security and maintenance work so it can work with the newer version of FusionPBX.

Upgrade First, part of your post shows you didn't follow the upgrade instructions. Maybe you didn't find the public instructions. But you need them because you performed an upgrade. The version upgrade instructions have been at the link below that I'm sharing for many years. This is documented...

- After changing the settings, did you press the RELOAD button on the Default Settings page? - If you did that, try restarting the email_queue service

What is your version of FusionPBX? You can see it from Status -> System Status. New install is likely 5.4, but it would be good to confirm it.

What is your version of FusionPBX? Did you recently upgrade? If so, from what version?

Check this next. Go to Advanced -> Access controls, make sure your public IP address for your phones are not in the providers access control list. If the phone IP address is in that list, then remove it. Then press the RELOAD button or go to Status -> SIP STATUS and press the RELOADACL button.

You can try restarting the xml_cdr service.

Check to make sure your IP address was not blocked by Event Guard. You can check by going to Status -> Event Guard and checking to see if your address was banned. If it was banned, you can press the UNBLOCK button to allow your IP address again.

I'm sorry it took me a bit to finish the support call I was on. I'm happy you stuck around so that I was able to help you. When we did get on a call together, we found that about everything from the fusionpbx-apps repo was installed. Several things in that repo are archived there and are old...

Go to Status -> SIP Status -> FLUSH CACHE button. This would clear the cache.

A way to test Event Guard is to register with a bad password or try and register to the IP address. However, you have to do this from an IP address that is not in the access control list and not registered to the system to intentionally get blocked. Using a mobile phone with Wifi turned off can...

I've upgraded many people, and I'm confident that all issues on your list will be resolved once your code is updated. Running the upgrade scheme and data types is required. My test machine is running PHP 8.2, the same version as you, and it is set up to show all errors by default. On the latest...

I think from the message it's likely you are on the master branch. Please update the source code and try again. I'm no longer recommending fail2ban because it generates too many false positives. I would only use it to protect SSH at this point, as well as the web server (nginx), for handling a...

For FusionPBX PHP 8.1, 8.2, and 8.3 are officially. If you are on the master branch, you need to run Upgrade -> Schema -> Data Types I think I'll optimize the Data Types code for speed and efficiency, and then incorporate it into the Upgrade -> Schema process. We don't change data types...

A newer version of FreeSWITCH occasionally has behavior changes. You good stop and start the gateway and look at the fs_cli or Status -> Log Viewer You can also use it to find your gateway registration attempt. ``` sngrep ```