The following table describes the server requirements for installing Click to Call.

The following table describes the client computer requirements for installing Click to Call.

Problem When you access a Sharepoint site from Internet Explorer and move the mouse over the online status indicator ( ) next to a contact name and then click on the online status indicator to display the Persona menu, a Redemption instance error is displayed. This error occurs when the user is running Click to Call with restricted non-administrator privileges and when protected mode is enabled in Internet Explorer.

Solution To resolve this issue on Windows Vista and Windows 7 machines, perform the following steps:

1. From Internet Explorer, select Tools > Internet Options > Security.
2. If present, uncheck the Enable Protected Mode check box.
3. Restart Internet Explorer.

Problem The Persona Menu is not displayed when you click on the online status indicator ( ) next to a contact name in SharePoint. This occurs when one of the following conditions exists:

• Microsoft Office is not installed.
• A version of Microsoft Office other than Office 2003 or Office 2007 is installed. If Microsoft Office 2010 is installed, it displays the contact card when you click on the online status indicator instead of the Persona Menu.
• A 64-bit version of Internet Explorer is running.
• If a user accesses a SharePoint site by browsing to the site from the Internet, the Internet Explorer settings prevent the site from loading the Persona Menu. If a user accesses the SharePoint site by typing the URL for the SharePoint site, Internet Explorer displays the Persona Menu.

Solution To resolve this issue, you can do the following:

• Install Microsoft Office 2003 or 2007.
• Close 64-bit Internet Explorer and run a 32-bit version of Internet Explorer.
• Use an Intranet URL to access the SharePoint site.

Problem If a user has a password that contains special characters, the CCMCIP server cannot handle the special characters and so Click to Call cannot determine if a user is an Extension Mobility user. Click to Call also cannot gather this data if the CCMCIP server is unavailable.

Solution In this situation, Click to Call displays an I am an Extension Mobility user check box on the Phones tab of the Click to Call Preferences dialog box. If you check this check box, an Extension Mobility device is listed in the list of phones for the user.

Note

If you check the I am an Extension Mobility user check box, an Extension Mobility device is listed in the list of phones for the user even if the Extension Mobility device is not configured for the user in Cisco Unified Communications Manager. Users must ensure that they are configured to use an Extension Mobility device in order to use Click to Call to make calls.

If a firewall or proxy server exists between Cisco Unified Communications Manager and the client PC, your end user may not be able to use Click to Call.

Click to Call sends request messages to Cisco Unified Communications Manager over HTTPS using port number 8443. Therefore, you need to configure the firewall or proxy server to allow message requests and responses between Click to Call and Cisco Unified Communications Manager over HTTPS using port number 8443.

Click to Call supports Microsoft PowerPoint 2007 and 2010. However, the Click to Call menu options are not available from the context menu in Powerpoint 2007 and 2010 when you highlight and right-click a number or a contact. The Click to Call functionality is only available from the Home tab on the Ribbon.

If you are running Microsoft Outlook 2003 without Microsoft Office 2003 or if the Smart Tag component is disabled during the Microsoft Outlook installation, the Persona menu is not available. Consequently, the Click to Call functionality under the Persona menu is not available in this situation.

Smart tags (dotted lines beneath text) in email messages are not supported with Click to Call and Outlook 2003. If smart tags are configured and working in such an environment, the smart tags can cause Click to Call to slow down the display of email.

For some East Asian locales, the Microsoft Global Input Method Editor (IME) feature is enabled by default in Microsoft Word. If the Microsoft Global IME is enabled in Microsoft Word 2003 or 2007, the Call option on the Click to Call right-click menu is not available; only the Call with Edit option is available. If you disable the Microsoft Global IME feature in Microsoft Word, the Call menu item will be available.

Click to Call does not currently support Cisco Unified Personal Communicator. Cisco Unified Personal Communicator is distributed with a modified version of Click to Call.

Click to Call does not currently support Cisco Unified Communications Integration for Microsoft Office Communicator. Cisco Unified Communications Integration for Microsoft Office Communicator is distributed with a modified version of Click to Call.

In Citrix XenApp environments, Click to Call sometimes displays the call notification window in an unexpected location on the desktop, for example, over the taskbar. This occurs if the resolution or display settings differ on the server and the client machine.

The End Call button on Click to Call terminates all active calls, including any calls that the user has on hold. The held call is terminated locally, but the remote held call remains active and the person on hold receives no indication that the call is terminated.

Note

