Jump to: navigation, search

Upgrading Feature Server

Use this procedure to upgrade from one version of SIP Feature Server 8.1.2 to another. Note the following restrictions:

  • Transitioning from SIP Voicemail to SIP Feature Server requires a fresh installation.
  • You cannot change installation modes (cluster to standalone or vice-versa).
Important
While upgrading Feature Server, launcher.xml will not be updated and the options in launcher.xml remain unchanged.

Upgrading while Feature Server is running (recommended)

To upgrade a running Feature Server environment, stop and upgrade one Feature Server Cassandra cluster instance at a time, beginning with the master Feature Server.

  1. On the Feature Server master node (which is also the Cassandra seeds node), back up all files in the etc folder, which includes the cassandra.yaml file.
  2. Stop or Graceful Stop Feature Server.
  3. Install Feature Server from the installation package. During the upgrade, the installer uses the values provided during a fresh installation.
  4. Start Feature Server.
  5. Repeat steps 2-4 for each Feature Server instance.
  6. Upgrade or install and configure the Feature Server GAX Plug-in.
  7. If you are updating a Feature Server 8.1.200.88 environment that also uses the Feature Server dial plan, you must run a migration script.
  8. Optionally, create and assign voicemail profiles.

Upgrading while Feature Server is stopped

To upgrade a running Feature Server environment, upgrade one Feature Server Cassandra cluster instance at a time. Upgrade the master Feature Server last.

  1. On the Feature Server master node (which is also the Cassandra seeds node), back up all files in the etc folder, which includes the cassandra.yaml file. Do not upgrade the master node until after you have upgraded all other nodes.
  2. On a non-master node, install Feature Server from the installation package. During the upgrade, the installer uses the values provided during a fresh installation.
  3. Start Feature Server.
  4. Repeat steps 2-3 for each Feature Server instance.
  5. Upgrade or install and configure the Feature Server GAX Plug-in.
  6. If you are updating a Feature Server 8.1.200.88 environment that also uses the Feature Server dial plan, you must run a migration script.
  7. Optionally, create and assign voicemail profiles.

Restore HTTPS configuration

The following procedure shows how to restore HTTPS configuration of Feature Server after an upgrade. This procedure is applicable only while upgrading Feature Server to version 8.1.201.92 or above.

  1. After upgrading to version 8.1.201.93 or above, the Feature Server installation folder contains the following files retrieved from the folder containing the previous versions: start.ini.bak and etc.bak in both Windows and Linux operating systems. Previously, when upgrading Feature Server overwrote these files rather than retrieving existing files.
  2. Compare and copy the difference in the values of start.ini, start.ini.bak and etc/jetty-ssl.xml, etc.bak/jetty-ssl.xml and apply the differences in start.ini and etc/jetty-ssl.xml.
  3. Copy etc.bak/keystore to etc/keystore to restore the configuration.
Important
After upgrading to Feature Server version 8.1.201.92, the backup of the etc folder and the start.ini file will be named as start.ini.backup (Windows), start.ini.bak (Linux), etc.backup (Windows), and etc.bak (Linux), respectively.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on May 12, 2017, at 00:06.