XMPP to Gmail: Unable to Use Presence and IM—the Problem Might Be Google Apps
If Office Communications Server users add Gmail.com federated users as contacts and are unable to exchange presence updates and instant message (IM) information, there’s a chance your domain is enabled for Google Talk. This can happen if users sign up for Google Apps. When a user signs up for Google Apps, it is automatically assumed that your domain will be used by Google Talk service and that requests for federation via XMPP will be denied. This article gives you the quick fix for this issue.
Author: Rob Pittfield
Publication date: December 2009
Product version: Office Communications Server 2007 R2 XMPP Gateway
If your users try to add Gmail.com federated users as contacts and are unable to exchange presence updates and instant message (IM) information, there’s a chance your domain could be enabled for Google Talk. This can happen if any of your users sign up for Google Apps. Whenever a user signs up for Google Apps, it is automatically assumed that your domain will be used by Google Talk service and that requests for federation via XMPP will be denied.
This issue can occur even if the validation to Gmail.com in the XMPP management console is successful. To find out if this is the problem, capture a network trace by using Network Monitor or Wireshark while you are reproducing the issue. When you open the network trace, filter it for TCP port 5269. In Wireshark, you would filter by typing tcp.port==5269 in the Filter field as shown in Figure 1.
When this field turns green, you know it’s typed correctly. Press Enter. The trace should then be filtered for XMPP related traffic. Because XMPP traffic is unencrypted, the traffic data can be examined. This enables you to look at the XMPP negotiation.
Here’s what happens in this scenario:
In the network trace, you’ll first see the standard TCP 3-way handshake as shown in Figure 2.
These three frames establish a TCP session with Gmail.com on TCP port 5269.
The Office Communications Server XMPP Gateway sends the following information to the Gmail.com XMPP server:
xmlns="jabber:server" xmlns:db="jabber:server:dialback" from="<your domain>"
to="gmail.com" id="123123123(this value varies)" version="1.0" xml:lang="en-US">
There will be a few other messages sent back and forth between the XMPP Gateway and the Gmail.com XMPP server, but those messages aren’t relevant to this issue.
Finally, the Gmail.com XMPP server returns a message stating that your domain is enabled for Google Apps with Google Talk service enabled. If you look at the last few packets that Gmail.com sends to your XMPP Gateway, you may notice the following error message:
streams"/><str:text xmlns:str="urn:ietf:params:xml:ns:xmpp-streams"><your domain>
is a Google Apps Domain with Talk service enabled.</str:text></stream:error>
If you do notice this message, it’s important to know if anyone in your organization happens to be using Google Apps, as that would block any type of federated communication with the Gmail.com XMPP servers. This is because they automatically enable Google Talk service for the addresses that sign up for it. You can find out by going to http://www.google.com/a/cpanel/domain/new and following the steps for administrators of your domain to disable Google Talk service if necessary.
If you’ve confirmed that your company is not using Google Apps or advertising itself as using Google Talk service and you’re still having trouble, please contact Microsoft Support Services for further assistance in troubleshooting your issue.
Visit the Office Communications Server main page at http://go.microsoft.com/fwlink/?LinkId=132607.
View the complete Office Communications Server documentation library at http://go.microsoft.com/fwlink/?LinkId=132106.
Follow tweets from the Office Communications Server team at http://go.microsoft.com/fwlink/?LinkId=167909.
Download all the Office Communications Server content as a Word document at http://go.microsoft.com/fwlink/?LinkId=133609.
Download all the Office Communications Server content as a compiled help file at http://go.microsoft.com/fwlink/?LinkId=160355. (Make sure you scroll down to the Additional Information section to download OCSDocumentation.chm.)