[Index]

Model: view/QuickSubscriber

Quick Add Subscriber

Full HTML Help

CISCO

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.

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

Related topics

• Provision Webex App
• Quick Add User Device Pool
• Quick Add User Class of Service
• Provision the Voice Service
• Quick Add Groups default model
• Configuration Templates
• Expose Device Pools and Class of Service in Quick Add User
• Webex Teams Quick Add
• Provision the Extension Mobility Service
• Provision the PexIP Conference Service
• Provision the Jabber or Dual Mode Device Service
• Provision the Contact Center Agent
• Enable Self Provisioning
• Reserve a Number for a User
• Manage Number Filters

Global Settings in the Core Feature Guide.

Introduction to Entitlement in the Core Feature Guide

Configure Cisco Quick User

To create or configure users, to enable users with services, or to associate users with devices, configure the following items on the system:

Add a user via Cisco Quick User

This procedure adds a UCM user via Cisco Quick User.

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 Quick Add 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 Shared Lines.

• If required, expose device pools and Class of Service (CoS) in Quick Add User. See Expose Device Pools and Class of Service in Quick Add User

• Ensure site defaults are correctly configured.

• Enable filtering at the hierarchy to use inventory filters. See Enable or disable filtering.

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 (Add a 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 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 Email.

   • 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 Quick Add Groups 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 Global Settings (General Settings).

   • Choose a device pool.

   • At Use next available line, select the checkbox to have the system automatically select the next available line that the system finds. This functionality is disabled by default.

     • When enabling Use next available line, and filtering is 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 disabling Use next available line, and 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 Inventory filters and "Use 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:

     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: Entitlement Profile (only if these exist on the deployment, and are associated with the user) Quick Add Group 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.

     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.

Related Topics

• Reserve a Number for a User
• Global Settings
• 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).

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: Quick Add Groups 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

Add Webex App service using Quick Add User

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.

Add a Contact Center agent using Quick Add User

• refer to UCCX Feature Reference

You can use Quick Add User to create a Contact Center (UCCX) agent.

The Contact Center Agent check box becomes visible if:

• The associated Entitlement Profile has Contact Center enabled
• A Contact Center Server is available at the hierarchy - Contact Center Servers
• The selected user is not already associated with an Agent

If the check box 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.

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)

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.

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.

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 Expose Device Pools and Class of Service in Quick Add User. 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).

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)

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.

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.

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 Expose Device Pools and Class of Service in Quick Add User. 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.

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 extension mobility service

Full HTML Help

Overview

In Automate, enabling extension mobility via Quick Add Subscriber (QAS) 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'.

Related Topics

Introduction to EMCC in the Core Feature Guide

Configuration Templates in the Core Feature Guide

Extension Mobility Profiles in the Core Feature Guide

EMCC and Multi-Cluster CallManager

A large organization (set up at the Automate 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).

