Lync on-premise federation to Office 365 partner

I got a request to set up federation with a client of ours who only uses Lync in Office 365.

I have been completely unable to get it to work. Part of the problem is confusion with the FQDN's they sent me.

For privacy sake I am going to rename all domain names.

Their email addresses show as name@TLI.com

So my first course of action was to add TLI.com as an allowed domain.

This didn't work, so I asked them for more. They sent me a very confusing email as follows:

"Our actual domain for the service is: TLInternational.onmicrosoft.com but I happen to have@TLI.com and @ marakon.com linked in. Does this help? I’ve had 2 other solution providers add us in and I think this is all they used (below). The portal for me to manage the lync service is very dummied down because it’s not hosted internally. There is nothing that actually calls our specific sipfed out. If this doesn’t help, let me know.

Lync autodiscover for federation and public IM connectivity

"

As you can see I now have TLI.com, TLInternational.onmicrosoft.com,marakon.com, and DomainName.com on my hands.

I was very confused by the table she included as it was all extremely generic info. Part of the reason I've been so confused is thatDomainName.com even though I did change that for privacy on here, the real one I was sent, was equally generic.

Further confusing me is the fact that TLInternational.onmicrosoft.com does not ping, but both_sipfederationtls.DomainName.com and edge.DomainName.com both ping.

As a note- I already have the sipfed.online.lync.com entry in there correctly.

I have tried many Hosted Provider and SIP Federated Domains entries and so far I've come up empy.