I’m testing out the SNGDEB-PBX17-amd64-12-8-0-2503-1 version of the FreePBX 17 installation ISO. I didn’t need commercial modules so I selected the OSO spice. However, it appears System Admin, which is needed for managing the web certificate and some other settings, is a commercial module and doesn’t get installed. The web UI lets you select it but there were a few issues encountered:
sysadmin and firewall have cross dependencies (firewall won’t install without /usr/lib/sysadmin/includes.php, sysadmin won’t install without firewall).
commercial module repo isn’t included with OSO spice, which makes sense but then the Commercial option should be hidden from the web UI. Otherwise you get the “sysadmin RPM out of date” error since the sysadmin RPM can’t be updated.
All that’s to say, the sysadmin module should probably be included in all spice levels and/or not marked as commercial, since there are multiple config bits that need to be tweaked in System Admin.
For now, I’m going to rebuild with the FOG spice level - give that a try.
Yeah, I see what you’re saying. “OSO” means open-source-only.. not just “non-commercial”. Problem is that System Admin has some important settings under it, such as the web certificate, registration, etc. I know some of those can be done from the CLI, others aren’t well documented. I’m just saying, it needs to be considered.
Question, when you say Sysadmin was not included, do you mean you could not get to the registration, power off or networking functions (shown below), OR, you were able to register but you are looking for the more advanced functions ?
The basics of system admin are included, the advanced commercial version is extra.
This image is the standard “System Admin” However, this does NOT show up until after you register.
So, First Question is, did you have an active internet connection (plugged in) to FreePBX while you were installing ? In past versions if you did not have the internet hooked to FreePBX and intended to just plug in later, the installation would crash (not complete properly) and you would get results like you are talking about. And this :“System Admin” module would never appear because you could not properly register the install.
Correct.. Because I chose the OSO spice, the System Admin module was not installed. Thus none of the menus in your screen shot, indeed not even the “System Admin” menu option itself, were available. Further, I couldn’t install that one module due to the issues I listed.
I installed PUB v17 version (using SNGDEB BETA ISO) and PC had accessible Internet while installing FreePBX. System Admin does not show up in menu and I cannot have Firewall running because it requires System Admin. Also, to install System Admin it is required to have Firewall already installed.
So, I am in the same situation as sosherof although I did not use OSO install.
As he noticed there is something strange going on. Module is commercial but free, but not available, and we cannot get it, and without it FreePBX is seriously crippled.
Is there way to get that commercial but free module somehow?
Documentation says nothing about all of this. It just states that System Admin is standard module and that there is commercial PRO version.
Problem is that “OSO” means open-source-only and that’s probably important for some folks. The sysadmin module is not open-source so while it might be free, it doesn’t meet the OSO definition. Bit of a conundrum. Perhaps in a future version they can break up the sysadmin module into components that could be open-source and components that still aren’t.
Regardless, I’m surprised you didn’t get the sysadmin module with the PUB installation. I used FOG because I’m installing on a VM and don’t care about support for physical cards. Something else to note: I found the 30GB minimum disk to be insufficient, mostly because /var is pretty small but holds all the apt-get cache, which ate most of the space. I had to increase the drive and use the various tools (parted [which isn’t installed by default], pvresize and lvextend) to expand /var. The lack of space bit me when trying to restore CDR data from another server I’m replacing.
Honestly, PUB, FOG and OSO are all the same thing with slightly minor differences.
PUB is for when you’re using physical hardware such as FXS, FXO, T1, PRI, etc. in the system. This would mainly apply to on-premises systems.
FOG is the same as PUB but it doesn’t install the OS level drivers for physical hardware cards. It can apply to either cloud or on-premises systems.
OSO is the same as FOG. It can apply to either cloud or on-premises systems. It doesn’t install commercial modules such as System Admin.
If people are getting the Firewall module installed during an OSO installation there’s a bug in the install script. It’s installing the Firewall module because it’s AGPLv3+ but it requires a commercial module to even be used. The OSO install should in no way install OSS modules that have a dependency on commercial modules.
Thanks but you are not answering my question just repeating what I already know.
So I have to conclude, the only way to get Firewall (although it is OpenSource module) is to buy Sangoma device with FreePBX on board.
Without Firewall, FreePBX is crippled and unsafe to use as vulnerable to attacks and hacking.
I am not against licensing, but before paying I want to see if configuration I want to have can work reliably. Without Firewall I am not keen to make FreePBX exposed to public Internet and without public access I cannot test configuration.
As I understand it, all you need to do is to agree to the terms of a free of charge commercial licence.
Also, the actual firewall is part of Linux; sysadmin provides means to configure it, but you can configure it using the Linux tools. (The “smart” part of the firewall, will be part of FreePBX, but the real time filtering is pure Linux.)
By selecting OSO, you are saying you want a configuration which is 100% open source.
Open source software isn’t necessarily free of charge, and proprietary (the OS community prefers this word to “commercial”) software doesn’t always have to be paid for.
Note that my interest is Asterisk, and I haven’t run FreePBX, so this is based on my understanding of what has been posted, on this forum, in the past.
The sys admin is included with the PUB install.
During install, did you have the internet connected ? If not, in previous versions teh install fails if the internet was not connected during install.
After you installed, did you register the machine ? If not, then that menu above that i show does not appear until after you register the install.
As I recall, after I started installation it just went on itself for about half of hour and ended up with login prompt. Do I have to go somewhere to register?
Yes, Machine had internet connection during install.
Ok, I am running installation from scratch to check whole procedure again.
The first time you log into the GUI, it has a pop up asking if you want to activate . (in addition to the 6 pop up for other things)
Nothing really works till you activate it. This is the screen you will see. Once you activate it, then you get the full menu above.
