The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Domains are groupings of users. For each grouping, one or more system users can be authorized to manage services for users within that Domain. In addition, rules or policies may be set on a Domain; those rules and policies will apply to services for users in that Domain. Common policies can also be applied on operations within a Domain.
A user can manage more than one Domain (if the user is assigned the proper authorization role). All of the user’s services are provisioned in the Service Area that you specify while adding the user (to add a user, choose User Provisioning).
After creating a Domain, you can add Service Areas and User roles that have access to your new Domain. You can also create service templates and assign them to a Service Area and User Role. A Service Template can be associated to several such combinations of Service Areas and User Roles.
To edit an existing domain, expand the list of Domains in the left pane, and click a particular Domain to edit. You can also click All Domains and then select a domain from the table and click Edit.
When configuring a Service Area, you can do the following:
Map the Service Area to the corresponding Call Processor objects by specifying its Call Processors and related objects (for a Cisco Unified Communications Manager, some examples are route partition, and device pool), Unified Message Processor, and Unified Presence Processor.
Specify the user types for the Service Area (only users within a Service Area can order products from it).
The Employee user role is the default based on the Domain rule DefaultUserType.
Create directory number blocks for the Service Area users.
Unified Presence Processor settings will list the Presence processor if the selected Call Processor has associated Presence processors.
Note | After a Service Area is assigned to a Domain, it cannot be moved to a different Domain. Further, after a Call Processor, Unified Message Processor, or Unified Presence Processor is assigned to a Service Area, it cannot be changed. |
To add a Service Area:
To edit an existing Service Area, expand the list of Service Areas in the left pane, and click a particular Service Area to edit. You can also select a Service Area from the table and click Edit.
Configuration of common device settings for the Service Area. The following settings are controlled by Common Device Configuration: |
|
Location to be assigned to a device. When adding a service area, this field is optional provided you have added one of the call processors associated with the domain through the Getting Started wizard. |
|
Route partition for the Service Area. This is the same as a partition in Cisco Unified Communications Manager. |
|
Device Pool |
Device pool for the Service Area. |
Voice Gateway References |
Voice gateway references for the Service Area. |
Email Processors |
Available only for Cisco Unity Connection and integrated with an external Exchange Server for IMAP client support. To configure an external Exchange Server for IMAP in Cisco Unity Connection, on the Cisco Unity Connection system, go to , and fill in the required fields. |
Subscriber Template without TTS Enabled |
Subscriber Template to be used to disable unified messaging for a user in the Unified Message Processor. |
Class of Service Template to be used to enable unified messaging for a user in the Unified Message Processor. It is used in conjunction with the Subscriber Template. To enable TTS for a CoS, you must configure the following in Cisco Unity Connection: |
|
Class of Service Template to be used to disable unified messaging for a user in the Unified Message Processor. It is used in conjunction with the Subscriber Template. |
|
Directory number block assigned for that Service Area. See Adding a Directory Number Block. |
Numbers within a directory number block are relative to the Cisco Unified Communications Manager on which they are being created. Prime Collaboration Provisioning handles directory numbers the same way as they are handled by Cisco Unified Communications Manager.
Note | The Minimum Length field indicates the minimum number of digits that a directory number can contain before the prefix is added. This is used by the system to pad numbers with zeros. For example, if prefix = 408, first number = 0, last number = 100, and minimum length = 4, then the range of the directory number block will be 4080000 through 4080100. |
To Edit, select the Directory Number Block, and click Edit. Make the necessary changes and click Save.
To discard the changes, click Cancel.
To delete a Directory Number Block, click Delete.
Prime Collaboration Provisioning is a user-centric provisioning product and requires human users and open space locations to be defined with a userID. This provides a convenient way to identify users, and devices in shared spaces. User roles can be used for several purposes. They provide policy enforcement, controlling which products and services are allowed to be ordered for different types of users such as contractors, executives or sales persons. They are also used in a filtering process that controls what choices are presented to order administrators at order time. The User Role setup also determines what services are ordered and which service templates are applied for a given user type during the Automatic Service Provisioning process. An administrator may create many User Roles to define different levels of services.
Employee—Default role assigned to new users.
Note | The default role is configured in the Domain Rules. |
The Employee user role should be configured to match the typical setup of employees in your organization. If you do not configure the employee user role to meet your needs, you may not see all the desired options during the service ordering process.
Pseudo—Used to provision endpoints that cannot have an associated user in Cisco Unified CM. Pseudo users are not registered with the Call Manager and cannot be renamed or removed.
You must first add a user (see Adding Users), then assign the user the Pseudo user role.
A pseudo user is authorized to manage phone and directory number inventory.
A pseudo user can have one or more endpoints associated with it. For example, conference rooms can be pseudo users with one or more endpoints, whereas a building can be a pseudo user with hundreds of endpoints associated with it.
These user roles exist in each Domain in Cisco Prime Collaboration Provisioning. Each set of user roles maybe customized in each Domain by adding, removing, or changing these predefined user roles.
To add a user role:
To change a user role configuration, select a user role, click Edit in the User Role for a specific domain, and save the modifications.
To delete a user role, select a user role, click Delete in the User Role for a specific domain, and click OK.
The user role quick view displays the domain, number of endpoints, services and service bundles selected for that user role.
A user whose role is associated with specific endpoints can order them. You can create orders for endpoints and services, individual services, or you can order bundled services. See Table 1.
Step 1 | Choose Provisioning Setup. | ||
Step 2 | In the All Domains pane, expand a specific domain, click User Roles. | ||
Step 3 | In the User Roles for the selected domain pane, click Add. | ||
Step 4 | Specify a name for the user role and associate it with the necessary Endpoints, Lines, Services and Service Bundles. You can check or uncheck as many Endpoints, Services and Service Bundles as needed.
| ||
Step 5 | Click Save. |
Domain synchronization aggregates data from synchronizations. Devices are not accessed during a Domain synchronization.
During a Domain synchronization, Prime Collaboration Provisioning does the following:
Synchronizes users and their services with the Provisioning inventory, creates new users, and updates the records.
Synchronizes user accounts and updates Prime Collaboration Provisioning so that users can log in (logins are created only if the self-care rule is enabled; see Business Rule Descriptions section in Cisco Prime Collaboration Provisioning Guide - Standard and Advanced, 11.x.
Associates services to Service Areas.
Synchronizes the assigned voicemail directory numbers in Unity Connection or Unity Express to those in Cisco Unified Communications Manager.
To fully synchronize a Domain, you must perform an infrastructure and user synchronization for each device in the Domain, and then perform a Domain Synchronization.
Perform the following steps, to synchronize domains:
Domain synchronization cannot be started without configuring synchronization rules.
Step 1 | Choose . |
Step 2 | From the Domains table, hover over quick view of the Domain you want to synchronize, and click Start Domain Synchronization.
A popup appears saying that the Domain Synchronization has started successfully. The Last Synchronization field in Quick View displays the status of synchronization along with the start and completion time. |
To add an Infrastructure Configuration Instance:
Step 1 | Choose . All available devices are listed in the left pane. | ||
Step 2 | Expand each device to view the infrastructure product of that device. | ||
Step 3 | Click the desired infrastructure product to cross launch or launch it natively:
|
To copy an Infrastructure Configuration instance a native launch, click Copy. In the Infrastructure Configuration - Configure Product Instance page, click the Draft Configuration tab and enter the necessary information. An asterisk next to a field indicates a required field. Applied Configuration tab shows the already configured instance. Click Apply or Save as Draft. The infrastructure configuration instance is saved with a “copy of” prefix.
To delete an Infrastructure Configuration instance for a native launch, you can do one of the following:
To immediately delete the configured instance from the device, click Delete.
If you want to push the order at a later time, click Schedule Delete.
If your configured instance is still saved locally, click Delete Draft.
The provisioning state of the object becomes Uncommitted Delete. The operational status is active.
Delete Draft does not make that instance unavailable for selection in other infrastructure products or user services. For example, if a route partition is marked for deletion, it is still available for selection in a Line or Phone product, as well as Calling Search Space.
To edit an Infrastructure Configuration Instance for a native launch, click the instance for which you want to make changes. In the Draft configuration tab, make the desired changes. An asterisk next to a field indicates a required field. Enter the required information.
You can click Apply or Save as Draft to save your changes.
Note | To clear the value of a setting that has a numeric value in Cisco Unified Communications Manager, you must enter a zero for the value. If you just clear the value, the setting does not get unset in Cisco Unified Communications Manager. |