OWA 2010 & OCS 2007 R2 integration: cannot send IM
Hi, I installed OCS 2007 R2 on Windows 2008 R2 (I know this is not yet supported by MS) and everything is working. With Communicator 2007 R2 clients I can see presence information and can send instant messages. I’ve configured Exchange 2010 OWA & OCS integration. Both the E2K10 CAS and OCS Servers are fully up-to-date with MS Update. From OWA 2010 I can see presence information and the Contacts list shows OCS contacts. When a user changes presence from within OWA this change is visible to other users. Problems: · Send IM from OWA to another user with OWA and Communicator 2007 R2 client signed in: IM arrives under Communicator 2007 client. A ‘reply’ results in: the following message was not delivered to <user> ID:504 · Cannot send IM from OWA to another user with OWA signed in and Communicator 2007 R2 client NOT signed in. After clicking on Send I get: This message couldn’t be delivered to all recipients because some recipients are offline or don’t want to be disturbed. Anyone any ideas? Martijn
December 31st, 2009 2:39pm

Yes. The OCS 2007 R2 hasn’t announced the support on the windows 2008 R2. Resources: OCS 2007 R2 and Windows 2008 R2 – what is the status? OCS 2007 R2 in a Windows Server 2008 R2 domainJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com
Free Windows Admin Tool Kit Click here and download it now
January 4th, 2010 5:46am

Hi Martijn,you need to install a hotfix for UCmaRedist in your OCS 2007 R2 server. the hotfix can be download from here:http://go.microsoft.com/fwlink/?LinkID=154247just download and install Ucmaredist.msp fileRegards,Raymond
January 5th, 2010 9:00am

I've removed OCS and installed OCS 2007 R2 on a new W2k8 SP2 Server. OWA 2010 IM is working fine now.Thanks!Martijn
Free Windows Admin Tool Kit Click here and download it now
January 8th, 2010 11:43am

I installed the hotfix and still doesn't work
February 16th, 2010 2:30pm

Oops my bad. Didn't mean to try to propose as answer. If you ran the lastest UCmaRedist update on your frontend, you will need to apply that update on to the Exchange CAS as well.Install the UCmaRedist.msp update on your Exchange 2010 CAS, then run an IISreset.
Free Windows Admin Tool Kit Click here and download it now
February 18th, 2010 4:44am

HiI have exactly the same issue - can send from OWA to Communicator but can't reply and can't IM between OWA usersAll of OCS is on 2008 SP2 and I have applied the patches. However, Exchange 2010 is on 2008 R2 - will that make a difference do you know ?The CAS Servers are load balanced so I have entered the names of the CAS servers and of the load balanced URL in the host authorization tab. The OCS Front End servers are also loadbalanced and I have entered the URL of the pool in the web.config file.Any help you can give much appreciated.Phil
February 24th, 2010 1:24am

And whats even more odd, is I could go from web to communicator, not the other way, I've now re-applied the above patch by hand and I can get from communicator to web, but not the other way round - in other words, the behaviour has swapped direction !You can see the web user typing in communicator (you get the "user x is typing a message" message so there must be connectivity but the wenb user gets the message "The message couldn't be delivered to all recipients because some recipients are offline or don't want to be disturbed"And whats really odd is if i start the conversation from communicator i get 2 way IM but if from OWA then its only one way !It wouldn't be that the web trust tool see's my cas servers as CASSERVER.DOMAIN.COM but the certificate on the cas server says casserver.domin.com - i.e. one is upper case and the other is lower case - I have heard that OCS can be v picky about its certificates so was just wondering.Phil
Free Windows Admin Tool Kit Click here and download it now
February 24th, 2010 2:35am

Phillip I was having the same issue that you were having. I had installed the patches and messaging was still not working from Fat Client to OWA. I found that our Firewall was dropping packets from OCS Front-Ends to Exchange 2010 Client Access Servers on TCP 5075. After looking through Technet, I found that ports 5075-5077 (TCP) are used for the Unified Messaging role. I had networks put in the firewall rules for these ports and IM now works. As a background to our Server Architecture, OCS is in a different subnet due to a Hardware Load Balancer so our Firewall affected this traffic. Here is a list to the Port Reference http://technet.microsoft.com/en-us/library/bb331973.aspx Jason.
June 17th, 2010 6:48pm

Hi Philip , where can I set TCP 5075 PORT? A.C.E
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2010 5:43am

In my environment, I have a firewall that separates the subnet that Exchange is on from the subnet with the Hardware Load Balance and OCS. I set the rule to allow traffic from OCS to Exchange CAS for TCP5075, 5076 and 5077. I was looking at the firewall logs and found 5075 traffic being dropped. I added the other 2 ports to the rule because they were listed as a group for the Exchange 2010 UM role ports to allow through firewall. Jason
June 24th, 2010 5:09am

Hey, The link is broken and I cannot find the hotfix. Do you know where I can get it? Thanks, Andrew
Free Windows Admin Tool Kit Click here and download it now
September 7th, 2010 1:38am

i have the same problem in APAC servers, but when i try to do a telnet for the local host (CAS server) 5075 responses the port, but not other two ports. I have a server in USA which responses the for port 5075 & 5076 both...what could be the issue, please help me out?
December 5th, 2010 10:52am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics