UC clients: CUCI-Lync and CUPC versions 8.5

Cisco announce that Cisco UC Integration™ for Microsoft Lync 8.5.1 is now orderable and available for first customer shipment.

For those not familiar with this product, it’s a softphone version that runs ‘attached’ (as a plug-in) to Lync client. It allows you to make and receive phone and video calls with Cisco Unified Communications Manager, while you still use Lync client to check presence and exchange Instant Messages. The previous releases were called CUCIMOC (v7.x and v8.0).

I don’t personally support this approach, because it’s a rather confusing experience to the end-user, and especially difficult to maintain for both voice, server and desktop support teams. But… if you already have a Cisco IP telephony and video (with MCU) in place, I would recommend to make a pilot and evaluate some of the benefits of this integration ;).

Check this video to see how you can use it to make phone calls, conference calls, meetings, and voice messages (using Cisco Unity Connection server).

Cisco also released the new version of his UC client. Cisco Unified Personal Communicator 8.5 looks a serious Lync competition. I start working with Cisco one year before OCS, but when I finally got my hands and manage to successfully install v7 of CUPS (presence server) and CUPC, I realized why Cisco was one of the UC market leaders, especially with the v8.

The interface is appealing and easy to use,  the context menus and options are on the right place. Contact pictures can be retrieve from a central location, including Active Directory (this was available  since earlier versions!). Sadly enough, In a virtualized desktop environment, full audio and video capabilities are only available on CUPC when you are using the desk phone for phone calls. If you are using the phone on your computer, only the voicemail features are supported.

Some interesting new features (most we already have on OCS/Lync):

  • Ability to escalate directly to Cisco WebEx Meetings;
  • Office 2010 Contact Card integration for Presence light-up and Click to Communicate capabilities;
  • Windows 7 and Office 64 bits support;
  • Click to communicate <im:uri> support (tel:uri was possible on v8.0);
  • Search for contacts by number;
  • Administrator have the ability to enable/disable IM and presence status capabilities.

Since v8.0:

  • Group chat and persistent chat rooms;
  • Offline instant messaging;
  • Wideband audio codec’s for higher fidelity audio;
  • VGA and 720p high definition video resolutions;
  • Support for deskphone control of the latest Cisco Unified IP Phone models;
  • Video on the PC while in deskphone control mode;
  • Ability to initiate & add participants to multiparty audio/video conference calls.

You can check the release notes for these a other details.

Post updates:
– Cisco announced on March 1st that CUPC will be rebranded (and improved) to Cisco Jabber;
– I already published my cucilync review and a CUPC review.

Comments are welcomed,

Advertisements

