Plantronics + Polycom. Now together as Poly Logo

Problems in Wireless with Galaxy Tab 10.1

Occasional Contributor

Problems in Wireless with Galaxy Tab 10.1

When I connect any wireless network and am using the Polycom VBP5300 ST as gatekeeper external I can't receive video.

 

In statistics always get 100% loss of video, but I send video perfectly without loss

 

And if you use the same wireless network in the same Polycom VBP5300 ST as gatekeeper external registering from iPad2 I send and receive normal video without loss

 

I've tested it on more than 5 different wireless networks and always happens the same problem.

 

Has anyone seen this problem?

 

Thanks

Message 1 of 4
3 REPLIES 3
Polycom Employee & Moderator

Re: Problems in Wireless with Galaxy Tab 10.1

The issue you describe is most likely due to the fact that the Android version of the RPM App does not support h.460 firewall traversal and the iPad2 App does.  There is a new version of the App (v1.0.3) due out any day now that will support h.460.  Please check for the new version over the next few days in the Markeplace. 

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Glenn Davis

Polycom Global Services

If you find my post helpful, and it answers your question, please mark it as an "Accepted Solution" and feel free to give me Kudos.

Please also make sure to check the below link for more RPM information
http://support.polycom.com/PolycomService/support/us/support/video/realpresence_mobile/realpresence_mobile_overview.html
Message 2 of 4
Occasional Visitor

Re: Problems in Wireless with Galaxy Tab 10.1

I have the same problem with my Galaxy Tab and Version 1.0.3.

I can connect via a VBP 5300 to a RMX 7.2.2 and get Video and Audio on the RMX
but I can not recive Audio and Video on the Galaxy Tab!
Tested with WiFi and G3.
With G3 I am able to join a meeting room, with WiFi not.
Message 3 of 4
Occasional Visitor

Re: Problems in Wireless with Galaxy Tab 10.1

I had the same problems and it cleared up with the upgrade to 1.0.3 

Message 4 of 4