Wiki source code of Combined PBX Installations

Last modified by michaely on 2021/09/09 20:55
Show last authors
1 {{layout}}
2 {{layout-section ac:type="two_equal"}}
3 {{layout-cell}}
4 iSymphony supports combining state from multiple PBX connections, in order to see and control Extensions, Queues, Conference Rooms, and Parking Lots across all the connected PBXs at once. This type of installation is more complicated than with a single PBX, and requires additional steps to set up.
5
6 = Before Beginning =
7
8 == Asterisk Setup ==
9
10 It is the responsibility of the Asterisk system administrator to set up bridge trunks between the Asterisk systems in order to allow transferring and originating of calls. iSymphony will assume that the bridge trunks are set up in such a way that the extension number used to dial a device is the same when originating from any of the Asterisk systems.
11 {{/layout-cell}}
12
13 {{layout-cell}}
14 {{panel title="On this page:"}}
15
16
17 {{toc maxLevel="2" indent="1"/}}
18 {{/panel}}
19 {{/layout-cell}}
20 {{/layout-section}}
21
22 {{layout-section ac:type="single"}}
23 {{layout-cell}}
24 == Licensing ==
25
26 Your iSymphony license will limit how many active PBX connections you can have at one time. For a combined PBX setup you will need a PBX connection on your license for each PBX you want iSymphony to connect to. See [[doc:PBX Connections]] for more information.
27
28 = Installation =
29
30 == Installation with FreePBX ==
31
32 By default, the iSymphony FreePBX module will remove any configuration from iSymphony that it does not know about. This ensures that when extensions, queues, etc. are removed from FreePBX, they will be removed from iSymphony as well. However, if multiple FreePBX installations are connected to the same installation of iSymphony, the FreePBX modules will "fight" with each other, and each module will remove the configuration that the the other modules have set up. To prevent this from happening,(% style="line-height: 1.4285715;" %) you need to login into FreePBX and navigate to **Admin->iSymphony V3** and uncheck **Clean Unknown Items** then **Save**. You will need to do this on each FreePBX-based system that will be added to iSymphony.
33
34 Once you have unchecked the **Clean Unknown Items** checkbox and saved, you can then proceed to the next steps.
35
36 {{info}}
37 The Clean Unknown Items option is only available in **iSymphony FreePBX Module 4.1.4 and above**.
38 {{/info}}
39
40 {{note}}
41 In a combined PBX system always **remember to uncheck Clean Unknown Items** before running Apply Config in FreePBX.
42 {{/note}}
43
44 == (% style="color: rgb(0,0,0);" %)Adding Local PBX Servers(%%) ==
45
46 If the PBX you are adding to the iSymphony installation is on the same machine as the iSymphony server, you simply need to setup the Server as you would normally. See [[doc:Asterisk Server (Vanilla) Installation]] or [[doc:FreePBX, Elastix and PBX in a Flash Installation]] for more information.
47
48 == Adding Remote PBX Servers ==
49
50 If the PBX you are adding to the combined installation is remote from the iSymphony server, you will need to follow the steps in the [[doc:Remote Installations]] section.
51
52 {{info}}
53 If you are using FreePBX, be sure to leave the **Server Name** field as **default **in **Admin->iSymphony V3** in FreePBX. This is covered in step 5 under **Modify The PBX Connection Information->Remote FreePBX Server** in the [[doc:Remote Installations]] document.
54 {{/info}}
55 {{/layout-cell}}
56 {{/layout-section}}
57 {{/layout}}

Search

Navigation

iSymphony