One Way Federation when OCS is Fed Route

Recently I migrated few users from OCS 2007 to Lync 2010 and federation route is still OCS 2007. Now users in OCS 2007 can still chat with Federated partners. Users migrated to Lync 2010 have one way federation issue. Case:1 If user from my company starts IM conversation with Company X, user from Company X cannot reply and gets this error "When contacting your support team, reference error ID 504 (source ID 239) and message bounces after a short try. If user at Company X starts IM conversation with our users, both parties can reply each other and there is no issue. We disabled the Federation on Lync 2010 Edge server and no luck. At this point we cannot move the federation to Lync 2010 to check. The behavior is similar when tried with both office communicator client and Lync 2013 client. Any clue would be greatly apprec

March 2nd, 2014 2:24pm

Did you associate Lync Edge pool with Lync Front End pool?

Please check the following link to configure Pilot Stack to connect Legacy Edge Servers:

http://technet.microsoft.com/en-us/library/gg398413(v=ocs.14).aspx

Free Windows Admin Tool Kit Click here and download it now
March 4th, 2014 3:27am

Lisa-Thanks for your reply. The Site Federation Route Assignment and Associate Edge pool (for media components) is already configured as per the article. Port 5061 is open from OCS (BackCompat site) edge and Lync2010 FE server and from OCS FE to Lync2010 FE.
March 4th, 2014 6:05am

Lisa-Thanks for your reply. The Site Federation Route Assignment and Associate Edge pool (for media components) is already configured as per the article. Port 5061 is open from OCS (BackCompat site) edge and Lync2010 FE server and from OCS FE to Lync2010 FE.

Snooper Log from my federated partner:

03/04/2014|19:28:57.647 4778:1F04 INFO  :: Data Received -129.225.250.240:443 (To Local Address: 172.25.36.143:53908) 974 bytes:
03/04/2014|19:28:57.647 4778:1F04 INFO  :: SIP/2.0 504 Server time-out
ms-user-logon-data: RemoteUser
Authentication-Info: NTLM qop="auth", opaque="BCFDBD0D", srand="72B4FE67", snum="205", rspauth="01000000000000004c65687f8e0133e2", targetname="directorserver.federateddomain.com", realm="SIP Communications Service", version=4
From: "" <sip:user@federateddomain.com>;epid=c3fe3b05f6;tag=6347928f13
To: "My Name"<sip:myname@mydomain.com>;tag=d9461c2f74;epid=bd1085744e
Call-ID: daacedd718114db9a6c42ee577813179
CSeq: 1 INFO
Via: SIP/2.0/TLS 172.25.36.143:53908;received=172.31.93.91;ms-received-port=31996;ms-received-cid=1D512800
Content-Length: 0
ms-edge-proxy-message-trust: ms-source-type=DirectPartner;ms-ep-fqdn=EdgePool.federateddomain.com;ms-source-verified-user=verified;ms-source-network=federation
ms-diagnostics: 1034;reason="Previous hop federated peer did not report diagnostic information";Domain="mydomain.com";PeerServer="sip.ocs.mydomain.com";source="SIP.federateddomain.com"
03/04/2014|19:28:57.648 4778:1F04 INFO  :: End of Data Received -129.225.250.240:443 (To Local Address: 172.25.36.143:53908) 974 byte
Free Windows Admin Tool Kit Click here and download it now
March 4th, 2014 2:03pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics