Search results

We are not only updating the pages now but also actively removing the old ones completely. They still exist in the background but no longer used. I just wanted to make sure you don’t get left hanging with the non existing page when time comes. There might be other users out there that use...

Now just make sure you can hit the reload XML button on the Variables page. If you rebooted the server it should work. Php should hopefully have the right permissions after the reboot. Otherwise you may experience issues in the future. This is a large Freeswitch upgrade. All these small things...

We made that page for you. But it’s not in fspbx menu by default. Feel free to change the menu link yourself to /pin-numbers

Yes, those steps are important. You might need to reboot the server. it could be due to PHP not having access to those directories. Recent php versions have stricter access limitations.

It’s not missing. We removed it because there was nothing important in it. You can reach the dashboard by clicking on the logo. And we moved the logout button to more appropriate place. People often couldn’t find a logout button.

AI wrote this response.

The new Freeswitch TLS script took over this one and broke it. I just pushed a fix for it and tested it on one of my servers. Download updates and retry. This script doesn't support a wildcard certificate. If you need a wildcard cert, your DNS service must support API. You will need to ask an...

It's meant to work. I'll test and report back

@dbz195 Update FS PBX to at least 1.9.1, then update Freeswitch.

Why not just dial the call flow's star code from any phone? It can also be set as a BLF button. https://www.fspbx.com/docs/tutorials/configuration/call-flows/how-to-set-up-call-flows/ https://www.fspbx.com/docs/configuration/call-flows/blf/

Let's Encrypt requirement was to have this in the Nginx config file server { listen 80 default_server; listen [::]:80 default_server; server_name _; location ^~ /.well-known/acme-challenge/ { default_type "text/plain"; root /var/www/fspbx/public...

@yaboc Even that is not needed. Just use one domain since they are all aliases anyway.

You can probably write a custom dialplan for it to accommodate the range. Otherwise, it will be one route for each number.

Forgot to mention. Because of the above, you don't need a wildcard for FS PBX.

@yaboc, there have been some changes to port 80 to accommodate the Let's Encrypt HTTP challenge. It may not work with your proxy out of the box. You may need to look into making changes so both work without conflicting. Why are your tenants using different domains? This isn't the intended way...

@davidbqzt I didn't see your message until today. Your version is very old. There has been so much new stuff added since then. Run these commands to update: cd /var/www/fspbx git stash git pull php artisan app:update php artisan migrate suerpvisorctl restart all Make sure to run these commands...

Thank you, @kenn10. We are working hard on improving the system every day

We've added support for the FreeSWITCH 1.11.1 release, and with it a feature a lot of you have asked for: free, automatically-renewing Let's Encrypt certificates for SIP-TLS and WSS — managed right from the FS PBX web interface. Why the new FreeSWITCH version matters 1.11.1 introduces the...

Starting with FS PBX version 1.9.1, we support the new version of Freeswitch 1.11.1 and Automatic Let's Encrypt certificate renewal. https://www.fspbx.com/docs/configuration/tls-certificates/lets-encrypt/ Freeswitch must be upgraded manually, independently of the FS PBX update.