Running FreePBX 16.0.41.4 with Digium D70 phones. Generally these can only be configured with EPM, which is putatively “free” for use with Sangoma and Digium phones. However, I am now running into an issue with EPM on systems running only Digium phones:
endpoint (Cur v. 16.0.86.11) should be upgraded to v. 16.0.92 to fix security issues: GHSA-qgj3-f9gj-98v9, GHSA-292p-rj6h-54cp, GHSA-m42g-xg4c-5f3h
Except it won’t upgrade. Is there a solution to this conundrum?
Did you once buy an EPM license and is it expired? If yes, you would have to contact Sangoma and ask them to reset your EPM license status (free version).
These installs never purchased the EPM license. There was no need to - they all have Digium only phones, and have never used any other brand of phone. And the EPM module already states its the “free” version.
On my system the current version of EPM is 16.0.95. I just did the update and it went through without problems. Did you try again…with version 16.0.95?
I am just a regular user…
What does it say in the console, when you enter
fwconsole ma upgrade endpoint
And nothing but crickets from Sangoma. 
I try to put in a support ticket, but since this install is using the “free” version of EPM (because its all Digium phones) it appears we would have to pay for “support” to fix an issue with a version of EPM that is required by the Digium phones. Where is that Penguin guy when there is an actual issue? penguinpbx
Are you using the “free” version of EPM on FreePBX 16? Self hosted or cloud hosted?
I always install freePBX as a Virtualbox machine in Linux Mint, the hardware is an Intel NUC.
I have several freePBX 15 servers but also two freePBX16 machines. One of them has the paid version of EPM installed, the other the free version.
EDIT: I think there is a –force option, where you can define the upgrade version of the module. But of course, it has to be available.
Where are the pros? Hello?
Have you installed any Clearly** modules by any chance?
No “Clearly” modules installed. The FreePBX 16s are hosted on Sangoma’s anointed cloud hosting service (FreePBXhosting.com/Cyberlynk). All three were deployed over 5 years ago and have been upgraded through FreePBX16
As much as those facilities pay Sangoma monthly (SIP Station, CyberLynk - well north of $500/mo each) I would think that one of Sangoma’s “evangelists” that monitor this “community” would jump in and provide a solution. Using the ticketing system is more painful than pulling teeth.
As I said, I am just a regular user…but could it be that your system is already compromised?
Usually, if there is a security issue, the cloud-based systems are attacked first.
All three? I doubt it. And only the EPM module is at issue. I’ve even tried uninstalling and reinstalling EPM on one to no effect.
Did you start this topic on a Saturday afternoon and then made this comment on the following Monday ?
Thanks for the ping @Charles_Darwin 
Thank you for that information – have you seen the CyberLynk page Elevate Your Server Performance with FreePBX Modules – it is a little different than generic VPS solutions elsewhere:
With every VPS and Dedicated Server we include both the SysAdmin Pro and End Point Manager Modules for FREE. Once you have processed your order you can open a support ticket with Sangoma to receive your license keys.
Did you open a ticket with CyberLynk ?
We can definitely work together to help sort it out, but, the CyberLynk team really knows its stuff, so, you might find a lot of help is available from them directly.
You might try this:
$ fwconsole ma downloadinstall endpoint --tag 16.0.92
@penguinpbx, I have been using and installing FreePBX asterisk systems since around 2005 - a good 20 years and well before Sangoma acquired either - back when FreePBX actually meant FREE, as in no deployment costs or annual fees, and when the module licensing whether for 1 year or 25 was a one-time costs without any annual “maintenance” fees. I have been deploying on FreePBXhosting (Cyberlynk) cloud hosting since around 2016.
While FreePBXHosting advertises that it includes the full version of EPM, that appears to have ended with FreePBX 15. Nor apparently does that appear to include the annual “support” fee imposed since version 15 which is apparently required to obtain EPM updates. And if EPM does not update, modules that depend on EPM will also not update. I discovered this back around 2022 when upgrading an installation from FreePBX 14 to 15 that utilized EPM with Cisco phones and started getting the upgrade warnings. For that particular installation, which is still running FreePBX 14, I will try submitting a ticket to Sangoma for a license key. However, if upgrading will trigger the requirement for paying for annual “maintenance" fees, I’ll leave that installation on FreePBX 14. Certainly if the maintenance fee is required for FreePBXHosting, that should be explained in the Cyberlynk offering, as it does not take many years for the maintenance fee to exceed the cost of the original purchase. And existing hosted users should have been notified of the change instead of being ambushed when trying to upgrade from v14 to 15. Instead, I get the impression that Sangoma has in a rather sneaky way changed the module licensing from a one-time purchase to a subscription service, given that many modules are interdependent and now one module that is not “upgraded” breaks many other modules.
As for the current issue I have raised, this involves three hosted deployments running V16 on FreePBXHosting that only have Digium phones, and have had Digium phones for about a decade or so. EPM has upgraded on those deployments without issue until V 16.0.92, which is required because of a security issue with prior versions of EPM. That does not appear to be a CyberLynk issue. I will put a ticket in to Cyberlynk, detailing the issue as I have here, and explain that you asserted the issue was with CyberLynk. I’ll post their response here.
My apologies that was a typo from earlier mention in this topic – latest version on my test v16 is actually 16.0.95, not 16.0.92, so please try:
fwconsole ma downloadinstall endpoint --tag 16.0.95
…just tested and ran fine for me.
Exact year TBD, but, mostly, likewise 
That is still possible!
Not in the slightest – the only assertion is that they as your hosting provider may be able to better assist you with your issue.
