.. _p_cisco_unified_communications_manager_configuration_in_voss-4-uc:

Cisco Unified Communications Manager Configuration in VOSS-4-UC
---------------------------------------------------------------


.. _19.2.1|EKB-2692:

Overview
........

Cisco Unified Communications Manager devices provide the core call processing
capabilities for HCS, and are a critical part of the VOSS-4-UC 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.

Shared versus Dedicated
.......................

To share the Unified CM across multiple customers, add the Unified CM at the
Provider or Reseller level. To dedicate the Unified CM to a single customer, add
the Unified CM at the Customer level.

When setting up Unified CM as a dedicated instance, you can opt to set up Unified
CM after you create the customer.

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-4-UC
..............................


Configuring a Unified CM device on VOSS-4-UC creates a scheduled data sync to
import model data from the device into VOSS-4-UC. The scheduled data sync ensures
that the VOSS-4-UC 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-4-UC 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/LicensedUser``
     * ``device/cucm/LicensingResourceUsage``
     * ``device/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-4-UC that requires information from Unified CM.

.. note:: 

   References to HCM-F and Shared Data Repository (SDR) are only relevant if
   installed.

When you set up an IM and Presence Service server, VOSS-4-UC 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 :ref:`controlling_a_data_sync_with_a_model_type_list` for
more information.

For details on Change Notification Sync in VOSS-4-UC and on switching 
between Full Sync and Change Notification Sync, refer to the 
topic on the Change Notification Feature (CNF) following :ref:`VOSS_CNF_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-4-UC 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-4-UC 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.