Repo for commercial modules not available

We set up an CentOS 7 server to use FreePBX with commercial modules, after initial setup and testing also with purchased modules. The dependencies can’t be compiled for Debian Linux, so we need to “failover” to CentOS.

Howto for that combination in FreePBX-Docs:


One of the configured repositories failed (Unknown),
Cannot find a valid baseurl for repo: schmooze-commercial/7/x86_64

We are aware we’re on our own, we wan’t to use CentOS instead of the Distro because of the stability of the OS.

It seems like an availability problem of the Repo or - a wrong topic in the Documentation?

As our ISP offers own SIP-packages with similar hardware and possibilities we could either use FreePBX’es commercial modules or a similar priced package from our ISP.

The Distro is derived from CentOS. They are essentially the same. The reason it is not and cannot be centos is because of trademarks. The packages, patches, updates are all virtually identical. There is no stability advantage for using straight centos. There is only more work because you are doing things manually.

That’s another reason why we wanted own solutions with opensource software on top instead of pre-made distros.
Without actually doing it you don’t quite get how something works.
The Distro is a thing you switch on, configure like you want and then it hopefully does the work, but you haven’t learned how to actually build DAHDI when the kernel version mismatches with the required version - or (in our far future) how to get caller data out of FreePBX / Asterisk CLI’s for customer management software to show the right things.
We need a project in which we learn things instead of a “configure and go” variant…

Can’t we use recent CenOS versions with commercial modules while not on the Distro? According to a comment we have to switch to older CentOS which may or may already have exploits sometime - and can’t patch them using a newer OS.

At this time we do not support manual commercial modules on centos 7

In the article you linked to it says

Commercial modules are only officially supported on the FreePBX Distro. Any FreePBX system with FreePBX 2.10 or greater, CentOS/RH/SL/EL 6.x and php 5.3 should work with most commercial modules

as long as the repo does not provide Sysadmin (which seems to be a dependency for nearly all commercial modules) - it doesn’t work with any module - at least in CentOS, even if we are on our own when using custom installations.
This probably lets users who want to have own solutions rather tend to AsteriskNOW or Digium Switchvox Solutions.

As previously stated. Commercial modules work on centos 6.6 only at the time. They can be installed using our guides manually without using the freepbx distro. So I could download centos 6.6 install it on a vm then follow the install guides on our wiki to enable the commercial repository. At this time we do not have a similar guide for centos 7. The commercial modules are closed source so this wouldn’t help with anything in terms of open source modules.

Sysadmin is not a requirement for open source modules. Many people install freepbx on debian based systems daily. One who actively engages with us weekly.

Follow the guide for 6.6 and you will have what you want.

Otherwise use centos 7 with only open source modules (non commercial). The guide for adding the commercial modules to centos 7 will come in time.

1 Like

The exact reason we’re using RHEL7 is because of the Stability of the OS. However, please don’t forget that FreePBX is primarily an Open Source application. FreePBX Distro just gives us (the developers) a solid and stable foundation to build on.

If you want to use Debian (or Ubuntu, or Arch, or …) then we actively encourage it - we even write the wiki pages on it ourselves! Just that for the Commercial Modules, we need a solid, stable, base. That’s what FreePBX Distro (and SNG7) gives us.

1 Like

CentOS 6 (which the FreePBX Distro is based on) will be supported - especially for security updates - until Nov 2020 (CentOS Wiki).

1 Like