Cisco Unified Communications Manager Configuration in VOSS Automate¶
Overview¶
Cisco Unified Communications Manager devices provide the core call processing capabilities for HCS, and are a critical part of the VOSS Automate provisioning workflows. You must configure the Unified CM devices before you complete the dial plan (if applicable), user, subscriber, line, and phone configuration.
Unified CM devices can be dedicated to a specific customer, or they can be shared between multiple customers. Unified CM devices must then be assigned to one or more Network Devices Lists (NDLs), and the NDL is then assigned to one or more sites. The NDL is used to select which Unified CM is used for configuration based on the site selected in the hierarchy context.
Servers within a Cisco Unified Communications Manager Cluster¶
Within a Unified CM cluster, you can configure the following nodes:
Cisco Unified Communications Manager Publisher
Cisco Unified Communications Manager Subscriber
IM and Presence Service Publisher
IM and Presence Service Subscriber
Configure a Cisco Unified Communications Manager Publisher node before configuring any other type node.
Configure an IM and Presence Service Publisher node before configuring an IM and Presence Service Subscriber node.
Synchronization with VOSS Automate¶
Configuring a Unified CM device on VOSS Automate creates a scheduled data sync to import model data from the device into VOSS Automate. The scheduled data sync ensures that the VOSS Automate cache maintains the most current view of the configured device. Any changes to the configuration occurring on the device, including additions, deletions, or modifications, will be reflected in VOSS Automate after the next data sync.
Note
There is no immediate data sync upon Update or Modification.
The scheduled data sync fails if the Unified CM administrator account credential has expired. Expiration of the administrator account credential can cause failures in Subscriber Management activities as well.
Some license-related models will now be excluded from CUCM imports by default:
device/cucm/LicensedUserdevice/cucm/LicensingResourceUsagedevice/cucm/HcsLicense
The recurring sync is scheduled to occur every 14 days, but is disabled by default. You can enable the sync and modify the schedule from Device Management > CUCM > Schedules. When determining the appropriate schedule setting, the frequency of the sync must be weighed against the additional processing and network activity associated with the data sync. You can also manually run the data sync at any time from Device Management > Advanced > Perform Publisher Actions, or from Administration Tools > Data Sync.
Important
Allow the initial data sync to complete before doing more configuration on VOSS Automate that requires information from Unified CM.
When you set up an IM and Presence Service server, VOSS Automate does not communicate directly with the IM and Presence Service server. The information provided is pushed to HCM-F and Service Assurance (if installed) for monitoring purposes.
The performance of a data sync can be improved by controlling the types of data that are synced. See Controlling a Data Sync with a Model Type List for more information.
For details on Change Notification Sync in VOSS Automate and on switching between Full Sync and Change Notification Sync, refer to the topic on the Change Notification Feature (CNF) following Change Notification Feature Overview.
Field Mappings in Unified CM¶
When setting up a Unified CM device with LDAP integration, you can map Unified CM user data to VOSS Automate user data for any field, based on the Field Mappings in the Unified CM server. These mappings are configured at the LDAP Directory in Unified CM. The mapped user data, for example location data, can later be used in a filter used to move users to sites.
On the Field Mappings tab, you can modify the mappings except for hard-coded mappings. Hard-coded mappings appear in gray and are read-only.
Note
The field name entered in the mapping on VOSS Automate must exactly match the field name entered in the mapping in the Unified CM in the Custom User Field Name field. If the field names do not match, the field is skipped during the sync.