Onboard user#
Microsoft Cisco
This procedure adds a user from a profile to enable user onboarding via defined a pre-defined profile determining services and service settings.
In the Admin Portal, set the hierarchy to the relevant site.
Go to Onboard User.
Note
This page has two tabs/panels:
Details
Existing Services - read-only, and displays and populates only once you select a username.
You can click the toolbar Switch to Tab/Panel icon to toggle between a tab or panel layout.
On the Details tab/panel, configure the following:
Mandatory. Select the username (mandatory).
Fields on the Existing Services tab/panel display and update to provide a read-only view of the selected user’s existing services. If the user has existing dual mode devices, this includes the name and destination for mobile identity, remote destination, and CTIRD remote destination.
Fields on the Details tab/panel updates with the user’s details, including name and contact details, and current settings.
Select the profile for configuring the user.
Note
The option you choose filters the existing services relevant to the profile. Profiles available in the drop-down depend on the user type and environment, and are generated by the system based on the username you choose. For example, let’s say you’re onboarding an unlicensed user from Microsoft Azure, where Microsoft Teams is not yet provisioned, then, when selecting the user, the system lists the relevant profiles for adding and provisioning the user.
Depending on the selected profile, new services may be automatically provisioned, for example, a line, a phone, an extension mobility profile, a Jabber device, and Webex Calling. If this is the case, read-only fields display with the details for the new services that will be provisioned for the user via the profile, once you save.
Fill out the user’s details. You can update their first name, last name, email address, mobile number.
Note
A value for Last Name is mandatory only for CUCM users, and optional when provisioning Microsoft or Webex Calling services.
Password and PIN fields become available once the profile is selected, as follows:
For an LDAP user: only the PIN field will be available
For a CUCM-LDAP user: only the PIN field will be available
For a Microsoft user: PIN and password fields will not be available
For a Webex user: PIN and password fields will be available
For a Local/CUCM-local/None-existing user: PIN and password fields will be available
Note
The corresponding CUCM, CUC, and Webex user password will be set with this password.
The corresponding CUCM and CUC user PIN will be set with this PIN.
At Use generated phone name, if the selected profile has voice service enabled, define whether to have the system generate a random phone name.
At Line filter, select a number inventory filter, if available. If you’re not selecting Use next available line, you can choose a number from the subset of lines returned by the line filter.
Note
You can only choose an inventory filter if filtering is enabled at the site. Either custom filters or shipped filters, or all enabled filters may be available, depending on the filter group enabled at the hierarchy. See Manage number filters.
At Use next available line, define whether to use the next available line from the inventory or from an inventory filter you choose.
Note
When using inventory filters with use next available line, the system selects the first available number in the subset of filtered available numbers included in the filter. If you’ve chosen a line filter to display only used lines, the system won’t find a next available line since only used lines are returned for the filter you’ve chosen. In this case, the transaction will fail with “no available lines”.
Numbers reserved for other users won’t be available, regardless of their status (available or used, reserved, etc). If an inventory filter is applied to display only numbers reserved for or belonging to the user you’re working with, only those numbers display.
Save your changes.
Related Topics