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.

OCS 2010 release date predicted by HP & Computerworld

HP has a “Microsoft product release chart” on its Large Enterprise Business page and it states that OCS 14 / 2010 will be released in Q4 of 2010 so in about a year from now,  i would have hoped for Q2 since i predict that its going to have some kick ass features.

Source http://h30458.www3.hp.com/us/us/ent/808787.html

However Computerworld wrote: SharePoint 2010 and OCS 2010 are expected to ship in May or June of next year, although Microsoft has not released an official ship date. about one week ago

You can read more in their article about Exchange 2010 here