Cisco Unified Personal Communicator (CUPC) is the client application that integrates into the Cisco Unified Presence Server (CUPS). This client runs on a Windows or Macintosh desktop environment and provides for several integrated communications features such as desk phone control, Instant Messaging (IM), Presence, softphone, communication escalation, and so on. This will cover the configuration steps required to configure CUPC.
The configuration of a user leveraging CUPC has several basic steps that need to be completed:
It is strongly recommended having LDAP synchronization configured in any CUCM installation. This brief section covers the steps required to configure a user in CUCMwithout LDAP integration. This is because when LDAP synchronization is enabled, the ability to add/delete users in the CUCM user interface is removed. All users are added or removed via the LDAP management interface. Follow the below steps:-
The user might not show up for several minutes on the CUP server. If it is taking too long, go to Cisco Unified Serviceability > Tools > Control Center-Feature Services, select the CUP server (publisher if in a cluster), and then start or restart Cisco UP Sync Agent.
When the user has been added to CUCM, it will be synchronized over to the CUP server. There is no need to add the user separately to the CUP server. LDAP synchronization is strongly recommended so most of these steps would not be necessary, and the rest can be done when doing the phone device provisioning in CUCM.
A common deployment model is for a single user to have both a desk phone and have CUPC act as a softphone during communications that take place away from the desk. CUPC offers a softphone capability that enables it to act as a phone device on a computer without the requirement of a desk phone, making the desk phone an optional device in a deployment. The use of a desk phone is optional and not required when deploying and configuring CUPC. Basic steps necessary in setting up an IP Phone to be used with CUPC are:-
NOTE:-Presence authorization works with Presence Groups to allow or block Presence requests between groups. This enables greater granularity in offering Presence services to groups or departments.
The SUBSCRIBE calling search space determines how CUCM routes Presence requests that come from the phone. This setting enables you to apply a calling search space separate from the call-processing search space for Presence (SUBSCRIBE) requests for the phone.
The phone now registers to CUCM with the proper settings and user association. Adding the phone allows users to have the option to control their phone through a computer telephony interface (CTI) with the CUPC client. This allows for the added software features offered by the CUPC client and still has a desk phone for a more reliable voice experience.
The next step is to set up a CUPC device in CUCM associated to the appropriate user and potentially connected to a desk phone. The first step in planning for the CUPC device configuration is to understand the naming convention required in CUCM. These requirements follow:
|CUCM Username||Associated Softphone Device Name|
When the naming convention has been decided, the CUPC device can now be added to CUCM:-
When saved, a new screen comes up that shows what devices are associated to the DN. This field should at least have the CUCP device associated with it. If it is a shared DN with a phone device, two devices should be listed: the CUPC and the phone device.
Now that the CUPC device is set up in CUCM and the users are configured, the client can be installed, and there will be Presence, desk phone connectivity (CTI), and softphone functionality.
If there is any service issues after a user has logged in, there are two basic things an end user can do to immediately confirm an issue and give administrators a good idea of what the problem is and how to resolve it follow:-
When the user and administrator have determined a specific problem, more troubleshooting will most likely be required.
There could be issues with an end user not being able to log in to CUPC. This can be because of several issues and the following are some ideas on where to look:-
Most common voicemail issues from the CUPC client stem from a user not being able to log on, or voicemail messages are not downloading or don't appear in the recent pane. Here are some things to look at to address voicemail issues on CUPC:-
The following provide solutions to some common LDAP problems. For instance, if there are no results when a user does a query in the Search pane, there can be several reasons for this; here are some things to look at to resolve the issue:-
Refer shortcut commands & Accessibility features