Hi. Currently I'm configuring attendant console in a CCM6 environment. For some reason we are unable to bring up the call control. We are always receiving "Initialization of Call Control Failed. Retrying" message.
We follow the configuration guide for CCM6 completly. Create the AC user as application user.. assigned the ac user to the CTI Allow Call Park Monitoring Group as well as the CTI Allow all devices super user group.. also I add the specific Attendant Phone to the AC user as well but no luck...
On the client running XP with no Firewall turn on we are having:
32[Thread-12]02/28 14:20:10.171 ERROR Thread-12 >>> ACClientTelephonyMgr.init(): Failed to do provider Login. com.cisco.ac.common.ACException: Unable to create provider -- user is not authorized, please check CM administration.
Hi, seems that you created the ACDeviceAuthentication application user, but did you make sure that this user matches the field on service parameters???
If you did not, please do so, by the way, you will need to associate the phones and pilots to this user.
Make sure that the user ID that you use for the device authentication user is the same as the value in the ACDeviceAuthentication field in the Service Parameters Configuration window for the Cisco CallManager Attendant Console Server service. For information on accessing the Cisco Unified CallManager Attendant Console service parameters
Thanks.. I already did that with the ACDeviceAuthentication user but the result was the same. So I deleted the user and right now I'm only using the ac user... I already associate the phones and pilots to the ac but problem persist. The only thing that is working is the line states.. but still having problems controlling the phone line and call control never comes up.
Here the error I found on the CTI SDI traces:
02/28/2008 14:48:31.524 CTI|authenticationDB::authenticateUserWithPassword(): Found applicationuser|<:STANDALONECLUSTER><:172.19.100.10><:ALL><:FFFF>
I got a similar problem following the instructions step by step. In my case after looking around I found that the app users (ac and ACDeviceAuthenticateUser) were missing from the following group: "Standard CTI Enabled".
Go to User Management and then to User Group, add both app users (ac and ACDeviceAuthenticateUser).
Keep in mind that I am assuming that you did everything else base on the documentation for "CCM6 Features and Service Guide"
I finally fix my problem my issue was the same and I fixed this way:
You must associate the attendant console application user to the Standard CTI Enabled users(both users) group and the Standard CTI Allow Call Park (both users), and Standard CTI Allow Control of All Devices (ac user).
- Inside of the user: ACDeviceAuthenticationUser associate the phone only.
- Inside the user: ac associate the pilot point only.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...