Combinded PBX Installations

Version 6.1 by michaely on 2021/09/09 18:01
Warning
For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

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.

Information

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. The iSymphony system 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.

Information

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 PBX Connections for more information.

On this page:

The [toc] macro is a standalone macro and it cannot be used inline. Click on this message for details.
 

Extra Steps For FreePBX Based Phone Systems

Since more than one iSymphony FreePBX module will be contributing configuration to the same Core Server instance on the iSymphony server, we need to ensure that one FreePBX module instance will not overwrite or remove configuration objects that another FreePBX module instance added. To do this 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 base system that will be configured in iSymphony.

Warning

At the moment the iSymphony FreePBX module, that is provided via the FreePBX repositories, does not include the Clean Unknown Items option. To get this options you need to install the beta iSymphony FreePBX module found in the Downloads Archive under iSymphony Development Builds. The module can be uploaded via Admin->Module Admin in FreePBX. Note that you should not upgrade the module after the beta version is installed as it will remove the Clean Unknown Items option and the module will start removing and overwriting configuration objects for other PBXs in iSymphony.

NOTE: If you are utilizing FreePBX 12 or higher the beta module will cause an unsigned module warning to appear in FreePBX. This warning will have no ill effect on the server.

Adding Local PBX Servers

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 Asterisk Server (Vanilla) Installation or FreePBX, Elastix and PBX in a Flash Installation for more information.

Adding Remote PBX Servers

If the FreePBX server that you are adding to the combined installation is remote from the iSymphony server, you will need to follow the steps in the Remote Installations section.

Information

Make sure to leave the Server Name filed 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 Remote Installations  document.