Synchronizing Processors, Users, and Domains Overview
There are three types of synchronizations in Cisco Prime Collaboration Provisioning:
-
Infrastructure Synchronization—Discovers all the objects in the device that Cisco 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 Cisco 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.
Synchronizing the data in Cisco Unified Communications Manager and Cisco Unity systems, and then synchronizing with the Domains, populates Cisco Prime Collaboration Provisioning with the existing active users and services, and provides a consolidated view of all of the infrastructure and user information.
Remember the following before running any synchronization:
-
Infrastructure and user synchronizations retrieve information from the device. They are unidirectional synchronizations. Provisioning does not update devices during these synchronizations. Infrastructure and user synchronizations should be completed on all devices before a Domain synchronization is started.
-
You can execute the synchronizations independently and in any order. However, to preserve the integrity of the data, it is recommended that you run the synchronizations consecutively, and in the following order:
-
Infrastructure synchronization.
-
User synchronization.
-
-
After a new Provisioning installation, the infrastructure synchronization must be executed first. You should not run more than one synchronization at a time.
-
Ensure that you have checked the connectivity of the device. Click Test Connection (under Actions) from the Device details Quick View before running any synchronization. The test results appear in the Device details Quick View.
- The test connection results must be successful before synchronizing Unified Message Processors. If you start synchronization for a Unified Message Processor when the test connection status is "In Progress" or "Failure", the synchronization will fail.
-
After a Call Processor or Unified Message Processor is synchronized, do not change the type of device. For example, if you add a Cisco Unified Communications Manager, do not change the Call Processor type to Cisco Unified Communications Manager Express.
-
After a Domain synchronization, you can use Cisco Prime Collaboration Provisioning to directly manage the individual user account. You no longer have to use the underlying Cisco Unified Communications Manager or Cisco Unity systems.
-
Any out-of-band configurations (meaning configurations that are performed directly on the processor but not synchronized with Provisioning) can result in failed orders. You must always keep Cisco Prime Collaboration Provisioning synchronized with the processors that it is provisioning.
Note |
When you click on Device’s infrastructure or user synchronization, a popup window appears with the message 'Start Synchronization will put the system into maintenance mode'. If you click OK, the system enters into maintenance mode and then the sync starts. Once the sync completes, the system comes out of the maintenance mode automatically. If you click Cancel, the system does not enter into maintenance mode and the sync does not start. If a parallel sync is already running, then the system waits for the other sync activity to complete and then comes out of the maintenance mode. |
Change Notification feature will be automatically enabled for Cisco Unified Communications Manager 10.0 and above versions. This feature is not supported for Cisco Unified Communications Manager versions less than 10.0.
Note |
From 10.6 release, Change Notification feature is supported when the Cisco Prime Collaboration Provisioning is running in maintenance mode. |
Any updates to infrastructure or user configuration of Cisco Unified Communications Manager will be automatically synchronized to Provisioning every 5 minutes. This avoids the need for daily or frequent synchronization with Cisco Unified Communications Manager.
As part of change notification, the user records are also updated to include the newly added services. To view the start and end time of change notification synchronization for a Cisco Unified Communications Manager, launch the quickview and click View Detailed Log in the Actions pane.
- Call Park
- Call Pickup Group
- CallManagerGroup
- CSS
- CmcInfo
- CommonPhoneConfig
- CommonDeviceConfig
- Conference Now
- CTIRoutePoint
- Device Profile
- DateTimeGroup
- DeviceMobility
- Endpoint
- Emergency Location (ELIN) Group
- FacInfo
- GeoLocation
- Hunt List
- Hunt Pilot
- H323Gateway
- Line
- Line Group
- Location
- MediaResourceList
- MediaResourceGroup
- MeetMe
- PhysicalLocation
- Remote Destincation Profile
- Route List
- Route Pattern
- RoutePartition
- Route Group
- SIPProfile
- SIPTrunk
- TransPattern
- UcService
- User
- VoiceMail Profile
- VoiceMail Pilot
- VG224
- VG310
- VG320