Search results

The link should direct you to the page where you can reset your password. If nothing happens, then your email client may be blocking clicks. Try to right-click and copy the link, then manually paste it into the browser.

For security reasons, you can only reset passwords and can't see them. Go to the security tab and reset the password. The user will receive an email. Users can also navigate to the login page and request their own password resets.

You posted in the FS PBX subforum. FS PBX is a fork of FusionPBX with a lot of enhancements. You may need to repost this in the FusionPBX subforum. Generally, there is a lot that's involved in getting the fax ATA to work correctly, if that's what you are asking.

Oh my bad, I understand what's happening now. Yeah, server failover won't help the endpoints. You might want to think of a backup internet connection or manual switching is the only way you have left.

Normally, trunk providers also have a failover that you can set up in standby mode. They send an SIP INVITE to your main server, and if it doesn't respond, they send an INVITE to the backup server. Pretty much every provider has this option. Please don't confuse it with load balancing. That's...

Any process executed through the portal runs under the www-data user. Because this user has limited permissions, it does not have the access required to perform a full restore. For your situation, a DNS failover will work very well. Health probes should be configured to check for valid SIP...

@sly I understand your point—a web-based restore feature would certainly be convenient. The challenge is that, by design, the web user (www-data) has very limited access outside of the web directory. That’s why many operations currently require SSH access. If we can design a secure method to...

Hi @sly It keeps 2 days of tarball file back-ups and 7 days of database backups. If you think adding a variable to the default settings is a good idea, I can add it in the next release. For disaster recovery, I would do the following: 1) Install a fresh copy of FS PBX 2) restore the database...

Hi @bfbmellc, I'm glad to hear you are enjoying the system. You are correct, the SMS messaging was redone entirely from scratch to utilize a proper queuing system. Many background processes are running on queues to free up vital resources for phone calls. I'm happy to help you navigate getting...

You might want to submit a bug to the developers or attempt to fix it and submit them a pull request. I've fixed many bugs like that in FS PBX. It takes time to get it right.

Try this ^(1003|1004|1002|1001|405)$ Also this is a good website to test regex https://regex101.com/

How about you simply register your other FusionPBX to an extension in your SBC FusionPBX? I do it for analog PBXs that have an IP interface.

yes you can definitely add a range if you play with regex. Yes, you can update 911 to 112, like in your example. 933 is a test for 911 in US.

Do they have their own VoIP service that you don't provide? Your outbound route would look like this. I added a condition to check if the call was from extension 1003. Then this outbound route can only be used by this extension

Have you set up outbound caller ID and correctly passed it to the carrier? This is the most likely issue.

If you used FusionPBX before, the way you set it up in FS PBX is mostly identical.

Alright then. I'll have to wait till it happens next time then. Thank you for trying. Does the page open now?

you can also force it to open more recent lines by runnign this command tail -n 200 -f /path/to/log.log

tail doesn’t open the whole log—logs can be huge. It shows the end of the file and then streams new lines as they’re written (like watching fs_cli events). So start tail, then reproduce the issue; the latest error will appear live.

You need another condition for each outbound route to match the extension. This way the dialplan selects the route that matches this condition and skips all others. Also, to be clear, I understand your use case and why you are doing it. But this is not a standard practice. Usually, users share...