Because this is unexpected behavior, we highly recommend that you provide your end users with the following description of how the End Call button operates when a user places a call on hold: When you press the End Call button on Click to Call, this ends all your current calls, including any calls you have on hold. For example, if you are on Call 1, and you place Call 1 on hold to take Call 2, when you press the End Call button to end Call 2, the application ends both Call 1 (on hold) and Call 2. However, Click to Call only disconnects the held call locally at your end of the call. The person you have placed on hold is not disconnected, and receives no indication that the call has ended.

Note that this is expected behavior on Cisco Unified Communications Manager. You can control this behavior on Cisco Unified Communications Manager using the cluster-wide phone device service parameter Enforce Privacy Setting on Held Calls. Privacy removes the call information from all phones that share lines and blocks other shared lines from barging in on its calls. Enabling the service parameter Enforce Privacy Setting on Held Calls enforces privacy when a call is placed on hold on a shared line; this service parameter is disabled by default.

Note

The Enforce Privacy Setting on Held Calls parameter is a cluster-wide service parameter. Therefore it applies to all phone devices and all users in the Cisco Unified Communications Manager cluster. The Enforce Privacy Setting on Held Calls parameter is only applicable to Cisco Unified Communications Manager versions 6.x and 7.x.

Note	This issue is not applicable if you are running Cisco Unified Communications Manager version 7.x or later.

Problem The Cisco WebDialer application is only expected to apply Application Dial Rules on Cisco Unified Communications Manager. However, if there are Directory Lookup Rules configured on Cisco Unified Communications Manager, the Cisco WebDialer application may apply the Directory Lookup Rules before it applies the Application Dial Rules.

This may cause call routing issues on the Click to Call application. When deploying Click to Call, ask your end users to report any inconsistent call behavior, as it may be related to this issue.

Solution Perform the following workaround on Cisco Unified Communications Manager. For each Application Dial Rule you have configured, create a corresponding dummy Directory Lookup Rule. The dummy Directory Lookup Rules should be invalid; Cisco Unified Communications Manager should not be able to match the dummy Directory Lookup Rules.

Prioritize the dummy Directory Lookup Rules at the top of the Directory Lookup Rule list, before any authentic Directory Lookup Rules. This ensures that the Cisco Webdialer application applies the Application Dial Rules first. In the Application Dial Rule list, configure the final Application Dial Rule to match any number that the other Application Dial Rules do not match. This ensures that the Cisco Webdialer application finds an Application Dial Rule match, and does not attempt to apply the Directory Lookup Rules.

Problem The user is unable to associate a phone on the Click to Call application.

Solution If your organization routes HTTP traffic via proxy servers to access the Internet, you must add an exception for the internal HTTPS traffic sent from the Click to Call application to the Cisco Unified Communications Manager server.

However, if this exception contains the server name of the Cisco Unified Communications Manager, and the IP address of the Cisco Unified Communications Manager is configured on the Click to Call application, this configuration may still route the HTTPS traffic externally. If this occurs, either add an exception for the IP address and port number of the Cisco Unified Communications Manager, or use the server name that is already covered by an exception. An example of the full exception rule is https://<ip-address|server-name>:8443.

Problem When you uninstall Click to Call on Internet Explorer, the Click to Call menu items are not removed.

Solution To resolve this issue, remove the following registry keys:

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\MenuExt\Ca&ll

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\MenuExt\Call with E&dit

Known problems (bugs) are graded according to severity level. These release notes contain descriptions of the following:

• Significant severity level 3 bugs.
• All customer-found bugs.

You can search for problems by using the Cisco Software Bug Toolkit.

Before You Begin

To access Bug Toolkit, you need the following items:

• Internet connection
• Web browser
• Cisco.com user ID and password

Procedure

1. To access the Bug Toolkit, go to http:/​/​tools.cisco.com/​Support/​BugToolKit/​action.do?hdnAction=searchBugs.
2. Log in with your Cisco.com user ID and password.
3. To look for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field, then click Go.

For information about how to search for bugs, create saved searches, and create bug groups, click Help in the Bug Toolkit page.

The caveats in the following table describe possible unexpected behavior in the Click to Call release. Bugs are listed in order of severity and then in alphanumeric order by bug identifier.

The following caveats have been resolved in version 8.1 of the product:

The English-language version of the online help and the User Guide for Click to Call on which the translations are based is slightly different from the English-language version that is built into the product and available from the corporate website. The following table lists the differences between the two versions: