R Series Application Brief
R Series Application Brief
R Series Application Brief
Application Summary
When high availability business communication
services are required, the R-Series appliances,
Asterisk and additional open-source tools can
be converged to create a completely redundant and mirrored clustered environment for
24x7 availability. What is high availability (HA)?
It can be defined as an approach to communications system design which emphasizes
service availability. In true HA systems, core
services are available at all times. For users of
business communications systems, this would
include key PBX services such as inbound and
outbound calling, voice mail, automated attendants, call queues and conferencing.
Deployment
The following diagram shows an R-Series
failover appliance managing PSTN connections to a pair of mirrored Asterisk Servers.
Server A is the primary sever while Server B is
a hot standby unit.
Components:
n
n
n
n
Preconditions:
This example uses the R850 appliance and digital
(T1) PSTN service
n Server A and Server B are running the software
configuration described below
n Server A is acting as the primary node
Asterisk is running on Server A
The R-Series unit has the T1(s) routed to
Server A
VoIP traffic is directed to an IP address bound
to Server A
n Server B is acting as a standby node for Server A
n
Trigger
Server A experiences a fatal software hardware
failure
General Flow
The host software on Server B detects that
Server A has left the cluster
n The host software on Server B instructs the
R-Series unit to direct the T1(s) to Server B
n The host software on Server B activates the
floating IP address locally
n The host software on Server B starts Asterisk
n Server A comes back online and rejoins the
cluster as a standby for Server B
n
Software Configuration
The software used for this method of automatic
failover includes Pacemaker, Corosync, and DRBD.
A brief description of each of these components is
listed below.
Pacemaker is a resource manager for clusters
(including clusters with just two nodes as outlined
in this example). The resource manager takes care
of starting and stopping services on the nodes
(computers) in the cluster. Think of Pacemaker as
the director it tells the other parts of the system
what to do.
www.clusterlabs.org
Digium Custom
Communications Solutions
Digium empowers users,
developers and integrators
to build custom telephony
solutions by offering a variety
of software, hardware, and
third-party components.
From basic voice applications
to sophisticated phone
systems, Digium makes it
possible for the world to
communicate at a fraction
of the cost of proprietary
solutions.
At the heart of these
offerings is Asterisk, the
powerful open source
telephony engine. Asterisk
is free software that turns
an ordinary computer
into a feature-rich voice
communications platform.
Its flexible architecture lets
you configure it as an IP PBX,
a voicemail server, IVR server,
VoIP gateway, call recorder,
automatic call distributor or
virtually any other voiceenabled application that you
can imagine.
Failure Detection
Pacemaker manages resources in a cluster.
A resource agent (RA) is a utility used by
Pacemaker to take care of the details of
managing a resource. For our purposes,
Pacemaker is managing resources in a twonode cluster. Pacemaker will be configured to
periodically poll the resource agent in charge
of the Asterisk process. One of the required
interfaces of a resource agent is to be able to
return the status of the resource.
The cluster messaging layer, Corosync, is in
charge of determining cluster membership. If it
loses contact with another node for any reason,
it will decide that it has failed and failover will
be initiated by notifying the R-Series appliance
to redirect the PSTN services.
www.drbd.org
Digium, Inc. 445 Jan Davis Drive NW, Huntsville, AL 35806, USA
Phone: +1 256-428-6000 Fax: +1 256-864-0464 www.digium.com
Copyright 2012 Digium, Inc. All rights reserved. Digium and Asterisk are registered trademarks of Digium, Inc.
All other trademarks are property of their respective owners. Version 1.0/6 August 2012