The purpose of the Quick Add Subscriber interface is to provide a single input form to add users on Unified Communications Manager as well as selected Voicemail and WebEx accounts, and to provide them with services such as SNR, Extension Mobility, and Jabber Device (Mobile Identity).

The Quick Add Group, which is a conglomeration of individual templates that configure each of the subscriber features, is required.

The interface also makes it possible to add lines for the Unified CM user.

Note	In order to add subscribers using Quick Add Subscriber, a default user template "voicemailtemplate" must already exist on the Unified CM. It is possible, as a part of Dial Plan management, to change this default by editing the Default CUC User Template value in the Site Defaults reference.

In order for self-provisioned phones to show as associated with a Subscriber, administrators should carry out a Cisco Unified Communications Manager Data Sync after setting up a self-provisioned phone.

Any modification of the added subscriber and associated services are done from the respective service menu item.

The Voicemail interface makes it easy for an Administrator to add, modify or delete CUC Voicemail users as well as associated Voicemail services from a single tabbed form. The user that is added to the system is also added to the CUC Voicemail system, and if the relevant services are selected these are also added to the CUC Voicemail system.

The following can be provisioned by means of the Voicemail interface:

• CUC Account - A CUC User, which includes a VM account name, a VM number and an associated subscriber template. The CUC Subscriber Template default value is pulled from the Site Defaults menu, which can be viewed and edited (if logged in at the appropriate administrator level) by choosing the CUC Defaults tab from Dial Plan Management > Site Defaults.

• Alternate Extensions - Alternate extension numbers that are available to the CUC Voicemail user.

• Credentials - Password and PIN

• Notification Devices - Devices used to notify the CUC user of Voicemails sent to the user. These include: Phone, HTML, SMTP (email), Pager, and SMS (if an SMPP Provider has been added on the relevant Voicemail server)

A Voicemail account can only be added if:

• The administrator has navigated to the relevant Provider, Customer, Site level.

• A CUC Server (VM Server) has already been provisioned at the Global, Provider, or Customer level.

• A Network Device List (NDL) and NDLR points have already been created.

When adding a new Voicemail account, the following workflow is executed:

1. A CUC account is added with the details input by the user.

2. Alternate extensions are added with the details input by the user (if applicable).

3. Credentials (password and PIN) are added with the details input by the user. The password and PIN can either be locked by the administrator, or the user can be prompted to change the credentials upon first login.

4. Notification Devices are added. The system automatically provisions default notification devices, however additional notification devices can also be added when adding a Voicemail account.

You can modify either an existing Voicemail account service information (details that were added to a Voicemail account during the Add Voicemail process), or you can modify a Voicemail account by adding new Voicemail services (those that were not added to the Voicemail account during the initial Add Voicemail process). For example, you can add additional alternate extensions and/or notification devices. After adding a Voicemail service to a subscriber, any lines that are used by any of the devices associated to the subscriber must be updated to reflect the proper call forward and Voicemail profile settings to enable the Call Forwarding to Voicemail and Voicemail buttons.

When modifying a Voicemail account, the workflow and processes are executed as with the Add workflow.

• Modular Add and Delete workflows can be carried out. For example, if more than one alternate extension or notification device is added to the Voicemail account, a pop-up form is available on the appropriate Alternate Extensions tab or Notification devices tab. Alternatively, for one-to-many or zero-to-many item instances such as an alternate extension, it can be deleted. These Add and Delete operations carry out a secondary workflow on the Voicemail instance.

When deleting a Voicemail account, the following should be noted about the workflow:

1. All elements associated with the Voicemail account are deleted.

2. Modular Delete workflows can be carried out as a part of a Modify workflow.

Site administrators manage the conferencing credentials of users if a WebEx server is available at the site level. The WebEx server on which users are administered can be identified with the Network Device Reference of the site, or else (according to the common reference resolution process) with the first such server in the current or higher up hierarchy level.

The default Conferencing input form that provides the interface to WebEx users displays the minimum of WebEx user properties that are mandatory. The Field Display Policies and Configuration Templates for this Conferencing input form can be modified according to the suggested customization procedure for Policies and Templates.

