Optimize your network for Hangouts
We announced a new communications product, Hangouts, in May 2013. Hangouts will replace Google Talk and does not support XMPP.
Hangouts uses separate network connections for transport of media and control channel data. The control channel uses standard HTTPS to port 443. The media channel is adaptive in the ways it attempts to establish a connection between a participant on your network and the Google conference servers.
The media connection methods are attempted in this preferred order:
- A UDP connection from the participant to Google on ports 19302 through 19308
- A TCP connection from the participant to Google on ports 19305 through 19308
- A TCP connection from the participant to Google on port 443
The ideal connection for a user to make to a hangout is through UDP. To allow this connection attempt to succeed, you must allow routes from your network to UDP ports 19302 through 19308.
At a minimum, your corporate network must allow access to the Internet on TCP ports 80 and 443 in order for Hangouts to work.
- 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.
Additional ports for Google Talk
In addition, we recommend opening these additional TCP ports for the following clients:
|5222, 5223, 5224||XMPP clients|
|5228 and 5229||Android phones|