I know, it has been a while something about FusionPBX RPM. Today, I have published in OKay's RPM repository RPMs for FusionPBX 4.4.0. FusionPBX is an open source FreeSWITCH GUI. FusionPBX can be used as a high available, single or domain based multi-tenant PBX, carrier-grade switch, call centre server, fax server, VoIP server, voicemail server, conference server, voice application server, appliance framework and more. FreeSWITCH is a highly scalable, multi-threaded, multi-platform communication platform. FusionPBX license is the MPL 1.1 license.
This is a vanilla FusionPBX some patches from my own, mainly to be able to run correctly the load-balanced cluster mode and to fix the class-based XML CDR importer. This RPM will install MySQL (for CentOS 6) or MariaDB (for Centos 7) as the database backend, all possible information will be stored there, such as dial plans, profile information, registrations and so on.
If you were wondering what is new in 4.4, I have found the following in a 15-minutes quick look:
I believe there are more. As I said, is a 15 minutes review.
As a premium add-on, installation using this RPM includes the LCR and Billing for FusionPBX in-app. You just need to activate it and start configuring. Please note that the Billing application is still not 100% compatible with FusionPBX 4.4.x.
RPM's are available for Centos 6 and 7. And you can find it if you type yum search fusionpbx.
By the way, I know FusioPBX 4.4 has been released. I will publish the RPM's soon.
One of the biggest problems I have seen with Joomla is that the well-known administrator is public. You may protect it with some .htaccess configuration (I will publish some of that later), but the problem is that since most Joomla websites are hosted and residential Internet providers give you dynamic IP, protecting by IP is useless.
On the bright side, remember when you are installing Joomla, the super admin username is not any more admin. You can select a different one, which it makes really difficult to guess it. However, there is still the thread of the DoS, many failed attempts may run out of resources your Web server, and this is why we need fail2ban.
Usually, this should not be a big deal, but since ISPConfig takes over many configurations it is important to take note of this. ISPConfig 3 will not log anything in the common log places (a.k.a /var/log/httpd), instead, it will store the logs related to your website into the /var/www/yourwebsite/logs/ directory. Because of that, using the classic fail2ban Joomla plugin will not work for a whole server; it could work if you are only interested on protecting one website and you hardcode the log path name.
Whatever it is your reason, sometimes you need to change things on how the components output your information in Joomla. The easiest way is doing a hack into the code, however easy is not always the correct way. Hacking the code (doing changes to the PHP files) is not upgrade safe, the next time Joomla publishes an update, your changes are gone for good.
You could do this with a template override as well, but modification would be tied to the template. Since the template I am not using doesn't override the com_content component, I did the call to do it this way.