...

When you set up the first system, it automatically is configured with the Management and Primary SIP Router roles. The Primary SIP Router role includes the proxy and registry/redirect services needed for call routing, and some other services such as the one that writes the Call Detail Records.

To add a distributed system for redundant call routing, add the system on the Systems page, and install the sipXecs software on the second system. Enable the Secondary SIP Router role on the system.

See Installing from ISO CD

Managing Processes on the Master and Distributed Server

After installing a high-availability system all sipXecs processes can be managed from the Web UI for both the master and slave server. Login to the Web UI as admin and navigate to Diagnostics / Services.Image RemovedSystem / Servers.

Image Added

Click on master server or one of the listed slave servers to see running services. A picture similar with the one below will be displayed

Image Added

Processes on the distributed system can be monitored, stopped, started restarted or restarted.Image Removedreloaded.
When reload button is pressed, configuration is loaded without stopping/starting the service
Note: Not all services may support reload functionality

Image Added

Monitoring Phone Registrations in an HA-System

In an HA system, each phone chooses either the Primary or some Secondary system with which to register. The load sharing distribution by default is evenly distributed across all SIP Router systems, but can be changed by configuring the DNS server. As soon as a phone registers with any server, sipXecs replicates this registration data to all other SIP Routers. Using the management Web UI you can see what phones used which server (which helps you measure whether your DNS is set up correctly and whether the phones can connect to the servers equally). The example below shows three phones, a Polycom, Snom and Grandstream, where two use the Master as their primary registrar and one used the Slave.

Image RemovedImage Added