Out of the blue, we began experiencing the issue described at https://community.freepbx.org/t/sangoma-phones-require-a-weekly-reboot/71721 - phones would just start behaving like they had a process running away, consuming 100% of their CPU time. It only affected the s500 & s705 phones, which were both running the .72 firmware.
Seeing there was a fix in .78, I applied the latest revision - .82 as of this post. I immediately began receiving complaints of poor call quality. People sounded tinny, the first few seconds of the call were extremely quiet, customers saying they can’t hear us, etc.
I am about to go up and revert these phones to .79 or .78 to hopefully resolve the issues, but wanted to report it. Worst case, I’ll put .72 back on & they can live with rebooting their phones when it happens…
Is anyone else experiencing problems like this with .82 ? Is there a known easy way to trigger a reboot of the phone from the server command line? (My thought is to write something to interface with the phone’s GUI, but am hoping there’s a tool already available. If I could schedule the phones to reboot themselves say 2 hours before people get here, it should eliminate the issue with .72…)