Self-Provisioning feature helps you provision phones for your network by giving
end users the ability to provision their own phones without contacting an
administrator. If the system is configured for self-provisioning, and an
individual end user is enabled for self-provisioning, that end user can
provision a new phone by plugging the phone into the network and then following
a few prompts. Cisco Unified Communications Manager configures the phone and
the phone line by applying pre-configured templates.
can be used either by administrators to provision phones on behalf of their end
users, or end users can use self-provisioning to provision their own phones.
You can configure
self-provisioning in one of two modes:
secure mode, users or administrators must be authenticated in order to access
self-provisioning. End users can be authenticated against their password or
PIN. Administrators can enter a pre-configured authentication code.
mode—In non-secure mode, users or administrators can enter their user ID, or a
self-provisioning ID, in order to associate the phone to a user account.
Non-secure mode is not recommended for day-to-day use.
through Universal Line and Device Templates
uses the universal line template and universal device template configurations
to configure provisioned phones and phone lines for an end user. When a user
provisions their own phone, the system references the user profile for that
user and applies the associated universal line template to the provisioned
phone line and the universal device template to the provisioned phone.
Once the feature
is configured, you can provision a phone by doing the following:
Plug the phone
into the network.
self-provisioning IVR extension.
prompts to configure the phone, and associate the phone to an end user.
Depending on how you have configured self-provisioning, the end user may to
enter the user password, PIN, or an administrative authentication code.
you are provisioning a large number of phones on behalf of your end users,
configure a speed dial on the universal device template that forwards to the
self-provisioning IVR extension.
Before your end users can use self-provisioning, your end users be configured with the following items:
Your end users
must have a primary extension.
Your end users must be associated to a user profile or feature group template that includes a universal line template, universal device template. The user profile must be enabled for self-provisioning. For details, see User Profile Configuration Task Flow.
From Cisco Unified CM Administration, choose, Device > CTI Route Points.
Complete either of the following steps:
Click Find and select an existing CTI route point.
Click Add New to create a new CTI route point.
In the Device Name field, enter a unique name to identify the route point.
From the Device Pool drop-down list box, select the device pool that specifies the properties for this device.
From the Location drop-down list box, select the appropriate location for this CTI route point.
From the Use Trusted Relay Point drop-down list box, enable or disable whether Cisco Unified Communications Manager inserts a trusted relay point (TRP) device with this media endpoint. The default setting is to use the Common Device Configuration setting that is associated to this device.
Complete the remaining fields in the CTI Route Point Configuration window. for help with the fields and their settings, refer to the online help.
Use this procedure to set up the extension that users will dial in order to access the self-provisioning IVR. You must associate this extension to the CTI route point that you want to use for self-provisioning.
Use this procedure
to configure your system for self-provisioning. Self-provisioning provides
users in your network with the ability to add their own desk phone or soft
client through an IVR system, without contacting an administrator.
In order to use
the self-provisioning feature, your end users must also have the feature
enabled in their user profiles.
Unified CM Administration, choose
Management > Self-Provisioning.
whether you want the self-provisioning IVR to authenticate end users by
clicking one of the following radio buttons:
Authentication—In order to use the self-provisioning IVR, end users
must enter their password, PIN, or a system authentication code.
Required—End users can access the self-provisioning IVR without
self-provisioning IVR is configured to require authentication, click one of the
following radio buttons to configure the method whereby the IVR authenticates
Allow authentication for
end users only—End users must enter their password or PIN.
Allow authentication for
users (via Password/PIN) and Administrators (via Authentication
Code)—End Users must enter an authentication code. If you choose
this option, configure the authentication code by entering an integer between 0
and 20 digits in the
Authentication Code text box.
Settings list boxes, use the arrows to select the Language that you
prefer to use for IVR prompts. The list of available languages depends on the
language packs that you have installed on your system. Refer to the Downloads
section of cisco.com if you want to download additional language packs.
Route Points drop-down list box, choose the CTI route point that
you have configured for your self-provisioning IVR.
Application User drop-down list box, choose the
application user that you have configured for self-provisioning.
What to Do Next
Optional. If you have a secure cluster that is operating in mixed mode, enable self-provisioning for secure clusters:
Perform the following tasks only if you want to use self-provisioning and your cluster is operating in mixed mode.
You can verify the security status by confirming that the Cluster Security Status enterprise parameter is set to 1 (Mixed). For details on how to set up cluster security for Cisco Unified Communications Manager, see the Security Guide for Cisco Unified Communications Manager.
On the machine that has JTAPI installed, locate the JTAPI client library folder. For example, on a Windows 7 machine, the path is C:\Program Files\Cisco\JTAPI64Tools\lib.
In a text editor such as Notepad, edit the jtapi.ini file as follows:
Find the SecurityProperty line.
In the SecurityProperty line, change the filepath from your local machine (for example, C\:/Program Files/Cisco/JTAPI64Tools/lib/) to the path that will be used on Cisco Unified Communications Manager (for example, /usr/local/cm/jar/).
Copy the following files from Cisco JTAPI machine to the /usr/local/cm/jar/ folder on the Cisco Unified Communications Manager publisher node:
Copy the keys from the JTAPI client library folder to the /usr/local/cm/jar/ folder on the Cisco Unified Communications Manager publisher node:
JtapiClientKeyStore,-<Application User>-<instance id>. For example, JtapiClientKeyStore-appUser-5555
JtapiServerKeyStore-<callmanager IP>. For example, JtapiClientKeyStore-10.10.10.5