This documentation relates to iSymphony 3.5. You can view older documentation on the Older Documentation page

Skip to end of metadata
Go to start of metadata

On this page:

This page goes over how to to determine which installation method is required for your system, along with how to determine your current installation method, in order to know which is the correct upgrade method. When upgrading you need to utilize the same method that was originally used to perform the installation.

When performing upgrades via the Automated upgrade mechanism, in the Administration Interface, the installation method is irrelevant. Determining your installation method is only needed when performing manual upgrades via the RPM or Tarball installation packages.

Installation Methods

There are two different installation methods for iSymphony. The RPM method has two separate RPM packages that could be used.

RPM

On RedHat based systems the iSymphony server is usually installed as an RPM. For upgrades, you can execute the following command to check if the server was installed via an RPM:

rpm -qa | grep iSymphony

You may have the iSymphony version 2 server installed via RPM. If so the version 2 RPM id will show up in the resulting list. Make sure that you only pay attention to RPM ids with 3.x.x in the version.

There are two separate RPM packages that you need to be aware of.

Vanilla RPM

This is the RPM that is distributed at www.getisymphony.com. The RPM is configured to run the iSymphony server as the root user. These RPMs will not contain "fpbx" in the RPM id.

FreePBX RPM

This is the RPM that is distributed with the FreePBX and Asterisk Now distros, and should be used in a FreePBX environment. The RPM is configured to run the iSymphony server as the asterisk user. These RPMs will contain "fpbx" in the RPM id, and should be used on all RedHat based FreePBX phone systems.

Tarball

The Tarball installation package is usually utilized on systems like Debian.

If no RPM id could be found for iSymphony, or the rpm -qa command cannot be run, the installation was more than likely performed via the Tarball.

 

  • No labels