Loadbalanced FusionPBX cluster scheme is considered an advanced active-active configuration. Both PBX servers act as a backup of each other, furthermore, they can process a call and interconnect between them.
This architecture has a high availability database cluster (DB1, DB2 and Arbitrator 1) while at least two nodes act as peers. Each peer shares the same information with the other PBX. In this example, PBX 1 and PBX 2 have access to the same information. An extension could register on any of them and could route a call.
When there is a failure, this architecture has enough resources to take over as follows:
When PBX 1 or Data Centre 1 fails, a DNS update should take place to forward the traffic to the active node.
There are some native DNS approaches that could make the server switch automatically (if the endpoint supports it) such as using the SRV and NAPTR records. There are other solutions such as OKay's PowerDNS add-on that not only update SRV records automatically but the A records as well. Because the switch happens on the user end, it requires that the endpoints and routers honour the DNS TTL. Some odd brands require a reboot to take the DNS update.
Since the recovery time of this clustering scheme is long comparing to others, this is ideal if you:
If you need any of these configurations in your own servers, please contact us. We will be more than happy to assist you.
However, OKay presents another affordable option. Just pay the rent of the servers and OKay will do the chosen configuration for free. All the servers must be under OKay's infrastructure to take advantage of this deal.