We are doing all of that except for we can't use the MOC client as a softphone (this is theoretically possible with the latest version of Call/Communication Manager from Cisco) as it requires setting up SIP trunks between your OCS and CUCM servers which we have not done. We have headsets for our Cisco desk phones though and can use MOC to take a Cisco phone off hook thereby allowing a person to make a call on the phone with MOC without touching the phone. It works great, which is evidenced by the fact that I have not touched my desk phone in almost a year. Tim
From: Senter, John [mailto:[email protected]] Sent: Wednesday, February 10, 2010 5:11 PM To: NT System Admin Issues Subject: OCS and Cisco Call Manager Just wanted to see if anyone in the community has worked to deploy a OCS system using Cisco Call Manager for call routing. We are in the process of deploying OCS for internal IM. We also have Call Manager in place and all users have desk phones. The plan would be to still have desk phones for all users, at this time, and also allow OCS to function as a soft phone if the user is at the office or away. So basically have a split setup so both phones ring, desk phone and OCS, the user can use either to answer. This should then update the OCS presence to indicate On Phone. I am being told there are issues connecting OCS to the Cisco RCC gateway (CUPS). Just curious if anyone has done this and what they found out. Thanks ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
