This document describes the guidelines and steps to configure Softphone device
Cisco Unified Personal Communicator
Cisco Unified Communication Manager
Configuring CUPC Users
In CUCM Administration, select User Management > End User > Add New.
Fill in at least the required user information (User ID and Last Name).
Associate Phones to User.
Device Associations can be left at the default.
Leave directory number associates at the default setting unless you already have a desk phone and directory number configured for this user.
Ensure that the user roles include Standard CCM End Users , Standard CTI Enabled and Standard CTI Allow Control of All Devices. A Primary Extension must be configured for each CUPC . Associate Devices like desk phones) with user for CTI support.
Select the Save button.
Perform the basic integration between CUCM and CUPC Licensing Capabilities Assignment, select System>Licensing>Capabilities Assignments.
Select the users recently added that will have Presence and CUPC capabilities.
Click both check boxes to enable CUP and CUPC features for the users
Configuring a Softphone Device for Each CUPC User
When you create a softphone device for each Cisco Unified Personal Communicator Release 8.0 user, you select the Cisco Unified Client Services Framework device type.
You must also specify a device name. Ensure that the device name conforms to these guidelines:
Can contain uppercase and lowercase letters, and numerals.
Contains no more than 15 characters.
No correlation to the username is required, but for convenience you might choose to include a username in the device name. For example, you might use the device name CSFabaker.
Sample Username Conversion for Cisco Unified Personal Communicator Softphone Device
Cisco Unified Communications Manager Username
Associated Softphone Device Name
You must create username that do not collide when converted, for example, the usernames johnnie_jackson and johnniejackson convert to the same softphone device name and therefore are said to collide.
Note:- If Cisco Unified Personal Communicator is unable to derive its softphone device name, it cannot properly register and cannot function as expected. You might have to reconfigure a user to use a name other than their normal username to avoid this problem.
To enable Cisco Unified Personal Communicator softphone features, you must manually create a new softphone device for each user.
The auto-registration features in Cisco Unified Communications Manager are not supported with Cisco Unified Personal Communicator.
Follow the below mentioned steps to configure it :-
(Cisco Unified Personal Communicator Release 8.x) Select Cisco Unified Client Services Framework from the Phone Type menu.
(Cisco Unified Personal Communicator Release 7.1) Select Cisco Unified Personal Communicator from the Phone Type menu.
Configure the following information:
a. Specify the softphone device name in the Device Name field.
b. Enter a descriptive name for the phone in the Description field. For example, enter Richard-softphone.
c. Cisco Unified Personal Communicator Release 8.x) Select Default from the Device Pool list.
d. (Cisco Unified Personal Communicator Release 8.x) Select Standard Client Services Framework from the Phone Button Templatelist.
e. Configure all the required fields for your environment.
f. Select the user ID from Owner User ID menu.
g. Select the device name of the Cisco Unified IP Phone to associate with Cisco Unified Personal Communicator from Primary Phone.
h. (Cisco Unified Personal Communicator Release 8.x) Check Allow Control of Device from CTI to enable CTI to control and monitor this device (Cisco Unified Personal Communicator Release 7.1) Uncheck Allow Control of Device from CTI.
i. Enter information in the Protocol Specific Information section, as follows:
Select Standard Presence Group.
evice Security Profile
(Cisco Unified Personal Communicator Release 8.0) Select Cisco Unified Client Services Framework - Standard SIP Non-Secure Profile.
(Cisco Unified Personal Communicator Release 7.1) Select Cisco Unified Personal Communicator - Standard SIP Non-Secure Profile.
Select Standard SIP Profile to specify the default SIP profile. SIP profiles provide specific SIP information for the phone such as registration and keep-alive timers, media ports, and Do Not Disturb control.
Select the user ID. This is the same user ID as the one you selected for Owner User ID.
Select the Add a New DN link in the Association Information section that displays on the left side of the window.
Configure the following information:
a. Enter the directory number and route partition for the Cisco Unified Personal Communicator.
b. Enter the caller ID in Display (Internal Caller ID), in the Line 1 on Device Device-Name section.
c. In the Multiple Call/Call Waiting section, specify the maximum number of calls that can be presented to Cisco Unified Personal Communicator in the Maximum Number of Calls field.
d. In the Multiple Call/Call Waiting section, specify the trigger after which an incoming call receives a busy signal in the Busy Trigger field.
Note:- The Busy Trigger setting works with the Maximum Number of Calls setting. For example, if the maximum number of calls is set to six and the busy trigger is set to six, the seventh incoming call receives a busy signal.
Make sure that the status shown at the top of the window indicates a successful save and that the resulting status is Ready.
Tips to remember
The directory number that is configured for Cisco Unified Personal Communicator and the Cisco Unified IP Phone must be identical. A directory number is configured with a partition, and you assign a directory number to Cisco Unified Personal Communicator and the Cisco Unified IP Phone. This configuration causes the Cisco Unified Personal Communicator to share the line with the Cisco Unified IP Phone for this user.
Cisco Unified Communications Manager reminds you that changes to line or directory number settings require a restart. However, a restart is required only when you edit lines on Cisco Unified IP Phones that are running at the time of the modifications.
From Cisco Unified Communications Manager Release 6.x, make sure that an association exists between the user and the line that is configured for that user so that the correct availability status in Cisco Unified Personal Communicator is displayed. Select Device > Phone, and view the association information for the device. Make sure that the user is associated with the line on the Directory Number configuration window. Make sure that you associate the line and user for all the phones used by the user for that directory number.
Few known Issues
Issue:- In the softphone field,error that it cannot connect on any of the CallManager servers.
Solution:- Make sure that no firewall is preventing the traffic.
Issue:- Users sometimes are unable to enable softphone feature in CUPC from the drop down menu.
Solution:- Make sure the device name should be in correct format and also see the Cisco Bug ID CSCsr65890. Services
hi guys, i am running cucm/imp 12.5 su2. Jabber is enabled for LDAP (EDI) to look up contacts and photos. Everything works fine internally. however when MRA is implemented, jabber does not fetch the photos. MRA uses UDS instea...
I hadn't worked on my Cisco phone system for a while, and the trial licenses on the unity express module have expired. I bought this used. What licenses do I need to just have a couple of voicemail mailboxes working on there? Mailbox and...
Hi, I hope someone can help me I have some questions about this configuration. -Is the Agent State Trace report a historical report or a real-time report? -If I activate this configuration to 15 agents, how much do the database resources in...
Hi, We notice the following certificates are set to expire and we want to make sure of the procedure as I have found some conflicting documentation regarding the procedure. Can someone provide the documentation which include the steps and is the...
A while back I was having some trouble with outbound caller-id and someone came up with a SIP profile that corrected my issue. And now I have another issue on the same router when it comes to caller-id on an outbound call. Hopefully someone ca...