MobicentsHADemo < Communications < TWiki

TWiki . Communications . MobicentsHADemo

Call Fail Over Example:

NOTE: THIS DOCUMENT IS OUT OF DATE. IT APPLIES TO VERSIONS OF MOBICENTS PRIOR TO 1.0.GA. AS OF MOBICENTS 1.2 THERE IS A NEW HA DOCUMENT - http://groups.google.com/group/mobicents-public/web/mobicents-sip-balancer?hl=en


NOTE: There is an early access prototype of registrar failover. To try it see the ongoing discussion thread. It shows how once registered SIP clients can still call each other after a server failure.

This document outlines a scenario which demonstrates the High Availability of Mobicents.

Use Case

  1. Two instances of Mobicents running on different VMs and shared cluster
  2. Two SIP clients register with Server1
  3. Client A calls client B
  4. Client B answers. See Figure 1.
  5. Server1 crashes
  6. Server2 takes over transparently to both clients. See Figure 2.
  7. Call continues uninterrupted
  8. Client A hangs up to end the call
  9. The management interface of Server2 should be able to present the totall bill for the call.

Notes:

How to start the proxy with the front end HA Forwarder

The front end HA proxy is really a limited stateless proxy server. It maintains a registration table of active proxy servers which register with it. The first live proxy server on the list is the current "hot" proxy server and others are replicas. To start the load balancer

You will notice that the front end load balancer registers a proxy server in its list of live proxy servers. The port that the proxy server uses is not important. Messages are sent to the HA Forwarder and not directly to the proxy server.

Figure 1

hademo1

Figure 2

hademo2

Figure 3

hademo3

Related Reading

The University of Columbia published a good paper on High Availability, Failover and Load Sharing: Download in PDF Format

-- Main.ivelin - 03 Jul 2005

----- Revision r7 - 06 Dec 2007 - 03:34:14 - Main.ivelin