Yes part of that problem was not a Sangoma issue, it was a RHEL issue. There are RHEL repos that the system pulls from now and they had an issue. If you review the RHEL
forums and other Google searches you’ll see a few weeks ago all sorts of RHEL users were having the same issue FreePBX users reported here.
Then that responsibility is a 100% on you. Your home phone service is managed and maintained by another entity (the provider) so if something goes wrong you can blame them. In this case if something goes wrong it’s on you. Sure you can point the blame back at Sangoma about this but if you’re so worried about rock solid performance than you should have a sandbox environment that you can make sure things like updates are solid and won’t mess up your PBX.
But let’s be real here, you can point to reports on this forum of people having issues with updates. In some cases those issues have been Sangoma’s doing or a third party (like RHEL in this recent issue) but a lot of these cases are non-Linux/non-Telephony guys updating their system and not understanding all the things that should be done in these cases.
So have there been updates that had errors or broken things and it was Sangoma’s fault? Yes.
Has every single update issue that has been reported on this forum Sangoma’s fault? No. By a large scale they are generally user generated issues.
Please just don’t “advise” people to not update their systems and gaslight them based on handfuls of reported issues when the user base is around 100’s of thousands. At the end of the day any software/appliance vendor out there would consider even a 1,000 users of a 500K user base having system update errors acceptable because it’s like .2%, hell I bet even half a percent is acceptable with those types of user bases.
Major vendors screw their users quite a lot with updates and those are generally the closed sourced vendors where you just can’t go in and issue a work around or the quick fix that a community member outlines. You’re stuck waiting for the vendor to fix their mistake and that generally takes a big backlash for that to happen quickly.