Recent content by pbxgeek

The easiest is not to use ports 5060 and 5080. Those are targeted every day. I have a system that was up for 300 days, with 0 IPs blocked, because my ports 5060 and 5080 are blocked.

Unblock actually just deletes the record. It doesn't permanently whitelist it. It sure looks like you may have port 5060 or 5080 open. On a secure system, I rarely see any blocks whatsoever. Check if that firewall is actually doing anything.

That's the nature of this business. You patch things, and a week later, they find more. If your system is protected from outside access, you should be ok.

You still didn't explain why you think it's not working? Have you started it? It should show on your SIP Status page if it's running.

This is an example of Telnyx IP authentication type or gateway. The screenshot is from FS PBX but the same settings will work in FusionPBX

How do you know it's not working? Is it IP-based authentication or registration trunk? I suggest you share what you did so far and maybe we can help

If you are not very familiar with the command line, I recommend starting a new server with Debian 13 and migrating everything manually. In-place upgrades from Debian 12 to 13 may require extensive command-line skills, as you will likely bump into unexpected issues and may or may not be able to...

A few points to note: Many users are often confused because they believe they cannot set their gateway providers to send inbound traffic to port 5080, but this is very rare—the provider almost always allows it. If you are fortunate enough to have a provider that refuses, then yes you can simply...

I'll test this and apply a patch if necessary.

@mcs3ss2 confirmed that this is now working for him.

But you should change the APP name to yours so it doesn't show "FS PBX" if you are white-labeling.

FS PBX generates its own email for this, and it can't be customized at the moment. You can fill in your company info in Default Settings -> email settings. So that line is not empty.

I meant, now that you have changed the .env file, are you accessing the PBX by going to https://pbx.mydomain.com.au? After the initial installation, you accessed it using the external IP. However, once you update the .env file, you must use your URL instead. Your screenshot looks fine to me.

something to do with the session variable not matching. You are on https://pbx.mydomaincom.au and not anything else, right? Once you set that in your .env file, that's the only URL you need to use. Make sure there are no spelling mistakes. Yesterday, a client missed one letter in their domain...

@mcs3ss2 What error are you getting? Did you run `php artisan config:cache` after updating the .env file? We have a superadmin password restore script if it's a password issue. https://www.fspbx.com/docs/configuration/users-and-groups/how-to-reset-superadmin-password/