- Details
- Category: Technology
Today I had a request to enable transcoding in one PBX. For those who are not familiar, transcoding allows different legs to use its codec. You can think of transcoding as a translating service. Each codec is a different language and FreeSWITCH works as a translator. Using transcoding is good if you have some endpoints with very little bandwidth (using a cheap codec such as 729, SILK or, GSM saves bandwidth). However, you must know that transcoding is CPU-hungry, this means, the more you transcode the more CPU will be requested, and this may backfire in some scenarios.
Read more: Enabling the Transcoding in FreeSWITCH 1.6 (and FusionPBX)
- Details
- Category: Technology
FusionPBX is a WEB frontend for FreeSWITCH. It allows you to do many things almost out of the box (don't take it wrong, it still needs configuration but you save time). FusionPBX has an in-app architecture that allows it to add different functionalities. These in-app are usually in the Advanced menu.
I have already coded Billing for FusionPBX and RSVP for FusionPBX. I will share some of the know-how to do this. In this article, I will explain the anatomy of a basic in-app. This will help developers to do their applications.
- Details
- Category: Technology
Syncthing is a software that allows file synchronization. It is especially thorough for road warriors as it handles two endpoints behind a NAT through its relay server. However, if you are like me with more than 600 GB of data to have synced between your laptop and desktop, and you modify files frequently, you will find that syncthing needs a lot of CPU to work.
As I see it, syncing is a background task. I am not usually on both computers at the same time. So, as it is not a real-time critical task, it does not matter if files are not updated right away. I figured out a way to fix this issue. In short terms, the use of cpulimit. I have already written about how to limit the CPU use in general. I will explain how I did with syncthing, since in Mageia 6, syncthing is a service and systemd is used.
This approach can be used on any systemd service.
- Details
- Category: Technology
Usually running the nice command with the correct priority could be enough to put a process in a using cap. But, nice doesn't limit CPU use, it does only a prioritization of processes. This means the given process will run using all CPU's power if there is no other process (with higher niceness) requiring the CPU. This is not the best in some cases, I found the project Cpulimit which does put a CPU use cap based on the percentage.
- Details
- Category: Technology
Memcache has proven to be an excellent option not only for caching but sharing information. One of the best use case scenarios I can think of right away is with High Availability and Load Balancing. With HA and LB you don't have a certitude about what server is serving, sharing information with Memcache is the best way to have session information shared.
I will discuss here how to set it up using CentOS 6 and 7, this applies as well to new Alma/Rocky distributions. You might figure out the correct paths for your distribution.
