Polycom CMA Desktop 5.2.5.35726 causes broadband outtage

[Anonymous]

Hi community

Got a strange issue here.

I downloaded the Polycom CMA Desktop 5.2.5.35726 client for Windows 7 (64-bit) in order to join a video conference on a specific provisioning server.

After joining the specially set up room, the audio and video feeds work absolutely fine ... for about 40 to 60 seconds. Then, I lose my broadband connection. I mean it is completely dropped and the modem-router has to re-poll for about 90 seconds in order re-connect to the intenet.

My normal telephone works just fine throughout this episode. Something about the CMA software is causing my broadband connection to fail. I've tried installing the same software on a different laptop and get exactly the same problem.

The strange thing is that I can use Skype without problem, I can use our company video-conferencing tool (with audio) without problem (this uses Adobe Connect) and I can download big files, stream movies, and basically use the internet for everything else EXCEPT to video conference using the CMA software.

I'm on a modest 8Mb/s download broadband package (where I realistically get 6Mb/s download speed) and get just about 1Mb/s upload speed. I have tried reducing the network settings in CMAD to 'Basic Broadband' @ 192kbps max. call rate.

Has anyone else got this issue or experienced anything like it before?

Thanks for your thoughts on this.

Tim

[Anonymous]

Who is your broadband provider?

[Anonymous]

I'm with O2 (UK).

But I'm not having much joy with their technical support team. Although a BT Openreach engineer came out to fix an apparent 'line fault' which they say was causing a noisy line, I still get the same problem with CMA even after resetting the modem/router a number of times, using ethernet rather than wireless, etc.

O2 support say it must be a problem with the CMA software because all my other internet activities are fine.

I also tried uninstalling and reinstalling. And I have just uninstalled the latest version and installed the older July 2012 version to see if it was a version issue.