Using ClusterLabs Pacemaker with OpenSIPS

Summary In this article we examine how Pacemaker and Corosync might be used to supercharge OpenSIPS and build a highly available clustered solution. The focus is entirely on High Availability rather than any form of load sharing. This means we are looking for a way to have more than one server contactable on the same IP … Read more…

Clustering OpenSIPS for High Availability – Part 3

In this, part 3, we examine how a virtual IP address can be switched between two Linux servers to provide an active/standby failover and how this impacts on OpenSIPS. Part 2 investigated the implications for far-end NAT traversal of clustering two OpenSIPS servers and concluded that the best solution is the use of a virtual IP address. … Read more…

Clustering OpenSIPS for High Availability – Part 2

In this, part 2, we investigate the implications of using more than one IP address on an OpenSIPS server and how this impacts on far-end NAT traversal. We will also see how the use of a virtual IP address can overcome these problems when clustering two OpenSIPS servers. Part 1 reviewed why we might want … Read more…

Clustering OpenSIPS for High Availability – Part 1

Why cluster OpenSIPS? Unlike Asterisk, a typical OpenSIPS server is able to handle a very large number of simultaneous SIP calls. It is generally very reliable and will keep running for many months, or even years, with little or no attention. As a consequence, it is the preferred choice for many VoIP service providers who … Read more…