Upgrading the FreePBX firmware
-
@aaronstuder said in Upgrading the FreePBX firmware:
@JaredBusch do you have to reboot between updates?
I am using System Admin to do updates, and it doing them one after another, without a reboot.
Do you have to reboot? No.
I reboot, because I want all things applied. including the system being booted to an updated kernel from the
yum updatethat it does. -
@JaredBusch, are you running the new distro from Sangoma yet?
-
@wls-itguy said in Upgrading the FreePBX firmware:
@JaredBusch, are you running the new distro from Sangoma yet?
We are running it in production, have been since release day. We actually had the final Release Candidate in production, we were that anxious.
-
@scottalanmiller Scott, I don't see an upgrade option through my SysAdmin page. Did you upgrade via CLI?
-
@wls-itguy said in Upgrading the FreePBX firmware:
@scottalanmiller Scott, I don't see an upgrade option through my SysAdmin page. Did you upgrade via CLI?
Upgrade from what? The RC just updated on its own.
-
@scottalanmiller I assume @WLS-ITGuy means from FreePBX 13
-
They don't have a script yet to go from 13 to 14.
-
@aaronstuder said in Upgrading the FreePBX firmware:
@scottalanmiller I assume @WLS-ITGuy means from FreePBX 13
We didn't upgrade from 13, we did a clean slate build.
-
-
@scottalanmiller said in Upgrading the FreePBX firmware:
@aaronstuder said in Upgrading the FreePBX firmware:
@scottalanmiller I assume @WLS-ITGuy means from FreePBX 13
We didn't upgrade from 13, we did a clean slate build.
So was this for a new install, or for a previous customer? If previous, how did you migrate all of your settings over?
-
@dashrender said in Upgrading the FreePBX firmware:
@scottalanmiller said in Upgrading the FreePBX firmware:
@aaronstuder said in Upgrading the FreePBX firmware:
@scottalanmiller I assume @WLS-ITGuy means from FreePBX 13
We didn't upgrade from 13, we did a clean slate build.
So was this for a new install, or for a previous customer? If previous, how did you migrate all of your settings over?
We did it on beta, so it was for internal. Wouldn't do that to outside customers.
PBX are really easy to migrate by hand, no need to bring cruft over. IF you have hundreds of users and complex IVRs, yeah that can be a pain. For a typical SMB, how long does a manual migration take, an hour? And if you are cleaning up craft as you go, pruning extensions, it can be a break even on time.
-
@scottalanmiller said in Upgrading the FreePBX firmware:
@dashrender said in Upgrading the FreePBX firmware:
@scottalanmiller said in Upgrading the FreePBX firmware:
@aaronstuder said in Upgrading the FreePBX firmware:
@scottalanmiller I assume @WLS-ITGuy means from FreePBX 13
We didn't upgrade from 13, we did a clean slate build.
So was this for a new install, or for a previous customer? If previous, how did you migrate all of your settings over?
We did it on beta, so it was for internal. Wouldn't do that to outside customers.
PBX are really easy to migrate by hand, no need to bring cruft over. IF you have hundreds of users and complex IVRs, yeah that can be a pain. For a typical SMB, how long does a manual migration take, an hour? And if you are cleaning up craft as you go, pruning extensions, it can be a break even on time.
Bullshit. Again you have no perspective.
An hour to migrate an entire PBX? Voicemail passwords? Extensions and secrets?
Bull fucking shit.
-
Sometimes I think SAM posts things to get @JaredBusch all fired up
-
@jaredbusch said in Upgrading the FreePBX firmware:
@scottalanmiller said in Upgrading the FreePBX firmware:
@dashrender said in Upgrading the FreePBX firmware:
@scottalanmiller said in Upgrading the FreePBX firmware:
@aaronstuder said in Upgrading the FreePBX firmware:
@scottalanmiller I assume @WLS-ITGuy means from FreePBX 13
We didn't upgrade from 13, we did a clean slate build.
So was this for a new install, or for a previous customer? If previous, how did you migrate all of your settings over?
We did it on beta, so it was for internal. Wouldn't do that to outside customers.
PBX are really easy to migrate by hand, no need to bring cruft over. IF you have hundreds of users and complex IVRs, yeah that can be a pain. For a typical SMB, how long does a manual migration take, an hour? And if you are cleaning up craft as you go, pruning extensions, it can be a break even on time.
Bullshit. Again you have no perspective.
An hour to migrate an entire PBX? Voicemail passwords? Extensions and secrets?
Bull fucking shit.
yeah, I tend to agree with JB here. Unless you can script the creation extensions with matching passwords, etc, etc, etc... anything more than a tiny shop will be more work to rebuild and manually migrate than to upgrade.
-
@dashrender I know I ain't building new and migrating
-
Firmware 21 released last week for FreePBX 13.
[root@fpbx ~]# cd updatescripts/ [root@fpbx updatescripts]# wget https://upgrades.freepbxdistro.org/stable/10.13.66/upgrade-10.13.66-21.sh --2017-07-31 14:28:22-- https://upgrades.freepbxdistro.org/stable/10.13.66/upgrade-10.13.66-21.sh Resolving upgrades.freepbxdistro.org... 199.102.239.49 Connecting to upgrades.freepbxdistro.org|199.102.239.49|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 13983 (14K) [application/x-sh] Saving to: “upgrade-10.13.66-21.sh” 100%[============================================================================================================>] 13,983 --.-K/s in 0s 2017-07-31 14:28:23 (273 MB/s) - “upgrade-10.13.66-21.sh” saved [13983/13983] [root@fpbx updatescripts]# chmod +x *.shAs you can see here, my PBX has been around a while.
[root@fpbx updatescripts]# ls upgrade-10.13.66-12.sh upgrade-10.13.66-14.sh upgrade-10.13.66-16.sh upgrade-10.13.66-18.sh upgrade-10.13.66-20.sh upgrade-10.13.66-13.sh upgrade-10.13.66-15.sh upgrade-10.13.66-17.sh upgrade-10.13.66-19.sh upgrade-10.13.66-21.shOn to the upgrade
[root@fpbx updatescripts]# /root/updatescripts/upgrade-10.13.66-21.sh Check to make sure this is a FreePBX Distro system before executing This appears to be a FreePBX Distro system as it has a Distro Version of 10.13.66-20 Your FreePBX Distro System is being upgraded to 10.13.66-21. Please standby... <snippers> Mon Jul 31 14:31:26 CDT 2017 UPGRADE 100% COMPLETED Unlocked. REBOOT YOUR BOX NOW FOR DAHDI CHANGES TO TAKE EFFECT If you would like to change your Asterisk release version to 11 or 13 you can do so by typing asterisk-version-switch from the linux CLI at anytime -
@scottalanmiller said in Upgrading the FreePBX firmware:
@dashrender said in Upgrading the FreePBX firmware:
@scottalanmiller said in Upgrading the FreePBX firmware:
@aaronstuder said in Upgrading the FreePBX firmware:
@scottalanmiller I assume @WLS-ITGuy means from FreePBX 13
We didn't upgrade from 13, we did a clean slate build.
So was this for a new install, or for a previous customer? If previous, how did you migrate all of your settings over?
We did it on beta, so it was for internal. Wouldn't do that to outside customers.
PBX are really easy to migrate by hand, no need to bring cruft over. IF you have hundreds of users and complex IVRs, yeah that can be a pain. For a typical SMB, how long does a manual migration take, an hour? And if you are cleaning up craft as you go, pruning extensions, it can be a break even on time.
Probably more like 10 mins, ammaright?
-
It appears that Firmware updates are now part of the system level updates done by
yumas of version 14. -
If I want to go from 13 to 14 I need to go here:
https://wiki.freepbx.org/display/PPS/Upgrading+from+Distro+6
-
@wls-itguy said in Upgrading the FreePBX firmware:
If I want to go from 13 to 14 I need to go here:
https://wiki.freepbx.org/display/PPS/Upgrading+from+Distro+6
Yes. It is certianly still beta. I had major issues the first time then minor issues the last time.
The last time was my company PBX and I have some strangeness with my desk phone connecting. But another user's desk phone is not having the same problems.
