Sunday, January 27, 2013

Federation issues after upgrading Lync Server 2013 Edge server from 2010

I was recently asked by a colleague who upgraded an Edge server from Lync Server 2010 to 2013 similar to the way I outlined here:

Upgrading Edge server from Lync Server 2010 to Lync Server 2013

The upgrade went well but he noticed that depending on where he set the Next hop pool:


… users’ federation contacts in the other pool wouldn’t work.  To clarify what I mean, if he were to set the Next hop pool to the Lync Server 2013 pool, users on the Lync Server 2010 pool’s federated contacts would be shown as Presence Unknown and while their federated contacts can initiate messages to them, they cannot.  They also noticed that messages begin to work once the communication has started (their federated contact messages them).  This becomes the same for the Lync Server 2013 users when the Next hop pool is set to Lync Server 2010.  I originally did not have much time to look at this for him so he I let him use my account to post a question on the partner forums but after not getting anywhere with the response he received, I had a look at it and noticed that he forgotten to check the Enable SIP federation checkbox for the Site settings:


This is actually similar to another issue I blogged about in the past even though not exactly the same:

Federation no longer works after moving user to new Lync Server 2013 pool to Lync Server 2010 during coexistence

Once the Enable SIP federation checkbox was checked:


… federated contacts worked properly for all users regardless of whether the Next hop pool was configured to point to the Lync Server 2010 or 2013 pool.


Unknown said...

We are happy to read this information providing blog.
The great loss of files often causes a user to a sense of disappointment.
But for the ease of end users, Specialists launched an alternative for data corruption situations.
If a removal of data situation is occured, user need to know which tool or software program to utilize as a way to handle this case of personal information damage.
recover outlook

Jason Lee said...
This comment has been removed by the author.
Jason Lee said...

Does this happen when you delete the 2010 Edge and Add a 2013 edge rather than having both Edge servers co-exist?

I found this to be the case when i upgraded and swapped out Edge servers...from 2010 to 2013.

Anonymous said...

Question: If Lync 2013 pools deployed in multiple Lync sites, but only has one edge pool configured for federation, where do I need to set the Site Federation Route Assignment->enable federation setting? Should I set it on the site where the federated edge pool is located in or the site without the federated edge pool?