.. p_welcome-to-voss-4-uc:

Welcome to VOSS-4-UC
----------------------

The primary objective of using VOSS-4-UC is to easily onboard customers and end
users with collaboration services. The fulfillment procedures to achieve this
objective may involve administrators at the provider, reseller, customer, and
site levels of the hierarchy.

This guide provides information about provisioning VOSS-4-UC, including 
provisioning steps and interactions between VOSS-4-UC and the UC applications of 
vendors that VOSS-4-UC supports, such as Cisco HCS. This guide also describes 
user and subscriber management, including LDAP-related move and push
operations.

This topic provides a high-level, example task workflow for configuring VOSS-4-UC and 
onboarding customers and users.


.. note::

   * This example task overview excludes customization and some optional configuration.
   * References to HCM-F and Shared Data Repository (SDR) are only relevant if
     installed.
   * Shared applications are configured at the Provider or Reseller level. Dedicated
     applications are configured at the Customer level.
   

**Before you begin**:

* HCM-F and any UC Applications to be used for provisioning customer sites and
  users must be installed and ready.
* For WebEx Cloud, the required licenses and accounts must be available for
  provisioning.



**Task Overview**:

1. :ref:`p_create_the_hcm-f_device`.
#. :ref:`p_create_a_provider`.
#. Optionally, :ref:`p_create_a_reseller`
#. :ref:`p_create_a_customer` at the appropriate Provider or Reseller hierarchy
   level.
#. :ref:`set_up_cisco_unified_communications_manager_servers`
#. Optionally, configure WebEx and UC applications at the appropriate hierarchy
   level:
   
   a. :ref:`set_up_cisco_webex`.
   b. :ref:`set_up_cisco_unity_connection`.
   c. :ref:`set_up_im_and_presence_service_servers`.
   
#. :ref:`configure_network_device_list`.
#. :ref:`p_create_a_site`.
#. :ref:`modify_site_defaults`.
#. :ref:`create_customer_dial_plan` and :ref:`create_site_dial_plan` as described
   under Dial Plan Management.
#. Configure Northbound Notification if desired as described under "Set Up
   Northbound Notification".
#. :ref:`set_up_an_ldap_server`.
#. :ref:`define_a_filter`.
#. :ref:`set_up_ldap_for_user_synchronization`.
#. :ref:`p_move_users`.
#. :ref:`manual_user_push_to_cisco_unified_cm`.
#. Perform end-user Collaboration Service provisioning as described under
   :ref:`add_subscribers`.




.. rubric:: CUCDM v8.x Changes

The major change in the configuration between Cisco Unified Communications
Domain Manager (CUCDM) from 8.x and VOSS-4-UC is the location of the master data.

In CUCDM 8.x deployments, the master copy of all data was stored in the Shared Data
Repository (SDR). Changes to the data were made in CUCDM and 
then synchronized down to the UC Applications, such as Cisco Unified Communications Manager (CUCM).

In VOSS-4-UC, the source of master data is distributed between VOSS-4-UC and the call
manager. A bidirectional sync is used to export and import data from VOSS-4-UC
and the applications. This approach enables configuration changes to be made on
either the VOSS-4-UC or the UC applications - giving greater flexibility and
faster problem resolution.