- Category: Blog
Since release 3.6 of FusionPBX, it is possible to deploy a voice over ip solution on the cloud that satisfies next characteristics:
- Balancing: servers split the load among them depending on different network conditions;
- Cluster: servers knows their peers and they send sync information each other;
- High Availavbility: servers detech when a pear is down and they split the load amon them.
This solution works without Kamailio.
OKay services can help you to do this kind of deployments. We explain in detail.
In a scene like next:
- One FusionPBX server in Buffalo, EUA
- One FusionPBX server in London, UK
- One FusionPBX in Singapore, Singapore
- One DNS server in Los Ángeles, EUA
- One DNS server in Jacksonville, EUA
Servers share same data base and they sync their file system on regular basics.
By monitoring algorithms, clients are forwarded to the server whose latency is the lowest.
According to the example, users from Vancouver (Canada), Mexico City (Mexico) and Buenos Aires (Argentina) will be forwarded to the server in Búfalo; users from Roma (Italy) are connedted to the server in London (UK); users in Sidney (Australia) and Tokio (Japan) are forwarded to the server in Singapour (Singapour).
The best way to get this done is by using the Low Latency PowerDNS Add-on.
When a user calls another user connected in same server, the call happens as a single deployment server. When a user calls a remote user (logged into another server), FusionPBX detects a non-local user and makes a connection to target server.
In this example, a user in Vancouver calls a user in Tokio. The PBX in Buffalo makes conexion to server in Singapore.
High Availability in this kind of deployment happens when a FusionPBX server fails; users are forwarded in minutes to the second nearest server.
In this case, when server in London fails, user in Roma is forwarded to the server in Buffalo.
This effect is archived thanks to a monitoring and smart DNS integration.
Availability of voice servers is monitoring always. When there is a failure, DNS server are updated.blog comments powered by Disqus