Strongly recommend sticking with FreePBX 12 for the foreseeable future. Didn't think it was possible but FreePBX 13 is considerably more proprietary than FreePBX 12.
Thanks for the answers.
And FreePBX 13 being more proprietary, what consequences does this have for me as a user?
Just for fun tried the upgrade to 13 using FreePBX upgrader on another non-production PIAF machine in VM. This didn't work at all and rendered the whole GUI unusable.
Correction: The upgrade ended with a screen full of errors, which made me think that the upgrade had failed. That's not the case, the errors were related to a particular module. It seems it is working fine, but I have not done a lot of testing with it.
If any 3rd party module does still function properly I am sure they are hard at work making sure it won't for much longer.
One of the main reasons we now have our own GPL module repository. New modules don't get pushed into our repo until they are thoroughly vetted. Think of them as refugees.
I dropped in to ask if these plans have changed at all now that it is possible to install FPBX13 from "scratch" on CentOS7. I understand the proprietary Sangoma modules are still a thorn in everyone's side but if we don't care about the System Admin module etc and just want a very basic PBX with the shiny GUI, would that be possible?
No plans for FreePBX 13 GPL modules at this time. But the New Year is just around the corner.
Link up your team and customers Phone System Live Chat Video Conferencing
Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.
Check your inbox!
We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).
Upon verification you will be directed to the 3CX setup wizard.