OCS cannot communicate with MSN users that using own domain

Resolution:
==========
This is expected and reasonable behavior.

For example, I have a live account named paolo@microsoft.com and my email(also ocs) account is paolo@microsoft.com. This is a conflict and communicator won’t understand who should be added.

The resolution right now is that MSN will periodically check the live account. If it detected someone’s live account has conflicted with MSN federated partner, this live account will receive a notification that he must change this live account to another email address.

During that period, we can contact with our internal OCS user only. Here are the steps to add like kind of contact. We should remove contact from our contact list. Type the name of user in communicator search bar. Add the user listed into our contacts list.

In this way, msn user won’t be listed and only internal OCS user only. So, we can send IM to this user.

Note: This is OCS communication. It is not possible to contact with MSN account anymore if his live account conflicted with MSN federated domain.

Call via work COMO

Hi

If the call via work option is grayed out check that you have done the following:

Configure the user account for enterprise voice.

Configure it with a line uri.

Enter the number in e164 format in the COMO client.

Building a supported OCS Voice platform with Cisco

Microsoft just released a document named: Microsoft and Cisco: Joint Interoperability Support Statement

Its a short and simple document explaining the different setup you can do.

  • Direct SIP Interoperability
  • Cisco UC Integration for Microsoft Office Communicator
  • Remote Call Control

read more and download here.