Search results

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...

This is only lines 62 through 70. I need all 70 lines.

It's a good practice to save dates in the UTC time zone in the DB. However, if the fax page isn't converting back properly to your timezone, it sounds like a bug to me or a feature request you need to put in.

@Andyd358 I'm sorry it happened to you. It happened to a couple of other people this month. Here is a quick fix. Run the updates cd /var/www/fspbx php artisan app:update php artisan migrate Before you do this, could you please go to the log file tail -f /var/www/fspbx/storage/logs/laravel.log...

I don't know, but you can always add new templates yourself.

@andycol I'd love that. Any contribution to the project is welcome! If you want, you can DM me and we can discuss further. I would love to see your SBC guide too. If you want to contribute to documentation, I can show you how to do it, too. Documentation is getting migrated to the main GitHub...

Paste a complete log so we can see where the problem is. Also try to update the firmware. Older Yealinks have weird issues like that sometimes. You may have to hunt the internet to find it, though if the phone is discontinued.

@jeroentjed I'm glad the article helped

@andycol We are actively developing the API and appreciate your patience as we work to complete it. Given the complexity of the system, our priority has been to enhance the overall experience for both administrators and end users in managing their phone systems. We fully recognize the importance...