We are experiencing the same problem. It appears that the m100 software is setting up the call with NAT appropriately and the responding video unit is replaying to appropriate NAT address, however the media ports specified under Call Settings are not listening on the local system. You can verify this by doing a "netstat -an" and searching for the default ports 3230-3237. So the returning traffic is dropped and you cannot see any video or hear any audio for the far side, but they can see and hear you.
If you disable the NAT and make a call, you can see the host is listening on the appropriate media ports. It's clearly a bug in the software in relation to NAT and media ports.
I can confirm the observation made by Sevendoh.
When NAT is disabled MediaProcessor.exe correctly listens on the 3230-3237 after establishing a call:
enabling NAT causes MediaProcessor.exe to listen to some random UDP ports after establishing a call: .
Not only that no video is getting through but also the CPU rises to 100%.
If official support is required please check how to phone or open a case here----------------
Thank you but I'm still trialling the software.
have you found a solution ?
No, unfortunately I didn't find a solution.
Maybe the problem has been solved in the latest version 1.0.5.
Please report back if you have tested the latest version.
I have tried the latest version and still no changes. I was hoping Polycom could provide us with a checklist for this problem or instructions regarding the ports...
In my case, this version fixed video but I still have Audio problem,