If conferencing was added for a Subscriber user when the Subscriber was added, the WebExId is defaulted to the userid. Note that the WebEx user properties that are shown on the Subscriber form may not correspond with those shown on the Conferencing input form. If the Conferencing feature is to be added for an existing subscriber, make sure that the WebExId is the same as the userid.

For Conference Workflows to function, make sure that the following is done at the Customer:

• A WebEx server is added.

• The WebEx server is added to a Network Device List (NDL).

• The required site references the relevant NDL.

User details can be added if a valid server is available.

When adding Conferencing from this input form, the mandatory fields are entered on the WebEx server.

Conferencing details can also be added as part of Subscriber Management. If the Web Ex Id is a Cisco Unified Communications Domain Manager 10.6(1) and Unified CM username of a Subscriber, the WebEx details are displayed on its Subscriber Management screen WebEx tab.

Modify Conferencing details on the selected item, or also add and delete details from the Subscriber Management form.

Deleting a Conference item will remove the details from the WebEx tab of Subscriber Management if the user is a Subscriber.

The Private Line Automatic Ringdown (PLAR) feature, also called Hotdial, automates the Unified CM configuration required to set up PLAR for a phone. The PLAR feature provides an administrator with a single interface and workflow for the management of the following elements of Unified CM:

• RoutePartition

• CSS

• TransPattern

• Phone

• Line

• SIP Dial Rule

The feature further provides an administrator with:

• A simplified user interface to select a Phone that must be enabled for PLAR, a destination number, and the destination CSS.

• The orchestration of a workflow to create the necessary Unified CM partition, CSS, Translation Pattern, and so on, and to apply these to the relevant Phone and Number.

To configure an existing phone for Hotdial, the user selects a pre-existing device and indicates that the device is a Hotdial device.

As soon as a PLAR configured phone goes off hook (or the NewCall softkey or line key gets pressed), the phone immediately dials a pre-configured destination number. The phone cannot dial any other number except the Hotdial destination that gets configured for PLAR.

The PLAR configuration can be added or deleted, but not modified.

When adding a new Hotdial Phone (PLAR configuration), the following workflow is executed:

1. A Unified CM route partition is created with:

   1. Name set to the selected Hotdial destination prefixed with "HotdialPT-".

   2. Description set to the Hotdial destination prefixed with "Hotdial Partition for Destination".

   3. Time Zone set to the time zone defined for the site.

   4. Partition Usage is set to General.

2. A Unified CM CSS is created with:

   1. Name set to the selected Hotdial destination prefixed with "HotdialCSS-".

   2. Description where the selected Hotdial destination is prefixed with "CSS for Hotdial/PLAR Destination".

   3. The Partition created above is made a member of the CSS.

   4. Partition Usage is set to General.

3. A Unified CM translation pattern is created with:

   1. Route Partition Name is set to the selected Hotdial destination prefixed with "HotdialPT-".

   2. Description is set to the selected Hotdial destination prefixed with "Used in Hotdial/PLAR for Destination".

   3. Calling Search Space Name set to the selected destination dialing CSS.

   4. Called Party Transformation Mask is set to the selected Hotdial destination.

   5. Route Option is set to Route this pattern.

   6. For SIP Phones only, a SIP Dial rule is created and the phone is set to use the SIP Dial Rule.

4. The Unified CM phone selected is updated as follows:

   1. CSS name set to the selected Hotdial destination prefixed with "HotdialCSS-".

   2. Hotline Device is set to true if the phone is marked as a Hotline Device by the user on the input form.

5. The Unified CM directory number selected as the Hotdial destination is updated as follows:

   1. The Route Partition Name is set to the route partition added in Step 1 above.

Cisco Unified Communications Domain Manager 10.6(1) automatically resets the phone when required.

When deleting Hotdial to disable Hotdial for a Phone (deleting the PLAR configuration), the following workflow is executed:

1. Update Phone CSS to the original CSS.

2. Update Line Partition and CSS to the original values.

3. Delete the Hotdial Translation pattern.

4. Delete the Hotdial CSS.

5. Delete the Hotdial Route Partition.

6. For SIP Phones only, the device is updated to use a Dial Rule of "None", and the Dial Rule is deleted.

Hunt Groups are relevant to Sites only, and can be configured by a site administrator, or higher level administrator who must first navigate to the relevant site hierarchy.

The purpose of hunt group management is to provide business context for the lines selected as members of line groups and to provide the user with a single consolidated view of the following hunting elements.

