cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
909
Views
0
Helpful
7
Replies

Attendant Console Call Control Buttons

Support Support
Level 1
Level 1

Hello,

A customer of ours is having problems with Cisco Unified Enterprise Attendant Console (CUEAC) whereby the call control buttons do not seem to be available. The problem follows the account, in that there are 2 working PCs, one working account and one non working account. The working account can log on to both PCs (and works), the non working account can log on to both PCs (and doesn't work). The call control buttons are greyed-out and there is a general 'All Queues' queue missing.

The system version is: OPR.9.1.1.1372. The server and clients have been rebooted. The End User, Device and Line have CTI control enabled. Any ideas?!

Thanks.

 

7 Replies 7

tonyperla
Spotlight
Spotlight

Hello,

Have you verified that the non-working account has the exact same permissions applied that the working account has?  You could log in with a full blown local admin account and test to verify that nothing is wrong with the CUEAC install.  You could also grant full-control abilities to the C:\program files\cisco\attendant console and also in the registry, HKLM\software\arc solutions to see if that resolves the issue.

 

Hope this helps

Tony

Please rate helpful posts

Please rate helpful posts
Thanks,
Tony

Hello,

The documentation says that the registry keys should be in HKEY_Local_Machine\Software\Arc Solutions, but it is not present (see attached). Is there any documentation that confirms exactly where this registry key is?

Thanks.

Is the attached screen shot from the client PC or the actual server?  What version of Windows is the client PC running?

Thanks.

Please rate helpful posts
Thanks,
Tony

Hello,

This is taken from the client, running Windows 7.

 

Is it 64-Bit OS?  Can you try looking under HKLM\Software\Wow6432Node\ and see if the Arc Solutions folder is there?

Thanks.

Please rate helpful posts
Thanks,
Tony

Hello,

I should have said whether it was 64-bit in the previous post. It is 64-bit, but the Administrator has logged-in and the operator which was getting the problem previously is still getting the same problem. This should remove any problems to do with permissions on files or the registry.

A restart of the CTI Manager service on CUCM fixed it!