yes they should - please test and open issues if you encounter anything
Hi @cdolese, for my good night sleep: Can you confirm the path from 17 beta to 17 GA would be:
apt update && apt -y upgrade && fwconsole ma upgradeall && fwconsole r
If the asterisk packages were updated, then add: fwconsole restart
Thanks a lot!
that sounds reasonable and is the same approach i would take today; however , as we move closer to GA announcement id look for something official at that time in case anything has changed
Any progress report on where development stands and what modules still need attention
With FreePBX 17 going to Debian, does that mean strictly Debian, or does it include OpSys based on Debian such as Ubuntu
So far most everything works on Ubuntu 20.04 I havenāt tried 24.04 yet
Bump. Itās now 5/28, I am wondering if there is something more concrete about a forthcoming GA for FreePBX 17?
2 Likes
If we followed this route, do you think there would be any foreseeable dependency or library compatibility issues? IE: āapt update && apt -y upgrade && fwconsole ma upgradeall && fwconsole rā
Or is it best to install the FreePBX 17 GA fresh when available and suck in my backup? I am happy to do either, as I want to ensure the path is safe in the long run. I am happily on the beta right now testing.
The repo theyāre publishing from right now is called āfreepbx17-prodā so my take on it is that this beta is going to flow directly to GA. I would not expect any problems simply updating your beta server to the GA versions using normal update procedures. But I am not an authority on this.
Excellent, sounds promising. Promising is good enough for me. Iām really impressed with the speed of progress on this release. Switching the project to Github was a good choice.
Iāll put it here so that I donāt have to open a new topic. Since we are getting closer to release date I have a question about the upgrade:
Our FreePBX is installed on a MiniPC (small office, 5 phones, 3 lines, has been working for 2 years without any problems). The FreePBX makes a daily backup to an FTP server (irrelevant for my question). And it makes a weekly warm spare backup via SSH to a separate, completely identical MiniPC. This has also been absolutely problem-free for 2 years (with the lines remaining deactivated on the backup systemā¦). The idea, of course, is that if the main PBX fails, we are up and running again with the backup PBX within minutes (so far, so unspectacular).
The EndPoint module is licensed on our main PBX (25-year license). Not on the backup PBX, of course. That is the initial situation.
My idea would be to keep our main PBX running. I would then upgrade to FreePBX 17 on the backup PBX, i.e. first Debian and then FreePBX and restore the last backup according to the guide. Once everything is tested and working on FreePBX 17, which I assume is the case as our setup is quite simple and I am confident, we would probably use this system as the main PBX (i.e. switch on the lines etc.) and then update the other MiniPC, which would then become the backup PBX. Now to the actual question: Can I activate the license of the EndPoint module? It seems to me that I have to deactivate it on the other one first and then activate it on the new one. But you canāt do that indefinitely (it seems to me 2x), which is a bit annoying if I lose one of two left activations, so to speak, just for an upgrade to a new FreePBX version. Could I get around this by reactivating the license on the same PC (where is activated now) or will I lose one activation anyway? Long story short: Is there a way to upgrade without loosing an activation of the EPM?
We also have an EPM license and curious about an answer. Currently Iām copying the configuration over and over a weekend I do a final migration and wonder on how to migrate EPM to the new server. Itās annoying that w/o a license it is not possible to already configure EPM.
Hello team, first post here. What support is there with V17 for iSymphony? I read that the iSymphony module is being deprecated, will FreePBX still work with iSymphony if the latter is installed as a standalone server and connected, or is this the end of the line? Any other ideas I may be overlooking for a decent operator dashboard?
Gerald Martin
Bumpā¦maybe this question should have had its own thread? I posted here because itās a possible change from v16 to v17ā¦
FOP2, is overall really stable pretty customizable. Reaching their support can be challenging at times.
The cxpanel module (the module that integrates FreePBX and iSymphony) has a v17 branch, so I donāt know whether itās deprecated but there is code there. GitHub - FreePBX/cxpanel: Module of FreePBX (iSymphonyV3) :: This module automatically configures the operator panel to reflect the PBX configuration.
Wasnāt FOP2 compromised? I purchased it way back, but had a compromised PBX and we thought FOP2 may have been responsible?
Hmm. I had watched a recent webinar recording where I thought they said that the cxpanel module was deprecated in v17. Is anyone alive over at iSymphony? Seems to be a dead project. I really, really wish there was a modern alternativeā¦
They had a vulnerability a while back.