Blueworx Voice Response version 7.11 achieves full redundancy with the introduction of redundancy for the Blueworx Resource Manager (BRM) component. It also introduces a new component, the Blueworx Admin Manager (BAM) for cluster management tasks.


BRM Redundancy


  • BRM was introduced in BVR for Linux 7.3 to enable a cluster of BVR machines to share configuration information and to provide centralized management and monitoring. This enabled BVR to become redundant; if one instance becomes unavailable, another instance can continue to take call using the configurations in BRM.
  • BRM itself can now be made redundant with a self-managing, self-healing architecture. Additional instances of BRM can be added to a cluster, and the BRMs will communicate and sync to provide a consistent and continuous service to all the BVR instances in the cluster. This means that should any BVR or BRM instance become unavailable, the cluster will continue to take calls without any intervention.

For further information see Redundancy


BAM Component


  • Cluster management tasks that are not critical to call handling have been divested from BRM into a new component called Blueworx Admin Manager (BAM). This increases the security and resilience of time-critical tasks for call handling, minimising the effect of external factors, such as runaway processes or DoS attacks.
  • Management and monitoring APIs used by the Web Admin Interface are now served by the BAM component.

For further information see BAM Operation