Cisco Unified Personal Communicator (CUPC) is a desktop application that allows users to communicate via voice, video, web conferencing, and presence. It allows users to check the availability of their contacts, search a corporate directory, collaborate via the web, use click-to-click dialing, and participate on video calls.
CUPC can interact with a variety of servers and applications including Communication Manager, Presence, Unity, Meeting Place, and Microsoft AD. CUPC works by connecting via SSL to Cisco Unified Presence Server then retrieves the server configuration and user preferences. Next, CUPC registers via Session Initiation Protocol (SIP) to Presence and subscribes to the user’s buddy list. While the CUPC obtains presence notifications from the Presence, it connects to the LDAP configured within Presence and not Communication Manager
Important Note: Communication Manager and Presence each create a connection to LDAP. When this occurs, make sure the username and extensions are the same, otherwise Presence will show limited connectivity, which isn’t good.
If the CUPC cannot connect to the LDAP, the contacts’ names will be listed as user IDs instead of display names, and will not have phone numbers in their contact cards. Based on user preferences, the CUPC either connects to CUCM via CTI (desk phone mode) or SIP (soft−phone mode). The default is to connect via desk phone mode if the CUPC has never been launched by that user account before. In parallel, the CUPC connects to Internet Message Access Protocol (IMAP) for voicemail if configured via CUP. Once the CUPC has connected to the CUP and CUCM, the CUPC application displays connected as its status. The user can now make calls.
If the CUPC cannot connect to the CUCM, it shows Disabled as the phone mode selection. You can try to switch phone modes and see if the phone connects or not, if it does you are ready to send instant messages and make calls from Cisco Unified Personal Communicator.
Author: Chris Foster