I was just helping with the particular example you gave. I will let Sangoma answer with their official position on this.
Yeah we have no issues with sysadmin.
Sangoma started doing that over ten years ago:
New this year is the forbidden license grace period and subsequent GUI disablement of the affected module. So this gives you time to do things like upgrade to a new major version via new ISO installation – which contains new module versions that you otherwise might not be able to access – then get your accounting ducks in a row once technically satisfied. But the Happy Path is to keep current and always update your renewal maintenance plan before your software. ![]()
That is expected behavior.
@daveellison this should be resolved now in the stable versions of sysadmin module 16.0.50.7 and 17.0.3.7 - please update and advise on the same.