Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -4,110 +4,24 @@
4	4
5	5	{{toc/}}
6	6
7		-When installing the iSymphony Server remotely from the PBX, extra steps need to be taken in order for the iSymphony Server to communicate with the remote PBX.
	7	+When installing the iSymphony Server remotely from the PBX extra steps need to be taken in order for iSymphony to communicate with the remote PBX.
8	8
9	9	= 1. Setup The Remote Voicemail And Recording Agent =
10	10
11		-In order for the iSymphony server to know about voicemail and recording file activity, on the remote PBX, you must install and configure a Remote Agent on the PBX. See [[doc:Remote Agents]], for information on how to install and configure a Remote Agent.
	11	+In order for the iSymphony server to know about voicemail and recording file activity on the remote PBX you must install and configure a Remote Agent on the PBX. See [[doc:Remote Agents]] for information on how to install and configure a Remote Agent.
12	12
13	13	{{info}}
14		-The remote agent is not required, however you will not have voicemail or recording management, in browser, if not set up.
	14	+The remote agent is not required however you will not have voicemail or recording management in browser if not set up.
15	15	{{/info}}
16	16
17		-= 2. Open Communication =
	17	+= 2. Modify The PBX Connection Information =
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 we need to ensure that no firewall, or IP access list is, blocking communication.
	19	+Depending on if you are using the iSymphony FreePBX module or not will determine where you modify this information.
20	20
21		-== Open Firewall Ports ==
	21	+{{note}}
	22	+Make sure that a firewall is not blocking communication on TCP ports **5038**, **55050** and **58080** between the PBX and the iSymphony Server.
	23	+{{/note}}
22	22
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		-
25		-== Asterisk Permit Entry ==
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 based on FreePBX, or not.
28		-
29		-=== Remote FreePBX Server ===
30		-
31		-Perform these steps on the remote FreePBX install.
32		-
33		-1. Log into FreePBX.
34		-1. Navigate to **Settings->Manager Users->cxpanel.**
35		-1. (((
36		-In the **Permit** field, append the following to the end. Replace **<HOST>** with the IP or hostname of the iSymphony server.
37		-
38		-{{code}}
39		-&<HOST>/255.255.255.255
40		-{{/code}}
41		-)))
42		-1. Ensure that all the **read **and **write** permissions are checked.
43		-1. Save and select** Apply Config.**
44		-
45		-=== **Remote Vanilla PBX Server** ===
46		-
47		-{{info}}
48		-Only perform these steps if your remote PBX is **not **based on FreePBX.
49		-{{/info}}
50		-
51		-1. On the remote server, open the file **/etc/asterisk/manager.conf**.
52		-1. (((
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.
54		-
55		-{{code}}
56		-[isymphony]
57		- secret = mysecret
58		- deny=0.0.0.0/0.0.0.0
59		- permit=127.0.0.1/255.255.255.0
60		- permit=[ip of the iSymphony Server]/255.255.255.255
61		- read = all
62		- write = all
63		-{{/code}}
64		-)))
65		-1. Save the file.
66		-1. (((
67		-Reload the Asterisk manager using the following command.
68		-
69		-{{code language="bash"}}
70		-asterisk -rx "manager reload"
71		-{{/code}}
72		-)))
73		-
74		-== iSymphony Server Permit Entry ==
75		-
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**
85		-1. (((
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.
87		-
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>
102		-{{/code}}
103		-)))
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.
106		-
107		-= 3. Modify The PBX Connection Information =
108		-
109		-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.
110		-
111	111	=== Vanilla Asterisk ===
112	112
113	113	1. Open the file **/etc/asterisk/manager.conf** on the PBX.