First of all, the comparison didn't last beyond one week because of what we found. Here are some highlights of our tests:
- Runaway process: We created a process which used almost 100% CPU. The FreePBX HA and Open Source solutions just sat there frozen or sluggish for an hour (until we manually rebooted them). Calls had choppy audio or didn't connect - just dropped. HAAst on the other hand immediately detected the problem and failed over to the other node.
- I/O Overload: We created a process simulating heavy disk IO. The FreePBX HA and Open Source solutions acted up, froze intermittently (and dropped calls), etc! HAAst on the other hand immediately detected the problem and failed over to the other node.
- Unplug the T1: FreePBX HA and Open Source didn't notice or care about the missing trunk; the first node just sat there not processing any calls! In contrast, HAAst detected the failure immediately and failed over. (By the way, HAAst could move the T1 trunk automatically, while the other 2 solutions required that we move a cable)
- Fail SIP provider access: FreePBX HA and Open Source didn't notice or care that the SIP provider was no longer reachable; the first node just sat there not processing any calls! Again, HAAst in contrast immediately detected the failure and failed over.
- Corrupt Asterisk: We corrupted the Asterisk process (overload the AMI socket), and FreePBX HA and Open Source didn't care, Asterisk just sat there brain dead, not bridging calls, but process alive. HAAst detected the Asterisk engine was misbehaving and failed over to the other node immediately.
- Corrupt the disk: We simply wrote "1"'s to a file taking up all space. FreePBX HA and Open Source didn't notice or care until the disk was full (Asterisk just started misbehaving), and they just sat there unable to process calls; briding didn't work, calls hungup on arrival, etc. When we manually failed over the FreePBX HA and Open Source clusters the other node would not start! The disk space problem was mirrored to the other node! HAAst not only detected the Asterisk failure, it failed over automatically, and it did NOT corrupt the other node, and did not fill the other disk with "1"'s.
I have posted the above on other sites where we compared products (one of them immediately took down my message by the way!!!). If you want details please email me [email removed] and I would be happy to share all of the test details and results.
One piece of advice Telium: get a marketing department! Why don't you advertise the difference between your products? The other guys have much better brochures, videos, and marketing stuff!