This same problem is back again on a completely different system which has no support contract
or commercial modules.
Has there been any progress on identifying what causes this or fixing it from happening.
Once again this is customer facing and I got a call from them.
It is very frustrating from that standpoint.
I like to take responsibility for these kinds of issues with my customers.
And I’m not sure how to take that responsibility in this case and explain to them why this happened.
”You’re using a “free” open source product and there are no warranties although may be true.
I do not feel it’s a good or proper answer to my customers.
The truth is: I have no idea why this is happening or how to assure it won’t keep happening is the answer I have to give them.
I’m doing my best.
Sorry.
V17, all fully up to date as of a few days ago.
17.0.2.36 Stable.
”updating activation” and rebooting did not fix this.
Only way I have found is to “deactivate” and activate again from scratch.
I was not paying really close attention but I think this may have also changed the deployment ID.
There have been no changes on the hardware whatsoever.
This just suddenly popped up a few days ago.
Same problem as before referenced in the previous post.
Showed “activation active/good with a date of 2030.
But also showed activation expired at the same time on the same page.
And on the dashboard.
Definitely a bug of sorts.
Verified all software was up to date including the OS.
And verified system time and date were correct. in Linux and CMOS/RTC.
So no problems there.
No updates available .
v17.0.2.39+ must be beta?
If this fixed it, this is great to hear that.
Thanks!
Verify that your deployment ID still shows up in portal.sangoma.com and that there are licenses still assigned to it. If not open a case. They will let you open cases and help you with licensing even if you have no support. Aslo go to the console and run ‘fwconsole sa update’. If an SysAdmin Activation Update doesn’t fix it.
Problem came right back after 4 days.
I will have to contact Sangoma support.
Last time this happened I saw NO problems in the portal or deployment.
I will have to try the “sa update” suggested.
But that is the same thing as updating the activation in the web ui no?
I also tried deactivating the deployment rebooting and re-activating and rebooting again. (said I only have one reactivation left when I did that).
Then it looked ok for a few days but problem came back.