Note: If we check the 'Enterprise Subscription', then the individual phones and device profile subscription not required.
Step 3: Device Profile Configuration
The device profile is a virtual profile which gets updated to the phone when we login via EM or EMCC. If you are running Extension Mobility on our network, this profiles likely to be there already. For the sake of lab, I'm adding a new Device Profile.
Go to Device > Device Settings > Device Profile > Add New
Note: The 'Extension Mobility Cross Cluster CSS' gets used as 'Device CSS' of the remote phone during EMCC login.
Step 4: Subscribe EMCC Service to Device Profile
Select the Device Profile > Related Links > Subscriber/ Unsubscribe > Go
Go ahead and Subscribe the Extension Mobility Cross Cluster service
Step 5: Subscribe EMCC Service to Phone and Enable EM
Go to Device >Phone > Related Links > Subscriber/ Unsubscribe > Go
Also, check the 'Enable Extension Mobility' box on the device page.
Note: Using EMCC Service, we are able to login to any phones in the Home Cluster (Just like EM). Try logging in to any available phone in the CL1. This is to make sure the service URL is working fine.
Step 6: End User Configuration
Go to User Management > End User > Find.
Select the user and set a PIN (this PIN will be used to authenticate extension mobility login).
Assign the Extension Mobility Profile to the user. Also, enable Extension Mobility Cross Clsuter check box.
Step 7: Customize Extension Mobility Service (Optional)
Go to System > Service Parameters > Select the Server where you have activated Extension Mobility Service & select service as Cisco Extension Mobility (Active)
Intra-Cluster Multiple Login Behaviour set to Auto Logout
Step 8: Configure Visiting Cluster CL2
Perform the above Steps 1 to 7 in Visiting Cluster - CL2 as well.
Step 9: Setup SFTP For Certificate Management
Install SolarWinds SFTP SCP Server on a Windows Machine. If you have already an SFTP Server running on your network, go ahead and use that. Please make sure this SFTP Server should be reachable from Home & Visiting Cluster.
Go to Bulk Administration > EMCC > EMCC Template > Add New
Step 13: Update EMCC
We need to update EMCC devices with the EMCC Template.
Go to Bulk Administration > EMCC > Insert/Update EMCC
Select the Update EMCC Devices radio button and EMCC Template created in Step 12, then run the job.
Step 14: Insert EMCC
Now we are going to insert the EMCC Virtual Devices. For this example, I'm adding 5 EMCC Devices.
Go to Bulk Administration > EMCC > Insert/Update EMCC
Select the Insert EMCC Devices radio button and enter the number of EMCC Devices, then run the BAT job.
Step 15: Configure Visiting Cluster CL2
Perform the Steps 11 - 14 in Visiting Cluster - CL2
Step 16: Configure Cluster ID on both Clusters
This parameter provides a unique identifier to the cluster.
Go to System > Enterprise Parameters
Set cluster ID for both Home and Visiting clusters.
Step 17: Add Geolocation Filter
Home Cluster will consider the Geolocation of the Visiting phone using the Geolocation filter specified in the EMCC Feature Configuration. Then match the Geolocation information from the home cluster to assign specific device pool.
When this parameter is set to None, EMCC will not function correctly; phones that attempt to login but cannot be assigned to a roaming device pool will fail to log in.
Note: Since I planned to put all the visiting phones in dedicated EMCC Device Pool (Based on the EMCC Template), I haven't configured any Geolocation for the visiting phone. But Geolocation filter is mandatory to configure EMCC
Go to System > Geolocation Filter > Add New, configure it as follows.
Step 18: EMCC Feature Configuration
These are the set of configurations used by EMCC.
Go to Advanced Services > EMCC > EMCC Feature Configuration
Default TFTP Server for EMCC Login Device: [Select TFTP Server]
This should be used by the phones logging in to EMCC from a remote cluster.
EMCC Geo Location Filter: [Select the filter created in Step 17]
Default Server For Remote Cluster Update: [Select a node where EM Service running]
Choose the default server name or IP address of the primary Cisco Unified CM server in this local cluster that has the Cisco Extension Mobility service activated. The remote cluster will access this server to get information about this local cluster.
Step 19: EMCC SIP Trunk
This is used Visiting Cluster PSTN Access for emergency dialling.
Go to Device > Trunk > Add New >
configure the trunk parameters as given below,
Please reset the SIP Trunk after saving.
Note: EMCC SIP Trunk doesn't have any destination IP Address!
Step 20: EMCC Intercluster Service Profile
We have to enable EMCC feature in this step. Also, specify the SIP trunk for PSTN access.
Advanced Features > EMCC > Inter Cluster Service Profile > Add new
You can click Validate to see the status.
Step 21: Add Remote Cluster
At this step, we specify the remote cluster where home cluster contacts for EMCC login.
Advanced Features > Cluster View > Add New
Step 22: Configure Visiting Cluster CL2
Perform Steps 17 - 21 on Visiting Cluster CL2
Step 23: Update EMCC Remote Cluster on both
Make sure home cluster and visiting cluster discover each other.
Advanced Features > Cluster View > Select the Remote Cluster
Perform the same on CL2
Great! We have done the EMCC Configurations successfully! Its time to test and understand the EMCC Registration.
Verify EMCC Login
Select any of the phones in Visiting Cluster CL2.
Press Service Button and select "Extension Mobility Cross Cluster" service. Enter the User ID and Password of the Home Cluster user.
Enter the User ID and Password of the Home Cluster user.
I have a home cluster user 'abdul.jaseem' trying to login to remote cluster phone which is highlighted below.
The device on the Visiting Cluster CL2 will unregister and the same device remotely registers with Home Cluster CL1.
Go to home cluster Device > Phones > Remotely Logged in Devices
You can see that the visiting cluster phone unregister from CL2 and register to CL1
That all about Extension Mobility Cross Cluster Configuration. I will be covering detailed information about the Call Routing In EMCC Login in my next article.
You find more information about EMCC Call Routing and EMCC Error codes for troubleshooting in the below links.
I ask me to explain the following:I have CUCM 12.5 Pub and Sub. There is CUCM 9.1 Pub only (for tests). Made SIP Trunk from 9.1 to 12.5 (only on Sub !!!) and from 12.5 to 9.1 (All Nodes is checked). Calls from 9.1 to 12.5 pass, from 12.5 to 9.1 no (503 er...
Is it possible for a Webex Org Full Admin to retrieve/view the chat history of an individual user? If so, how? This is referring to chat in the native Webex app, NOT for example chats that are part of a Webex meeting, or connected Jabber chat etc.
I’ve come across a strange problem with extension mobility on our CUCM 220.127.116.1100-7, it’s not site or even cluster wide, just 8 phones on a site.These 8 phones (various models) show users are logged in but the phones has been rejected. Registration...
Hi Guys, I am using AA service and when deial 1 for sales and the sales phone is ringing but I see there is 1 call in queue and handset LED is flashing, how to cancel it? because it makes a problem when no one answer the phone then it keeps ringing!&...
Hi All, We are planning to buy new BE6K and currently we have cucm unity and uccx 11.5 .Please suggest steps/process for this migration.Also new be6k is comes with esxi 7.0 so cucm unity and uccx 11.5 support this esxi version? Thanks in advance...