When an attendant attempts to log on to the Attendant Console, it is possible that a few errors show up while the Attenadant Console is set up. These are some of the error messages:
Initialization of Telephony Failed
Initialization of Call Control Failed
Attendant Cannot Access Server Error Message
Error—Initialization of Telephony Fails
Symptom—The attendant receives an error message that the initialization of telephony failed.
Possible Cause—You must associate the AC user to the Standard CTI Allow Park Monitoring user group in Cisco Unified CallManager Administration.
These are some possible additional causes:
The pilot point and/or the controlled phones are not in the controlled device list of the AC user.
No AC user exists.
There is an AC user password mismatch.
The AC user is not associated to the Standard CTI Enabled user group in the Cisco Unified CallManager Administration.
It is recommended to complete these steps:
From Cisco Unified CallManager Administration, choose User Management > User Groups. The Find and List User Groups window displays.
Choose the Standard CTI Allow Park Monitoring user group link. The User Group Configuration window displays.
Choose Add Application Users to Group. The Find and List Application Users window displays.
Enter the AC username in the search box, and click Find.
Check the check box next to the AC user, and choose Add Selected.
Error—Initialization of Call Control Fails
Allow Control of Device from CTI
Make sure that you check the Allow Control of Device from the CTI checkbox on the Phone Configuration window for each attendant phone. The system enables this field by default. If this checkbox is not checked for the attendant phone, call control does not come up for the attendant console.
Possible Cause—You installed Microsoft Windows XP SP2 on the attendant PC, and you did not unblock the firewall.
It is recommended that when you start Cisco Unified CallManager Attendant Console for the first time after you install Windows XP SP2, a dialog box displays that indicates that Windows Firewall has blocked some features of the ACClient application. In order to create an exception in the Windows Firewall, so you can continue to use Cisco Unified CallManager Attendant Console, choose Unblock. The operating system configures the exception automatically.
If you do not choose Unblock when you open Cisco Unified CallManager Attendant Console for the first time after you install Windows XP SP2, use this procedure in order to create an exception, so you can continue to use Cisco Unified CallManager Attendant Console:
Choose Start > Settings > Control Panel > Windows Firewall. The Windows Firewall dialog box displays.
Choose Add Program. The Add a Program dialog box displays.
Choose Browse. Navigate to the ACClient.exe file and click Open. The ACClient displays in the application list on the Exceptions tab of the Windows Firewall dialog box.
Choose Edit. The Edit a Program dialog box displays.
Choose Change Scope. The Change Scope dialog box displays.
Make sure that you choose the Any computer (including those on the internet) radio button.
Click OK twice.
Error—Attendant Cannot Access Server Error Message Displays
When the attendant attempted to log in to the server, a dialog box stated that the attendant cannot access the server.
The version of the attendant console that is on the attendant PC and the version of the attendant console that is available through Cisco Unified CallManager Administration do not match.
Upgrade the version of the attendant console that runs on the attendant PC with the use of these steps:
From each Cisco Unified CallManager Attendant Console PC, browse into a server that runs Cisco Unified CallManager Administration and log in with administrative privileges.
From Cisco Unified CallManager Administration, choose Application > Plugins.
Click the Download link next to Cisco Unified CallManager Attendant Console.