Scenario: Unable to federate with partner who newly configured their own edge server with own domain/sip.

Us: closed, non discoverable. Federated successfully with over 30 partners, both open & closed. Telnet with Port 5061 successfully, and installed the provided certs from said partner. We are US based.

Them: Newly configured edge server with own domain/sip vs having one supported by Microsoft. Partner successfully communicates with other partners that are set to open, but has not federated with a closed set up. They are Isreal based.

Right off the bat, you would think the issue is on them based on the information above, but they insist the issue is with us. For the sake of customer service and due diligence, I told them I will explore. Is there something I am missing? A bad certification?I've used Lync Connectivity Analyzer, everything checks out fine with us. Very likely the issue is not on our end, but is there a direction I can point him to? It's tough to really dive into considering the time difference.

*Edit* From what I've researched the above error indicates a possible certification/port issue.

Hi exchangesysadmin,

Please check the followings:

1. First of all ,please make sure the federation configurations are configured correctly in your hand.

Try to nslookup on command prompt and type below.

Set q=srv

_sipfederationtls._tcp.domainname.com

You will get the exact edge FQDN and verify with access edge FQDN which you configured in External access, under allowed domain.

2. If you are using enhanced federation, you can ask your partner to check the certificate which they provided. The certificate for their federated access edge must match the sip domain of their user.

If the federation still does not work, you can try to put the FQDN of the access edge server and the domain name in like in the screen shot below.

Best regards,

Eric

Hi Eric,

Thank you for the information. This has been resolved.

• Marked as answer by exchangesysadmin 8 hours 30 minutes ago
• Unmarked as answer by exchangesysadmin 8 hours 30 minutes ago

Hi Eric,

Thank you for the information. This has been resolved.

• Marked as answer by exchangesysadmin Friday, April 03, 2015 10:51 PM
• Unmarked as answer by exchangesysadmin Friday, April 03, 2015 10:51 PM

Hi Eric,

Thank you for the information. This has been resolved.

• Marked as answer by exchangesysadmin Friday, April 03, 2015 10:51 PM
• Unmarked as answer by exchangesysadmin Friday, April 03, 2015 10:51 PM

Hi Eric,

Thank you for the information. This has been resolved.

• Marked as answer by exchangesysadmin Friday, April 03, 2015 10:51 PM
• Unmarked as answer by exchangesysadmin Friday, April 03, 2015 10:51 PM