Hello,
is there a planned release date for the final FreePBX 17?
Thanks,
Thomas
Hi Thomas , our goal is for GA by June 2024⌠approximately 3.5 months
We look forward to any feedback you have testing the beta in the meantime
1 Like
Will it possible upgrade a beta17 to an official17 without reinstalling?
No⌠there is no sane upgrade path from CentOS to debian. That said backup and restore should make reinstall trivial. Make sure you have migrated all trunks and extensions to pjsip prior to upgrading.
Who asked to switch from CentOS to Debian? Not me!! I wrote beta17 (freepbx) to official17. I already run Freepbx17 beta on Debian 12.5. I am just asking if i will need to reinstall all from scratch or if beta-to-official will be simply a fpbx upgrade.
About pjsip; maybe you donât know that both drivers (sip and pjsip) will be available. Tested sip on Freepbx 17 beta without any problems (asterisk 20 but 21 too).
Beta to GA means that the code has been tested and considered stable enough to graduate itâs beta period. So no, you wonât need to re-install FreePBX.
With that being said, AFAIK, thereâs no public solution for commercial modules yet, so if youâll want commercial modules, youâll have to follow Sangomaâs announcements on how to proceed.
1 Like
Uhm⌠i run 2 commercial modules on my Freepbx 17 (Debian 12,5) without any kind of problems. EPM and Sysadmin Pro payed and fully functionally. Currently registered to deployment.
who asked for this
i guess Red Hat did in a way âŚ
- you should not have to install from scratch⌠but i would suggest you do
- you could move your existing deployment ID over now⌠i wouldnât suggest this either
changes related to install script actions are one concern and my tests of running the install script over an existing install is limited
i see GA coinciding with certain module versions along with a GA christened install script⌠not a forced reinstall
for production systems id suggest having laid the foundation with the most recent GA install script , a fresh install
do not count on chan_sip
Centos 7 (and so SNG7 Distro) is going EOL on June 30, 2024.
As far as I understand, our production systems would need to move to Debian 12 + FreePBX 17 (new certified system). (using the handy âhttps://sng_freepbx_debian_install.shâ script.
Since FreePBX 17 GA is scheduled by June 2024, there is not much time to prepare this migration?
I guess the question from @Peo is: If we already spin up a new machine using the FPBX 17 BETA, can we just keep using it after the GA? Or do we need to install a new one install from scratch afterwards?
2 Likes
Iâm not going to speak for Sangoma officials but this is what I would expect as a path from 17 beta to 17 GA:
apt update && apt -y upgrade && fwconsole ma upgradeall && fwconsole r
If the asterisk packages were updated, then add: fwconsole restart
ok thanks a lot @billsimon ! If we have confirmation from Sangoma, that would be great for our good night sleep 
.
1 Like
You do know that âGoing EOLâ does not mean âstop workingâ?
True, it does not. However, some companies want more than âIt still worksâ, they want support and continued updates/development which is what EOL products/software do not have.
Of course I know that and I know you know that but my post was for those that donât know that.
I have come across people still using trixbox 2.6.2.3 some things last forever if you keep your sticky fingers off of them lol
1 Like
If you think about it, all phones are technically âEnd of Lineâ
1 Like
Thanks for the heads up 
Glad to hear that.
No uhm, still having security updates for a production system in 2024 sounds like a good idea.
There likely wonât be any âsecurity updatesâ for FreePBX 17 until it first becomes stable, then a security problem has been identified and can only come from Sangoma. Debian 12 already has regular security updates and older versions FreePBX can happily run on it.
Do correctly paid and licensed commercial modules run on Beta 17?
Thatâs part of what the beta program will be able to confirm.