Fusion 4.4.0 => 4.4.5

Just in case this affects anyone else.

I upgraded one of my test boxes today from 4.4.0 to 4.4.5, it all went smoothly apart from the upgrade schema in the GUI. It made changes to v_ring_groups and v_xml_cdr. With v_xml_cdr the upgrade tried to both add a new column and rename an old column to the name of the newly added one:
SQL:
ALTER TABLE v_xml_cdr ADD xml_cdr_uuid uuid;
ALTER TABLE v_xml_cdr RENAME COLUMN uuid to xml_cdr_uuid;
The rename fails so, in Adminer, I had to manually delete column xml_cdr_uuid and then rename uuid to xml_cdr_uuid.

Adrian.
 
@ElecBoy Glad you have solved it. For information, the section in my pg_hba.conf looks like this:
Code:
#Database administrative login by Unix domain socket
# TYPE  DATABASE        USER            ADDRESS                 METHOD
# "local" is for Unix domain socket connections only
local   all             postgres                                peer
# "local" is for Unix domain socket connections only
local   all             all                                     peer
# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5
The other thing I was going to suggest was in Advanced -> Defaults, under Adminer, there is an option to set auto_login to true. then (after logging out and back in again to refresh the session) Advanced -> Adminer takes you straight in.
 
I need to do a 4.4.1 to current 4.4 branch.
Can I just run through each of the check marks and test things out or do we need do do additional commands?

The documentation (https://docs.fusionpbx.com/en/latest/advanced/upgrade.html) implies that the check marks don't upgrade everything and lists some commands to go through, but that info also seems out dated. Also the video on the Upgrade page shows basically just going through the check marks and and the pull command because the source upgrade didn't fail.

I plan on doing this on a test server but would still like to know the "correct" way to do it.

To add to that the server is on Debian 8.11, would that be an issue?
 
Last edited:

ad5ou

Active Member
You should be able to just do the GUI based upgrade.
You will probably need to run the “upgrade schema” multiple times since there have been quite a few changes in the database since 4.4.1

Debian 8 will still work fine but you should consider updating the OS soon.
 
You should be able to just do the GUI based upgrade.
You will probably need to run the “upgrade schema” multiple times since there have been quite a few changes in the database since 4.4.1

Debian 8 will still work fine but you should consider updating the OS soon.
Thanks!

So far in testing it seems to have worked well.

Do you know is Freeswitch max out at Version 1.6.20 for Debian 8, that didn't upgrade. I did run apt-update/upgrade as well and so far things are working just didn't see a freeswitch upgrade.

Also Music on Hold will not play from the web. The files are there and appear to have same permissions as production server. Any thoughts?
Thanks for the help. If this should go in a new thread I'll do that.
 

ad5ou

Active Member
Upgrade from GUI only upgrades the Fusionpbx files and database structure. To upgrade Freeswitch etc, would be from OS package manager.

I seem to remember there was a pull request regarding moh playback from web but not sure. I’m using master branch (4.5) so not sure what problems 4.4 has at the moment.