Remote Call control ONLY on CUPS+CUCM+OCS RRS feed

  • Question

  • Hi,

    I would like to ask some questions about high level OCS-CUPS integration. Perhaps this is kind of silly deployment type, but we are just thinking in the high level. Any comments on PROS and CONS of doing this "RCC only" will be appreciated. Let's say in our environment, we are thinking about using only RCC mode (no enterprise voice users) so MOC will always use Cisco IP phone to call out. Apparently, there will be no mediation server sitting between CUCM and OCS, since OCS will be used to generate any calls to neither PSTN nor Cisco IP phones. For remote users, they will use both MOC and Cisco IP Communicator at the same time. MOC will use RCC to control Cisco IP Communicator software instead of hard phones.

    1) Can MOC use RCC to control Cisco IP Communicator just like other SCCPs?

    2) With a user having multiple Cisco IP phones shared the same extension, where exactly do we configure what phone MOC wants to control?. Is that something an end user can manipulate and change it?

    3) Doing this type of deployment if you only use RCC mode, I would think we pretty lose most features on OCS side. (conference/video/audio). What is PROS and CONS for doing this?.


    Thank you

    Yui chu


    Wednesday, January 16, 2008 6:13 AM

All replies

  • I believe this will become a common scenario, whether we are talking about Cisco or another PBX vendor, the ability to tie a phone system into a PC's user experience will become an important way that we enable employees to collaborate and become more effective in their communication.


    As far as Cisco goes, you are correct that there isn't any need for a mediation server as the Cisco Presence Server essentially accomplishes this task of "translating" between SCCP and SIP.  The benefit of using this scenario is the ability to put the phone routing, security, quality of the call, etc. in Cisco's hands and you need only use the MOC client to initiate calls -- less complicated OCS environent.  So, if you have a fully functioning Cisco environment, you can leverage the investement and integrate with OCS and not have to worry about that layer of complexity.


    1 - MOC can RCC any SCCP phone -- IP Communicator to CallManager is just another phone, so you can use MOC to conrol it.


    2 - That's a good question, I need to try that scenario in my lab, but I believe that it will relate to how the phone is associated and how CUPS handles multiple line appearances -- more to come.


    3 - RCC is a great way to give end-users "click to dial" which in a Cisco world can be a big leap forward.  You do give up some of the tighter integration pieces like adding video to an established call and the ease of creating a conference call, but you can always fall back to the phone and do it from there.


    Like I said I think this scenario is going to crop up more and more.  It seems to me that end-users can really benefit when you combine some of the best from both worlds.


    Tuesday, January 22, 2008 5:07 AM
  • For 3 - presumably you would still have MOC-MOC multi-party video-conferencing?  Is it just the integration of a phone call with video that you are losing.

    Tuesday, January 22, 2008 5:05 PM
  • Great answers. Please let me know when you find out more about RCC stuff.


    Thursday, January 24, 2008 6:07 AM
  • Yui chu.


    I've just spent some time performing a large-scale RCC-integration and have posted quite a few times lately about different aspects of it.  Here are some previous threads related to your questions:


    2. We ran into this very same scenario and found a fix (from Cisco) for a couple of the issues, but still are working on others.  Here is how to specify which phone to control:


    But the current issue is when an inbound call is picked up on a second phone (e.g. secretary answering another line) OCS drops the current call on the first phone.  Cisco supposedly has a fix for this, but in the latest version of CUPS only.


    3. I have so far been unable to disable Communicator calls and only allow RCC calls:





    I recommend reading through the other blogs entry on Matt's site, as he has posted quite a few items regarding OCS+CUPS integration, specifcally using RCC.  I agree that RCC will be seen more in the future, but the truth is that Microsoft is moving away from supporting RCC.  The RCC feature-set has been crippled some since LCS 2005, and they are really pushing EV as the desired solution, which will not apply for a pretty large base of companies with expensive, new Cisco IP phone deployments already financially committed to the hardware and licenses.  RCC is a no-brainer sale for clients with e-Cals (they already paid for OCS!), but it is difficult to deploy in a scenario that is most-beneficial these types of customers.

    Thursday, January 24, 2008 2:06 PM
  • Hi Jeff,

    On your point #3, does it mean that when OCS client is in RCC mode, it can still receive both RCC alert and PC-to-PC alerts?. That's going to be confusing for users whether they should pick up and listen from phone headset or from PC-headset. Also confusing, it is presence status that someone could be busy with on call deskphone or on call PC-to-PC?. I am just thinking whether it is possible to somehow hardcode OCS clients to always use RCC mode, disallowing users to change the mode to Enterprise voice. That way there will be no PC-to-PC call.


    Thank you



    Monday, January 28, 2008 2:43 AM