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.
Thats only true to a point, as they keep pushing commercial options for it, your county/city/state/countries consumer law may apply.
Here we have a fit for purpose regulation, if you sell me something with a 12 months warranty, if a reasonable person would expect it to last longer, like 3 years, they can be compelled to repair/replace under that “expired” warranty at no cost to the purchaser. Not exactly apples for apples, but you know your consumer laws better.
Corporations like to hide behind statements like sangomas because most people are oblivious to their rights.
Where is “here”, the US? Because there is no federalized version of that, it would be state by state and in many states the addition of “No implied warranties” or “Sold as is” nullify the Fit for Purpose Regulation. As well the burden is on buyer to show it didn’t last.
However, when it comes to software that’s a different ball game. Implied warranties, i.e. fit for purpose, don’t apply to software as software is considered licensed not sold. Even in the rare cases it might be an issue the commercial EULA as wording as such “AS IS” and “No implied warranties”.
So yes, you should be aware of those laws such as in Michigan properly done disclaimers are always upheld (I’m also from Michigan). So Sangoma is most likely protected from fit for purpose.
Also, what @michiganbroadband is telling their customers has nothing to do with Sangoma’s actual warranties or agreements. It’s generic fluff to help calm the natives.
In the UK, at least, consumer protection only applies to humans buying in a personal capacity. Businesses are expected to be able to take into account the impact of warranty disclaimers.