none
lync 2013 hybrid and more than one sip domain RRS feed

  • Question

  • Dear all,

    We have configured hybrid for lync 2013 server, the lync pool has 2 edges on different location.

    Location A - A.com (all federation to external parties)

    Location B - B.com

    Online user from A.com can chat and see presence of onprem user in A.com

    Online user from A.com CANNOT chat and see presence of onprem user in B.com

    Online user from B.com can chat and see presence of onprem and online user in both A.com and B.com

    Both online users from A.com and B.com has no problem to chat and see presence of federated external parties

    Any idea what i am missing ?  Thanks

    Friday, January 3, 2020 9:02 AM

Answers

  • Hi Jimmy,

    Checked all DNS records are pointing to the right place, we've found the problem where the external cert of B.com is missing some SAN for A.com, we do compare both external cert and re-issue the external cert of B.com which resolve the issue, now both A.com and B.com users either on-prem or Online can communicate with each others and presence showing correctly, thanks.

    • Marked as answer by Ededfufu Wednesday, January 22, 2020 10:18 AM
    Wednesday, January 22, 2020 10:17 AM

All replies

  • Hi eddfung!

    Does only location A has all federation to external parties?  

    Can on-premise user from B.com chat online user and see presence in A.com?

    According to your description, we recommend you check if your DNS configuration meet these requirements:

    1)For public DNS, all SIP domain SRV records resolve to On Premise Edge

    2)For internal DNS, all SIP domain sipfederationtls SRV records resolve to  On premise Edge external.

    Besides, we also recommend you check if there are any error messages in your server.

    For more details about deploying Skype for Business Hybrid with multiple SIP domains, please refer to this video:

    https://channel9.msdn.com/Events/Ignite/New-Zealand-2016/M385

     

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Best Regards,
    Jimmy Yang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
    Monday, January 6, 2020 10:31 AM
  • Hi Jimmy,

    Correct, only location A has all federation to external parties.

    Yes, on-prem user from B.com can chat and see presence of online user in A.com, once on-prem user from B.com initial the communication, then online user from A.com can chat and see presence of on-prem user in B.com.

    Getting log from both edge and front end server, i got “error 504, server time-out” and ”ms-diagnostics: 1017; reason="Cannot route From and To domains in this combination"; summary="Domain type analysis indicates that the ms-split-domain-info header in the message is the wrong type””

    i found a link from MS  

    “https://docs.microsoft.com/en-us/skypeforbusiness/troubleshoot/hybrid-im-presence/sfb-online-users-cant-im”

    and it’s giving me a solution

    To resolve this problem, add the Office 365 domain to the on-premises topology.

    However, I don’t get the meaning of it, do you have any idea? 

    Thanks!!!

    Monday, January 6, 2020 3:00 PM
  • I should make a correction for this:

    Yes, on-prem user from B.com can chat and see presence of online user in A.com.

    Once on-prem user from B.com initial the communication, then online user from A.com can chat back to on-prem user in B.com but online user from A.com is still unable to see the presence of on-perm user from B.com

    Tuesday, January 7, 2020 7:44 AM
  • Hi!

    Please make sure your federation DNS records pointed to the on-premises edge server for all domains that are verified by the Office 365 organization.

    Domain matching must be configured in the same manner for both the on-premises deployment and the Office 365 organization.  If partner discovery is enabled on the on-premises deployment, then open federation must be configured for your online tenant. If partner discovery is not enabled, then closed federation must be configured for your online tenant. For more details, you can refer to:

    https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/plan-hybrid-connectivity

    Best Regards,
    Jimmy Yang


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



    Friday, January 10, 2020 9:44 AM
  • Hi,
    Is there any update on this case?
    Please feel free to drop us a note if there is any update.
    Have a nice day!

    Best Regards,
    Jimmy Yang


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

    Thursday, January 16, 2020 9:52 AM
  • Hi Jimmy,

    Checked all DNS records are pointing to the right place, we've found the problem where the external cert of B.com is missing some SAN for A.com, we do compare both external cert and re-issue the external cert of B.com which resolve the issue, now both A.com and B.com users either on-prem or Online can communicate with each others and presence showing correctly, thanks.

    • Marked as answer by Ededfufu Wednesday, January 22, 2020 10:18 AM
    Wednesday, January 22, 2020 10:17 AM