This is normally a directory integration error. This could be LDAP, Active Directory, or DC Directory for example. Based on what method of directory integration is used, troubleshooting can vary. Check that the Active Directory server is running. If there is an issue here, run the Directory plug-in and Admin utility from Cisco CallManager. If the problem exists with LDAP, check that the DirUser.jar file is present. This issue can also occur if there is no device profile associated with the user that attempts to login.
Check if the users have device profiles associated with them under the User Configuration > Extension Mobility page. If not, update users with device profiles for Extension Mobility login.
Troubleshooting Extension Mobility in Cisco CallManager:
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.