12-08-2006 08:28 AM - edited 03-18-2019 06:42 PM
i had a cisco callmanager v 3.3(2) that had been configured in a different domain as the primary callmanager and it was working properly. during redeployment to a different site i configured basic stuff and all calls were working. i decided to configure the extension mobility feature but each time a user tries to login to a phone an error message "unsuccessful login error:[11]" always appeared.i decided to make the callmanager the AD server and see whether it works. i also changed the server name from network identity (my computer properties. after the whole process, the call manager service cannot start and the administration page doesn't load. The services page loads but doesn't list any server, instead it displays an error message. Right now am trying to demote the AD and its taking ages.
12-08-2006 09:10 AM
unsuccessful login error:[11]:
Device Does Not Exist: The specified device for login or logout does not exist in the system.
12-12-2006 01:23 PM
You can't run AD on the callmanager and you also can't just change the name of callmanager. There is a procedure of changing the name but several steps involved. I don't think that you will get callmanager to start anymore. You may have to reload.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide