From SIPfoundry sipx, The Open Source SIP PBX for Linux - Calivia

[edit] Upgrading from sipX 3.4 on FC4 to sipX 3.4 on FC5

Instead of starting with a fresh install of Fedora Core 5, you might be tempted to try and upgrade using yum. In theory that should work fine and several articles suggest fairly simple procedures: (1) and (2).

Be warned: On a host running sipX this upgrade will not be automatic

[edit] Upgrade Procedure

Here is what was found to work:

1. Make a backup of the configuration and voicemail store of sipX using the Config Server user interface
2. Stop sipX and postgresql: service sipxpbx stop and service postgresql stop
3. Remove the sipX installation: sipx-uninstall
4. Uninstall postgresql and postgresql-server: yum remove postgresql-server postgresql
5. Remove the postgres data directory: rm -rf /var/lib/pgsql
6. Upgrade FC4 to FC5: see (1)

   rpm -U http://download.fedora.redhat.com/pub/fedora/linux/core/5/i386/os/Fedora/RPMS/fedora-release-5-5.noarch.rpm

   rpm -ivh http://download.fedora.redhat.com/pub/fedora/linux/core/5/i386/os/Fedora/RPMS/fedora-release-5-5.noarch.rpm

   yum update yum

   yum upgrade

7. Reboot
8. Re-install sipX 3.4 using the single file installer
9. Save the httpd.conf file: cp /etc/sipxpbx/httpd.conf /etc/sipxpbx/httpd.conf.fc5
10. Restore the saved sipX configuration and mailstore using restore-configs and restore-mailstore. The backup files have to be in directories backup-configs and backup-mailstore in your home directory.
11. Copy the new httpd.conf file back: cp /etc/sipxpbx/httpd.conf.fc5 /etc/sipxpbx/httpd.conf
12. Start sipX

[edit] Some Explanations

1. Removing sipX: Upgrading with sipX installed leads to unresolvable dependencies during yum upgrade. Yum aborts and the upgrade cannot be done. Uninstalling sipX first resolves this problem.

2. Postgresql: Fedora Core uses the old version 7.4 of the Postgres server while Fedora Core 5 upgraded to version 8. The data set between the two versions is not compatible, so that after upgrading the postgresql-server RPM to version 8, Postgres will not start and print an error message. Deleting the directory /var/lib/pgsql deletes all the old data sets and allows you to start fresh.

3. httpd Configuration: The file /etc/sipxpbx/httpd.conf is backed up as part of the sipX configuration and then restored. However, the file required for FC5 is different. Therefore, after restoring from backup the respective file that was installed for FC5 needs to be copied back in.

4. Re-installing sipX 3.4: In order to be able to restore the sipX backup, the same version of sipX has to be running on the system. Therefore, before you attempt to upgrade to a newer version (e.g. sipX 3.6), you have to re-install the version for which you have taken a backup.