SPLIT FROM => Here <=
We've encountered have the same issue. It's definitely only started happening with our hardware upgrade.
We deployed new HP EliteBook 8460p laptops and 8200 Elite SFF desktops, and we hear loud static every time a user makes a voice or video call over Communicator 2007 R2.
If we swap out the CX100 for a cheap speaker and microphone, the call quality is great. We try these same CX100s on older HP hardware generations running the same version of our SOE and the problem doesn't reoccur.
We found that the CX100 creates static when plugged into any USB port on the desktop, or any port on the laptop docking station. For laptop users, we found that they could plug it into the USB port on the left side of the 8460p and it works, but we have no solution for the desktops.
Could it be an IRQ conflict maybe? Are there any firmware or driver upgrades available for these devices? These things are out of warranty, but this should be solveable. I fear that we might get into a situation where Polycom say "talk to HP", and HP say "talk to Polycom".
welcome to the Polycom Community.
The CX100 is simply a hardware reference design that Polycom manufacturers based on Microsoft’s specs.
There is no software running on the phone that has been developed by Polycom.
This device rely totally on the PC OCS or LYNC Client in order to operate.
Any issues need to be investigated by Microsoft support teams as Polycom only has control over the physical hardware.
Microsoft support can be found at this link https://premier.microsoft.com/ or if you do not have an account or support contract with Microsoft they do offer support on a per issue basis at this link http://support.microsoft.com/
As you have already mentioned the Unit works perfectly if used with an older revision of HP's Hardware so therefore you may want to raise this as well with HP to work with Microsoft.
Polycom Global Services
For the record, the problem also exists with the 8100 Elite Small Form Factor PC.
We're going to log incidents with both HP and Microsoft. I'll post an update here if/when we get a solution.