I am trying to make a modification of the agent Id in terms of providing the extension number to login. While doing the changes and save them, the values get reflected in UCCX. In this case, I am making an extension number change and the changes are not being reflected in UCCX with the result the agent is not able to login to new extension. Please help !!!!
There are a few things to check here. First, verify that you have performed a Manual Synchronization of Directory Services in UCCX. This is usually the one that takes care of the problem. Go to Cisco Desktop Administrator and under "Services Configuration" see the entry "Synchronize Directory Services". There is a button there you click to manually Synchronize. If the first attempt fails, try again until you see a "Transaction Complete" message.
If that didn't work, ensure the extension number has been added to the list of controlled devices under rmcm application user in CUCM. If the IP 7942 device wasn't previously added, add it and save your changes.
If that didn't work, ensure the extension number has been added to the agent's end user profile - more specifically, make sure the MAC address of the IP 7942 is shown under the profile for "Controlled Devices" and also make sure the correct extension number is listed for the IPCC extension under "Directory Number Associations" in his profile.
Usually I add agents in reverse of the steps listed above by first adding phone MAC and IPCC Extension to end user profile, then adding MAC/DN of phone to rmcm application user and then finally performing a manual synchronization of directory services in UCCX.
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.