Extension Mobility / Extension Mobility Cross Cluster (EM/EMCC)

Extension Mobility / Extension Mobility Cross Cluster

(EM/EMCC)

Prior to certificate consolidation, start with the cluster ID naming and Certificate export/consolidate/import is already in place for two clusters

EMCC devices available per cluster is already set to 100. Assumption is that no more than 100 EMCC users will be concurrently visiting the same cluster and use EMCC, if this is the case, it’s safe to increase the limit to 500 EMCC device. This change from 100 to 500 will not cause any IP Phone interruption.

1. Add EMCC IP Phone Service:

Service URL is: http://X.X.X.X:8080/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#

Where X.X.X.X represents the IP Address of the CUCM node where EM service is activated/started.

Make sure to enable “Enterprise Subscription”, this check box will appear once only when a new service is added.

Enable EM on IP Phones:

2. Create one partition and create one calling search space, assign the created partition to the created calling search space for emergency calling.

3. Create extension mobility User Device Profile for end users. On the Device Profile Configuration page, for the “Extension Mobility Cross Cluster CSS” assign the CSS created in step 3.

4. On the end user page assign the EM profile and enable EMCC

And

5. Add emergency route pattern(s). Partition accessible by the calling search space assigned to UDP “Extension Mobility Cross Cluster CSS”. The Gateway/Route List MUST point to a Standard Local Route Group.

6. Add Geo location filter to match:

7. add/update GEO Location configuration. Example of GEO Location:

8. On all IP Phone Device Pools, add the GEO Location Configuration created. Do not apply any GEO Location filter here.

9. Add Roaming GEO Location configuration that will match the GEO Location configuration set on the visiting phone. This is necessary to place the visiting IP Phone in the correct Roaming device pool.

10. Add Roaming Device Pool and apply the filter. Roaming device pool must reflect the correct time zone of the visiting cluster. Apply the GEO Location filter here. On the same Roaming device pool, make sure the correct Media Resource Group list is selected.

11. Create EMCC SIP Trunk. Critical: the Trunk’s Inbound CSS MUST have access the emergency Route Pattern(s) partition used by the users on the visiting cluster.

12. EMCC Feature Configuration. EMCC Region Max Audio Bit Rate value must be the same on all cluster participating in the EMCC network.

13. EMCC Inter-cluster Service Profile. Validation must be successful.

14. Configure Cluster View. EMCC/TFTP enabled.