• Hunt Pilot

• Hunt List

• Line Groups

All fields of the hunt pilot and hunt list are mapped to the user input. Note that not all hunt group fields are exposed to the Site Admin. The user must select the lines that belong to line groups or any existing line groups that must be added to the hunt list members.

Searches can be performed on any of the details of the hunt pilot.

A hunt group is a combination of the above elements that are automatically linked together using unique identifiers for the following:

• The hunt pilot's hunt list is set to the name of the hunt list. Note that the hunt list name must be configured first in order for it to appear in the hunt pilot tab.

• The hunt list's line group members is set to the name of the associated line groups.

Certain default values for hunt groups are populated by the site defaults menu item, which can be viewed and edited (depending on your log in level). Go to Dialplan Management > Site Defaults and click on the required site name in the list view.

Hunt groups can be:

• Added - where the user specifies the parameters of the hunt pilot and the hunt list, and selects one or more new or pre-existing line groups. If your administrator has enabled the number inventory feature, the Hunt Pilot Pattern can be selected from a drop-down list of available numbers. If the feature is disabled, the Hunt Pilot Pattern field is a free text field or a drop-down containing only selected available numbers. To allow the successful use of call forwarding in a hunt pilot, the defaults for Max Callers In Queue (32) and Max Wait Time In Queue (900) are cleared to allow the successful use of call forwarding in a hunt pilot. To use queueing instead of call forwarding, set these values other than the default, for example to 33 and 901.

• Modified - where the user modifies the parameters of the hunt pilot or hunt list, for example by adding or deleting additional line groups, and adding or deleting line group members.

• Deleted - where the user deletes a hunt group.

When adding a new Hunt Group, the following workflow is executed:

1. A hunt pilot is added with the details input by the user.

2. A hunt list is added with the details input by the user.

3. One or more line groups are created with the specified directory numbers as members.

When modifying a Hunt Group, the following workflow is executed (depending on what was modified):

1. The line group details are modified.

2. Added line groups are added. Note that removed line groups are not deleted.

3. The hunt list is modified

4. The hunt pilot is modified.

When deleting a Hunt Group, the following workflow is executed:

1. The line groups that are members of the hunt list are deleted (if they are not used by any other hunt list in the system).

2. The hunt pilot is deleted.

3. The hunt list is deleted.

Certain default values for call pickup groups are populated by the site defaults menu item, which can be viewed and edited (depending on your log in level). Go to Dialplan Management > Site Defaults and click on the required site name in the list view.

The Call Pickup Groups feature provides an administrator with the following:

• A single interface on which to create call pickup groups, and to select one or more lines as members of a pickup group.

• The ability to add Unified CM call pickup groups and to modify the call forward and call pickup settings of each Unified CM directory number for membership to a newly added call pickup group. When adding a call pickup group, If your administrator has enabled the number inventory feature, the Pattern can be selected from a drop-down list of available numbers. If the feature is disabled, the Pattern field is a free text field or a drop-down containing only selected available numbers.

• The ability to add lines to an existing call pickup group by selecting the pattern (directory number). When adding a member line, if your administrator has enabled the number inventory feature, the Pattern can be selected from a drop-down list of available numbers. If the feature is disabled, the Pattern field is a free text field or a drop-down containing only selected available numbers. The Route Partition Name field is populated automatically based on the selected Pattern.

• The ability to delete a pre-existing call pickup group, and to delete one or more lines from an existing call pickup group.

The first member of the associated pickup group name is set the newly created pickup group, and associated pickup groups can be added as part of the workflow.

When creating a Call Pickup Group, the following workflow is executed:

1. Adds a Unified CM Call Pickup Group.

2. Modifies the Call Forward and Call Pickup Settings of each line by setting the Call Pickup Group to the newly created Call Pickup Group.

When deleting a Call Pickup Group, the following workflow is executed:

1. All lines belonging to the call pickup group are updated to remove them from the call pickup group.

2. All associated pickup groups are modified to remove the call pickup group associations to the deleted call pickup group.

3. The call pickup group is deleted from Unified CM.

When modifying a Call Pickup Group:

• A change to the name of the Call Pickup Group also requires a corresponding change to the name in the list of Included Call Pickup Groups.