You can protect the Sipelia™ role against hardware failures by assigning standby servers to the role.
Before you begin
- Your SIP devices (intercoms, SIP phones, etc.) need to be able to connect to two SIP servers to get failover on Sipelia™. Verify with your manufacturer that your devices support that configuration type.
- You require a centralized SQL database.
- Install Sipelia™ Server on a main and at least one expansion server to use as a standby server for the Sipelia™ role.
- The Sipelia™ servers need access to a shared database and a shared network drive.
- RabbitMQ should be installed on a third server.
- From the Config Tool home page, open the Plugins task.
- Select the Sipelia™ role () and click Resources.
- Under the Servers list, click Add an item () and select a server where Sipelia™ Server has been installed.
If you want the primary server to take control of the role after it is
restored, select the Force execution on highest priority
By default, the role remains on the secondary server after a failover occurs to minimize system disruptions.
Configure the Sipelia™ database to be
shared with both the primary and secondary servers.
The database is set up when you create the plugin role.
- Configure the recording folder of each server to point to the shared network drive.
You can register your SIP devices to the primary and the secondary SIP servers that you configured. See your manufacturer's user guide to get detailed information about your SIP device configuration.