Extension Mobility Cross Cluster (EMCC) Configuration
-----------------------------------------------------

.. _19.2.1|VOSS-205:

Extension Mobility Cross Cluster (EMCC) extends VOSS Automate's current extension
mobility functionality to allow the user to log in to a device, from within a
connected cluster, anywhere in the world. This enables the user to retain the
settings, services and lines he/she is familiar with at their home location.

VOSS Automate automates most of the EMCC provisioning to enable this feature to work
on all dial plans across multiple Cisco Unified Communications Manager (Unified CM)
clusters that are managed by the same platform instance. A small number of manual
configurations remain, specifically around network security, which is outlined in
a separate section. VOSS Automate only automates provisioning of the home cluster in
cases where the Unified CM clusters are managed by separate platforms, that is,
cross-cluster configuration across multiple platforms is not supported.


EMCC Use Case
.............

.. tabularcolumns:: |p{8cm}|p{8cm}|

+-----------------------+----------------------------------------------------+
| HOME Cluster          | VISITING Cluster                                   |
+=======================+====================================================+
| User Profile          | Phone (with Geolocation)                           |
+-----------------------+----------------------------------------------------+
| Geolocation Filter    |                                                    |
+-----------------------+----------------------------------------------------+
| Roaming Device Pool   |                                                    |
| (with Geolocation)    |                                                    |
+-----------------------+----------------------------------------------------+


* A user from the HOME cluster goes to the VISITING cluster and logs onto a phone.
  The two clusters can be in different countries/territories.
* The user cannot be authenticated in the VISITING cluster, but since the cluster
  is EMCC enabled, and the phone is subscribed to the EMCC service, the cluster
  searches for the user in defined EMCC remote clusters.
* Once the user (also subscribed to the EMCC service) is authenticated, the phone
  is unregistered from the VISITING cluster, and re-registered to the HOME cluster.
* The geolocation of the phone is sent to the HOME cluster. This enables the HOME
  cluster to associate the relevant roaming device pool to the user's phone using
  the geolocation filter.
* The phone behaves and dials exactly the same as if the user was logged in at the
  HOME cluster, and all his/her settings and preferences are preserved.
* Calls to the HOME cluster emergency numbers as well as the VISITING cluster
  emergency numbers break out at the VISITING cluster (physical location).
* Various other elements such as trunks, EMCC countries, and so on, must be
  configured on both the HOME-and VISITING clusters to ensure the feature functions.
  
  
.. note::

   Refer to the "Cisco Unified Communications Manager Features and Services Guide"
   for more information about the EMCC feature.
   
   
Prerequisites for Configuring EMCC using VOSS Automate
.......................................................

Before you can configure Extension Mobility Cross Cluster (EMCC) using VOSS Automate,
make sure that the following parameters have already been configured on each required
EMCC cluster (Unified CM) located at the relevant Customers:

* EMCC Feature Configuration such as Default TFTP Server for EMCC Login Device,
  EMCC Geolocation Filter

.. .. note::

..  This information will change drastically for Phase 2, to include how these parameters
..  are configured using VOSS Automate templates.