Doesn’t “run fine for me” Same response as before from CLI
Can you explain how the hosting provider may be better able to assist me with a Sangoma “free” module updating?
And my experience going back to FreePBX 15, is that it is not “still possible” to have EPM on a FreePBX (Cyberlynk) Host deployment without costs or annual fees. Perhaps you would care to clarify exactly what you believe is “still possible”? Clarification would be much appreciated.
Ticket submitted to CyberLynk:
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. to 16.0.92 or later (16.0.95)
I have discussed the issue with a Sangoma Rep and he has stated that Cyberlynk provides a “free” full license for the EPM, and to contact Cyberlynk to resolve the issue. But we do not need a “free” full license as we use only Digium phones. We only need the FREE version of EPM that is available for Digium and Sangoma phones. Further, our deployment indicates that we are on the Sangoma (FreePBX) “Free” version for Digium and Sangoma phones. We have tried a force upgrade from the CLI but the response is “endpoint is the same version as the online version, unable to upgrade.” I can provide screenshots of any relevant settings that you my need to troubleshoot and resolve this issue.
————-
I will post the response here.
It is “still possible” to install open source FreePBX. But EPM is commercial and has been around for ten years or more.
And MY point was that EPM has always been “free” for users of Digium phones, and prior to Sangoma’s acquisition of FreePBX and Digium, was a one-time purchase for the “full” version and not a stealth subscription. No offense Penguin, but you replies are a bit disingenuous and clearly not helpful for resolving this issue.
Here is the reply from CyberLynk:
———————————————–
”You’ll need to open a ticket with Sangoma and provide your deployment ID and request to have your EPM license downgraded to the free version of EPM if you want to avoid paying the annual maintenance fee. If you open a billing ticket via https://portal.sangoma.com they will typically handle this pretty quickly for you.
Let us know if you need anything else.
Thank you,”
_______________________________________
EXCEPT as I have previously pointed out, the deployment is ALREADY “downgraded” to the “free” version, but will not upgrade to EPM 16.0.92 or later, and remains on a vulnerable version. Here is a screenshot again of the current deployment:
“Always” is such a long time! 
…so, not “always” “free”, although, that change was seven years ago.
A few years before that, was this:
…and yes there were some changes around that time ten years ago:
…but back a couple years before that, when the module was launched, maybe (IDK) then it was:
…however, was it even the same thing as it is now, or, do the twelve years of updates and improvements mean that it is something different (?) from when it was launched:
…and many of those quotes still seem applicable, despite the growth and change in what we call EPM to what it is now:
Either way, it looks like your D70 phones were EOL’d almost a decade ago, but props for keeping them going – hopefully on an extremely isolated network – and props to the Sangoma phone engineering team for making that possible as well as continuing to put out great replacements like the P-Series phones):
Maybe then it is time to open the support ticket with Sangoma that CyberLynk suggested and DM us the ticket number 
And as usual your disingenuous replies miss several points. In the 1st place, much of what you point out occurred AFTER these facilities were already using FreePBX, well before Sangoma aquired FreePBX or Digium, and no notifications were directly sent to end users to my knowledge. What you describe as “improvements” were in many cases simply Sangoma attempting to monetize what was previously provided without cost. The fact that the Digium phones are “EOL” is actually irrelevant to this discussion. It was Sangoma that discontinued the Digium phones after acquiring Digium, including the newer models deployed at my other client offices - this is simply the oldest (a call center). Again self serving on Sangoma’s part to sell their own phones.
In any event, who should I DM the ticket number for the Sangoma support ticket? And BTW, that IS NOT what you suggested previously. I certainly understand now why to are not exactly well liked here 
and why Sangoma appears to be dragging down both FreePBX and Digium (Asterisk) reputation.
Was that before 2018 when Sangoma first made EPM available for free to users of Digium phones ?
Asked Duck Duck Go AI for help on this one:
What does end of life mean in product management ?
End of life (EOL) in product management refers to the stage when a product is officially retired from the market, meaning it is no longer sold or supported by the manufacturer. This phase can occur due to various reasons, such as technological advancements, changes in consumer demand, or the product no longer being profitable.
Still learning 
You might want to DM your account rep and @mwhite.
Agreed! As more information was provided beyond your OP, the response was customized to your unique situation, which is, to wit, trying to run EOL’d phones with the latest version of the FreePBX endpoint module software on a hosting provider that already offers you a different pinned version of said software but the license purchase does not fit into your budget at this time. (Please clarify if this is incorrect.)
AGAIN, the phone model, EOL or otherwise, is not relevant to the issue. The model is STILL supported in EPM. Please explain how you find the model, EOL or otherwise, relevant to THIS issue ??? What business upgrades hundreds or even dozens of phones just because the manufacturer decides to EOL them ???
And AGAIN, this deployment has NEVER used or needed any “pinned” version of EPM, and the host was in fact listed in the earlier comments. Further, as listed in earlier comments, the deployment was NOT on any “pinned” version, but on the free version. Screenshots were provided. That was not new information.
So again, your comments are both irrelevant to the issue and disingenuous.
Further response from CyberLynk:
Thank you for that update. Unfortunately, Sangoma owns and operates the development and licensing of FreePBX and its respective modules. We merely provide the hosting infrastructure of the pre-loaded FreePBX Virtual Private Servers. Anything related to licensing and module development is beyond our control. I am a bit confiused on what Sangoma would have told you the problem on our end would be. This seems like a pretty cut and dry case. You provisioned a FreePBX VPS in our datacenter that came preloaded with the Commercial License of EPM. Not needing the “paid” commercial version of EPM, you must have opened a ticket with Sangoma to have them downgrade it. You now cannot update EPM due to this downgrade that Sangoma initiated and pushed through.
This is something completely out of our control as this is in regards to Sangoma’s licensing model and how modules can be updated/upgraded due to said licensing. I would check back in your Sangoma ticket history and reference the ticket that you opened with them to downgrade EPM to the free version. Then push back on them and state that something is clearly wrong with what they did when they downgraded you, as you are no longer able to update the module to the current stable “free” version.”
Re-reading this comment of yours from earlier:
So what then is different now ? How/when were you updating this for free before ? Your current version 16.0.86.11 is almost two years old.
There’s got to be some out there… 
But how then this – where you quoted CyberLynk:
Again, you are in a unique situation. Did you ask for (and receive) a customized free downgrade ? And now you want a customized free upgrade ?
Please provide the output of fwconsole setting MODULE_REPO and consider posting your modules list in pastebin.freepbx.org
WTF? “Customized” free downgrade? And we just want the “downgrade” we are currently provisioned for to UPDATE!!!
Why is that so hard for you to understand? Willful ignorance?
Opening a ticket to request a downgrade for your specific system is very much a custom activity. Is that what happened ?
1 Like
So let me understand your reasoning: anything involving a support ticket is now a “custom activity”? And AGAIN, how is that even relevant to the issue at hand. If in fact a “downgrade” was requested at some point in the distant past, that should have nothing to do with why upgrades of the “free” version of EPM, which the deployment is clearly currently on, should suddenly stop and EPM v 16xxx not be available.
Your replies are with all DUE respect, irrelevant and at times nonsensical.
Did you ask for and receive a downgrade ?
It matters because you might be at a fixed previous version, or limited range of versions IDK, due to your custom request. Not being able to upgrade to newer versions after requesting to stay frozen at an earlier version could be a feature not a bug.
Can you help me understand what you are thinking?
That IS NOT how the “downgrade” is explained by CyberLynk. Reverting from CyberLynk’s installed version, which BTW to my knowledge did not even include a subscription ID in Admin, should not have resulted in some sort of “freeze.” And as I have pointed out, updates have been working without issue UNTIL EPM 16xx, so that would not explain your version “freeze” hypothesis. And I fail to see how reverting from the “paid” version to the “free” version that is supplied with the FreePBX Distro, is some sort of “custom” modification that will break updates some arbitrary point in the future. And there was no request to stay frozen at an earlier version. As for when the “free” EPM module was last updated, that would have been determined by the GUI module updates, and there is no indication that any previous updates failed before 16.xx, or that there in fact were any updates subsequent to 15xx from less than two years ago. According to the GUI, and the CLI, its up to date. That is very obviously a Sangoma issue, is that not correct?
As for some of your other apparently irrelevant comments, please help me understand the relevance to this issue and address the questions:
How is the model of the phone even remotely relevant to the issue here? The model is still supported in EPM.
The ”free” EPM module for Digium and Sangomas phones is still entitled to support from Sangoma, is it not?