Blueworx, a provider of Interactive Voice and Customer Experience solutions designed to deliver efficient, scalable, and reliable voice technologies, announces two new releases for Blueworx Voice Response for Linux. The new releases provide enhancements for both on-premise and Blueworx Cloud solutions with the same secure, rock-solid stability and unparalleled scalability expected from Blueworx Voice Response.
Dynamic Redundancy Quorum
With the release of Blueworx Voice Response for Linux 7.16, the Blueworx platform is able to support even higher availability thanks to Dynamic Redundancy Quorum.
Multiple instances of Blueworx Voice Response (BVR) and Blueworx Resource Manager (BRM) are preferable in situations where downtime must be kept to a minimum. Should any of the instances fail, another can take over its workload. Any BVR instance is already able to handle any call or any application thanks to BRM orchestrating the cluster. BRM provides BVR with the right configuration for handling the call. Because of its critical nature, we introduced redundancy support for BRM last year which allows another BRM instance to seamlessly take over the tasks of a BRM instance that becomes unavailable, providing a self-managing, self-healing cluster. However, this needed to be configured in advance.
With BVR for Linux 7.16, BRM instances can be added to and removed from a cluster while the cluster is actively taking calls in the same way as BVR instances, keeping downtime to a minimum. This means that all components responsible for taking calls are now completely disposable – instances can be created and removed as needed to update VMs or scale to different call patterns dynamically, with little configuration needed.
Blueworx Voice Response version 7.16 also includes improvements to failover handling when a BRM in a highly available cluster is shutdown along with updates to internal libraries for PCI compliance.
Enhanced SIP Proxy Support
Next, with the release of Blueworx Voice Response for Linux 7.17, you can choose a different SIP Trunk provider for each application rather than the whole system being tied to one vendor.
For example, you may find that while you’re happy with the SIP Trunk provider and SIP proxy for your domestic calls, your international applications would be more cost effective over a different SIP proxy. Or you may host two different IVRs on the same system, each with their own SIP proxy.
Active monitoring of each SIP proxy can be configured to provide an immediate failover should a SIP proxy become unavailable, increasing availability even further. Configuration of SIP proxy connections is now performed through the Blueworx Admin Manager (BAM) to isolate administrative tasks from the time-sensitive runtime tasks of BVR and BRM.
For further information on these new releases, please Contact Us.