Skip to Content
Last modified by michaely on 2021/09/09 20:55
From version 1.1
edited by michaely
on 2021/09/09 18:01
Change comment: Import
To version 2.1
edited by michaely
on 2021/09/09 18:01
Change comment: Import

Summary

Details

Page properties
Content
... ... @@ -1,11 +1,5 @@
1 -**//On this page~://**
1 +This page goes over how to determine which installation method was used to install your iSymphony server. Knowing which installation method was used is crucial when performing upgrades, and will allow you to determine which package to download for the upgrade.
2 2  
3 -
4 -
5 -{{toc maxLevel="3"/}}
6 -
7 -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.
8 -
9 9  {{info}}
10 10  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.
11 11  {{/info}}
... ... @@ -12,11 +12,11 @@
12 12  
13 13  = Installation Methods =
14 14  
15 -There are two different installation methods for iSymphony. The RPM method has two separate RPM packages that could be used.
9 +There are three different installation methods for iSymphony.
16 16  
17 17  == RPM ==
18 18  
19 -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:
13 +On RedHat based systems the iSymphony server is usually installed as an RPM. You can execute the following command to check if the server was installed via an RPM:
20 20  
21 21  {{code language="bash"}}
22 22  rpm -qa | grep iSymphony
... ... @@ -28,18 +28,12 @@
28 28  
29 29  There are two separate RPM packages that you need to be aware of.
30 30  
31 -==== Vanilla RPM ====
25 +=== Vanilla RPM ===
32 32  
33 -This is the RPM that is distributed at [[www.getisymphony.com.>>url:http://www.getisymphony.com./||shape="rect"]] The RPM is configured to run the iSymphony server as the **root** user. These RPMs **will** **not** contain "//fpbx//" in the RPM id.
27 +This is the RPM that is distributed at [[www.getisymphony.com.>>url:http://www.getisymphony.com./||shape="rect"]] The RPM is configured to run the iSymphony server as the **root** user. These RPMs will **not** contain "//fpbx//" in the RPM id.
34 34  
35 -==== FreePBX RPM ====
29 +=== FreePBX RPM ===
36 36  
37 -This is the RPM that is distributed with the FreePBX and Asterisk Now distros. 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.
31 +This is the RPM that is distributed with the FreePBX and Asterisk Now distros. The RPM is configured to run the iSymphony server as the **asterisk** user. These RPMs will contain "//fpbx//" in the RPM id.
38 38  
39 -== Tarball ==
40 -
41 -The Tarball installation package is usually utilized on systems like Debian.
42 -
43 -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.
44 -
45 45