Search results

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.

Hmmm, actually, there is no way to reset the pending transcription that is stuck at the moment. I should probably add a Retry button. I'll address this in future updates. Good news is you probably won't have this issue again now that it works. The URL wasn't mentioned in the video because you...

@willy Lafort any time you make a change in the .env file you need to run this command. Saving the file is not enough as it keeps using the cached values until you run the command: cd /var/www/fspbx php artisan config:cache

You can also navigate to /horizon page and see under Completed jobs if the Scheduled Announcement job is being executed

I already have clients who tried it; it confirmed it works for them. The default setting may be cached for an hour after you change it. Wait a little bit and try to schedule another call.

I was trying to keep the module simple. Question though. When you select a reject option, you also don't get billed, and in my tests from my cell phone, I heard a message generated by my cell phone carrier that the number is not in service. Same thing, no?

Yes, we don't plan on using that page going forward. You can still access it by typing the URL directly in the browser. If you need the URL, I can dig it up for you.

It has an option to send them to VM. It's close to what you are trying to do. I'll think of adding another option in there.

You haven’t typed anything in the filter yet. The list is very long. You can also scroll.

That means the update didn't go through. Make sure you don't have anything to stash before you run git pull. Then run the update again

Should be all there. I just pulled one up - GRP26xx (v1.0.8)