[Index]
Quick Add Subscriber (QAS) provides a single page where you can:
QAS supports many user types, including:
If the Default Self-service Language is set on the SDD, Users will be assigned the corresponding Self-service language.
A Quick Add Group (QAG) is a collection of templates that configure the subscriber features, and is mandatory when adding a QAS.
Note
To add subscribers using QAS, a default user template called "voicemailusertemplate" must exist on the Unified CM. This default can be edited by editing the default CUC User Template value in the SDD.
For self-provisioned phones to show as being associated with a Subscriber, perform a Cisco Unified Communications Manager Data Sync after setting up a self-provisioned phone.
Any modifications of the added subscriber and associated services are done from the respective service menu items.
The Quick Add Subscriber input form shows a number of check boxes to enable user services such as Voicemail, Extension Mobility, Single Number Reach, WebEx, CMR, Webex Teams (Webex Teams Quick Add), etc. Selecting certain check boxes exposes additional fields.
If the Entitlement profile selected on the QAS form does not include a particular service, then the check boxes for that service is not available. For example, if the selected Entitlement profile for the Subscriber does not include Voice services, then the check box controls for Voice, Jabber, and Self Service ID will not show on the form. The choice of Entitlement profile will filter the available options in the Phone Type drop-down to show only the enabled devices in the Entitlement profile.
For the Voicemail service, controls will also not be available if the site's SDD has no default value on the CUC Defaults tab for the Default CUC Subscriber Template. This default value (voicemailusertemplate) should already exist on the Unified CM and is automatically populated on an HCS system when a VoiceMail Pilot is created. A Cisco Unity Connection device must also be configured at the related NDL (Network Device List) at site level.
While the GUI hides controls if services are not available, API and Bulk Load operations have Provisioning Workflow checks 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.
If no Unified CM has been configured at the hierarchy that the Subscriber belongs, then Quick Add Subscriber bulk load transactions and API calls will show a warning message: No Call Manager has been configured.
Webex Teams Quick Add
If you select the Webex Teams check box, the Webex Teams User Template drop-down is exposed. From this, you can select the Webex Teams User Template to use for the user. This selection overrides the default user template referenced in the Quick Add User Group associated to the user. If a Webex Teams User Template is not selected from the drop-down, selection falls back to the Webex Teams User Template referenced in the associated Quick Add User Group. If you want customized values, clone the Webex Teams User Template (Customizations > Configuration Templates) and edit as required.
A Device Pool contains system, device, and location-related information, and is mandatory when adding a Subscriber using Quick Add Subscriber. A Device Pool can be referenced by:
Site Defaults Doc
The Device Pool referenced in the SDD makes sure that a Subscriber's devices are always associated to a Device Pool. If there is no Device Pool referenced in either the QAG or Admin GUI drop-down (see below) the value defaults to the SDD.
Quick Add Subscriber Group (QAG)
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 GUI drop-down (if exposed). See Quick Add Subscriber Group for details.
Admin GUI
An Administrator can expose a Device Pool drop-down on the QAS page on the Admin GUI by editing or cloning the Field Display Policy. See Expose Device Pools and Class of Service in Quick Add Subscriber. 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
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 make sure 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 GUI to drive the Device Pool selection include:
For details to provision services to users, follow these instructions:
When creating users with the Quick Add Subscriber function, consider these conditions:
A check box called Send welcome email is displayed when you type in a user email address only if the following configuration has been made and is enabled:
A welcome email is then sent to the subscriber email address using the configured "Quick Add Subscriber" HTML email template that applies to the hierarchy (Email)
From the Quick Add Subscriber Group menu, create a custom group or use the default group.
You can edit existing users Cisco Unified Communications Manager through Quick Add Subscriber only if the users exist at the Site level.
A check box called Include users at higher hierarchy can be displayed by means of a custom Field Display Policy (field name: lookUpForUser, hidden by default), so that the User drop-down list will also show users above the current site hierarchy. This setting is also available for bulk load sheets and API calls.
A check box called Fail Transaction if user not found can be displayed by means of a custom Field Display Policy (field name: failIfNotFound, hidden by default) to prevent adding users not on Cisco Unified Communications Manager. By default, the transaction will not fail. The option is used for the case where users have not been synced from LDAP to Cisco Unified Communications Manager. This setting is also available for bulk load sheets and API calls.
LDAP synced or LDAP integrated at Cisco Unified Communications Manager user fields are always read-only and cannot be edited.
You can associate a Line with multiple phones.
You can associate a Phone with multiple Lines.
If you choose to add a Phone for the user, the Phone Name drop-down list will show available phones at the user's site, according to the Phone Type as specified in the Site Defaults for the site.
The phones available from the drop-down list are those in the associated Quick Add Subscriber Group at the Customer level, which have synced from Unified CM, as well as the phones that are available at the specific site level.
You can also add a new phone if required by entering a valid name in the Phone Name field. The Phone Name must consist of a prefix, for instance SEP, followed by a MAC address, which is 12 hexadecimal characters. If you enter the Phone Name incorrectly, for example too few or too many characters, then subsequent associated transactions will fail.
Associate an Entitlement Profile with the Subscriber.
You can create multiple devices for a user. Therefore, the Voice check box is always visible. When the Voice check box is selected, four optional fields are exposed: Phone Type, Phone Protocol, Phone Button Template, and Phone Security Profile.
Values set in the Phone Type, Phone Protocol, Phone Button Template, and Phone Security Profile fields will override any existing values in QAG or CFT, as well as the SDD or any other backend CFTs (CFTs that can not be edited). If a field is blank, the existing values in QAG, CFT, SDD or other backend CFTs will be used.
You can override the default Phone Button Template value by entering a custom value in the Phone Button Template field. The entered value will be applied on Unified CM if the Unified CM allows it for that phone type.
Note
To reduce the likelihood of conflicting QAS settings when completing the optional fields mentioned above, we strongly recommend setting the required fields in the order as displayed on the Quick Add Subscriber screen:
You can set only one Extension Mobility profile for a user. Therefore, the Extension Mobility check box is not visible after you create an Extension Mobility profile.
You can set only one WebEx account for a user.
See Contact Center Agent Quick Add.
You can associate multiple Jabber and Dual Mode devices to a user.
Jabber and Dual Mode devices get the first line assigned to them that is specified in the QAS form.
You can create a Directory Number in Unified Communications Manager in two ways:
When you create a Voicemail or Voicemail Line using Quick Add Subscriber, the Directory Number Used field is set to "true" under Subscriber Management > Directory Number Inventory.
A Directory Number created without any device associations (for example, a Voicemail Line) is tagged under Subscriber Management > Lines as 'DN created without device from QAS.'
When the Enable Self Provisioning check box is selected, phone lines are added using the Universal Line Template (ULT) referenced in the Self Provisioning User Profile chosen from the Self Provisioning User Profile drop-down list which is exposed upon selecting the check box.
If a User is added with lines but no devices, then selecting the Enable Self Provisioning check box automatically sets the CUCM User Primary Extension to the QAS line pattern and ULT route partition. If a user is added with devices and lines, then selecting this check box also automatically sets the CUCM User Primary Extension to the QAS line pattern and ULT route partition.
Choose the required User Profile from the Self Provisioning User Profile drop-down list. The available User Profiles are those under User Management > Self Provisioning > User Profile. A User Profile must be selected when a user is enabled for Self Provisioning. A default User Profile (as shown under Site Management > Site-Defaults) is selected. Change this default if required.
Contact Center Agent Quick Add
refer to UCCX Feature Reference
The Quick Add Subscriber feature supports the easy creation of an UCCX agent.
The Contact Center Agent check box becomes visible if:
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 Subscriber 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:
An IPCC extension is automatically managed for the Unified CM user associated with the Contact Center Agent.
Procedure
Procedure
Procedure
Procedure
Choose Subscriber Management > Quick Add Subscriber, and choose the user for whom you want to provision Single Number Reach from the Username drop-down list.
Choose the Single Number Reach tab. The SNR Mobile Number field appears.
In the SNR Mobile Number field, optionally enter the mobile number. Do not add any spaces or special characters to the number.
The SNR Mobile Number can be the same as the user's Mobile Number shown in User Management > Users.
Click Save.
Choose Subscriber Management > Quick Add Subscriber, and choose the same user from the Username drop-down list.
Choose the Existing Services tab.
Make sure that the Single Number Reach displays the Single Number Reach profile name.
The Single Number Reach profile name is the user name followed by "-RDP". For example: jsmith-RDP.
Procedure
Choose Subscriber Management > Quick Add Subscriber. From the Username drop-down, select a user.
Select the Jabber/Dual-Mode Device check box. The Jabber and Dual-Mode Devices field appears.
Click + next to Jabber and Dual-Mode Devices to expose the Jabber/Dual Mode Agent drop-down and Device Name field.
Choose a device type from the Jabber/Dual Mode Agent drop-down. The Device Name field is automatically generated in the following format:
<device type prefix><username><random number>, where:
See examples in table below.
Example Device Type and Device Name Combinations
For this type of device | Device Name (automatically generated) |
---|---|
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 | Format (regex): "[a-zA-Z0-9]{1,15}" For example: CIMJOHNSMI |
CTI Remote Device | Format (regex): "[a-zA-Z0-9]{1,15}" For example: CTIJOHNSMI |
For the following Agents, also select the Mobile Identity check box to enable Mobile Identity if required:
Click Save.
Choose Subscriber Management > Quick Add Subscriber. From the Username list, choose the same user.
Choose the Existing Services tab.
Make sure that the Phones field displays the Jabber device.
For each device type, a Configuration Template that is associated with the Subscriber's Quick Add Group is used to provision the device. For defaults, see: 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.
Procedure
If the Enhanced INI Filtering feature is enabled, administrators have access to the Inventory Filter dropdown list menu for lines on the following forms:
The filter would typically be used to show a filtered, shorter dropdown list of directory numbers.
Note
If the Internal Number Inventory (INI) feature is not enabled, Enhanced INI Filtering will not be applied and all the list of numbers are obtained from the device.
The following options are available in the Inventory Filter list:
Default
This filter - enabled by default - corresponds with the standard filter of Directory Numbers:
Show Unused Numbers with Associated E164's (Site Only)
Show Unused Numbers with Associated E164's
Show Used Numbers (Site Only)
Show Used Numbers
Show Numbers belonging to this Subscriber
A Class of Service (CoS) allows the user to specify a Calling Search Space (CSS) for devices and lines, respectively. A CSS, in turn, is mandatory for lines and devices when adding a Subscriber using Quick Add Subscriber. A Calling Search Space can be referenced by:
Site Defaults Doc
The Calling Search Space values referenced in the SDD ensure that a Subscriber'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 QAG or via the Class of Service field in the Admin GUI drop-down (see below) the value defaults to the SDD.
Quick Add Subscriber Group (QAG)
The Calling Search Space values referenced by a Configuration Template (CFT) in the QAG take precedence over the Calling Search Space values referenced in either the SDD or the Class of Service via the Admin GUI drop-down (if exposed). See Quick Add Subscriber Group for details.
Admin GUI
An Administrator can expose a Class of Service drop-down on the QAS page on the Admin GUI by editing or cloning the Field Display Policy. See Expose Device Pools and Class of Service in Quick Add Subscriber. 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 is done to make sure 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 GUI to drive the Calling Search Space values include:
Administrators with access to Field Display Policies (FDP) can expose the Device Pools field and Class of Service (CoS) field on the Quick Add Subscriber (QAS) interface at a specific hierarchy.
If an administrator is at the hierarchy where the cloned FDP is created or at a lower hierarchy, and then navigates to Subscriber Management > Quick Add Subscriber, a drop-down field with the title: Device Pools or Class of Service is exposed.
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
User Details | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Username * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
First Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Last Name * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Email Address |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Send welcome email | Send Email to user using predefined HTML Email Template. Email template used is 'Quick Add Subscriber' |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Password | The corresponding CUCM, CUC and WebEx user password will be set with this password |
|
|||||||||||||||||||||||||||||||||||||||||||||||
PIN | The corresponding CUCM and CUC user PIN will be set with this PIN |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Entitlement Profile |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Quick Add Group * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Device Pools |
|
||||||||||||||||||||||||||||||||||||||||||||||||
User status |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Lines |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Directory Number |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Voice |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Phone Type |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Phone Protocol |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Phone Button Template |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Phone Security Profile |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Use Activation Code Onboarding | Enabling this checbox will instruct this workflow to add one phone only, using the Activation-Code based registration method. The code will be automatically generated. When selected, the Phone name field also gets hidden because the phone name will be automatically generated when this onboarding method is used. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Phones |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Phone Name | Name of phone to provision for e.g. SEPABCDEFABCDEF |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Extension Mobility |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Voicemail |
|
||||||||||||||||||||||||||||||||||||||||||||||||
WebEx |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Single Number Reach |
|
||||||||||||||||||||||||||||||||||||||||||||||||
SNR Mobile Number |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Webex Teams | Webex Teams |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Webex Teams User Template | Webex Teams User Template |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Jabber / Dual-Mode Device | When adding a Jabber device also specify a line to be associated. The first line specified will be used for any Jabber device added here. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Jabber and Dual-Mode Devices |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Jabber / Dual-Mode Agent |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Device Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Mobile Identity |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Destination |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Self Provisioning |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Self Provisioning User Profile |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Is PhoneType Entitled? |
|
||||||||||||||||||||||||||||||||||||||||||||||||
External Auto Trigger? |
|
||||||||||||||||||||||||||||||||||||||||||||||||
does_phonetype_support_pac |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Agent Extension |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Agent Device Type | Default: Phone |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Agent Device |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Existing Services | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Existing Services |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Phones |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Extension Mobility Profiles |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Voicemail Extension |
|
||||||||||||||||||||||||||||||||||||||||||||||||
WebEx |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Single Number Reach |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Webex Teams | Webex Teams |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Contact Center |
|