22 thoughts on “UC clients: CUCI-Lync and CUPC versions 8.5

  1. Adis 08/04/2011 / 21:55

    Is it me or CUPC now looks exactly like Lync?

    • LuisR 09/04/2011 / 19:53

      Not. CUPC has a dark blue window and Lync a light gray one… 🙂
      I’m also planning a blog to compare them. Right after a CUPC review, so you’re invited to come back 😉

  2. tomouh 15/03/2012 / 02:10

    hello, please MRS luis i have project to federation inter-domain lync server and cisco presence i want real architecture global for this integration with all protocoles and devises and software
    please realy i need it.
    thank u my email is tomouh.hassane@gmail.com

    • LuisR 15/03/2012 / 19:24

      I made one ‘internal federation’ (no DMZ) between CUCM/CUPS Lync so far… how can I help?
      There’s now a very good documentation at Cisco to explain the major steps: http://www.cisco.com/en/US/products/ps6837/products_installation_and_configuration_guides_list.html

      Some things you shoul know:
      * Presence and IM is done between CUPS and Lync;
      * Voice is only possible at telephony level, i.e. trunk between CUCMLync
      * Video was working, but we didn’t go deeper;
      * Content sharing interoperability is not possible.
      * Both CUPS and Lync can ‘share’ the same Active Directory 😉

      • venkat 01/06/2012 / 15:18

        Hi,
        We are also looking for a coexistance of CUPC and Lync within the same domain. Can you please tell us how you did it. We couldn’t find any documentation to do this with in the same domain.
        Can we make CUPC as the primary source for presence in this scenario and flow the presence information to Lync?

      • LuisR 01/06/2012 / 17:46

        Hi,
        I’m not quite sure what you are refering ‘same domain’ (Windows or SIP domain)?
        Also: CUPC as primary source and flow the presence information to Lync?

        You can explain with an example

  3. tomouh 16/03/2012 / 14:45

    thks MRS luisR for this information
    i want know the topologie network of this integration and if i need to add just switch betwin cups and lync or more complexe schema
    please i just want have a topologie network with protocole for this integration

    • LuisR 17/03/2012 / 17:41

      If CUPS and Lync are inside your corporate LAN/WAN you can connect directly them.
      You will need an Cisco ASA Lync Edge to connect users if you need some ‘safety’ dmz between them (or connect using Internet link).

  4. mawsine 08/05/2012 / 12:00

    I have a problem: instant messaging and presence that does not work between CUPC and Lync? can you help me

    • LuisR 08/05/2012 / 20:45

      Yes, it does work.
      It a simple federation that allows you to to exchange presence and IM, and you can also extend to voice+video

      Sorry for not giving much more information for now. But this knowledge is important for my company business advantage offer.

      • mawsine 09/05/2012 / 11:17

        ok thank you even though I need your help, for documentation, I tried several document but only the busy status which detects when the client Lync makes a call, but the presence and IM Not work. this my @: lost_11@live.fr

      • LuisR 09/05/2012 / 18:34

        Sounds like a missing acl connection rule, the SIP listenet port (CUPS) or application trust (Lync).
        You might want to define SIP over TCP at both sides first, to limit and better trace communications.

        If you can see the busy status, at this point a trace (log and network) will give some clues.

  5. samia 08/05/2012 / 14:12

    please its possible to integrate lync with CUPC in the same Active directory because the IM and presence doesnt enable in this case

    • LuisR 08/05/2012 / 20:52

      Yes CUPS and Lync can share the same AD without any problems.
      in fact the screenshoots are an example of the benefits:
      – Use one authentication realm;
      – You have by default a share address list between clients (Lync can search CUPC users, and vice versa).
      This is specially interesting for a multiplatform of UC service provider

  6. tomouh 08/05/2012 / 19:59

    it’s possible MRS luis to make internal federation between lync cucm and cup ???? because i can’t found any document for this fedederation its possible with ocs/lcs not lync that what i found

    • LuisR 08/05/2012 / 20:47

      It’s possible.
      You can use the cisco documentation for interdomain federation as a start.
      Just don’t use the lync edge server and the cisco ASA

  7. tomouh 08/05/2012 / 22:53

    i see your answer it work with documentation federation intradomain lcs/ocs but how to configure lync for sharedaddspace please i just want how to configure sharedaddspace

    • LuisR 09/05/2012 / 18:30

      If sharedaddsspace you mean (same sip domain) I don’t believe it will work well.
      CUPS states that you can do that, but in Lync you can only find support for share Office365 accounts. It might be a possible good way to trick Lync here 😉

  8. samia 10/05/2012 / 14:00

    please i have a problem in lync server when i use cmd:enable-cstopology to saving my configuration i have this error:Echec to creat the new instanc for: “microsoft.management.ADConnect.shema.ADMicrsoftSCP for “domain”

    • LuisR 10/05/2012 / 21:02

      Looks like you might have issues with Lync schema preparation, or have some old legacy AD configuration stores.
      You can use the command Remove-CsConfigurationStoreLocation to clear any possible old or previous configurations.

  9. Frex 10/05/2012 / 21:08

    i run this cmd(remove..) , and after i run publish-cstopology; then , enable-cstopology but the same problem;

    • LuisR 10/05/2012 / 22:23

      I don’t think it will solve the issue but have you tried the command with more options (like SkipPrepareCheck?)
      ex: Enable-CSTopology -GlobalCatalog Fqdn -GlobalSettingsDomainController Fqdn -SkipPrepareCheck $True

      I suggest you post on Microsoft foruns, so more people can see your problem and help
      really… not everybody comes to like to visit my blog 😦

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s