Overview

The auto-provisioning feature in Control Hub enables the self-provisioning of the user's devices in Unified CM for Calling in Dedicated Instance without any administrator's intervention. This feature avoids over-provisioning of multiple devices for a user in Unified CM and eliminates the need of approaching the administrator every time their personal device is changed. Devices are auto created in Unified CM, when a user is provisioned for Calling in Webex (Unified CM) and signs in with their registered email address or User ID to Webex App.

Administrators are not required to go to Unified CM to pre-provision any of the Webex App devices for users in their organization. When the user signs in to the Webex App using any device for the first time, the new device type is auto created for the user even if the device is not already available in the Unified CM server.

This feature allows auto-provisioning of following device types in Unified CM for the users when they sign into Webex App from various device platforms:

  • Android Device (BOT)

  • Chromebook/iPad Devices (TAB)

  • Windows/MAC Devices (CSF)

  • iPhone Device (TCT)

Enable-Disable Auto-Provisioning

Before you plan to allow auto-provisioning of Webex App devices in the Unified CM, make sure that the following requirements are met:

  • The minimum supported Webex App version is 41.12 and higher.

  • Ensure that the User ID or email ID of Unified CM users matches with the User ID of the user records entity in Webex Identity Service. Also, the users configured in the Unified CM server should be available in the organizations’ Webex Identity Service.

You can choose to auto-provision the device type for a user at the organization level and at user calling settings level.

Organization Settings

  1. From the customer view in Control Hub (https://admin.webex.com), go to Services > Calling > Client Settings.

  2. Define the policy to determine which devices are allowed for Auto-provisioning. Choose from an option:

    • Desktop and mobile

    • Desktop only

    • Mobile only

    You can configure auto-provisioning Webex app for users on desktop, mobile, or both.

    You can also change this setting at the user level for specific users in Control Hub. For user level settings, see User Settings.


    The user level settings take priority over the organization’s default level settings for the auto-provisioning of Webex app feature.

User Settings

  1. From the customer view in https://admin.webex.com, go to Management > Users.

  2. Select the user to modify and click Calling.

  3. Under Unified Communications Manager settings, select the allowed device option from the drop-down list. The default device type is Desktop and mobile.

    • Desktop and mobile

    • Desktop only

    • Mobile only

Device Type and Template Settings

Following table lists the scenarios and the template settings used when a new device is created.

Scenarios Existing Devices Settings Used for New Device
User logs in for the first time from a new mobile or desktop device No device available

Device Settings—User profile device template is used in the following order of preference:

  1. Mobile and desktop Universal Device Template (UDT)

  2. Cisco IP Phone (desk phone) UDT

  3. Auto-registration template (system defined) of the cluster is used, if UDT is not available.


 

Device creation fails if none of the above 3 options are available.

Phone Button Template—Standard Model Specific Template

User logs in for the first time from a new mobile or desktop device Any device

Device Settings—Users' existing device settings is used for the new device in the following order of preference: Mobile, Desktop, or Cisco IP Phone.

Phone Button Template—Standard Model Specific Phone Button Template

Phone Security Data for New Devices Provisioned

Based on the old phone security profile, the new phone chooses one of these new profiles for a newly created device.

Old Security Profile Settings New Mapped Profile Name
Universal Security Profile (model independent) Universal Security Profile (model independent)
Standard Model Specific Security Profile Standard New Model Specific Security Profile
Custom Model Specific Security Profile Standard New Model Specific Security Profile
Custom Universal Security Profile (model independent) Custom Universal Security Profile (model independent)