I do not hate windows, I use it frequebtly, and it is adequate for the machine I use to access this forum. It is not even close to adequate to process my voice communications for mission critical uninterupted service. I do not use it for such.
I do not either hate call manager, but it will become adequate when Cisco migrates away from a windows baesd OS for voice processing. Cisco shares this opinion about the windows based voice processing, as they are changing away from the windows OS in the future. In their experience they have come to the same conclusion about this OS. So, I guess that Cisco hates the OS, because it has caused them to change the call manager to another OS due to its performance issues. The cost to Cisco would justify them hating the windows OS, personaly, I do not hate it as I do not use it for functions beryond its capabilities, or reliabilities. I like it, but I am not trying to use a stapler to drive a nail, which I equate to using windows OS for voice processing. It can do it, but it is not designed or equipped to do so on an ongoing, reliable, efficient, stable manner. I like my stapler, it staples. I like my hammer, it drives nails. I like my windows OS, it processes data. I like my voice services, they do not use windows OS.
Call manager is hindered by windows, that is an issue of windows, not call manager. When they get off windows OS, they will become an exponentialy better product for voice processing.
That will allow call manager to be judged in the same class as non-windows based voice processing. Until then, it is not an apples to apples comparison, due to performance, security, and stability issues with the OS.
"What good is a hybrid if the site links are flaky?" It can place calls via the telco to other sites. This is also true if the LAN is down or has issues. I understand the LAN is under the control of the company, do you consider the LAN as reliable as the hybrid off LAN infrastructure? If no, then we have some agreement, if yes, then I disagree with your assesment.