How do I allow my internal XMPP client or server to connect to the Talk service?

We announced a new communications product, Hangouts, in May 2013. Hangouts will replace Google Talk and does not support XMPP.

Please note: The information below should be used only to assist in firewall configuration, not for connecting to the Google Talk service.

The Google Talk service supports both XMPP client-to-server connectivity and XMPP server-to-server connectivity. If your organization has a firewall that restricts the traffic to or from the Internet, you'll need to configure it to allow connectivity with the Google Talk service. We recommend that you don't restrict the incoming IP addresses to your federation service and instead rely on existing federation authentication mechanisms.

To allow XMPP client connectivity to the Google Talk service, you must:

  • Allow your XMPP clients to connect to all IP addresses contained in the IP blocks listed in Google's ASN of 15169, on TCP port 5222.

To allow full voice and video interoperability with the Google Talk service, you must:

  • Allow your XMPP clients to connect to all IP addresses contained in the IP blocks listed in Google's ASN of 15169, on:
    • UDP ports 4893, 19295, and 19302
    • or
    • TCP port 19294

To allow your XMPP server to establish XMPP server-to-server federation with the Google Talk service, you must:

  • Allow your XMPP server to connect to all IP addresses contained in the IP blocks listed in Google's ASN of 15169, on TCP port 5269.
  • Allow your XMPP server to accept incoming connections from all IP addresses contained in the IP blocks listed in Google's ASN of 15169, on the XMPP federation port published in your SRV record.

The set of IP addresses that the ASN contains will change over time. If you have a firewall that requires updating whenever IP addresses are added, you may want to use a BGP monitoring tool that can notify you of any changes or use a BGP lookup tool.