I keep getting a critical error on login that indicates the commercial module voicemail reports is expired. Why? I know I have not renewed it as I don’t need it right now, but I have a valid license. It is annoying,. If I remove the error message it comes back after I login a few times. I therefore have removed voicemail reports from my Debian Freepbx system, thinking that might be the issue, but it reappears none the less.
I have other similar ‘expired’ commercial modules that I have not renewed that do not give this error.
If you’re not using it and the error is from updates I would just remove the module from the system. It won’t try to update and won’t error. Again if I am understanding this correctly the checks in framework that make this alert probably just need an if statement to say in not installed continue.
Anyone have an idea how to do this? Tech Suppoort emailed:
"I received an update from our team. The maintenance alert is coming from the portal. Even if you uninstall the module, you will continue to receive the alert because it is triggered by the portal and cannot be disabled or stopped from the PBX.
You have to remove the voicemail report module in the portal for your deployment to avoid the alert message."
I don’t see a way to do so? I emailed back but have not yet received a response.
Curious as to why I need to remove this commercial module since it has a 25-year license.
Also, interesting why no other 25-year commercial modules are complaining, just Voicemail Reports.
Voicecmail Reports has been removed from the pbx for many days now.
I did add a technical work around but it is untested and frankly may break things. I would say put in a feature request to allow disabling of “nag” messages. From a business standpoint it is an awful ideal they want you getting those but that is the best route.
Thx. Seems like it would be an easy code fix for them. I am not sure why it only impacts Voicemail Reports so far, for us anyway. We have been running this way for years, and this annoyance only started recently, and several weeks after migrating to Debian.
Seems like maybe a bug was introduced recently on perhaps the code that James showed.
I hate to say it but based on this email from tech support this morning, nickzed’s analysis at Why are you bugging me for a module I am not even using? - #9 by nickzed feels correct. I have expired maintenance for commercial licenses I no longer want or need, I can disable or remove these commercial modules from the pbx, but have no way to remove them from the portal, and no way to suppress the “critical warning” so it does sound like their plan is that we have to live with getting nagged to death or else renew something we no longer need or want. To me, this seems really a bad decision or ploy, to have no way to opt out of commercial licenses or suppress the “critical warnings” when commercial modules are no longer needed, regardless of the statement below that says “We are not recommending that you renew the maintenance; we simply want to clarify that the alert is expected behavior based on the current product design.”. In my opinion the security argument holds not water as I can remove the commercial modules from the system, just not the portal. Also in my opinion, this is ridiculous statement from their website linked below: “Besides the problematic security update issues outlined above, several forthcoming expanded commercial module license checks will (soon) show new Dashboard and other alerts — similar to these — and cause said commercial modules’ web interfaces to stop working after the grace period on systems for which valid licenses do not exist.” So if I want to keep a commercial license I MUST renew it.
I also think the even the Sangoma tech support not fully aware of this policy as it took many days of back and forth to get this reply. .Here is what I received this morning 07/07/2026 from tech support:
Hi,
I checked with my team and they confirmed that the maintenance alert cannot be disabled while the module’s maintenance has expired.
This functionality was introduced as part of a recent design change and is working as intended. Until the module maintenance is renewed, the alert will continue to be displayed and there is currently no option to suppress or disable it.
As discussed, you confirmed that you are not actively using this module. We are not recommending that you renew the maintenance; we simply want to clarify that the alert is expected behavior based on the current product design.
