Architecture of Click to Call in a Cisco Unified Communications System
•Overview of Click to Call
•Click to Call Executable Files
•Architecture of Click to Call
•Synchronization of the Roaming Profile
•Click to Call in Complex Virtualized Environments
Overview of Click to Call
Click to Call enables you to place calls from within your applications, or from your clipboard. Click to Call includes a series of plug-ins that work with your applications, multiple DLL files, and several executable files.
You can install Click to Call directly on the computers of your users, or you can publish Click to Call in a virtualized environment, such as Citrix XenApp.
Click to Call Executable Files
Table 1-1 lists the Click to Call executable files.
Table 1-1 Click to Call Executable Files
|
|
CiscoCallApplication.exe |
This executable file enables you to do the following: •Place calls to numbers and contacts in your applications. •Displays the Call with Edit dialog box. Use this dialog box to place calls to numbers on your clipboard. You can use the keyboard shortcut Ctrl+Alt+D to open this dialog box. •Place calls to numbers with the tel protocol. You can place a call to any number that is formatted as follows: tel:<number> •View your call history. |
clicktocall.exe |
This is the Click to Call configuration application. This executable file enables you to do the following: •Double-click in your notification area of your Windows taskbar to open the Call with Edit dialog box. •Right-click to open a menu that enables you to configure Click to Call, set your preferences, select a phone to use with Click to Call, call a number from your call history, open the Click to Call online help, and more. |
ProblemReportingTool.exe |
This executable file enables you to run the Problem Reporting Tool. This tool collects logs and information from your system if something unexpected occurs, or if an application crashes. The tool compresses these logs up and puts the compressed file on the desktop. |
Table 1-2 lists the default locations for the Click to Call executable files.
Table 1-2 Location of Click to Call Executable Files
|
|
32-bit |
C:\Program Files\Cisco Systems\Click to Call |
64-bit |
C:\Program Files (x86)\Cisco Systems\Click to Call |
Note When you deploy Click to Call in a virtualized environment, the path to the executable files must be the same on every server in the virtualized domain, regardless whether the domain comprises 32-bit and 64-bit servers. For example, if your domain comprises a mixture of 32-bit and 64-bit servers, you must modify the default installation path for one or other server type during the Click to Call installation to ensure that the path to the executable files is the same for all servers.
Architecture of Click to Call
The Click to Call architecture is designed to support both local installations of Click to Call, and deployments of Click to Call in virtualized environments.
The Click to Call architecture includes plug-ins for each of the applications that Click to Call supports. The Click to Call assembly, called CoWebDialerProvider.exe, reads the Click to Call configuration data, creates calls, displays notification windows, and writes the history of calls to the roaming profile of the user in the %APPDATA% folder.
Figure 1-1 illustrates the Click to Call architecture.
Figure 1-1 Click to Call Architecture
Synchronization of the Roaming Profile
The Click to Call configuration data, call history, and logs are stored in the %APPDATA% folder of the user, also referred to as the roaming profile. If Click to Call is installed locally, the files are synchronized across the Click to Call plug-ins.
In a virtualized environment, these files might not be synchronized. If the files are not synchronized, users might see incomplete call history, or might need to specify their Click to Call configuration more than once.
For more information about how to implement roaming profiles in a Citrix environment, go to the following URL:
http://support.citrix.com/article/CTX120285
Click to Call in Complex Virtualized Environments
This guide describes the Click to Call architecture, and how Click to Call works. If you integrate Click to Call with a complex virtualized environment, and you experience unexpected behavior in Click to Call, ensure that you understand how Click to Call works. Group policies, firewalls, proxies, or other features of your virtualized environment might cause unexpected behavior in Click to Call.