Search results

I confirmed that this email actually had a duplicate header. I removed it and committed the fix. Please try again after the update. This had no effect on the other mail carriers.

Many have already switched to FS PBX and are using it in production. We developed it in-house for our own business. It's not going away, and we are releasing new updates weekly. We have an active Discord channel, and the number of stars on GitHub keeps growing. It also comes with support plans...

I'm going to look into this on my test server and get back to you.

You can also copy the files, such as recordings and voicemails, over ssh to the respective folders.

@kenn10 The easiest solution is to install the new system and then restore the database from the backup of the original machine.

Fixed has been pushed. Please update and let me know if you experience any further issues. It had to do with the Australian numbers, as I suspected.

I pushed a fix for this. Please, update and try again

I'm sure we can add something like this in the future.

They are stored in /var/www/fspbx/resources/views/emails

Yes right now it seems to be this way. We will need to make it more centralized in future updates.

This might be due to the same issue on a different page. Let me look into this and push another update.

This is a very old phone. But I've seen it working. Call our suuport and we'll try to help you get it up an runnning

I pushed an update. Please update and try again. Let me know if it's all good.

I believe your concern was resolved on our Discord channel.

I would have to circle back and add new voices if they are supported. We added all the options they had at the time we were coding the first version. Rebuilding of an old recordings page is on the roadmap. When we do, you will be able to generate recordings on one page and use them elsewhere...

I have many clients, small and large, that go with a primary-backup pair of servers. This way, both servers and databases are geographically redundant. You can always spin up new servers, add them to the cluster, and remove the old ones. I like your idea of manually moving clients. Believe it...

https://www.pbxforums.com/threads/remove-a-domain.8958/

Let me push a quick update to allow this type of number. Stand by

We simplified things in FS PBX. You register against your main domain and pass the tenant domain in the header. It's a unified way of doing things. If you must, you can still make tenant domains routable, but it's not a hard requirement, and it makes things a lot easier in the long run. For...

If your plan is to export the data and import it to FS PBX, why do you need to keep the domain name the same? This is a perfect time to adopt the unified name convention that uses only lowercase.