Recent content by pbxgeek

I see what you are doing. Well, we personally address that with BLFs, restaurant A only gets BLFs from their location and Restaurant B only gets their BLFs. Then, when they pick up calls, there is no mix-up between the locations. This could easily be done within different departments too in the...

@TheMoebius A lot of the information in older posts is outdated, so rather than going back and forth here, why don’t we jump on a quick Zoom call and I can show you the differences firsthand? We’re a service provider just like you, and FS PBX was originally built to solve the challenges we were...

If you don't put anything in the pickup group options, it works too. Are you doing it via BLFs, right? I personally haven't tested it, but my impression has always been this: if you put something in the pickup group, you are limiting the pickup ability to just that group.

@TheMoebius FS PBX is the right choice. We are happy to have you here.

This is a very rarely used feature, and cluttering the main list view with it makes no sense. However, a report can be created to export the data you need to see. Reach out to support, and we can get this done for you.

I see one possible issue with your plan. If there is a confirm option, then the call isn't really forwarded until the person confirms. Which means there will be no diversion header. The whole point of the confirm option is to keep the call in the system in case the end user declines.

This has been fixed in the latest commit

I built it for Yealink RPS. Are you using RPS or YMCS? I'm now reading more about the differences, and it looks like they are using different APIs.

try (.*)@fax.mydomain.com.au instead of .*@fax.mydomain.com.au

The URL giving you an error is correct. It's not supposed to be a URL you can open in the browser. This is how I have it set up for my test server. It looks like you did everything correctly. But please double-check your setup. Did you pass the verification for your domain in Mailgun...

There have been no changes to how Caller ID works for extensions in over a year. If you set it up on the extension itself, those are the values passed unless you override them in your dialplan. I tested with the vanilla dialplan that ships with FS PBX just now and received an expected result...

There are a few underlying things that need upgrading. But we take it slow since we don't want to bring anyone's production system to a stop. So far, we've been managing most of the updates with as few hiccups as possible. Specifically, about Node.js, once the assets are built during updates...

We’ve added native Yealink Redirection and Provisioning Service (RPS) integration to FS PBX. Yealink RPS solves the “first connection” problem for new and factory-reset phones. Instead of manually entering a provisioning URL or configuring DHCP option 66, the phone contacts Yealink RPS and is...

@yaboc Thank you for the detailed example. I found the bug and committed a fix. Please go ahead and try updating again. For anyone else who updated prior to this fix and experiences the same issue, here is how to fix it. Run these commands on both servers: su postgres psql fusionpbx...

@yaboc, that means you might have an issue with database replication. Our update guide specifically outlines how to perform updates and database migrations for redundant servers. You might have missed a step. Postgres log can confirm that