- Details
- Category: Technology
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 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 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 is very cool if you ask me.
Read more: Better suport for High Availability and Load Balancing for VoIP with PowerDNS
- Details
- Category: Technology
When you live in multi-lingual countries such as Canada, some laws enforce multiple language support. Therefore, it is very common you have in the same tenant people who prefer one language over the other. Well, you are not alone, this is not the first time I have been asked about this.
Read more: Setting a Language to a specific Extension in FusionPBX
- Details
- Category: Technology
In the VoIP world, many companies have started to offer you what they call hybrid PBX systems. In general terms, a hybrid system uses VoIP and PSTN (traditional telephony) at the same time. The strategy is not always important, some will suggest a fallback strategy others will suggest a least-cost route strategy. Whatever the strategy is, it is just a dial-plan configuration.
Read more: Routing Outgoing Calls through an ATA for Hybrid PBX Systems
- Details
- Category: Technology
Last week, one of my very best customers asked me to do a dial plan that forwards an incoming call to an external server. So far, that can be done with a bridge statement pointing to sofia/internal/xxxx@server>. But it was more complex than it seemed. The system administrator of the remote server claimed that no calls were arriving.
- Details
- Category: Technology
This is new to me. Since CentOS 7.3, there have been some security changes. Among those changes, is the use of the PrivateTmp flag in many services, and of course, Apache is one of them. For those who are more curious about what this flag means, here is the manual text:
PrivateTmp=
Takes a boolean argument. If true, sets up a new file system namespace for the executed processes and mounts private /tmp and /var/tmp directories inside it that is not shared by processes outside of the namespace. This is useful to secure access to temporary files of the process, but makes sharing between processes via /tmp or /var/tmp impossible. If this is enabled, all temporary files created by a service in these directories will be removed after the service is stopped. Defaults to false. It is possible to run two or more units within the same private /tmp and /var/tmp namespace by using the JoinsNamespaceOf= directive, see systemd.unit(5) for details. Note that using this setting will disconnect propagation of mounts from the service to the host (propagation in the opposite direction continues to work). This means that this setting may not be used for services which shall be able to install mount points in the main mount namespace.
I am going to explain an Issue I had with one of my customer's PBX.
Read more: PHP (or any other language) code fails to write in the /tmp Directory
