.. _cisco-quick-user: Cisco Quick User ----------------------------- .. index:: Quick Add User (Feature) :bdg-primary:`Cisco` .. _19.2.1|VOSS-630|EKB-1208: .. _19.2.1|VOSS-630|EKB-1210: .. _19.3.1|VOSS-577: .. _21.3|EKB-10424: .. _21.3-PB1|EKB-12278: .. _21.3-PB2|EKB-12677: .. _21.4|VOSS-1061: .. _21.4-PB2|EKB-16245: .. _21.4-PB4|EKB-16760: .. _21.4-PB5|EKB-18840: .. _24.1|EKB-18255: .. _24.1-PB2|EKB-21316: .. _24.2|VOSS-1471: .. _24.2|VOSS-1382: .. _25.1|VOSS-1210: .. _25.2|EKB-24946: .. _25.3|EKB-26436: .. _25.4|EKB-27489: .. _25.4|EKB-27248: .. model: view/QuickSubscriber .. tip:: :ref:`use-action-search-to-navigate-automate` Overview ......... Cisco Quick User provides a single page where you can add a Cisco UCM user with a line, a voicemail, and a Webex account, and provision the user with services such as voice, extension mobility, single number reach (SNR), and conferencing and collaboration services. .. note:: During Cisco Quick User provisioning, Cisco-specific identity values (for example usernames for Cisco UCM and Cisco Unity Connection) are automatically populated and maintained by provisioning workflows. These values are derived from the selected user, Quick Add Group, and associated Cisco services, and are not manually managed as part of the Cisco Quick User process. .. important:: Cisco Quick User is a simple, generic method for provisioning users that applies single values from configuration templates (via Quick Add Groups), and the site defaults. For more complex provisioning requirements, such as adding route partitions or multiple values for other service fields (such as two or more lines), use Automate's advanced user management functionality (**Cisco Advanced User**), or bulk loaders. For example, you could use Cisco Quick User to add users with only the first line on phones, then use advanced user management to add the second line to the phone. For details around how Quick Add User handles the application of a Line configuration template associated with a selected Quick Add Group (QAG) when adding or updating a user, see :ref:`shared-lines`. .. rubric:: Supported User Types Quick Add User for UCM users supports several user types, including: * LDAP users * UCM-integrated users * LDAP-integrated users on UCM * Manually created users .. note:: If the default Self-service Language is set on the site default docs (SDD), users are assigned the corresponding Self-service language. .. image:: /src/images/quick-add-subscriber-cucm.png .. rubric:: Related topics * :ref:`provision-webex-app` * :ref:`quick-add-subscriber-class-of-service` * :ref:`provision-the-voice-service` * :ref:`quick-add-subscriber-group-default-model` * :ref:`concepts-config-templates` * :ref:`expose-class-of-service-on-QAS` * :ref:`qas-webex-teams` * :ref:`provision-the-extension-mobility-service` * :ref:`provision-the-pexip-service` * :ref:`provision-the-jabber-device-service` * :ref:`enable-self-provisioning` * :ref:`ini-reserve-for` * :ref:`manage-number-filters` * .. raw:: latex Global Settings in the Core Feature Guide. .. raw:: html Global Settings * .. raw:: latex Introduction to Entitlement in the Core Feature Guide .. raw:: html Introduction to Entitlement .. _qas-configuration: Configure Cisco Quick User ......................................... .. index:: Quick User (Feature);Feature Configuration To create or configure users, to enable users with services, or to associate users with devices, configure the following items on the system: .. tabularcolumns:: |p{5cm}|p{10cm}| +--------------------------------+-------------------------------------------------------------+ | Configuration | Description | +================================+=============================================================+ | 1. Configure servers | Configure the following servers in Automate: | | | | | | * Cisco Unified Communications Manager (UCM) server | | | | | | Adding a UCM server allows the following: | | | | | | * Syncing of manually provisioned users or | | | LDAP-integrated users in UCM to Automate | | | * Syncing in of users phones, directory numbers, | | | extension mobility profiles in UCM to Automate | | | * Creation of users (push users to UCM) | | | * Pushing of users' associated phones, directory numbers, | | | and extension mobility profiles, to UCM. | | | | | | * LDAP server | | | | | | Required only if you want to configure LDAP-synced users | | | in Automate, else, optional. | | | | | | * Cisco Unity Connection (CUC) server | | | | | | Required only if you want to add CUC voicemail users that | | | are configured in Automate. | +--------------------------------+-------------------------------------------------------------+ | 2. Configure dial plans | Provider deployment only. Configure a dial plan at both the | | | customer and site hierarchies. | +--------------------------------+-------------------------------------------------------------+ | 3. Configure voicemail service | Deploy voicemail service with a pilot number created and | | | associated to a site in Automate (via the | | | **Voicemail** page). This step is required to create a | | | "Default CUC User Template" (via the | | | **Site Defaults** page for CUC. | | | The template is required to create CUC | | | voicemail users. | +--------------------------------+-------------------------------------------------------------+ | 4. Configure Webex service | Configure a Webex Server in Automate to deploy any | | | Webex users provisioned through Quick Add User. Set a | | | password for Webex users in the Site Defaults. | +--------------------------------+-------------------------------------------------------------+ Add a user via Cisco Quick User ........................................... This procedure adds a UCM user via Cisco Quick User. .. rubric:: Prerequisites: * Configure **Phones** settings in the Global Settings to select phones by their description or description and line. * Default user template (``voicemailusertemplate``) must exist on UCM. You can update the default by editing the default CUC User Template value in the SDD. * Configure Quick Add Groups. See :ref:`quick-add-subscriber-groups` .. note:: For details around how Quick Add User handles the application of a Line configuration template associated with a selected Quick Add Group (QAG) when adding or updating a user, see :ref:`shared-lines`. * If required, expose device pools and Class of Service (CoS) in Quick Add User. See :ref:`expose-class-of-service-on-QAS` * Ensure site defaults are correctly configured. * Enable filtering at the hierarchy to use inventory filters. See :ref:`enable-disable-filtering`. .. rubric:: Add user via Quick Add User 1. In the Admin Portal, go to **Cisco Quick Add User**. .. note:: * You can switch between a tab or panel layout on this form. * The **Existing Services** tab/panel displays devices and services associated with the user you choose. If the user has existing dual mode devices, the **Phones** field includes details for mobile identity, remote destination, and CTIRD remote destination. Existing services are associated with services enabled/disabled at the customer level via the Global Settings. 2. Configure user details on the **User Details** tab/panel: .. note:: LDAP-synced or LDAP-integrated at UCM user fields are read-only. * Mandatory. Select the username. * If the username you require doesn't exist at the current site, select **Include users at higher hierarchy** to add users above the current site. .. note:: * You can only edit existing UCM users via Quick Add User if these users exist at site level. * The field associated with this checkbox (``lookUpForUser``), is hidden by default. You can expose it via a custom field display policy. This setting is also available for bulk load sheets and API calls. * To prevent adding users that don't exist on UCM, select **Fail Transaction if user not found**. .. note:: The field associated with this checkbox (``failIfNotFound``) is hidden by default. You can expose it via a custom field display policy. By default, the transaction won't fail. This option is used when users have not been synced from LDAP to UCM. This setting is also available for bulk load sheets and API calls. * Mandatory. Fill out a first name and a last name. .. note:: First name is mandatory only if you're provisioning the user with a Webex account. You can set only one Webex account per user. The first name and last name is auto-populated as a display name on the Webex user record. The display name is used when making Webex calls. * Optionally, fill out an email address. If you wish to send the user a welcome email, select **Send welcome email**. .. note:: *Send welcome email* displays only once you add an email address, provided you have the following enabled and configured: * SMTP server must be set up (:ref:`SMTP-server`) * In the Global Settings (Email tab), enable (for the relevant hierarchy) **Allow email to be sent to user after Quick Add User**. See :ref:`global-settings` A welcome email is sent to the user email address using the configured "Quick Add User" HTML email template that applies to the hierarchy. See :ref:`email-setup`. When a welcome email is sent during the Cisco Quick User process, the user's email address is included in the final transaction message. * Fill out a PIN. * Choose an entitlement profile, if one exists, to associate with the user you're adding. * Choose a Quick Add Group (QAG), or select the default. .. note:: Quick Add Groups are filtered by vendor (see :ref:`quick-add-subscriber-vendor-filtering`), and are restricted to those available at a selected hierarchy, based on the option selected for **Quick Add Group & Subscriber Profile lookup level** in the :ref:`global-settings` (**General Settings**). * Choose a device pool. * At **Use next available line**, if you want to enable this functionality (disabled by default), select the checkbox. When enabled: * The system prioritizes local numbers (numbers available at the current site) before checking for available numbers from higher levels in the hierarchy. * Reserved numbers are excluded (numbers reserved for the user you're working with and numbers reserved for other users). * If filtering is also enabled at the hierarchy, select an inventory filter to have the system choose the first available line it finds from the filtered list of numbers. If filtering is disabled, the system automatically selects the next available line. When disabled: * If filtering is enabled at the hierarchy, select the inventory filter, then select the line from the **Directory Number** drop-down. * If filtering is disabled, select a number from the **Directory Number** drop-down. For details around how *Use next available* lines integrates with inventory filters, see :ref:`inventory-filters-and-next-available-line`. .. note:: You can create directory numbers in UCM in two ways: * Create a voice mail line in Quick Add User * Create a line in Quick Add User When creating a voicemail or voicemail line using Quick Add User, the **Directory Number Used** field is set to "true" in the **Number Inventory**. A directory number created without any device associations (for example, a voice mail line), is tagged in the user **Lines** page as *DN created without device from QAS*'. * Select services: .. tabularcolumns:: |p{5cm}|p{10cm}| +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Service | Description | +===========================+===========================================================================================================================================================================================================+ | Voice | Provisions the voice service. Since you can create multiple devices for a user, this checkbox is always available. Selecting the Voice service displays these additional fields: | | | | | | * **Phone Type** (Lists phone types allowed by the entitlement profile, if one exists, else, phone type is retrieved from the QAG) | | | * **Phone Protocol** | | | * **Phone Button Template** (You can override the default phone button template value by entering a custom value in this field. However, the new value is only applied on the UCM if allowed for the | | | phone type.) | | | * **Phone Security Profile** | | | * **Phones** | | | | | | Add one or more phones. You can associate a line with multiple phones, and you can associate a phone with multiple lines. The **Phone Name** drop-down lists available phones at the user's site, | | | based on the phone type specified in the SDD for this site, in the associated QAG at the customer level, or synced from UCM. To add a new phone, you can enter a valid name in the **Phone Name** | | | field. The phone name must consist of a prefix, for instance `SEP`, followed by a MAC address (12 hexadecimal characters). The transaction will fail if you enter the phone name incorrectly | | | (for example, too few or too many characters). | | | | | | Choosing alternative options in these fields overrides values set up in the Quick Add Group (QAG), configuration template (CFT), site defaults document (SDD), or any other backend (read-only) CFTs. If | | | the QAG does not specify a phone template, or if the specified phone template has blank values for the phone fields, the phone field values are pulled from the SDD. To avoid conflicting Quick Add User | | | settings, it is recommended that you configure settings on the Quick Add User page in the following order: | | | | | | 1. Entitlement Profile (only if these exist on the deployment, and are associated with the user) | | | 2. Quick Add Group | | | 3. Voice (then choose phone type, phone protocol, phone button template, and phone security profile) | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Extension Mobility | Provisions extension mobility. Only one extension mobility profile per user, so the checkbox displays only until you create an extension mobility profile. | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Voicemail | Provisions voicemail service. | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ .. tabularcolumns:: |p{5cm}|p{10cm}| +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Service | Description | +===========================+===========================================================================================================================================================================================================+ | Single Number Reach | Provisions single number reach (SNR) service, and allows you to specify the SNR mobile number. If a mobile number is already configured for a user, it is used to pre-populate the Mobile Number | | | field when adding SNR for that user. You can enter a different mobile number for SNR, if required. SNR mobile numbers are formatted with a Plus (+) and the number, for example `+99218732876`. | | | SNR mobile numbers cannot include include spaces, dashes, or other special characters. The SNR mobile number can be the same as the user's number that displays on the **Users** page. | | | | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Jabber / Dual-Mode Device | Provisions Jabber / Dual-mode device service, and allows you to add Jabber and Dual-Mode devices. You can associate multiple Jabber and Dual Mode devices to a user. Jabber and Dual Mode devices get the | | | first line assigned to them (specified in Quick Add User). | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Enable self-provisioning | Defines whether to enable self-provisioning for this user, and allows you to choose the relevant self-provisioning user profile. When enabled, phone lines are added using the Universal Line Template | | | (ULT) referenced in the selected self-provisioning user profile. When adding a user with lines but no devices, or when adding a user with devices and lines, enabling self-provisioning here | | | automatically sets the *UCM User Primary Extension* to the Quick Add User line pattern and ULT route partition. Existing self-provisioning user profiles display on the **User Profile** page, | | | (and can be seen in the site's Site Defaults). You can change this default, if required. | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 3. Save your changes. The user is added. * If you've provisioned SNR (single number reach), verify, on the **Existing Services** tab/panel, that the **Single Number Reach** field displays the SNR profile name, which is the user name, followed by `\"-RDP\"`. For example: `jsmith-RDP`. * If you wish to update a user or their associated services (after adding the user via Quick User), this is done from the relevant service menu items. * For self-provisioned phones to show as being associated with a user, perform a UCM data sync after setting up a self-provisioned phone. .. rubric:: Related Topics * :ref:`ini-reserve-for` * :ref:`global-settings` * :ref:`manage-number-filters` Enable services in Cisco Quick User ........................................... When adding a user via Cisco Quick User, you can enable user services, such as voicemail, extension mobility, single number reach, conferencing (meetings), and collaboration (messaging) services (such as Webex App). The Quick Add User page displays services included in a selected entitlement profile (if entitlement profiles are used). For example, if the entitlement profile excludes voice services, the checkboxes for Voice, Jabber, and Self Service ID won't appear on the page. The selected entitlement profile also filters options available in the **Phone Type** drop-down (showing only devices enabled in the entitlement profile). .. note:: It is possible to use Cisco Quick User to add a user without an entitlement profile. For example, entitlement profiles may not exist on the deployment, or they may not be associated with the user. In this case, a phone type, for example, may still be associated with the user via the Quick Add Group (QAG). For the Voicemail service: * Configuration settings are only available if the site's SDD has a default value on the CUC Defaults tab for the Default CUC User Template. The default value (``voicemailusertemplate``) should already exist on the UCM and is automatically populated on an HCS system when a voicemail pilot is created. * A CUC device must be configured at the related Network Device List (NDL), at site level. * If the selected QAG specifies any CFT entries for UserPin or UserPassword, these are applied. Otherwise, the values from the User Template defined on CUC apply. For default CFTs, see: :ref:`quick-add-subscriber-group-default-model`. While the Admin Portal hides configuration settings for unavailable services, API and bulk load operations have provisioning workflow checks that check for the presence of the Default CUC User Template in the SDD and a configured Webex server in the NDL, before the selected services can be added. A UCM (call manager) must be configured at the user's hierarchy. If this does not exist, the Quick Add User bulk load transactions and API calls display the following warning: *No Call Manager has been configured* .. _qas-webex-teams: Add Webex App service using Quick Add User ................................................... .. note:: When using Quick Add User to provision WebexApp services, the SiteDefaultsDoc - **User Defaults** tab values should be set to either: * **Webex App - Use Organization's Domain** = True or * **Webex App - UC Manager Profile** = Selecting the **Webex App** checkbox on the Quick Add User page displays the **Webex Teams User Template** drop-down, where you can select a **Webex Teams User Template** to apply to the user. * Choosing a template from the drop-down overrides the default user template referenced in the Quick Add User Group (QAG) associated with the user. * If you don't select a **Webex Teams User Template** from the drop-down, the **Webex App User Template** referenced in the associated QAG is applied. If you want customized values, clone the **Webex Teams User Template** (**Customizations > Configuration Templates**) and edit as required. The Webex Teams User Template for UCM Calling provides for a **Settings** group of controls for the specification of Calling Behavior and provisioning of Jabber devices if relevant to the calling behavior. .. _Contact-Center-Agent-Quick-Add: Add a Contact Center agent using Quick Add User .......................................................... You can use Quick Add User to create a Contact Center (UCCX) agent. The **Contact Center Agent** checkbox displays if: * The associated Entitlement Profile has Contact Center enabled * A Contact Center Server is available at the hierarchy. .. raw:: latex See *Configure UCCX server* in the Core Feature Guide. .. raw:: html See Configure UCCX server * The selected user is not already associated with an Agent If the checkbox is selected: * A **Contact Center Agent Profile** drop-down list is available to select an agent profile. .. note:: The **Contact Center Agent Profile** needs to be created before adding the Contact Center Agent from the Quick Add User feature. The agent profile will determine the team, resource group and skills assigned to the newly created agent. See *Agent Profiles*. * The **Agent Extension** can be selected. The extension will be a list of specified Lines, in other words, the administrator must specify the Line to be created or reused before selecting the **Contact Center** check box. * The **Agent Device Type** can be selected: either Extension Mobility or Phone: * If Extension Mobility is selected, the **Extension Mobility** check box is automatically enabled. * If Phone is selected, the administrator must first enable **Voice** and specify a Phone to be created or reused before selecting the **Contact Center** check box. An IPCC extension is automatically managed for the UCM user associated with the Contact Center agent. .. rubric:: Related topics * .. raw:: latex Contact Center in the User Guide .. raw:: html Contact Center .. _quick-add-subscriber-device-pool: Quick Add User device pool ................................... When adding a user via Cisco Quick User, you can associate a device pool to the user's newly associated devices or services (other than the device pool provided in the Site Defaults Doc or referenced configuration template in the Quick Add Group). A device pool contains system, device, and location-related information, and is mandatory when adding a user using Cisco Quick User. A device pool can be referenced by: * Site Defaults Doc (SDD) * Reference Configuration Template (CFT) referenced in the Quick Add User Group (QAG) * Admin Portal (if exposed) .. rubric:: Device pool and Site Defaults Doc The device pool referenced in the SDD ensures that a user's devices are always associated to a device pool. If there is no device pool referenced in either the QAG or Admin Portal drop-down (see below) the value defaults to the SDD. .. rubric:: Device pool and Quick Add Group The device pool referenced by a Configuration Template (CFT) in the QAG takes precedence over the device pool referenced in either the SDD or the Admin Portal drop-down (if exposed). See Quick Add Groups for details. .. rubric:: Device pool and Admin Portal An administrator can expose a **Device Pool** drop-down on the Quick Add User page on the Admin Portal by editing or cloning the Field Display Policy. See :ref:`expose-class-of-service-on-QAS`. The **Device Pool** drop-down allows an administrator to overwrite the value in the SDD by selecting a custom device pool from the drop-down list. The options available in the list are the site-level device pools if they are available, otherwise it displays all device pools available at customer level (NDLR aware). .. note:: * Where multiple device pools are available at a site, a load balance check is available on the number of phones using the Device Pools in order to assign the phone to the least used device pool. Contact VOSS if this load balance check is required. * When exposing the **Device Pool** drop-down, the administrator **must** remove the value in the **Device Pool** field of the CFT referenced in the QAG, that is, the field must be blank. This is done to ensure that the value in the CFT does not overwrite the custom value in the drop-down. The CFTs and their target models for which the device pool name can be made blank to allow the Portal to drive the device pool selection include: * Phone templates (device/cucm/Phone) * Jabber device templates (device/cucm/Phone) * Remote Destination Profile templates (device/cucm/RemoteDestinationProfile) .. _quick-add-subscriber-class-of-service: Cisco Quick User Class of Service ........................................ With Cisco Quick User you can associate Calling Search Space (CSS) values to a user's newly associated lines, devices, or services (other than the CSS's provided in the Site Defaults Doc or referenced configuration template in the Quick Add Group), by selecting a Class of Service (CoS). A Class of Service (CoS) allows you to specify a Calling Search Space (CSS) for devices and lines. A CSS is mandatory for lines and devices when adding a user using Quick Add User. A CSS can be referenced by: * Site Defaults Doc (SDD) * Reference Configuration Template (CFT) referenced in the Quick Add Group (QAG) * Admin Portal, via the Class of Service field (if exposed) .. rubric:: Class of Service and Site Defaults Doc The Calling Search Space values referenced in the SDD ensure that a user's lines and devices always have a Calling Search Space associated to it. If there are no Calling Search Space values referenced in either the Quick Add Group or via the Class of Service field in the Admin Portal drop-down (see below) the value defaults to the SDD. .. rubric:: Class of Service and Quick Add Group The Calling Search Space values referenced by a Configuration Template (CFT) in the Quick Add Group take precedence over the Calling Search Space values referenced in either the SDD or the Class of Service via the Admin Portal drop-down (if exposed). See Quick Add Groups for details. .. rubric:: Class of Service and Admin Portal An administrator can expose a **Class of Service** drop-down on the Quick Add User page on the Admin Portal by editing or cloning the Field Display Policy. See :ref:`expose-class-of-service-on-QAS`. The **Class of Service** drop-down allows an administrator to overwrite the Calling Search Space values in the SDD by selecting a custom Class of Service from the drop-down list. The Class of Service, in turn, contains a custom Calling Search Space for lines and devices, respectively. The options available in the list are the customer-level Class of Service instances, as created by the relevant administrator. .. note:: When exposing the **Class of Service** drop-down, the administrator **must** remove the values in the Calling Search Space fields of the CFT's referenced in the QAG, that is, the field must be blank. This ensures that the value in the CFT does not overwrite the custom Calling Search Space value as defined in the selected Class of Service. The CFTs and their target models for which the Calling Search Space name can be made blank to allow the Portal to drive the Calling Search Space values include: * Line templates (device/cucm/Line) * Phone templates (device/cucm/Phone) * Jabber device templates (device/cucm/Phone) * Remote Destination Profile templates (device/cucm/RemoteDestinationProfile) .. _expose-class-of-service-on-QAS: Expose device pools and Class of Service in Cisco Quick User .................................................................... This procedure exposes the **Device Pools** field and **Class of Service (CoS)** field on the Cisco Quick User form, at a specified hierarchy. **Pre-requisites**: * You must be logged on as an administrator with access to Field Display Policies (FDP) **Perform these steps**: 1. In the Admin Portal, go to **Field Display Policies**. 2. Filter the **Target Model Type** on ``view/QuickSubscriber``. 3. Choose an option, depending on the hierarchy where the **Device Pools** or **Class of Service** fields should be exposed in Cisco Quick User: * **The FDP exists at the correct hierarchy**? Click on the FDP to open it. * **The FDP does not exist at the required hierarchy**? Clone one of the FDPs at a hierarchy above the required hierarchy. 4. Open the FDP to edit it, and go to the first group's **Available** list in the **Fields** block. 5. Select **device_pool** or **class_of_service**, then click the **Move** icon to move the **device_pool** or **class_of_service** from the **Available** list to the **Selected** list. 6. Use the **Move up** and **Move down** icons to move the label to the desired position relative the the other field labels. 7. Ensure that the cloned FDP name is "default", then click **Save**. 8. If you're at the hierarchy where the cloned FDP is created or at a lower hierarchy, go to **Cisco Quick User**, where you will see the relevant field exposed (either **Device Pools** or **Class of Service**). .. _provision-the-voice-service: Provision the voice service ................................ This procedure provisions a voice service in Cisco Quick User. 1. Go to **Cisco Quick User**. 2. Select a user from the **Username** drop-down; then, select the **Voice** checkbox. 3. Optionally, select phone details in these fields: * Phone Type * Phone Protocol * Phone Button Template * Phone Security Profile .. note:: * To prevent conflicting Quick User settings, fill out the optional fields in the order displayed on the form. * Default values depend on the selected Quick Add Group (QAG). New values you define for the optional fields override existing values in QAG, CFT (configuration template), and in any other backend (non-editable) CFTs. The system populates any fields left blank with values from QAG, CFT, SDD (Site Defaults Document), or other backend CFTs. * The template you select (for example, *Phone Type*), must exist in the QAG and must be allowed by the entitlement profile, which filters the **Phone Type** drop-down to display only devices enabled by this profile. * If a phone button template is not specified in QAG, or if the specified phone button template has blank values for the phone fields, the phone field values are pulled from the SDD. To override the default phone button template, enter a new value in the **Phone Button Template** field. The new value is applied on Unified CM, if it allows the phone type. 4. (Mandatory). In the **Lines** section, select a line from the **Directory Number** drop-down. .. note:: The line must be one of the directory numbers in **Subscriber Management > Directory Number Inventory**. 5. (Mandatory). In the **Phones** section, select a phone from the **Phone Name** drop-down. .. important:: * Phones available in this drop-down are: * In the assigned Quick Add Subscriber Group, which have possibly synced from Unified CM * Available at the specific site * Not currently owned by any other user The ability to associate an existing, un-associated phone to a user in Cisco Quick User depends on the Global Settings setup for phones. * If you wish to add a new phone, enter a valid name in the **Phone Name** field. Ensure you enter the phone name correctly (including the correct number of characters). The phone name must have: * A prefix (such as SEP) * A MAC address (12 hexadecimal characters) To add more phones, repeat this step until you have all the phones you need. 6. Click **Save**. .. rubric:: Related topics * :ref:`global-settings` .. _provision-the-jabber-device-service: Provisioning the Jabber or dual mode device service ...................................................... .. _18.1-Patch-Bundle-3|EKB-261: .. _19.3.4|EKB-6094: .. tip:: :ref:`use-action-search-to-navigate-automate` This procedure provisions a user with the Jabber or dual mode device service, using Quick User. 1. Go to **Quick User**. #. From the **Username** drop-down, choose a user. #. Select the **Jabber/Dual-Mode Device** checkbox. The **Jabber and Dual-Mode Devices** field appears. #. Click the Plus icon (+) at **Jabber and Dual-Mode Devices** to expose the **Jabber/Dual Mode Agent** drop-down and **Device Name** field. #. At **Jabber/Dual Mode Agent**, choose a device type. The **Device Name** field is automatically generated as follows: a. If no device name exists in the format ````, then in this format: ```` b. If device name exists in the format ```` or ````, then in the format: ```` where ```` is generated and unique. * ````: Always three characters, either BOT, CSF, TAB, TCT, CIM, or CTI. * ````: Maximum 8 characters. If a username contains '_' and '.' characters, these characters are removed from the automatically generated username. Automatically generated usernames can be edited if required. * ````: Dependent on length of username, to make up a total of 11 characters along with the username. See examples in table below. Example Device Type and Device Name Combinations +------------------------------------------+----------------------------------------+ | For this type of device | Device Name (automatically generated) | | | | | | Format (regex): "[a-zA-Z0-9]{1,15}" | +==========================================+========================================+ | Android | For example: BOTJOHND003938 | | (Cisco Dual Mode for Android) | | +------------------------------------------+----------------------------------------+ | CSF | For example: CSFROBWOR77891 | | (Cisco Unified Client Services Framework)| | +------------------------------------------+----------------------------------------+ | iPad | For example: TABRQUENT18947 | | (Cisco Jabber for Tablet) | | +------------------------------------------+----------------------------------------+ | iPhone | For example: TCTPDEVILLI156 | | (Cisco Dual Mode for iPhone) | | +------------------------------------------+----------------------------------------+ | Carrier Integrated Mobile | For example: CIMJOHNSMI | +------------------------------------------+----------------------------------------+ | CTI Remote Device | For example: CTIJOHNSMI | +------------------------------------------+----------------------------------------+ For the following Agents, also select the **Mobile Identity** checkbox to enable Mobile Identity if required: * Android * iPhone * Carrier Integrated Mobile #. Click **Save**. #. Go to **Quick User**. #. From the **Username** list, choose the same user. #. On the **Existing Services** tab, ensure that the **Phones** field displays the Jabber device. For each device type, a Configuration Template that is associated with the user's Quick Add Group is used to provision the device. For defaults, see: :ref:`quick-add-subscriber-group-default-model`. .. note:: If a CSF Jabber device type is selected, all lines are associated to the CSF Jabber device by default. .. _provision-the-extension-mobility-service: Provision extension mobility ............................................ .. tip:: :ref:`use-action-search-to-navigate-automate` Overview '''''''''''' Enabling extension mobility via Quick User creates a device profile for the user on CallManager (the call processing component of CUCM). A CUCM user device profile may be considered a dummy phone with lines. When the user logs in to a physical phone associated with the CallManager and enters their username and pin, CallManager applies their device profile to the phone (with their line, settings, and extension number), effectively assigning ownership of the phone to the user for the period they're logged in. Provided a user is logged in to a physical phone via their device profile username and pin, they're always reachable via the extension number assigned to their device profile, regardless of the physical device they're using. The user's extension number is associated with their device profile and not to a physical device and is thus always 'mobile'. |device-profile-config-cucm| .. rubric:: Related topics * .. raw:: latex Introduction to EMCC in the Core Feature Guide .. raw:: html Introduction to EMCC * .. raw:: latex Configuration Templates in the Core Feature Guide .. raw:: html Configuration Templates * .. raw:: latex Extension mobility in the Core Feature Guide .. raw:: html Extension mobility EMCC and multi-cluster CallManager '''''''''''''''''''''''''''''''''''' A large organization (set up at the Customer hierarchy) may have multiple CallManager clusters (separate CallManager servers in a multi-cluster setup). For example, a CallManager cluster located in London (providing phones and services to the London office), and a CallManager cluster located in New York (providing phones and services to the New York office). In this scenario, CallManager allows inter-cluster calls between these locations; each CallManager has a different IP address, and each has different data (the phones, users, and services, for either London or New York, in this case). |apps-management-cucm-servers| A CUCM administrator configures cross-cluster via the CUCM Extension Mobility Cross Cluster (EMCC) feature settings on CUCM, and in VOSS (via the **EMCC** page). Once configured on CUCM, EMCC may be enabled per user in CUCM, and a EMCC calling search space (CSS) is chosen for the user device profile. |cucm-device-profile-choose-emcc-css| .. note:: In VOSS, EMCC groups define the clusters and countries to be used together for extension mobility. When saving an EMCC group, VOSS creates the relevant route partitions, device pools, and the CSS related to the countries selected for the EMCC group. A user enabled for EMCC can use their extension at another location that is part of the cluster. For example, a user can log in to a desk phone in London in the morning, travel to New York, and log in to a desk phone at the New York office when they arrive. Regardless of their physical location, the user remains reachable via the same extension number, provided they're logged in to a physical phone in a connected cluster, using their home cluster device profile username and pin. EMCC, Quick User, and configuration templates '''''''''''''''''''''''''''''''''''''''''''''''' Quick User references a selected Quick Add Group, which contains a number of configuration templates that define values for various settings. For example, the CUCM user template, or the extension mobility template (which defines the user device profile settings). For example, you can assign to the QAG, a CUCM user template that has **Enable Extension Mobility Cross Cluster** set to *True*, so that all subscribers added via Quick User with this QAG are automatically enabled for EMCC. |customizations-config-template-cucm-user-template| EMCC device profiles and extension mobility profiles '''''''''''''''''''''''''''''''''''''''''''''''''''''' A CallManager device profile is called an extension mobility profile in VOSS. Device profiles are configured in VOSS via device profile configuration templates. EMCC CSS may be automatically assigned via device profile configuration template. Assigning extension mobility via Quick User '''''''''''''''''''''''''''''''''''''''''''''' 1. Go to **Quick User**, and choose a user from the **Username** drop-down list. 2. Select **Extension Mobility**. |qas-extension-mobility| 3. To enable EMCC, select **EMCC**. .. note:: The **EMCC** checkbox displays only if you've selected the **Extension Mobility** checkbox. 4. Click **Save**. * The CUCM user is added on CUCM. * The CUCM device profile user is added on CUCM, based on settings in the device profile configuration template in the QAG. * The device profile is associated with the CUCM user. * If you've enabled EMCC: * EMCC is enabled for the device profile on CUCM. * The EMCC calling search space (CSS) is set for the device profile. The CSS name is based on the country associated with the site, for example, ``EMCC-CSS-USA`` * The device profile is subscribed to the ``EMCC Login/Logout`` phone service on CUCM (which will allow the user to log in and log out of a physical device to use their extension remotely). Automate requires this service to exist on CUCM, or the provisioning will fail. 5. Verify that the extension mobility profile name appears in the **Extension Mobility Profiles** field on the **Existing Services** tab. .. note:: Extension mobility can also be enabled and inspected via the **User Management** list view (click on the user and check the settings on the following tabs: * User * Extension Mobility .. _enable-self-provisioning: Enable self-provisioning '''''''''''''''''''''''''' This procedure enables self-provisioning via Quick User. .. tip:: :ref:`use-action-search-to-navigate-automate` 1. Go to **Quick User**, then, from the **Username** drop-down, select a user. 2. Select the **Enable Self Provisioning** checkbox. The **Self Provisioning User Profile** drop-down appears. 3. From the **Self Provisioning User Profile** drop-down, choose a Self Provisioning User Profile. These were previously created under **User Profile**. 4. In the **Lines** field, click the Plus icon (+) to display the **Directory Number** drop-down. 5. Choose a line from the **Directory Number** drop-down. 6. Click **Save**. 7. Manage the user and verify that the **Self-service** and **User Profile** fields display the same settings as those set in Quick User. .. |qas-extension-mobility| image:: /src/images/qas-extension-mobility.png .. |device-profile-config-cucm| image:: /src/images/device-profile-config-cucm.png .. |apps-management-cucm-servers| image:: /src/images/apps-management-cucm-servers.png .. |customizations-config-template-cucm-user-template| image:: /src/images/customizations-config-template-cucm-user-template.png .. |cucm-device-profile-choose-emcc-css| image:: /src/images/cucm-device-profile-choose-emcc-css.png