The robo-voice problem appears to be a bug in either skype or router or modem firmware, and is definitely not a caused by poor bandwidth, OS bugs, or hardware failure. I have not tried creating a new profile, nor updating to the latest version of skype. Pass the -C option to turn on CPU display mode. From the above output it is clear that I have total 8 core in my system from cpu0 to cpu7 and you can see stats easily.
other reporters of this issue have claimed that creating a new profile solves the problem. Sample outputs: Fig.01: How to find the usage of Individual cpu core usage on FreeBSD Unix system. after a short (2 second) pause, the robotic/garbled voice goes away for another 53 minutes. Click the 'Show additional plans' option to expand the list. If you dont see this option, click 'Hardware and Sound' and then select 'Power Options'. my workaround has always been to put the call on hold. Open the Control Panel and select 'Power Options'. i recently switched to a laptop, and it is now occurring after 20 minutes. But, 10.8 Mountain Lion was probably the most stable for the recent ones. I think that once MacOS became free, the quality went down hill.
I think 10.6 Snow Leopard was probably the most stable OSX, it was my favorite.
it occurs on multiple machines on mac osx with skype 2.8. I think this is the model that bought used 5 years ago, then upgraded the RAM, and gave to my parents to use. After all, without some very intentional. While some users reported that Skype is slow in macOS Mojave, others say Skype causes high CPU usage. Probably the most useful tool to check and kill processes is called Terminal, which is an application that provides access to the lower levels of the Mac OS X operating system and files. for me, the robotic voice occurs after exactly 53 minutes and 17 seconds, every time. It typically comes down to either too much stress on the CPU or a hard drive reading issue. For macOS Mojave users, there seems to be a few issues. I also have this problem, and have had it for years. when using skype on other networks with other routers, i do not have the error. I have confirmed that this issue occurs on a single router/modem combination only.