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.
The Infrastructure Configuration page lets you browse the infrastructure configuration settings of a Call Processor and Unified Message Processor. Through this page, you can add, edit, or delete the configuration settings.
![]() Note | The Infrastructure Configuration feature applies to Call Processors that are based on Cisco Unified Communications Manager devices and Unified Message Processors that are based on only Cisco Unity Connection. |
An infrastructure configuration request goes through when you perform infrastructure configuration activities.
Following are the infrastructure configuration process states:
Uncommitted Add—Configuration created locally but does not exist on the device.
Add in Progress—A pending configuration is in progress and being configured through an order. No changes are allowed in this state.
Add Failed—An operation on this object failed.
Add Scheduled—A pending configured object is scheduled in one of the tasks waiting to be executed. No changes are allowed in this state.
Uncommitted Update—An object that exists on the device has been modified locally but has not been submitted to the device.
Update in progress—Modify operation is in progress as part of an order. No changes are allowed in this state.
Updated Failed—Modify operation failed.
Update Scheduled—A pending configuration to change an object on the device is scheduled as part of a task. No changes are allowed in this state.
Uncommitted Delete—An object that exists on the device has been marked for deletion. The request to delete the object has not been made to the device.
Delete in progress—Delete operation is in progress as part of an order. No changes are allowed in this state.
Delete Failed—Delete operation failed.
Delete Scheduled—A pending configuration to delete an object from the device is scheduled as part of a task. No changes are allowed in this state.
You must add devices to Prime Collaboration Provisioning to provision services for users.
Note the following points while you are adding a device to Prime Collaboration Provisioning:
Before you add devices to Prime Collaboration Provisioning, you must ensure that Cisco Unified Communications Manager and Cisco Unity Connection devices are configured correctly.
There are some significant differences in how a Generic IOS Router is set up in Prime Collaboration Provisioning in comparison to a Cisco Unified Communications Manager or a Cisco Unity device. Most notably, Generic IOS Routers are not synchronized and they are not associated to a Domain or a Service Area.
To view the details of the device, hover over Quick View. You can start synchronization, view synchronization logs, test the connectivity of the device, and cross launch Cisco Unified CM Serviceability and Cisco Unity Connection Serviceability from Quick View.
To update or change the device details, click Edit.
To import devices from Prime Collaboration Assurance, click Import. The Device Setup page lists the devices in Prime Collaboration Assurance (devices that are in managed state only appear in the list). Select the device you want to import and click Import Selected Devices.
You can add Prime License Manager and Deployment Manager from the Infrastructure Setup page. After you add these devices, Prime License Manager and Deployment Manager links are displayed under the Administration menu. Click on the Prime License Manager or Deployment Manager link to cross launch the Prime License Manager or Deployment Manager login page.
![]() Note | You can add only one Prime License Manager and Deployment Manager device to Prime Collaboration Provisioning. If you try to add another Prime License Manager or Deployment Manager device, an error message will be displayed. |
For Cisco Unity Connection clustering and failover support, be aware of the following:
When adding a Cisco Unity Connection that includes a Cisco Unity Connection cluster server pair, add only the publisher server of the pair.
If the primary Cisco Unity Connection fails over to a secondary Cisco Unity Connection, you can change the IP address to the secondary device, and Prime Collaboration Provisioning will communicate with the secondary device before failback occurs.
If a network has more than one location, individually add all of the locations for either the Cisco Unity Connection server or Cisco Unity Connection cluster to Prime Collaboration Provisioning.
If Cisco Unity is used in the configuration, configure the Cisco Unified Communications Manager voicemail ports.
There are three types of synchronizations in Prime Collaboration Provisioning:
Infrastructure Synchronization—Discovers all the objects in the device that Prime Collaboration Provisioning uses and that are not specific to individual users. The infrastructure data are the configurations that are required to exist on the device before Prime Collaboration Provisioning can configure user services.
User Synchronization—Discovers all objects related to individual users.
Domain Synchronization—Puts existing users discovered during user synchronization into the Domain.
Use the infrastructure synchronization to synchronize the infrastructure data in the devices. The infrastructure synchronization retrieves device information that is used across multiple users.
To synchronize infrastructure configuration products and users:
Step 1 | Choose . | ||
Step 2 | Hover over Quick View of the device for which you want to run synchronization. | ||
Step 3 | Do one of the following:
The progress of synchronization is displayed in the Quick View under Synchronization Status. | ||
Step 4 | Click View Detailed Logs.
A synchronization log is created, listing the objects that could not be assigned. It also shows a warning message if an unknown element is received from the device. This log is replaced each time a synchronization occurs.
|
If the status of an infrastructure or user synchronization does not change for an extended period of time, verify that the Nice service is running in PCP via CLI (logged in as Root user). Run the following command to check if the Nice service is running:
ps -aef | grep nice
If the Nice service is stopped, restart the service, and then restart the infrastructure or user synchronization.
If you wish to manage the Analog Phones, you have to update the ipt.properties file. In this file, update the dfc.ipt.cisco.callmanager.analog_phone_support to Y and then do the user synchronization. You must restart Provisioning after the user synchronization is completed.
You use the infrastructure synchronization to synchronize the unified messaging infrastructure data in Provisioning with the Unified Message Processor:
SubscriberTemplate—A Subscriber Template in Cisco Unity, Cisco Unity Connection, and the e-mail message processor.
UnifiedMessagingFeatureSpecification—A class of service in Cisco Unity, Cisco Unity Connection, and the e-mail message processor.
You use the user synchronization to synchronize the unified messaging user data in Provisioning with the Unified Message Processor.
UMInfo—A user in Cisco Unity, Cisco Unity Connection, and Cisco Unity Express in conjunction with their user’s voicemail and e-mail information.
VoiceMailInfo—A user in Cisco Unity, Cisco Unity Connection, and Cisco Unity Express in conjunction with UMInfo and EmailInfo.
EmailInfo—A user in Cisco Unity and Cisco Unity Connection in conjunction with VoiceMailInfo and UMInfo.
![]() Note | IM and Presence 9.0 and higher versions are integrated with Cisco Unified Communications Manager. Due to this, user synchronization will be disabled for IM and Presence 9.0 and higher versions. User information will be directly synchronized from Cisco Unified Communications Manager. |
For IM and Presence, use the Infrastructure synchronization to synchronize the User Settings Infrastructure data with Provisioning.
![]() Note | After upgrading your Cisco Unified Communications Manager, you must perform User Synchronization manually to synchronize change notification settings. |
Perform the following steps to configure LDAP Server Synchronization from Prime Collaboration Provisioning:
Step 1 | Choose Provisioning Setup . |
Step 2 | In the Domains pane, select a Domain and click Edit. |
Step 3 | In the Domain Configuration page, select the Directory Source you have configured on the Device Setup page. |
Step 4 | In the settings pane, you configure the information Prime Collaboration Provisioning gets from the servers. These settings are used to synchronize and authenticate the users from the Directory/ACS server to Prime Collaboration. |
Step 5 | For all the changes on the LDAP server to be synchronized to Prime Collaboration Provisioning, select the following:
|
Step 6 | Click Save. |
Scheduling and Performing LDAP Synchronization To schedule synchronization, set the Synchronization Interval and Synchronization Start Date in the LDAP Settings pane.
After saving the Domain Configuration page, select the Domain and hover over Quick view. Select Start LDAP Synchronization.
After an LDAP synchronization, a report is created. The report lists the operations that could not be performed during synchronization. Operation failure can be due to incorrect data entered into the LDAP server or incorrect user settings.
You cannot delete an LDAP server which is associated to a Domain. Remove the LDAP server from the Domain to delete it.
The following table provides details about the LDAP Configuration fields.
|
|||
The user search base of a domain. Provisioning searches for users under the base under Active Directory. For example, CN=Users, DC=Cisco, DC=com. This search base is used only for LDAP synchronization. If using Microsoft Active Directory server, you can use the command dsquery user to list the complete user search base.
|
|||
Lists which user fields in Cisco Unified Communications Manager correspond to certain LDAP user fields. The only fields you can configure in Prime Collaboration Provisioning are the following: |
|||
![]() Note | Using "IN" filter in Automatic Service Provisioning, you can configure multiple queries. For example:
Likewise, you can use '=' and '!=' operators to configure queries. For example, if you provide a single userID:
Using * with userID such as User123* fetches all the users whose id starts with User123. |
To completely remove a device from Prime Collaboration Provisioning, you must delete it through the Infrastructure Setup page. Note the following points when you are deleting a device:
No active released orders, including unrecoverable or recoverable errors.
No active batch projects.
No synchronizations in progress.
If these conditions are not met, a message appears on the page when you attempt to delete a device. Avoid performing any activities until the deletion is complete.
You can enable Cisco Jabber services for devices in Prime Collaboration Provisioning. Cisco Jabber services allow you to interact with instant messaging and presence.
![]() Note | Cisco Jabber service is available for Cisco Unified Communications Manager 9.1.1 and above version, and Cisco Unified Presence only. |
Step 1 | Choose . | ||
Step 2 | Hover over Quick View of the device and click the UC Services tab and click Enable | ||
Step 3 | Enter the SIP Profile, Service Profile, Softkey template fields and Service Parameter information, and click Apply. You can click View Order to see the order details in the User Record page. The date when the Jabber Service is enabled is displayed.
|