.. _nextgen-vm-overview:


Introduction
------------

.. _18.1-Patch-Bundle-3|EKB-672:

The Unity SIP Integration tooling provisions complete SIP integration between
redundantly deployed Cisco Call Managers (CUCM) and Cisco Unity Connection (CUC)
servers. This integration tooling can be used to define the primary only integration
that the legacy Voicemail Service provides. 

The integration tooling provides a repeatable process to manage the integration of
CUCM and CUC, while also providing the ability to:

* Define the dial plan used for integration so that the administrator deploying the 
  integration does not need to have dial plan knowledge.
* Override the dial plan input mechanism mentioned above for advanced deployment.
* Deploy CUCM and CUC SIP integration in full redundancy supporting optional tenants.


.. important::

   Contact your dedicated VOSS support representative for details on how to set up
   and configure the Unity SIP Integration feature.

.. note::

   If this feature is not exposed in the Admin Portal menu layout, refer to the Optional
   Features Appendix: Unity SIP Integration - Menu Layout Changes and Access Profile
   Changes.

  
Unity SIP Integration Scope
...........................

The Unity SIP Integration tooling provides support for:

* Dual trunks to Unity publisher/subscriber
* Multiple SIP server destinations to CUCMs (SIP redundancy)
* Specifically defined number of Unity port build per Unity node
* Dynamic creation of CUCM route list/route group or the ability to update if they
  already exist
* Creation of Unity tenants for shared architectural deployments
* Creation of Unity integration utilizing tenants
* Support for multi-cluster deployments