Routing that includes user-to-user instant messaging breaks in Microsoft Office Communications Server (OCS) 2007 R2. When this behavior occurs, instant messages are blocked. This problem occurs when the following conditions are true:
A user's deployment contains a third-party application.
The third-party application uses the otherIpPhone attribute.
The otherIpPhone attribute contains a telephone Uniform Resource Identifier (URI) or a Session Initiation Protocol (SIP) URI.
This problem occurs because User Replicator replicates the otherIpPhone attribute for regular users. However, the otherIpPhone attribute should only be used for application contact objects. This behavior causes the server to incorrectly perform static routing instead of the regular default routing.
To fix this problem, apply the following update:
977345 Description of cumulative update for Office Communications Server 2007 R2: January, 2010
After you apply this update, User Replicator only uses the otherIpPhone attribute for application contact objects.
If SIP is not enabled for the user after the update is applied, enable SIP for the user.
If SIP is enabled before you apply the update, the database is not updated retroactively. In this case, perform one of the following:
Disable and then re-enable SIP for the user. Or, move the user to another pool and then move the user back.
Run the following query on the back-end server to clear stale data:
update phr set phr.ForwardingUrl = null from rtc.dbo.ResourceDirectory as d inner join rtc.dbo.HomedResource as phr on (phr.ResourceId = d.ResourceId) where d.AdUserSid is not null and phr.ForwardingUrl is not null