01-25-2013 03:00 PM
We have an SSID that is fairly locked down for BYOD, and are having issues getting Google Hangouts to work properly...we just get timeout errors on the devices.
We move the device (a Nexus 7 is our test device) to an unrestriced WIFI network, and it works fine. I have opened up the ports in the ACL as required by Google below, but no dice...anyone have run into this?
According to Google:
Hangouts are adapative in the ways they attempt to establish a network connection between a participant on your network and the Google conference servers.
The connection methods are attempted in this preferenced order:
UDP connection from the participant to Google on ports 19305 through 19309
TCP connection from the participant to Google on ports 19305 through 19309
TCP connection from the participant to Google on port 80
TCP connection from the participant to Google on port 443 (SSL)
The ideal connection for a user to make to a hangout is through UDP. To allow this connection attempt to succeed you will need to allow connections into your network from UDP ports 19305 through 19309.
At a minimum, your corporate network must allow access to the Internet on TCP ports 80 and 443 in order for hangouts to work.
Consult the documentation from your firewall vendor if you need information about opening UDP and TCP ports.
All traffic back to the client from our conference servers will originate from the same port that the client is sending to, and be directed back to the port that the client is sending from.
The UDP traffic consists of STUN, RTP, and RTCP packets, with SRTP encrypted data payloads.
We are unable to provide any specific IP addresses for our conference servers, but the IP ranges of Google services can be found at any given time by running the following command:
nslookup -q=TXT _netblocks.google.com 220.127.116.11
01-25-2013 05:37 PM
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base