Step 1
| Log in to the
Cisco
Unified CM Administration interface.
|
Step 2
| Select
.
Find and List Phones window opens. |
Step 3
| Select
Add
New.
|
Step 4
| From the Phone Type drop-down list, select the option that is applicable to the device type you are configuring and then select Next.
For Jabber users, you can only create one type of device per user although you can create multiple devices for each user. For example, you can create one tablet device and one CSF device but not two CSF devices.
|
Step 5
| From the
Owner
User ID drop-down list, select the user for whom you want to create
the device.
For the
Cisco Unified Client Services Framework option in a
Phone mode deployment, ensure that
User is selected.
|
Step 6
| In the
Device
Name field, use the applicable format to specify a name for the
device:
If
You Select
|
Required Format
|
CTI Remote
Device
|
-
When you select Owner User ID, the device name field populates with
CTIRD<owner user ID>. You can change this value.
The device name does not have to begin with
CTIRD.
-
Valid characters: a–z, A–Z, 0–9, period (.), underscore (_),
hyphen (-).
-
15-character limit.
|
Cisco Unified Client
Services Framework
|
|
Cisco Dual Mode for
iPhone
|
-
The device name must begin with
TCT.
For example, if you create a TCT device for user, Tanya Adams,
whose username is tadams, enter
TCTTADAMS.
Must be uppercase.
-
Valid characters: A–Z, 0–9, period (.), underscore (_),
hyphen (-).
-
15-character limit.
|
Cisco Jabber for
Tablet
|
-
The device name must begin with
TAB.
For example, if you create a TAB device for user, Tanya Adams,
whose username is tadams, enter
TABTADAMS.
Must be uppercase.
-
Valid characters: A–Z, 0–9, period (.), underscore (_),
hyphen (-).
-
15-character limit.
|
Cisco Dual Mode for
Android
|
-
The device name must begin with
BOT.
For example, if you create a BOT device for user, Tanya Adams,
whose username is tadams, enter
BOTTADAMS.
Must be uppercase.
-
Valid characters: A–Z, 0–9, period (.), underscore (_),
hyphen (-).
-
15-character limit.
|
|
Step 7
| If you are
creating a CTI Remote Device, in the
Protocol Specific Information section, select an
appropriate option from the
Rerouting Calling Search Space drop-down list.
The Rerouting
Calling Search Space defines the calling search space for rerouting and ensures
that users can send and receive calls from the CTI remote device.
|
Step 8
| To generate an
authentication string that you can provide to end users to access their devices
and securely register to Cisco Unified Communications Manager, navigate to the
Certification Authority Proxy Function (CAPF)
Information section.
|
Step 9
| From the
Certificate Operation drop-down list, select
Install/Upgrade.
|
Step 10
| From the
Authentication Mode drop-down list, select
By
Authentication String or
By
Null String.
Note
|
Using the CAPF Authentication mode By Null String with VXME and Jabber for Windows CSF devices is not supported. It causes Jabber registration with Cisco Unified Communications Manager (CUCM) to fail.
|
|
Step 11
| Click
Generate String.
The
Authentication String autopopulates with a string value. This is the string
that you will provide to end users.
|
Step 12
| From the
Key
Size (Bits) drop-down list, select the same key size that you set
in the phone security profile.
|
Step 13
| In the Operation Completes By fields, specify an expiration value for the authentication string or leave as default. |
Step 14
| If you are using a group configuration file, specify it in the Cisco Support Field of the Desktop Client Settings. Cisco Jabber does not use any other settings that are available on the Desktop Client Settings. |
Step 15
| Select
Save.
|
Step 16
| Click
Apply Config.
|