...
Notes
- When performing an upgrade is always a good idea to backup your production system. It is also good to perform the update on a test system first in order to mitigate risks in production.
- It is also NOT recommended you use the administration web interface to upgrade your system from one version to another. The administration web interface for upgrading is best used for minor bug updates.
- You can upgrade from any version to any version as long as you follow the manual steps both before and after your upgrade.
- If you have multiple systems in a cluster (all managed by one Management server). Complete upgrade process on the master server before proceeding to the slave nodes. Once all the systems have been upgraded, log in to the the management UI, go to
System -> Servers, select all the servers and pressSend Profiles. Reboot any services when administration service instructs you to do so.
Upgrade Instructions
Step 1. Follow each of the pre-install instructions starting with the version you currently have installed. Then come back to this step and continue. So if you currently have version 4.0.4 installed, you want to start with the instructions for 4.0.4 and then proceed to the end of the pre-install instructions for each version.
...
- The binaries were probably built with the latest packages
- If ever you needed to update a package for security reasons, you'd want to minimize the changes to your system
- It's often a requirement for getting assistance on mailing list
- If you do have any problems, most likely others will see the problem as well and provide a quick solution to your issue.
...
- .
Step 4. Follow each of the post-install instructions starting with the version you currently have installed. Then come back to this step and continue.
...
| Code Block |
|---|
service sipxecs start |
DoneComplete. See notes however above if you are upgrading a clustered system.
Before upgrading from 3.10.x
...