All HA for PBX based on open source?

Features, capabilities, and information about HAAst
User avatar
CRM User
Posts: 116
Joined: Sun Nov 27, 2016 3:41 pm

All HA for PBX based on open source?

Postby CRM User » Mon Mar 12, 2018 1:12 pm

I'm researching HA products for our PBX. We run an Asterisk PBX with approx. 300 active calls at any time. We use a config generator (but only to create our config files, nothing else).

One of the vendors mentioned that every HA for Asterisk on the market uses the same open source packages: DRBD + Corosync +Pacemaker, so they're all the same.

Are you just selling me the stuff as everyone else?
Account for questions transferred from CRM system
User avatar
Telium Support
Posts: 152
Joined: Sun Nov 27, 2016 3:27 pm

Re: All HA for PBX based on open source?

Postby Telium Support » Mon Mar 12, 2018 1:22 pm

No - that's not correct. While every other HA solution on the market is comprised of essentially the same open source packages, HAAst is not - it's written from top to bottom in C++ by Telium. Here's why:

Heartbeat & Health: The generic heartbeat/health package (Pacemaker) does not take into account latency variations between peers (which may be normal), health of Asterisk, external factors such as trunk & route availability, available file handles, available memory, etc. Pacemaker is a very simple package with dead/alive detection of the box/process (not Asterisk performance aware). HAAst has its own proprietary heartbeat and health detection, written exclusively to monitor and detect Asterisk PBX's and their environments. HAAst can detect route status, trunk status, switch health, etc.

Synchronization: DRBD (or other shared disk solutions like NFS/Samba/iSCSI) all put your data at risk since file corruption by one failing peer immediately corrupts the other peer. With those open source solutions a failing process on one peer may destroy your entire cluster (the same goes for Corosync). As well, network loss during updates may leave your files/databases in invalid states. HAAst synchronizes data between peers, but only if the peers are healthy. As well, HAAst synchronizes databases (MySQL/PostgreSQL) at the SQL transaction level, so you are never left with a database with corrupt tables (and a PBX that won't start).

Reliability & Security: Open source packages may troll logs looking for failure which is slow and unreliable, or monitoring nothing more than a PID that exists (which could be days before the software realizes the process is dead). HAAst is written entirely in C++ so it's FAST, with < 1 second detection and failover trigger. HAAst has an encrypted link between peers so there is no risk of Man In The Middle attack, and no risk of hackers gaining control of the PBX. (Open source products have well published and unencrypted protocols that are easy to tap in to, and are overly simplistic).

Performance: The bottom line is how do these HA solutions perform in real life. Have a look at to see customers say about the performance of various solutions.

All of the open source packages are wonderful products in their own right, each with a specific purpose. If you spend enough time adding your own code on top of these then you can make a simple cluster. After 10 years of continuous development we have created a very sophisticated product which can detect and recover gracefully from an enormous number of failure scenarios, building our own heartbeat/synchronization/health detection/etc tailored to telephony environments.

So unlike other HA 'solutions', HAAst is not a collection of open source packages relabeled as an HA product.