Hi all,

The customer I'm currently working with has a Lync 2010 RTM environment and IM's from external domains fail (according to the sender as a failed message appears) however the IM is actually received EXACTLY 10 minutes later. Sometimes sending IMs externally works, but more often does not. Sending IMs internally there are no issues. I can initiate Lync video conferences with an external domain however they randomly end. The Free/Busy information works fine and an external domain can see my status change instantly.

I've checked the DNS SRV records for Dymantec Federation and they are present, port 5061 is open and the SIP address is present in the SAN certificate. I haven't confirmed whether the Dynamic Federation configuration is correct yet. I'm going to enable Message Queueing Routing feature on the Edge server Monday.

My initial questions are:

1. Has anyone come across this issue before?
2. Is this fixed in an CU release?
3. What further troubleshooting can I complete?

I can provide the logs from Snooper if that helps? I've noticed that the session from the external domain is received almost instantly in the Snooper log however it's another 10 minutes in the log analysis until there seems to be another session which is when the IM is actually displayed in my IM window.

Thanks in advance.

Hi,

From your description above, would you please tell us have you installed any update for Lync Server 2010?

If you haven't installed any update for Lync Server 2010, please firstly install the latest version of update for Lync Server 2010 (including the Edge Server).

Please double check if there is any network issue between Edge Server and FE Server.

Please check if the issue only happen for only one federated domain or for multiple domains, please also check if the issue happen when the users of your corporation external the corporation make IM/Video with the Lync users in the internal network.

Please check if there is any error message in the Event Viewer on both Edge Server and FE Server as well.

Best Regards

There were many many issues at RTM that were resolved, and while I haven't tracked all of them, I'd urge you to start by getting to the most recent updates.  It's likely that this is resolved if nothing else is getting in the way.  Remember when updating that it's not as simple as performing a patch, you need to run the database updates as well.

The most recent update (as of me typing this) and the install-csdatabase commands you'll need to run are here: https://support.microsoft.com/en-us/kb/2493736

If after patching, it's still not looking like it's resolved, I'd run snooper and watch SIPStack.  See if you can see if the delay is the SIP INVITE hitting the edge, or it being passed on further.