This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Remove From My Forums

Lync 2013/S4B - question regarding federated partner after pool failover

Question
0

Sign in to vote

We have a SIP Federation with our parent entity and with our Lab. Before executing a pool failover to a different DataCenter pool in the same Lync Site, (but different AD site), I changed the federation route to our second Edge DR Edge Pool as well as the next hop for both Front End Pools. After doing this, the Lab Federation broke, and was fixed once I rebooted the lab edge server and worked fine after that. The Federated Partner was not able to reboot their edge server, but did try restarting all Lync Services. The SIP trace from our DR Edge Server:

Direction: outgoing;source="local";destination="external edge"
Peer: sipfed.parentcompnay.com:56095
Message-Type: response
Start-Line: SIP/2.0 504 Server time-out
From: "john doe"<sip:john.doe@parentcopmany.com>;tag=1464d95945;epid=4b001ccd66
To: <sip:me@mycompany.com>;tag=6296

Question: Assuming that the partner would have had to restart their Edge Server to fix this like in our lab, is there anything to try short of that? We can't expect for them to reboot their Edge Server if we fail over to our DR site.

Monday, May 20, 2019 4:06 PM

All replies

0

Sign in to vote

Hi Brandon74,

According to your description, the settings for the federations should be configured right, such as certificate、the SRV record(_sipfederationTLS._tcp.yourdomain.com) and etc.

For your issue, it seems this is the cache issue. I suggest you could also try to refresh DNS in the Edge Server after you change the federation route. If it takes no effect, it seems you need to restart the Lync services or restart Edge Server in your environment.
Best Regards,
Evan Jiang

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

Tuesday, May 21, 2019 5:25 AM
0

Sign in to vote

The DNS name for our address of our Edge External IP address is configured in their SIP federation settings. sip.domain.com resolves to both of our Edge Pools.

FlushDNS and restarting the Lync Services didn't work. Rebooting is a bit extreme and I was hoping to avoid asking our partner to do that if someone knows a trick...

Tuesday, May 21, 2019 1:41 PM
0

Sign in to vote
Hi Brandon74,

As you could fix this issue by rebooting the server, this issue is more related to the cache files in the server.

According to your description, FlushDNS and restarting Lync Services did not work, we could not find anything others need to flush/restart with the information above.

For this issue, could you also try to check whether there're any Event errors in the Edge server when this issue occurs. In addition, as we could not find the cause from the trace you provided, could you please provide more about the trace in the forum. Note: if you provide the trace in our forum, please hide the information such as IP address、domain and etc.
Best Regards,
Evan Jiang

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
- Proposed as answer by woshixiaobai Monday, May 27, 2019 6:44 AM
Friday, May 24, 2019 6:47 AM
0

Sign in to vote

Hi Brandon74,

Is there any update for this issue? If the reply is helpful to you, please try to mark it as an answer, it will help others who have the similar issue.
Best Regards,
Evan Jiang

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

Tuesday, May 28, 2019 2:22 AM