Lync 2013 XMPP federation set up is relatively easy – saying that on one deployment I was presented with the following error messages. The XMPP Translating Gateway Proxy failed to send a stanza to a remote server. Remote domain: gmail.com Detail: MS diagnostic code: 32020 The XMPP Translating Gateway Proxy encountered an error communicating with a remote server. Remote domain: gmail.com Direction: Outbound State: TCP_ConnectInProgress Category: Network Detail: SocketError, ConnectionRefused Diagnostic code:32020 Exception:- The XMPP Translating Gateway Proxy encountered an error communicating with a remote server. Remote domain: gmail.com Direction: Inbound State: STREAM_StreamOpened Category: Network Detail: SocketError, Success Diagnostic code:32019 Exception:- Solution Since there aren’t many moving parts in XMPP federation on its own, troubleshooting is (or as I want to say – ‘should be’) fairly straightforward. 1. XMPP enabled on the edge server / pool ? Select Edge server and pool in TB. If not enabled, Enable it in TB, publish topology, run ‘Setup or Remove Lync Server Components’. 2. Federation route set up in topology ? Select Site in TB. If not, Enable it in TB, Publish topology. 3. Check if federation is enabled on the edge servers – Get-CsAccessEdgeConfiguration. Else run Set-CsAccessEdgeConfiguration -AllowFederatedUsers $true 4. Public DNS SRV record of _xmpp-server._tcp.<sipdomain> created ? 5. Is the above SRV record pointing to the 1. Access Edge FQDN ? 2. or a separate fqdn (for e.g. xmpp.) ? If separate, then a public DNS A record for the same should point to Access Edge public IP. 6. Does the access edge certificate have 1. [...]
The post Troubleshooting Lync 2013 XMPP federation appeared first on UnifiedMe.