Communication Manager 8.x: Cross Cluster Extension Mobility lab attempt - part 2

EMCC lab attempt notes

Time to continue discussing my lab attempts with EMCC, which started about a month ago and is still 'work in progress' (mainly due to time constrains). Here is the link to my previous post on it: http://www.networkworld.com/community/node/60986

It took significant amount of time to get two CUCM 8.x instances to run on my laptop, I didn't go through the install twice. Instead I installed once and duplicated the VM, started it, renamed the host and changed its IP address. Installing CUCM on VMware is no longer a challenge (since version 6.x) and in 8.x it's even supported. The challenge was getting both servers running at the same time and being able to access the ccmadmin web page. For some reason it didn't work when the VMware network card was set to NAT, the first machine to boot would be accessible and the second would time out. The only way this worked was in bridged mode.

The EMCC config guide state that you need a secure ftp server to share certificates between the clusters, this is also a requirement for backup since CUCM 5.x but was a challenge on my win7, 64bit os, for some reason none of the simple free servers worked until I figured out that the freeFTPd gui was not showing me the start service button and used tab to get it going. I really wish Cisco would create an SFTP server, and TFTP while at it. It's really hard to recommend and support 3rd party servers which are only used for UC products backup.

Well, to make things even better, after spending all that time on SFTP, it appeared to be a redundant step which is only required when using secured CUCM cluster, oh well.

EMCC is based on a cluster to cluster communication which runs over SIP, the clusters need to be unique (non default cluster ID) and to know about each other, aside from that it's nothing more than the good old Extension Mobility. This leads to the following configuration steps:

  1. Activating the required services (CM, TFTP, EM and Bulk Provisioning).
  2. Adding the EMCC XML phone service.
  3. Adding users, devices and device profiles (just like you do in standard EM).
  4. Add EMCC templates using the BAT tool.
  5. Add an EMCC SIP trunk.
  6. Configure the EMCC Feature and Service profile and then add a remote cluster for every cluster you want to talk EMCC with.

The configuration checklist on Cisco's manual was pretty easy to follow and aside from the redundant SFTP step it was pretty accurate. This is why I haven't included screen captures on this post but if you need, comment and I'll add a post for that.

At last it was testing time, can I have my CIPC registered to cluster B and load my device profile which resides in cluster A, unfortunately the login attempt came back with the message Login is unavailable(213), which means the device does not support EMCC. Guess it makes sense since CIPC can just point to the home cluster but I wish it was documented under 'system requirements' in the manual. At this time I have no physical phone to test with so the test results will wait for next time.

That's it for now; hopefully a successful lab report will be my next post along with confirmed list of phones that can support EMCC.

Join the Network World communities on Facebook and LinkedIn to comment on topics that are top of mind.
Related:
Now read: Getting grounded in IoT