I have been around UCCE since 4.6.2 and CUCM 3.0 and customers of mine tend to use Extension Mobility since then. Apart from PEBKAC problems, it just worked fine, even though I need to tell you the largest call center was around 1000 agents, so I don't know whether it is valid with an 8K call center).
Thanks for the response. Can you define what PEBKAC represents? Also, I would be interested to know your experience with the management portal as a tool for configuring agents and cucm users. Have you found any issues with using the tool?
PEBKAC (Problem Exists Between Keyboard And Chair), for instance:
- from the administrator's side: helpdesk guy forgets to assign the Extension Mobility service to Device and/or Device profile
- from the agent's side: agent forgets the simple fact she needs to log into both the telephone and the call center, or she logs on to a different telephone, this leads to situations when calls arrive to the desktop but it actually rings in a completely different city.
But apart from that, nothing.
Of course, it's always good to keep an eye on the release notes and just to be on the safe side, never install the latest version of CUCM ;-)
UCCE 8.x can use the EM, and there are lots of issue with EM and CTI manager in cucm 8.6 since it having major CTI architectural changes.
one of the issue that we have faced here is that ICM is allowing agent to login even if the agents not logged in to cisco phone using their EM profile. this will resolve only either by recreate the device profile for the user or restart the CTI manager service on all nodes.
for more information please refer page no : 29 on Cisco Unified Contact Center EnterpriseSolution Reference Network Design (SRND).
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.