A CUCM administrator configures cross-cluster via the CUCM Extension Mobility Cross Cluster (EMCC) feature settings on CUCM, and in Automate (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.

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.

Quick Add Subscriber and Configuration Templates

QAS references a selected QAG, 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 QAS with this QAG are automatically enabled for EMCC.

Device Profiles and Extension Mobility Profiles

A CallManager device profile is called an extension mobility profile in Automate. Device profiles are configured in Automate via device profile configuration templates. EMCC CSS may be automatically assigned via device profile configuration template.

Assigning extension mobility via QAS

1. Go to Quick Add Subscriber, and choose a user from the Username drop-down list.

2. Select 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.

Provision the Jabber or dual mode device service

Full HTML Help

This procedure provisions a user with the Jabber or dual mode device service, using Quick Add User.

1. Go to Quick Add User.

2. From the Username drop-down, choose a user.

3. Select the Jabber/Dual-Mode Device checkbox. The Jabber and Dual-Mode Devices field appears.

4. Click the Plus icon (+) at Jabber and Dual-Mode Devices to expose the Jabber/Dual Mode Agent drop-down and Device Name field.

5. At Jabber/Dual Mode Agent, choose a device type. The Device Name field is automatically generated as follows:

   1. If no device name exists in the format <device type prefix><username>, then in this format:

      <device type prefix><username>

   2. If device name exists in the format <device type prefix><username> or <device type prefix><username><number>, then in the format:

      <device type prefix><username><random number>

      where <random number> is generated and unique.

   • <device type prefix> - always three characters, either BOT, CSF, TAB, TCT, CIM, or CTI.
   • <username> - 8 characters maximum. If a username contains '_' and '.' characters, these characters are removed from the automatically generated username. Automatically generated usernames can be edited if required.
   • <random number> - 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 (Cisco Dual Mode for Android)	For example: BOTJOHND003938
   CSF (Cisco Unified Client Services Framework)	For example: CSFROBWOR77891
   iPad (Cisco Jabber for Tablet)	For example: TABRQUENT18947
   iPhone (Cisco Dual Mode for iPhone)	For example: TCTPDEVILLI156
   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

6. Click Save.

7. Go to Quick Add User.

8. From the Username list, choose the same user.

9. 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: Quick Add Groups default model.

Cisco Webex App users

Full HTML Help

Overview

You can add Cisco Webex App users into Automate in various ways:

• Add Webex App User (relation/SparkUser)

  Webex Contact Center agents can be added if a user is assigned a Contact Center Premium Agent or Contact Center Standard Agent license. Refer to the Assigned Licenses entry below, particularly the Contact Center panel form that allows for Contact Center agent management.

• Add Webex App user via Webex Quick Add User (view/WebexTeamsSubscriberQas)

  Go to Webex Quick Add User

  Note

  In this case, it is recommended you add Webex App users on a Webex Control Hub with the wholesale customer service. See Create Webex App Service and Quick Add Groups.

  In Webex Quick User, choose a Webex Teams User Template from the drop-down, or use the default user template (which is referenced in the Quick Add Groups associated with the user). If you want customized values, clone the Webex Teams User Template via the Configuration Templates page, and edit as required.

• Add Webex App user via the Users page (relation/MultiVendorSubscriber)

  Go to Add a Subscriber

• Add Webex App user via the flow through provisioning procedure.

  Go to Sync Webex App Users with Flow-through Provisioning

Related topics

• Provision Cisco Webex for an existing user (see Provision Webex App)
• Webex Quick Add User

View Webex user

To view a Cisco Webex App user:

1. Go to Webex User Services (dashboard), then:

   • Go to Manage Users (relation/MultiVendorSubscribers), then select a user to view and/or manage their user details, licenses, calling settings, phones, or services. You can also access quick actions available for the user, and enable or disable their login.

     Note

     If the user is associated with a phone (device) you can click the link adjacent to the device to go to relation/WebexDevice to view and manage the device settings.

     Multiple Jabber devices can be added to a Webex User as long as the user does not have an existing device of the same device type.

   • Go to Webex User Details (relation/SparkUser), then select a user to view and/or manage their account details and calling type, calling behavior, assigned licenses, or their roles and addresses.

   • Go to System User Details (relation/User), then select a user to view and/or manage their user details (including their authorized admin hierarchy and sync source), their account information, license audit details, their provisioning and hybrid status, their contact details, and their services.

Add Webex user via Webex User Details page

This procedure adds a new Cisco Webex user via the Webex User Details page in Automate.

1. Log in to the Admin Portal as a Provider, Reseller, Customer, or Site administrator.

2. Go to the Webex User Details list view.

3. Click the Plus icon (+) to add a new record, then choose the relevant site.

4. Configure account details and calling type on the Account Details & Calling Settings tab/panel:

   Note

   Location is read-only, synced from Control Hub.

   • (Mandatory). Select an email address. This value is used to match users when they're moved during an overbuild.

   • Fill out a first name and last name.

   • (Mandatory) At Display Name, fill out a display name for this user, typically, name and surname.

   • At Manager ID, select the manager's email address.

   • At Calling Behavior, choose an option to auto-populate settings:

     Note

     The default calling behavior is Calling in Webex App.

     • Calling in Webex App

     • Calling in Webex App (Unified CM)

     • Cisco Jabber app

     • Third Party app

       Note

       For Calling in Webex App (Unified CM), fields for device creation (Iphone, Android, CSF, Tablet) are displayed and checked by default.

   • Phone Numbers: The fields: Type (e.g. "Work") and Number are available for each entry.

   • Extension: Webex Calling extension is available if a user has a Webex Calling license.

   • Assigned Licenses: selected from licenses available on the Cisco Webex service as synced in from the Webex Control Hub.

     • Depending on a user's license, services such as Collaboration, Conferencing and Contact Center are available.

     • If Webex calling is enabled and a user is assigned a Webex Calling - Professional license, a Calling Settings panel on the form allows for the user management of Calling Settings (such as Barge In, Caller ID, Call Forward, Call Recording, Call Waiting, Intercept).

       Note

       If a user has Calling Settings available, these need to be removed and to be re-provisioned if it is necessary to move the user to another site. For details, see Move users, without services.

     • Configure Contact Center settings - displays only if the user is assigned a Contact Center Premium Agent license. Settings include:

       • User profile ID, Site ID, Team IDs, Skill Profile ID. See Webex Contact Center User Management

       • Agent Profile ID, Multimedia Profile ID. See Webex Contact Center Desktop Experience

         Note

         At Agent Profile ID, all global and only desktop profiles assigned to the same contact center site as the user are available.

6. On the Roles & Addresses tab/panel, select relevant roles:

   No administrator privileges	Default
   Full administrator privileges	Assigns access to all portal features, including: Assign roles Company policy and templates Device management Licenses and upgrades
   Read-only administrator privileges	Assigns read-only access to content available to a full privilege admin
   Support administrator privileges	Assigns access to user information and support logs
   User and Device Administrator	.
   Device Administrator	.

7. If available, on the Wholesale Package tab/panel, manage settings for packages in the Webex for Wholesale service, and their status, for example, provisioned.

   This tab/panel displays only when the Webex for Wholesale service is available. See Create Webex App Service.

   Depending on the package selected, the user's assigned licenses, as available on the Webex for Wholesale service, are then also updated when the user is provisioned.

   Note

   When modifying a Webex user and UCM Calling Licensing is deleted and the work phone number is also set to empty, the number is removed from the user. Work phone number remains assigned to the user if it's not set to empty.

8. Save your changes.

   The Cisco Webex App user is added. You can view added details in the summary list view, which also displays:

   • On-Prem UCM Calling Service (True/False) - Defines whether calling services are on-premise or cloud. The On-Prem UCM Calling license is removed if the Cisco Webex Calling (with UCM) is removed from the user.
   • Calling Behavior (determines license use) - options are:
     • Calling in Webex App - Allows calling via the Webex app using native Webex calling
     • Calling in Webex App (Unified CM) - Allows calling via the Webex app using a registration to UCM
     • Cisco Jabber App - Allows calling using a Cisco Jabber client registered to UCM
     • Third Party App - Allows calling using a third party app registered to UCM
       • Use Organization's Domain (True/False) - When enabled, the Cisco Webex organization domain is used for calling in Cisco Webex (Unified CM)
       • UC Manager Profile - May be used to identify the required UCM cluster when a calling behavior using UCM is selected. If the default UCM domain is selected, this is not required.
       • User Type - "Person", "Bot" or "App User (Guest User)".
       • Status - the current Cisco Webex App user status: for example: active/inactive, in a call/meeting/presenting, and so on. If unknown, then displayed as: "The user status could not be determined".

Delete a Cisco Webex App user

This procedure deletes an existing Cisco Webex App user (a synced in user, or one added via Automate).

1. Log in to the Admin Portal as a Provider, Reseller, Customer, or Site administrator.

2. Set the hierarchy to the Customer or Site level.

3. Go to Webex User Services. Choose an option to open a list view of users. See View Webex user.

4. From the list view, select users to delete, one or more; then, click the Delete icon.

5. Click Yes to confirm.

   Note

   When deleting a user with Cisco Webex App, the internal number inventory (INI) is updated as the number status is changed to Available, and the description, if any, is removed.

Provisioning users with Cisco Webex

This section describes how to provision Cisco Webex for a user, either via the Users list view, or via Webex Quick User.

Related topics

• Add Webex App User
• Webex Teams Quick Add

Enable self-provisioning

Full HTML Help

This procedure enables self-provisioning for a subscriber using Quick user (QAS).

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. Go to Subscribers and choose the same user from the Subscribers list view.
8. Verify that the Self-service and User Profile fields display the same settings as those set in Quick user.

Enhanced INI Filtering

Full HTML Help

If the Enhanced INI Filtering feature is enabled, administrators have access to the Inventory Filter dropdown list menu for lines on the following forms:

• Phones
• Quick Add Subscriber
• Subscribers

The filter would typically be used to show a filtered, shorter dropdown list of directory numbers.

The following options are available in the Inventory Filter list:

• Default

  This filter - enabled by default - corresponds with the standard filter of Directory Numbers:

  • used and unused INI numbers above and at the current hierarchy.
  • used and unused Associated E164 numbers above and at the current hierarchy.

• Show Unused Numbers with Associated E164's (Site Only)

  • Shows unused INI numbers with Associated E164 numbers at the current site only.
  • Format is: <INI number> <E164 number>. Example: 99003 \+279990003.

• Show Unused Numbers with Associated E164's

  • Shows unused INI numbers with Associated E164 numbers above and at the current hierarchy.
  • Format is: <INI number> <E164 number>. Example: 99003 \+279990003.

• Show Used Numbers (Site Only)

  • Shows used numbers at the current site only.
  • Format is: <INI number> (used) or <INI number> (used) <E164 number>. Example: 99000 (used) \+279990000.

• Show Used Numbers

  • Shows used numbers above and at the current hierarchy.
  • Format is: <INI number> (used) or <INI number> (used) <E164 number>. Example: 99000 (used) \+279990000.

• Show Numbers belonging to this Subscriber

  • The option shows results if a subscriber is selected on the Quick Add Subscriber or Subscriber form, or is associated with the selected phone on the Phones form.
  • Format is: <INI number> (used) or <INI number> (used) <E164 number>. Example: 99000 (used) \+279990000.

Model Details: view/QuickSubscriber