- Details
- Category: Technology
Everyone knows that CentOS only takes care of some specific core packages. All others, if you want to continue using RPMs, must be used from alternative Repositories. There are many alternatives:
- EPEL: you will find here many useful packages. Packages get updates for critical bugs.
- Remi: you will find here backports for the most useful packages.
- OKay: you will find here some specific packages for servers, audio, and video.
I especially make contributions to the OKay repository. So, if you want to use OKay follow these steps:
- Install the EPEL repository, you may try typing yum install epel-release. I think at least Centos/Rocky/Alma 7, 8 and 9 have it out of the box.
- Install the okay-release RPM. Type:
- Centos 6 on 32 bits: rpm -ivh http://repo.okay.com.mx/centos/6/i386/release/okay-release-1-3.el6.noarch.rpm?
- Centos 6 on 64 bits: rpm -ivh http://repo.okay.com.mx/centos/6/x86_64/release/okay-release-1-3.el6.noarch.rpm?
- Centos 7 on 64 bits: rpm -ivh http://repo.okay.com.mx/centos/7/x86_64/release/okay-release-1-3.el7.noarch.rpm?
- Centos/Rocky/Alma 8 on 64 bits: rpm -ivh http://repo.okay.com.mx/centos/8/x86_64/release/okay-release-1-3.el8.noarch.rpm?
- Centos/Rocky/Alma 9 on 64 bits: rpm -ivh http://repo.okay.com.mx/centos/9/x86_64/release/okay-release-1-3.el9.noarch.rpm?
I will post later as I publish some updates or packages.
Soon I will stop updating the CentOS 6 repository.
UPDATE: I have stopped doing RPMS for CentOS 6.
- Details
- Category: Technology
f you are looking forward to having an IP Telephony business at some point you will get into the economics of the business. After all, it is a business and if you don't profit, there is no sense to do it.
When you are looking for your termination trunks (termination, in this case, is for outgoing calls from the point of view of your PBX), the idea here is to get the best carrier (if you are going to select only one) with the overall best rate.
- Details
- Category: Technology
I have written before about the different types of FusionPBX clusters. The first one is the one with the load-balanced approach, in which it implements the active-active scheme but the fault tolerance relies on the ability of the endpoints to jump to the second-best node. The second one is the one with the high availability approach, this is active-passive but the fault tolerance relies on the server end, and the endpoints do not realize any cluster existence. I have also said that each approach does not exclude the other, in other words, you can have a cluster combining the two techniques.
Read more: The Ultimate PBX Cluster Overview: Load Balancing + High Availability
- Details
- Category: Technology
If you are looking for a cluster, but you have a low budget, there is another cluster schema you can have. It is what I call all the eggs in the same nest. This approach is not load-balanced and is far from a high-availability one. It is more a fault tolerance one, which means you still have some downtime but you can recover very easily.
So, just to be clear. This approach I will write about is not load-balanced, nor high-availability.
- Details
- Category: Technology
So you are very happy with your VoIP service and suddenly from nothing, your telephone starts ringing repeatedly and no one is on the other side. This is what we call a "Ghost Call". In this article, I will explain why they happen and what we can do to prevent (or at least have less of them).
Read more: What are VoIP Ghost Calls and How to Prevent Them
