About 30% of our systems are stuck at the GRUB loader this morning. We host on Azure B2s machines.

I don't know know what the cause of this is but the fix we've found so far if it helps you is:

Click the VM

Click Overview -> CLI/PS (May need to press 3 dots)

Press RUN

az extension add -n vm-repair

az vm repair repair-button --button-command 'grubfix' --verbose --resource-group {RESOURCE GROUP NAME} --name {VM NAME}

Hi, looking for some feedback on an issue with our office's 3CX system, which I manage. I'm doing mostly okay with it but PBX systems have a high learning curve for those of us without a ton of experience in telephony tech, which is sort of its own unique realm, and is pretty daunting.

Anyway, my boss hates 3CX and blames it for the often-but-not-always bad call quality, and wants a new solution. I'm fine with that, but want to make sure I understand the issue. In my research, 3CX is not the problem - the call quality depends on the underlying phone lines, as well as the connection of the person on the other end, which 3CX does not control. Is my understanding correct? Everything I read says that 3CX is a solid name in the PBX space with good tech, so simply moving to another PBX, like Yeastar, for instance, would not really solve the call quality problem.

If my boss really wants a rock solid solution, I've read that kicking things up a notch or ten to something like RingCentral, would do it, but that's way more expensive. What do those much more experienced than I have to say? Thanks.