Cisco Presence - MS Lync Federation

[Sergey Svishenko]

Hello!

I try to configure CUP - MS Lync Federation within Enterprise.

My Lync client can send message to my Cisco Jabber and vise versa.

My Cisco Jabber can see status of my Lync client, but my Lync client

can't see status of my Cisco Jabber.

Can anybody help me?

[Jonathan Schulenberg]

First off, the 8.6 release of CUP doesn't support Lync, only OCS so this may not work. Having said that usually this is because the user account doesn't have the msRTCSIP-PrimaryUserAddress attribute set on their AD object. OCS auto-populates this but if the user never existing in OCS it needs to be set manually to their SIP URI.

While you're at it don't forget about the proxyAddress attribute as well.

Please remember to rate helpful responses and identify helpful or correct answers.

[Sergey Svishenko]

Why CUP 8.6 doesn't support Lync?

From following guide i've seen CUP 8.6 support Lync:

Integration Guide for Configuring Cisco Unified Presence Release 8.6 for Interdomain Federation.

When i configure CUP-Lync Integration should i configure TCP and TLS communication (5060 and 5061),

now i've configured only TCP communication between CUP and Lync.

Also i have not configure DNS SRV records for my CUP server (5061 port).

[Jonathan Schulenberg]

I can't answer the why as I'm not a Cisco employee. The Compatibility Matrix clearly says 'No' in the Intradomain federation section of Table 2 on the Microsoft Lync row with CUP 8.6.

Please remember to rate helpful responses and identify helpful or correct answers.

[Sergey Svishenko]

Intradomain - is this same SIP domain or same AD domain or same Forest AD?

It's all different.

I have two different AD domain in one AD forest.

[Jonathan Schulenberg]

Domain in this context refers to the presence domain being used by CUP and OCS. Example jdoe@mycompany.com. This is not referring to an AD domain.

Please remember to rate helpful responses and identify helpful or correct answers.

[gbljoba]

Im a little confused. We are in a similar situation. WE have a deployment of OCS/Lync Clients (Lync back end) to 4000+ users. We have no enterprise standard PBX but are working towards a cisco model so the presence and telephony decisions need to be clear where we need to go. Since its very economical for us to have MS with our agreement it was assumed Lync would be the successor in the IM+P, P2P voice/Video and possibly conferencing. Meaning the Cisco locations used CUCiLync.

Now Cisco are giving Jabber away certainly the countries we have with Cisco clusters would like to take advantage. The problem i cant get my head round is how it should be connected. Lync owns our SIP domain e.g JDoe@ABC.com so what can Jabber do? JDoe@jabber.ABC.com?

The main thing is that the user must not notice the difference, that is, using either client they should be able to search, add, IM+P users on either system without having to think about who is on what system.

Have i over complicated things?

/Jon

[Qite Li]

Hi, the Compatibility Matrix has been updated to include the support for Lync Server 2010 intradomain federation.

"Partitioned Intradomain Federation  between Cisco Unified Presence and Microsoft Lync Server 2010 is  available only from Release 8.6(4)SU2. For Partitioned Intradomain  Federation with Microsoft Lync, you must configure TLS; TCP is not  supported. See Partitioned Intradomain Federation for Cisco Unified Presence for more information. "

Regards,

Edwin