Upgrade to the next maintenance release
A maintenance release is a minor release that typically includes major bug fixes that have impaired operation of a released version in production. Occasionally maintenance releases can also include minor upgrades to device plugins for the support of new firmware revisions or other minor feature enhancements.
Upgrading to the next higher maintenance release is done using your favorite package management tool, such as yum, up2date, yast or whatever. sipXecs needs to be stopped prior to the upgrade. Configuration of the system is not altered and no other configuration is required after the upgrade. Just restart sipXecs.
Upgrade to the next major release
A major release adds significant new features. The upgrade and data migration procedure involved with a major upgrade is automated. The RPM installation files include the necessary mechanisms to migrate and upgrade the database structure and content as well as the entire system configuration. Use your favorite package management system to initiate a major release upgrade. sipXecs needs to be stopped prior to the upgrade and then restarted.
Upgrade the operating system
Upgrading the operating system requires following the procedures outlines by the operating system provider. sipXecs is compiled against a specific version of the operating system. Therefore, as part of an OS upgrade sipXecs needs to be upgraded to the version compiled for that new version of the OS.
Uninstalling sipXecs
The following procedure will get sipXecs uninstalled on CentOS or Fedora operating systems:
service sipxpbx stop
service postgresql stop
yum remove sipxportlib
rm -rf /var/sipxdata
rm -rf /var/log/sipxpbx
rm -rf /etc/sipxpbx
rm -rf /var/lib/pgsql/data/*
To re-install sipXecs do this:
yum install sipxecs
cd directory where you generated the certificate
/usr/bin/ssl-cert/install-cert.sh
service sipxpbx start