We have an internal hosted Standard Edition Front End/Edge server are trying to connect to Office 365 users but always get this errors. We've tried direct federation and federation providers with Lync online but it doesn't help. I'm afraid the error message is not clear to us - can someone please explain what this relates to:

504  Server time-out

ms-diagnostics:  1017;reason="Cannot route From and To domains in this combination";info="Possible server configuration issue";summary="Domain type analysis indicates that the ms-split-domain-info header in the message is the wrong type";external-domain="<their domain>";external-type="domain-type-local";internal-domain="<our domain>";internal-type="domain-type-remote";source="sipfed0E.online.lync.com";OriginalPresenceState="0";CurrentPresenceState="0";MeInsideUser="Yes";ConversationInitiatedBy="6";SourceNetwork="4";RemotePartyCanDoIM="Yes"

• Edited by PanosE 13 hours 11 minutes ago

Can you federate with anyone else?  If run your domain through https://testconnectivity.microsoft.com/ what is the output?  Does it seem to indicate you're set up properly or does it show errors?

I'm afraid we don't have anyone else to federate with at the moment and only have network access to Office 365 to test. Connectivity tester doesn't reports any errors:

Testing remote connectivity for user <a user> to the Microsoft Lync server.
 The specified user successfully signed in to Microsoft Lync server remotely through the Lync Access Edge Server.
 
Additional Details
 
Elapsed Time: 2307 ms.

 
Test Steps
 
Attempting to resolve the host name sip.<our domain> in DNS.
 The host name resolved successfully.
 
Additional Details
 
IP addresses returned: <the IP>

Elapsed Time: 351 ms.

Testing TCP port 443 on host sip.<our domain> to ensure it's listening and open.
 The port was opened successfully.
 
Additional Details
 
Elapsed Time: 279 ms.

Testing the SSL certificate to make sure it's valid.
 The certificate passed all validation requirements.
 
Additional Details
 
Elapsed Time: 429 ms.

 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server sip.<the domain> on port 443.
 The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
 
Additional Details
 
Remote Certificate Subject: CN=sip.<our domain ,,, certificate details>.

Elapsed Time: 390 ms.

Validating the certificate name.
 The certificate name was validated successfully.
 
Additional Details
 
Host name sip.<our domain> was found in the Certificate Subject Common name.

Elapsed Time: 0 ms.

Certificate trust is being validated.
 The certificate is trusted and all certificates are present in the chain.
 
Test Steps
 
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=sip.<our domain>
 One or more certificate chains were constructed successfully.
 
Additional Details
 
A total of 1 chains were built. The highest quality chain ends in root certificate <Public CA Certificate>

Elapsed Time: 14 ms.

Analyzing the certificate chains for compatibility problems with versions of Windows.
 Potential compatibility problems were identified with some versions of Windows.
 
Additional Details
 
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.

Elapsed Time: 2 ms.

Testing the certificate date to confirm the certificate is valid.
 Date validation passed. The certificate hasn't expired.
 
Additional Details
 
The certificate is valid. NotBefore = <date/time>, NotAfter = <date/time>

Elapsed Time: 0 ms.

Testing remote connectivity for user <sip for user> to the Microsoft Lync server.
 The specified user successfully signed in to Microsoft Lync server remotely through the Lync Access Edge Server.
 
Additional Details
 
Registration completed successfully.

Elapsed Time: 981 ms.

• Edited by PanosE 9 hours 17 minutes ago

Hi PanosE,

Have you configured the required SRV record for federation ?

_sipfederationtls._tcp.Domain.com

 

In addition, can you contact your partner and confirm that they have enabled federation and added your domain in allowed list ?

 

Best regards,

Eric