TIPS What functions or features are part of the IncrediblePBX module?

[Halea]

The title says it all. The story below is what prompted me to ask it (so you can skip it if you're not in the mood for reading).

I've been running a Debian 11 + IncrediblePBX-2022 Beta version for several months now as a test-bed (probably since right after Ward released it) and earlier today I noticed that something had changed on its GUI, although I couldn't tell what exactly until I went back and forth between a production system and the test system a couple of times.

The difference turned out to be mostly cosmetic (or so I guess, this is why I'm posting this message), as all the IncrediblePBX logos were replaced by FreePBX logos.

After some investigation, I figured out that our systems tech mistakenly disabled the "IncrediblePBX" module on that test system which is scheduled to be audited next week for commercial licensing of all installed software.
Our auditors expect us to produce proper licensing paperwork for every bit of software on our systems that use tags such as "commercial", "proprietary", etc.

Since our production level IncrediblePBX systems only use GPL modules, they usually pass those audits with very little fuss. But, on that one test system, somehow we forgot to disable the commercial modules (one from Sangoma and 3 from ClearlyIP) during the original install.

After discovering the issue our operations' tech called our system admin and he received instructions to get into the GUI and disable those modules. But apparently he got the impression that all ClearlyIP modules were commercial in essence, therefore without paying much attention to the corresponding license-type field he disabled all ClearlyIP modules, including "IncrediblePBX".

This was a couple of days ago. Since the test system is only used when we run specific test sessions we didn't notice anything until today when I wanted to do troubleshoot some upstream termination issues.
Then I started to wonder what else is part of that module.

 

[wardmundy]

Incredible PBX module replaces the artwork as you've noticed. It also changes the repos from FreePBX to ClearlyIP. Because of the differences in module signatures between the two repositories, this can generate all sorts of errors.

 

[ostridge]

changes the repos from FreePBX to ClearlyIP

which would perhaps explain why get a sig error on framework module? and so FreePBX Module Admin wants to reload it.

 

[Halea]

@ostridge : I was just about to post a follow up question to @wardmundy about the same.

Interestingly after enabling the IncrediblePBX module and rebooting the machine (so I should definitely be on the ClearlyIP repos and sigs), I wanted to update some modules, including the framework module at which time I hit that exact same issue.
On the GUI there is a red highlight and the signature status reads "Module has been tampered. Please redownload."
I am not sure if signature verification was turned off or not on this (test) system.
Edit: I just ran sig-fix and the red highlight is gone - as expected. But the underlying issue of signature mismatch is apparently still there. Just as a FYI

 

[wardmundy]

Just reinstall the module with the signature mismatch...

fwconsole ma downloadinstall framework

 

[wardmundy]

If that didn't fix it, check your repository setting:

mysql -u root -ppassw0rd asterisk -e "SELECT value from freepbx_settings where keyword='MODULE_REPO'"

If it doesn't point to ClearlyIP repository, do the following:

mysql -u root -ppassw0rd asterisk -e "UPDATE freepbx_settings SET value = 'https://mirror.clearlyip.com' where keyword = 'MODULE_REPO';"
rm /tmp/*
fwconsole ma upgradeall
fwconsole reload
/root/sig-fix
/root/sig-fix

HINT: Don't mess with the Incredible PBX Module.

 

[Halea]

Thank you Ward. Reinstalling the framework module worked well in my case.
The repository info command (and its fix) is a valuable tool to be kept in mind. It certainly went into my engineering notebook.

As a side note, when I started to look into this issue I noticed unusually large and a large number of files in the /tmp directory which seemed be related to the pbx. I even wondered if the machine wasn't hacked. The log files were quite hefty too. But after deleting the temp files and reinstalling the framework module and doing some basic housekeeping, everything is now ok.