I'm having problems trying to set up Attendant Console, and I have scoured these forums looking for a solution. After digging through all my trace logs, I've found out that my TCD service is not able to log in. I created the ac account with the default password (12345), and was able to log into that account via the CCMUser page. I even followed the directions to change the password, but that made no difference. The error I'm receiving in my TCD log is:
Unable to create provider -- bad login or password.
In my CTI trace I get this:
kCtiProviderOpenFailure - CTI application failed to open provider CTIconnectionId:2 Login User Id:ac UNKNOWN_PARAMNAME:ReasonCode:2362179680
Also it could be possible that the passwords are not matching. The attendant console stores the password in the file ACServer.properties located in the ..\Program Files\Cisco\CallManager Attendant Console\etc directory. The password is encrypted. Make sure that this password is the same as the one for the "ac" user in DC Directory. You may want to use the "passwordutils" tool to check the password. Since you have already changed the password for the "ac" user in DC Directory, use the passwordutils tool to get the encrypted password and copy and paste it in the ACServer.properties file.
I had this exact error after upgrading from 3.14 to 3.3.3. I never had a user "ac" so I had to create one, but then I had no idea what the password would be. I used the passwordutil to set the pwd in the properties file under JTAPI password.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...