Page Comparison

The following procedure was documented for taking a CentOS 5 - 3.10.X sipXecs system and upgrading to 4.0.1.

Upgrade Notes:

1. The local domain bind zone is "emptied", there is an open issue on this, but for good measure 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. The upgrade instructions work but the DNS thing seems as though it should be mentioned on the wiki page.

2. System > Internet Calling > Subnets may lose it's other subnets other than the one sipx is sitting on (need to confirm confirm this).

Step 1 - Stop sipXecs services

  service sipxpbx stop

Step 2 - Prepare Repository for SipXecs 4.0.x Upgrade

This will prepare the sipXecs repository file to upgrade the system. Type the following commands: * cd /etc/yum.repos.d/

  wget http://sipxecssw.org/pub/sipXecs/sipxecs-stable-centos.repo
      (this repo URL can be obtained from http://sipxecssw.org/pub/sipXecs/)

  Note 1: For any CentOS updates you will need to press Y to accept the importing of the key the 1st time.
 

  Note 2: For the 4.0.1 release the repository signing should be gpgcheck=0. This may be taken care of if you use the repo above. If 'yum update' below complains about sipxecs components not being signed, edit the repo (nano -w /etc/yum.repos.d/sipxecs-stable-centos.repo), set gpgcheck=0 and re-run 'yum update'.

Step 3 - Perform the SipXecs 4.0.1 Upgrade

This will perform the sipXecs upgrade of the system. Type the following commands:

  yum update (223 packages ~277 MB)

  nano -w /etc/yum.repos.d/sipxecs.repo and replace all references to 5.2 with 5

  yum install sipxecs (28 packages ~13 MB)

  yum install java-fonts (10 packages ~43 MB)

  reboot

Step 3a - HA Distributed Systems Upgrade Step

• This will perform the necessary update on an HA distributed system. Follow the same steps however this step is required for HA distributed servers. Type the following command: * sipxecs-upgrade
• Press Continue 3 times
• On the master system go into the web management and System -> Servers screen. Enter the IP address and Note the password for use in the next step.
• On the slave system back in the startup wizard enter the Master Hostname and setup password from the previous step.
• reboot

Step 4 - Post Upgrade Steps of SipXecs 4.0.1

...

The best way to avoid the problem is to just do the upgrade from the shell command line (you must be logged in as 'root'):

Check your yum repository configuration to make sure that it points to the stable release area:

[sipxecs-stable]
name=SIPfoundry sipXecs pbx - latest stable version
baseurl=http://sipxecs.sipfoundry.org/pub/sipXecs/LatestStable/CentOS/$releasever/$basearch/RPM
gpgcheck=0
enabled=1

1. Run 'yum update -y'.
2. If you have multiple systems in a cluster (all managed by one Management server), upgrade all the systems as above
3. Reboot (management system first).
4. Log in to the the management UI, go to System -> Servers, select the management server, and press Send Profiles.
5. Reboot each distributed server, and when it is up select it on the servers page and press Send Profiles.

Upgrading directly 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.

The DHCP 120 test will fail if you are using the on board DHCP server. To correct this you need to add the following to the /etc/dhcpd.conf and restart dhcpd (service dhcpd restart). This is not required if you aren't using the Counterpath Enterprise Clients.

# 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";