Telium Support Group

HAAst includes approximately 18 “internal sensors” which are used to determine if the PBX and it’s environment are within normal parameters, and allow the PBX to properly offer telephony services. These sensors are used to assess whether or not the node can keep operating or must demote and let the peer take over. This is a binary decision (yes/no) determined by HAAst. This assessment and determination are made behind the scenes, and have nothing to do with the sensors graph in the GUI.

Aside from the internal sensors, HAAst also has the ability to monitor optional “external sensors”. These sensor are defined by you (the administrator) and can sense just about anything. For example, clients have used external sensors to measure:

1. Performance of a network path: Counting pings lost from source IP to destination IP. This can be used to measure route quality, or even something as simple as sense an unplugged network cable.
2. Calls in progress: Some large call centers never have less than X calls per second coming in from their carrier. If this drops to 0 it might mean an upstream carrier issue, 800 number failure, etc.
3. Data center environmental temperature: If the data center room temperature exceeds X degrees HAAst can initiate a fail over.
4. Custom: Anything from a contact closure (big red fail over button), to a local CRM systems being down, to power supply voltages out of range, etc.

Each of the above sensors turns an input value (number/string/etc) into a numeric value, which adds to the health score. That health score is what you see on the GUI’s sensors graph as show below. If the score reaches a danger threshold set by you (the administrator), HAAst can automatically run scripts or take some other action. And if that score reaches the fail over threshold, then HAAst will transfer control to the peer.

You can define as many or as few sensors as your like, and weight their scores as you like, to create a health scoring system meaningful to your environment. Similarly, you can set the critical and fail over thresholds to suit your needs.

Telium would be pleased to assist you in designing and setting up sensors. As well, we would be happy to create custom sensors to gather input from any device/service you wish (as a professional services project). We have interfaced with serial devices, thermostats, 1-wire networks, Bluetooth devices, and more.

Please remember that external sensors are completely optional and need to be tailored to your unique environment. Many clients run without any additional (external) sensors.

• This reply was modified 4 years, 11 months ago by WebMaster.

HAAst uses “activation”, exactly as Microsoft Windows does. If you change your network card in Windows then Windows will operate in non-activated mode. You have to reactivate your Windows installation with Microsoft by phone or online in order to reactivate your license. Like Windows, HAAst detects the change and switches back to the Free Edition. Once you reactivate it returns to the commercial edition.

We face the same problem as Microsoft or any other software vendor: piracy. So unfortunately activation is necessary. But, we are looking at an online licensing system so that you can move your license around (so long as your PBX has an internet connection). Many emergency call centers will not allow a dependence on the internet to permit their systems to operate, so for them we will always offer an activation license file.

Please ensure you only activate HAAst once your hardware platform is finalized (this includes virtualized hardware). Most customers won’t need to reactivate an installation unless something fails (which might happen every few years, and we’re happy to reactive for you). If you need to reactivate every few months then you are doing something wrong!

The unlimited edition of HAAst does not impose any limit on number of simultaneous calls. From a practical standpoint HAAst is limited only by the capacity of your hardware, and the design of Asterisk.

We have HAast “PBX” deployments with over 14500 phone sets, 3500+ simultaneous calls, 800 call setups per minute, etc. HAAst operates perfectly in those environments. We also have HAast “gateway” deployments (i.e. HAast is bridging calls and offering services, but is part of a larger telephony service) with tens of thousands of simultaneous calls.

Properly sizing your host to support a desired call volume is outside the scope/role of HAast. But you need to consider many factors like transcoding (CPU heavy), recording (I/O heavy), bridging/conferencing, etc. As well, placing Asterisk inside a container or virtual machine imposes other limits on CPU and IO availability. If Telium is provide a turnkey HA solution we assume responsibility for scaling the solution to meet your needs; however, in general Telium does not providing hardware scaling assistance.

For companies requiring HA for call volumes beyond what a single host/VM/container can support, we recommend running multiple clusters to achieve HA. To keep the clusters in sync we recommend adding our PBXsync product.

If you are at the point of sizing hardware for purchase, we recommend adding 5% to CPU capacity, and 500MB to memory capacity for HAast, above what is demanded by Asterisk. (Which in the overall scale of these systems is negligible).

As an additional note, you may wish to have a look at our LoDi product. It can act as an outbound proxy / LCR / and more. LoDi includes an HA option so it might be an easy way to achieve what you are looking for.

That message means that the source IP is known to be used by hackers and that the connection attempts are most likely hack attempts. However, the user is using valid credentials!

So if this blocking is correct then change the account name and secret for the account in question.

If you don’t want SecAst to block this IP address you can raise the threshold for hacker detection.

We don’t sell the LED lights directly, but we have partnered with a company called Cleware to provide them. You can purchase their LED lights here: http://www.cleware-shop.de/USB-Ampel-EN

We fully support the Cleware product, and can assist you in making the LED’s change color with our product state, etc. For example:

• HAAst: Red=Standby, Yellow=Transitioning, Green=Active peer
• SecAst: Red=Threat level high, Yellow=Threat level medium, Green=Threat level low
• LoDi: Red=>90% load, Yellow=>80% load, Green=

• This reply was modified 4 years, 11 months ago by WebMaster.

You are welcome to download the Free Edition of any of our products to experiment with the functionality, capabilities, etc., and to create a demonstration system. You can also post questions on these support forums for assistance (we respond on a best effort basis, at least once per week). All for free.

If you would like a trial license (which enables all features) and support during your installation process you would need to purchase a trial edition (priced at 50% of the Commercial Unlimited edition). In return we will help you get a complete functional demo up and running. As well, since there is no difference in the code base between the Free and Commercial Editions, your client can simply add a license file and turn the demonstration system into a production system. Will will also credit this amount towards the final sale if you decide to purchase the Commercial Unlimited edition.

Note: Trial licenses impose limitations to prevent the software from running indefinitely.

Yes HAAst lets you create a high availability fax cluster. HAAst will synchronize fax queues, logs, settings, etc. for Hylafax/Avantfax/iFax so one node can pickup exactly where the other left off. All fully integrated into Asterisk (so your fax extensions, trunks, etc. all move over automatically in case of failover). HAAst will also control other services, synchronizes other files/databases you need, etc.

In addition to detecting an managing failover in case of equipment failure, trunks failure, etc. HAAst can transition the cluster in case of regional power failure. HAAst can create a cluster across different data centers, on different continents! So if you’re worried about the fax service going down due to a power outage in one city, the other cluster node can resume service transparently in a data center in another city!

In the HAAst installation package you will see sample sync settings for various supported products, including Hylafax. After setting up your base Asterisk+Hylafax+HAAst software, just copy the sample hylafax settings file to the /etc/xdg/telium/haast.conf.d directory and that’s it!

(Full installation instructions for setting up HAAst can be found in the /docs directory of the package, and full installation instructions for settings up Hyalfax/iFax/Avantfax are available from the manufacturers).