Search results

Please update and retest. We made adjustments.

Update your server and use this variable MAIL_VERIFY_PEER=false This should bypass server certificate validation.

Perhaps you are using an old link to open this page? Use this page instead: https://fspbx.yourdomain.net/speed-dial Before you go there, run the updates. There was a small bug that I just corrected

Hang on. I'll push the update, and you'll be able to configure to bypass certificate validation.

The one you sent earlier had nothing to do with the certificate, as I've seen it many times on various systems. So if you have a new error, please post it here.

Can you send me the exact error from the log so I can investigate and find a solution? I'm pretty sure this can be done.

What this means is that you didn't fill MAIL_FROM_ADDRESS MAIL_FROM_NAME In the .env file. Once you do you need to run php artisan config:cache and then try sending email again.

Yes, the old fusion settings will be removed in future versions. They are no longer used. The official way to set up email in FS PBX is via the .env file. Can you follow the troubleshooting steps in this article, tail the main log, and then try sending an email to see what shows up as an error...

Hi @willy Lafort. After configuring your email settings in the .env file, you can create new users and click the password reset button. It will email the link with login instructions.

Don't set one up on the trunk level. Set one up on the tenant level in Dialplan->Dialplan manager-> DEFAULT CALLER ID Fill the values with your preferred CALLER ID. When the MAIN COMPANY NUMBER is selected on the extension level, the one set on this screen will be used.

Make sure the new gateway is started and it's configured with the higher priority in your Dialplan. I assume you didn't forget to create an outbound route using that gateway? Also, a very good place to troubleshoot is fs_cli.

@dbz195 Inbound fax is handled directly by a Freeswitch module. There isn't much difference between FusionPBX and FS PBX. This is likely a misconfiguration issue. Our defaults should've worked. If you changed something, there is a chance of a misconfiguration, but it could also be on the SIP...

@kenn10 We thought we had carefully orchestrated that, but I guess it was not perfect. I apologize for the inconvenience. /usr/share/freeswitch/scripts is simlinked to a directory inside FS PBX - /var/www/fspbx/resources/freeswitch_scripts You should create a directory inside of it, and call...

Missing a cache flush after your changes, by any chance?

Hello, and welcome. You mentioned both FS PBX and FusionPBX? Which one are you using?

You should look up how to use toll_allow for extensions and make the use of that variable

I don't know what your original intent was, so I answered your direct question on how to make an "Allow everyone EXCEPT" rule. It now seems like you might be overcomplicating your dialplan or approaching your solution incorrectly, since a lot of things broke.

that makes sense you are not allowing that extension to call. Other variables that might be helpful are direction and toll allow. There are examples how to use those in this forum

Hi @jeroentjed, are you using FS PBX? Try this ^(?!(?:300|301|302|303|310)$).+$ This would mean: Allow everyone EXCEPT 300, 301, 302, 303, and 310

@kenn10 I would hold off installing the newest version until they work out all the bugs. We have been manually adding the required updates to the 1.10.12 version, which ultimately became part of the 1.11 version. This is how we made FS PBX compatible with Debian 13 in the first place. One of...