...
- Run '
yum update -y
'. - If you have multiple systems in a cluster (all managed by one Management server), upgrade all the systems as above
- Reboot (management system first).
- Log in to the the management UI, go to
System -> Servers
, select the management server, and pressSend Profiles
. - Reboot each distributed server, and when it is up select it on the servers page and press
Send Profiles
.
Upgrading
...
from 3.10.x
The local domain bind zone is "emptied", if you are using the system as a DNS server, you should copy or backup your zone file before the update. It doesn't effect other zone files on the system, just the one sipx is attached to.
...
Code Block |
---|
# header section of dhcpd.conf option sip-servers-name code 120 = text; # subnet section of dhcpd.conf option sip-servers-name "<hostname>:12000/cmcprov/login"; |
Upgrading from 4.0.4
If you originally installed your system from the sipfoundry ISO in 4.0.4 and are having issues updating, here's some help:
First you have to determine what your redhat-release is:
Code Block |
---|
cat /etc/redhat-release |
If it doesn't say CentOS but says (sipXecs 4.x), then here's what you need to do, AFTER YOU GET A PROPER BACKUP..
- Rename your repo file:
(If you do not have a CentOS-Base.repo or other repos in there, it's OK, this will probably fix a lot, just hold on).Code Block ls \-l /etc/yum.repos.d sipxecs-stable-centos.repo
Code Block mv sipxecs-stable-centos.repo CentOS-Base.repo
- Edit the repo to make it JUST a CentOS repo again - remove these lines and save it:
Code Block [sipxecs-stable] name=SIPfoundry sipXecs pbx - latest stable version baseurl=[http://sipxecs.sipfoundry.org/pub/sipXecs/4.0.4/CentOS/5/i386/RPM/] gpgcheck=0 gpgkey=[https://secure2.pingtel.com/RPM-GPG-KEY-pingtel] enabled=1
- Get the correct repo for sipx:
Code Block cd /etc/yum.repos.d wget http://download.sipfoundry.org/pub/sipXecs/sipxecs-4.2.0-centos-i386.repo
Now you can go from 4.0.4 (ONLY from the command line) with "yum update". DO NOT use the web interface. After you have 4.2.0 working properly and another backup, you should jump right into 4.2.1, which is much easier.