Changes for page Remote Installations
Last modified by ryanp on 2021/09/09 20:55
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -16,24 +16,24 @@ 16 16 17 17 = 2. Open Communication = 18 18 19 -iSymphony will need a clear path of communication between it and the PBX. Specific ports need to be accessible between the servers, so weneed to ensure that no firewall, or IP access listis, blocking communication.19 +iSymphony will need a clear path of communication between it and the PBX. Specific ports need to be accessible between the servers, so you need to ensure that no firewall, ACL, or other IP access lists, are blocking communication. 20 20 21 -== Open Ports on theFirewall ==21 +== Open Firewall Ports == 22 22 23 23 iSymphony connects to the PBX on TCP port **5038**. If using FreePBX, the FreePBX iSymphony module will connect to the the iSymphony Server, on TCP ports **55050**, and **58080. **These ports must be open on any firewalls, between the servers. 24 24 25 25 == Asterisk Permit Entry == 26 26 27 -In order for iSymphony to connect to the Asterisk server, you will need to add the IP of the iSymphony server to the manager entry of the remote PBX. How this is done depends on if your remote PBX is isbased on FreePBX, or not.27 +In order for iSymphony to connect to the Asterisk server, you will need to add the IP of the iSymphony server to the manager entry of the remote PBX. How this is done depends on if your remote PBX is based on FreePBX, or not. 28 28 29 29 === Remote FreePBX Server === 30 30 31 -Perform these steps on the remote PBX. 31 +Perform these steps on the remote FreePBX install. 32 32 33 33 1. Log into FreePBX. 34 34 1. Navigate to **Settings->Manager Users->cxpanel.** 35 35 1. ((( 36 -In the **Permit** field, append the following to the end ,wheresthe IP or hostname of the iSymphony server.36 +In the **Permit** field, append the following to the end. Replace **<HOST>** with the IP or hostname of the iSymphony server. 37 37 38 38 {{code}} 39 39 &<HOST>/255.255.255.255 ... ... @@ -45,34 +45,12 @@ 45 45 === **Remote Vanilla PBX Server** === 46 46 47 47 {{info}} 48 -Only perform these steps if your remote serveris **not **based on FreePBX.48 +Only perform these steps if your remote PBX is **not **based on FreePBX. 49 49 {{/info}} 50 50 51 - 52 - 53 - 54 - 55 - 56 - 57 - 58 - 59 - 60 - 61 -= 3. Modify The PBX Connection Information = 62 - 63 -In order to set up a remote PBX connection, with the iSymphony Server, you need to configure the iSymphony Server with the connection information of the PBX. In the case of a remote FreePBX installation, you will also need to configure the iSymphony FreePBX module, with the connection information of the iSymphony Server. The additional connection information, in the FreePBX module, will allow the module to synchronize the configuration, between FreePBX and the iSymphony Server. 64 - 65 -{{note}} 66 -Make sure that a firewall is not blocking communication on TCP ports **5038**, **55050,** and **58080,** between the PBX and the iSymphony Server. 67 - 68 -Port **5038 **is used by iSymphony to communicate with the Asterisk server. Ports **55050** and **58080** are used, by the FreePBX module, to synchronize configuration between FreePBX and the iSymphony Server. Vanilla Asterisk installations do not need to have **55050,** or **58080,** open to the remote PBX. 69 -{{/note}} 70 - 71 -=== Vanilla Asterisk === 72 - 73 -1. Open the file **/etc/asterisk/manager.conf** on the PBX. 51 +1. On the remote server, open the file **/etc/asterisk/manager.conf**. 74 74 1. ((( 75 -Add a permit entry into the iSymphony manager connection that specifies the IP of the iSymphony Server an dsave the file.53 +Add a permit entry into the iSymphony manager connection, that specifies the IP of the iSymphony Server. This must be done on the manager login entry, the iSymphony server will be connecting with. If you do not yet have a manager entry on the PBX, for iSymphony, see [[doc:Asterisk Server (Vanilla) Installation]] for more information on how to add one. 76 76 77 77 {{code}} 78 78 [isymphony] ... ... @@ -84,6 +84,7 @@ 84 84 write = all 85 85 {{/code}} 86 86 ))) 65 +1. Save the file. 87 87 1. ((( 88 88 Reload the Asterisk manager using the following command. 89 89 ... ... @@ -91,31 +91,63 @@ 91 91 asterisk -rx "manager reload" 92 92 {{/code}} 93 93 ))) 94 -1. Log into the iSymphony Administration Interface. See [[doc:Connecting to the Administration Interface]] for more information. 95 -1. Navigate to the settings for your PBX Connection and set the **Host** field to the IP or hostname of the remote PBX. This will tell iSymphony how to connect to the remote PBX. See [[doc:PBX Connections]] for more information. 96 96 97 -== =FreePBX===74 +== iSymphony Server Permit Entry == 98 98 99 -1. Open the file **/opt/isymphony3/server/conf/security.xml** on the iSymphony Server. 100 -1. In the **communication_manager** **SecurityContext** add the IP of the PBX to the **IPAccess** **WhiteList**. See [[doc:Security]] for more information. 101 -1. Restart the iSymphony Server. See [[doc:Starting And Stopping The iSymphony Server]] for more information. 102 -1. Log into FreePBX. 76 +{{info}} 77 +Only perform these steps if your remote PBX is FreePBX based. 78 +{{/info}} 79 + 80 +When setting up a remote FreePBX installation, you need to ensure that the iSymphony server will allow the iSymphony module, on the remote FreePBX server, to connect. By default, the iSymphony server will only allow connections from localhost. You will need to modify the **security.xml** file, on the iSymphony Server, to allow connections from the IP of the remote FreePBX server. 81 + 82 +Perform the following steps on the iSymphony Server: 83 + 84 +1. Open the file **/opt/isymphony3/server/conf/security.xml** 103 103 1. ((( 104 - Navigateto**Settings->Asterisk API/ManagerUsers->cxpanel**and add a permitentryforthe IP of theiSymphonyServer by appendingthefollowingtoendofthecontentsof the**Permit**sectionandsavethe configuration.86 +In the **communication_manager** SecurityContext, add the IP of the PBX to the IPAccess **WhiteList**. Replace **[HOST]** with the IP of the remote PBX. (% style="line-height: 1.4285715;" %)See [[doc:Security]] for more information. 105 105 106 -{{code}} 107 -&<IP of the iSymphony Server>/255.255.255.255 88 +{{code language="xml"}} 89 + <!-- Security context for the communication manager and REST service --> 90 + <SecurityContext servlet="communication_manager" enabled="true"> 91 + ... 92 + <IPAccess enabled="true"> 93 + <WhiteList> 94 + <IP>127.0.0.1</IP> 95 + <IP>0:0:0:0:0:0:0:1</IP> 96 + <IP>[HOST]</IP> 97 + </WhiteList> 98 + <BlackList> 99 + </BlackList> 100 + </IPAccess> 101 + </SecurityContext> 108 108 {{/code}} 109 109 ))) 110 -1. Navigate to the iSymphony FreePBX Module page. See [[doc:FreePBX Module Administration]] for more information. 111 -1. ((( 112 -If you are adding an additional PBX to your iSymphony Server instance make sure to change the **Server Name** property under **Server Settings** to something other than **default**. If you only have one PBX you can leave this value as **default**. See [[doc:Core Servers]] for more information. 104 +1. Save the file. 105 +1. Restart the iSymphony Server, for the changes to take effect. See [[doc:Starting And Stopping The iSymphony Server]] for more information. 113 113 114 -{{note}} 115 -If you have two FreePBX instances with one iSymphony Server instance and both FreePBX instances have the same value for the **Server Name** property the two modules will conflict when trying to write out their configuration to the server. 116 -{{/note}} 117 -))) 118 -1. Modify the **Server API Host** field under **Server Settings** to the IP or hostname of the iSymphony Server. This tells the iSymphony FreePBX Module how to connect to the iSymphony Server. 119 -1. Modify the **Asterisk Server Host** field to the IP or hostname of the PBX. this tells the iSymphony Server how to connect to Asterisk. 120 -1. Modify the Client Host field to the IP or hostname of the iSymphony Server. This value is used to construct the URL to point to the iSymphony Client Interface. See [[doc:FreePBX Module Administration]] for more information. 121 -1. Save the configuration and **Apply Config** in FreePBX. 107 += 3. Modify The PBX Connection Information = 108 + 109 +You need to ensure that the iSymphony server knows the connection information for the remote PBX. In the case of a FreePBX based remote server, you will also need to ensure that the FreePBX module knows the connection information for the iSymphony Server. How this is done depends on if your remote PBX is based on FreePBX, or not. 110 + 111 +=== Remote FreePBX Server === 112 + 113 +Perform these steps on the remote FreePBX install. 114 + 115 +1. Log into FreePBX. 116 +1. Navigate to **Admin->iSympony V3**. 117 +1. Set the **Server API Host** field, to the IP address or hostname of the iSymphony server. This lets the module know how to connect to the iSymphony server. 118 +1. Set the **Asterisk Server Host** field to the IP address or hostname of the remote PBX. This is normally the IP or hostname, that you utilize to access the FreePBX GUI. This will let the iSymphony server know how to connect to Asterisk. 119 +1. (Optional) If you are attempting to set up an additional Core Server (organization), for a hosted type environment, you will need to set a unique name for the sever in the **Server Name** field. For all other situations, including a combined PBX setup, leave the **Server Name** as **default**. 120 +1. Save and select **Apply Config**. 121 + 122 +=== **Remote Vanilla PBX Server** === 123 + 124 +{{info}} 125 +Only perform these steps if your remote PBX is **not **based on FreePBX. 126 +{{/info}} 127 + 128 +1. Log into the iSymphony Administration Interface. See [[doc:Connecting to the Administration Interface]] for more information. 129 +1. Navigate to **Phone System->PBX Connections**. 130 +1. Click on **add** in the top right hand corner of the page. 131 +1. Fill in the connection information based on the manager entry you created for iSymphony. See [[doc:PBX Connections]] for more information. 132 +1. Save the PBX connection.