So the scenario is pretty straight forward. I have a Lync On-Prem deployment and when I try to find a person who is hosted on Office 365, their presence is listed as unknown. If they try to start an IM conversation, they get:
SIP/2.0 403 Forbidden
Server: IncomingFederation/5.0.0.0
ms-diagnostics: 1034;reason="Previous hop federated peer did not report diagnostic information";Domain="acme2014.onmicrosoft.com";PeerServer="sipfed.online.lync.com";source="sip.domain.com"
The Office 365 person can see the presence of the Lync On-Prem user and can successfully start an IM and everything works.
My O365 External Communications is set to On except for blocked domains and there are no blocked domains.
So we can clearly see that the O365 is enabled for federation. Next thing to verify is my DNS records for my O365 tenant and using OCS Connectivity it comes back as successful and green validating all DNS records are published.
So everything looks right on the O365 side. On the Lync On-Prem side, we have the Hosted Partner setup:
Identity : LyncOnline
Name : LyncOnline
ProxyFqdn : sipfed.online.lync.com
VerificationLevel : AlwaysVerifiable
Enabled : True
EnabledSharedAddressSpace : False
HostsOCSUsers : False
IsLocal : False
AutodiscoverUrl :
And than we also have added the domain to the allow list.
Lastly, we only have a single SIP Domain in our Lync On-Prem deployment so the default domain is the only one domain.
Where else can I look for additional information.
Thanks,
Joe