High Availability for Asterisk [CC Module]
Transparently continue calls and conferences in progress
»
callrecovery
Voice & Video Survives Failover
All calls and conferences in progress will survive a cluster failover so users can continue their conversations without taking any action. If Asterisk is configured to use direct media, then all conversations are unaware that a failover has taken place since there is no interruption or delay to media (voice/video). If Asterisk is not configured to use direct media, then users experience a brief silence as failover takes place and then media resumes. WebRTC clients also transition to the new Asterisk server without noticing any change. HAast-CC will seamlessly transition SIP, RTP, SRTP, DTLS, TLS, and more so that sessions move transparently.
Resume Entire Dialplan & State
HAast-CC doesn't just continue calls and conferences, it actually restores the position in the dialplan of all connected endpoints. If callers were interacting with an IVR, then HAast-CC will place them back into the same position in the IVR (and all variables will be restored to their previous values). Media playback will resume from the previous position (+/- 2 seconds), ACD queues will be rebuilt placing callers back into their previous positions, etc.
Initiate Custom Dialplan Actions
HAast-CC can integrate with your dialplan to perform various actions upon cluster failover such as initiating (local) calls into the dialplan, triggering HAast events (and launching scripts), and more. HAast-CC can readily integrate with dialplans from most popular configuration generators (e.g. Isabell®, FreePBX® / PBIAF® / Thirdlane® / more) for simple customization from the GUI.
Automatically Synchronize State Information
HAast-CC stores all state and call information in a MySQL database. This database is synchronized between cluster nodes using HAast's built-in synchronization engine. Failover of the cluster will cause HAast-CC to resume exactly where the previous node left off, +/- seconds.
Standard SIP Phone Compatibility
HAast-CC performs all of its actions on the server side, meaning that the interface to the endpoints uses standard SIP. There is no need for any special features in the SIP phones, in fact the phones won't even realize that a failover has taken place. All user-visible phone features will continue just like before failover including calls (active or on hold), voicemail indicators, BLF lights, central directories, etc. Administrators have the option of adding HA status information to the phone screens (for certain Cisco and Polycom models), so that select users can monitor HAast status from the phone screen / menu.