When you live in multi-lingual countries such as Canada, there are some laws that enforce multiple language support. Therefore, it is very common you have in the same tenant people who prefers one language over the other. Well, you are not alone, this is not the first time I get asked about this.
Today was a very productive day. For those who don't know, I have coded a DNS plugin that works with PowerDNS that allows FusionPBX (and FreeSWITCH of course) to run in load balanced mode. This will allow in a PBX network to have many servers across the globe and your customers will connect to them depending on some network metrics. I should say that this approach doesn't need any SIP proxy servers in front of VoIP the servers (many people use Kamailio for this). The magic happens in the VoIP servers. They know where to bridge the call and all the logic happens within the FreeSWITCH, which it is very cool if you ask me.
The big difference about my software against others is that the network decision is based on the actual network metrics (traceroutes, pings) and not just a geolocalization like most part of load balancing services such as Amazon WS DNS service.
The new release I am working on is the 1.2.3. Among the bug fixing I have been doing, it has NAPTR record support. Some IP phones such as Polycom needs NAPTR records in order to know what SRV records it should use.
Another cool capability that was requested from a customer of mine is the ability to do server groups. Grouping is very useful, for example, all servers in the same datacenter should belong to the same group. With this, all metrics shouldn't be done as metric for server A would be almost the same for server B if they are in the same location. This was though to get around of data centers that have blocked the traffic, such as Azure where you can not do traceroutes or pings.
If you want to read more about this plugin, you can visit the official PowerDNS Add-on page for High Availability and Load Balancing page.
This is something that happened this weekend. A customer of mine asked a way to save money when someone calls to a DID that is already hosted in the PBX. Currently, in any FusionPBX default installation, when you dial a number it is already hosted in your PBX it will go through your carrier and come back causing you unnecessary costs.
So, there should be a way to avoid this PSTN trip and route the call internally, even if it is inter-tenant. Please note that this is a capability I will include in the LCR for FusionPBX 2 (also know as pseud-enum support), but he couldn't wait, so here is a way to manually work around it.