Installation

This chapter describes how to install the Cisco Unified CallConnector for Microsoft Dynamics CRM 3.0 with the following software:

Prerequisites

•

If you are upgrading from a previous version of the Cisco Unified CallConnector for Microsoft Dynamics CRM (version 2.x), you must uninstall the old version before installing this version.

•

If you are integrating with Cisco Unified Contact Center Express, you must follow the Cisco Unified Communications Manager installation steps as described in the Cisco Unified Communications Manager technical documentation, and then complete the "Integrating with Cisco Unified Contact Center Express" steps as described in the Cisco Unified Contact Center Express technical documentation to complete the configuration process.

•

Install, configure, and verify the proper operation of Cisco Telephony Application Programming Interface (Cisco TAPI) software must be before proceeding with the installation of the Cisco Unified CallConnector for Microsoft Dynamics CRM components.

•

Install the Microsoft .NET Framework before proceeding with the Cisco Unified CallConnector for Microsoft Dynamics CRM installation.

Restrictions

•

The installation process is supported by Virtual Network Computing (VNC) and other remote control desktop software, but is not supported by Terminal Services.

About Installing Cisco Unified CallConnector for Microsoft Dynamics CRM

Install and ensure operation of the Cisco Unified CallConnector for Microsoft Dynamics CRM server component on the Microsoft CRM server itself. To allow for maximum ease of installation during the client phase, install and ensure operation of the Cisco Unified CallConnector for Microsoft Dynamics CRM server component and service before installing clients because they will attempt to contact the Cisco Unified CallConnector for Microsoft Dynamics CRM server component during their own installation.

Note Configure the Cisco TAPI client software properly and ensure it is running before proceeding with the installation of the Cisco Unified CallConnector for Microsoft Dynamics CRM software. Verify that you can monitor and control the end-user phone extension associated with the client PC. Failure to do so will cause problems during the Cisco Unified CallConnector for Microsoft Dynamics CRM installation. For more information about installing and configuring the Cisco TAPI software, see the Cisco Unified Communications Manager technical documentation.

Software Installation Order

You must install the Cisco Unified CallConnector for Microsoft Dynamics CRM server and client components in the following order:

Cisco Unified CallConnector for Microsoft Dynamics CRM server component (installed on Microsoft CRM server)

Cisco Unified CallConnector for Microsoft Dynamics CRM client component (installed on all client PCs using the Cisco Unified CallConnector for Microsoft Dynamics CRM)

Installing the Cisco Unified CallConnector for Microsoft Dynamics CRM Server

Use the following steps to install the Cisco Unified CallConnector for Microsoft Dynamics CRM server.

Step 2

Locate and double-click the Setup.exe file for the Cisco Unified CallConnector for Microsoft Dynamics CRM Server installer (see Figure 1) to bring up the Setup Wizard (see Figure 2).

Figure 1 Server Setup.Exe File: Cisco Unified CallConnector for Microsoft Dynamics CRM

Figure 2 Server Setup Wizard: Cisco Unified CallConnector for Microsoft Dynamics CRM

Figure 3 Server License Agreement Window: Cisco Unified CallConnector for Microsoft Dynamics CRM

Figure 4 Select Installation Folder Window: Cisco Unified CallConnector for Microsoft Dynamics CRM

Step 6

Click Next to accept the default installation folder location (we recommend this).

Figure 5 Server Installation Confirmation Window: Cisco Unified CallConnector for Microsoft Dynamics CRM

Figure 6 shows how this configuration dialog might appear after configuration, before configuring the phone number processors. In this example, "triton" is the Microsoft CRM server name and it runs on port 5555. Include the remainder of the path that you see in the example (specifically, /MSCRMServices/2006/CrmService.asmx).

Figure 6 Server Configuration Window—Server Configuration Tab: Cisco Unified CallConnector for Microsoft Dynamics CRM

When you click the Test button next to the CRM Services URL, you may receive various responses. Figure 7 shows what you want to see. "The URL is Valid" means that the C4 Server Service successfully contacted the Microsoft CRM Web Services.

Figure 8 shows a validation error. In this instance, the URL is probably not the correct location to the Microsoft CRM Web Services. Verify the URL and try again.

Figure 8 Validation Error Message: Cisco Unified CallConnector for Microsoft Dynamics CRM

Figure 9 shows a Simple Object Access Protocol (SOAP) error. This could indicate that the user installing the C4 Server Service does not have access to Microsoft CRM.

Figure 9 Validation Error Message: Cisco Unified CallConnector for Microsoft Dynamics CRM

Step 9

In the Server Configuration tab (see Figure 6) check or uncheck the Enable CRM Keepalive Searches field to enable or disable keepalive searches.

Use the keepalive feature to ensure that the Microsoft CRM server is continuously polled so that it does not drop objects from its cache, which could negatively affect a demonstration environment. You do not need to use this feature in a live deployment or production environment.

•

Domain—User domain to use when authenticating for performing keepalive searches.

•

Username—Username to use when authenticating for performing keepalive searches.

•

Password—User password to use when authenticating for performing keepalive searches.

•

Delay—Delay in seconds to wait after performing any search before initiating a keepalive search.

Figure 10 Server Configuration Window—Performance Counter Tab: Cisco Unified CallConnector for Microsoft Dynamics CRM

Step 12

In the Performance Counter tab, check or uncheck the Enable Performance Counters box to enable or disable performance monitor counters. To view these objects, add "C4.Server" as a counter within the Windows Performance Monitor, and select the objects to monitor.

•

Number of Remoting Calls—Total number of client-initiated server requests.

•

Remoting calls per second—Average number of client-initiated requests per second.

•

Average time/Search (seconds)—Average time in seconds to complete a full search.

•

Average time/SubSearch (seconds)—Average time in seconds to complete a search of any specific entity.

•

Total Number of Searches—Total number of searches that have been performed.

•

Number of Active Searches—Number of searches that are currently executing.

The Search Configuration tab displays the entities and fields within Microsoft CRM that the Cisco Unified CallConnector for Microsoft Dynamics CRM will search to match the Caller ID or name to a customer record. You do not need to manipulate this file for initial program usage.

Figure 11 Server Configuration Window—Search Configuration Tab: Cisco Unified CallConnector for Microsoft Dynamics CRM

Figure 12 Server Configuration Window—Logging Tab: Cisco Unified CallConnector for Microsoft Dynamics CRM

•

Maximum log file age—Maximum age in days of old (existing) log files. You must use dynamic filenames.

•

Maximum log file size—Maximum approximate size in KB of any single log file.

•

Ignore inbound/outbound phone numbers—Allows you to specify phone numbers that the Cisco Unified CallConnector for Microsoft Dynamics CRM client should ignore when processing inbound and outbound phone numbers. The first four boxes allow you to specify numbers to ignore when the phone number either begins with, ends with, is exactly, or contains the specified digit strings. Only digits are allowed. The fifth box, "Custom/Advanced," allows you to specify regular expressions of phone number digit strings to ignore.

•

Edit Phone Number Processor Configs—Click to configure the phone number processors.

•

Default PNP Config—Default phone number processor configuration for clients with unspecified or invalid phone number processor configurations.

When you first configure the Cisco Unified CallConnector for Microsoft Dynamics CRM server component and enter the Phone Number Processor (PNP) Configuration window, you see a blank configuration area, as shown in Figure 13, because you must first create a new phone number processor configuration.

Step 16

In the Phone Number Processor Configuration window, click New to begin a new configuration.

Step 17

In the New PNP Configuration window, enter a configuration name and click OK.

You can configure each client to use one of the multiple configurations that you have defined. You can define each additional configuration as a site, for use with branch or remote offices that have a different area code than the main business location where the Microsoft CRM server is located.

Step 18

The Phone Number Processor Configuration window appears, as shown in Figure 15. Some defaults are loaded based on the United States 10-digit dialing rules.

Step 19

Click the import defaults for your area. The supported configurations include the following:

All of these predefined configurations require additional custimization for your specific area. To import one of these configurations, click Import Country-Specific Defaults near the bottom of the dialog window, and select a configuration. Figure 16 shows the details of the lower right section of the Phone Number Processor Configuration window.

Note If you do this with a predefined configuration, it will be overwritten, and you will lose any custom dialing rules (specifically pattern recognizers and search formats).

Step 20

Configure the Phone Number Processor Configuration window, as shown in Figure 17. The values that you can configure in the Phone Number Processor Configuration window are described in Table 2.


Section	Configurable Values
Access Codes	You can define five access codes. Their actual use is dictated by the values provided in the "How to dial..." section, but their general use is described below. Each access code has a mnemonic associated with it, which is shown in curly braces. •Obtain a local outside line {out}—Digit string that is typically dialed before placing local calls. •Obtain a long-distance outside line {ldout}—Digit string typically dialed before placing local long-distance and international calls. •National Long Distance Prefix {ldp}—Digit string typically dialed before the area code when placing long-distance and international calls. •International Long Distance Prefix {idp}—Digit string that is typically dialed to indicate the call is international. •Local Country Code {localcc}—Digit string representing the country the user is located in when users dial from another country.
How to dial...	Each box in this section defines how to dial a phone number after it is divided into parts (country code, area code, etc.). Typically, the values provided in each style phone number field are combinations of codes that are built into the program, although you could also provide numbers directly in each box. The codes that are available are the same codes shown in the Access Codes and Phone Number Pattern Recognition sections, plus one special code, "{}," which means all digits. The "Ask?" check box next to each field tells the client whether to ask the user to verify the phone number before dialing when using click-to-dial, and when there is only one phone number for the requested click-to-dial contact.
Area Codes	The values in these boxes are used by the "Phone Number Pattern Recognition" section to determine the accurate parts of each phone number, and to determine the style (local, long distance, etc.) of the phone number being processed. The exact way in which these area codes are used is determined by the Phone Number Pattern Recognition section, but the intended meaning of values in each box are: •Local—Values are considered local area codes. •Long Distance—Values are considered long-distance area codes. •Split Local/LD—Values are local and long distance area codes. •Local Exchanges—For each area code in the "Split Local/LD" box, values are the local exchanges for that area code. Values in this box are maintained individually for each area code in the "Split Local/LD" box. The Enable a Default Area Code check box allows the system to assign the user's local area code if it is not in the contact's record. If the area code is in the CRM contact record, then this field is not used during processing.
Phone Number and Pattern Recognition	This area is what really allows the client to pick the parts of the phone number for efficient CRM searching and for accurate no-touch click-to-dial capability. It uses Microsoft .NET Regular Expressions to identify each part of the phone number. The patterns are used during both incoming and outgoing phone call detection for efficient CRM searches, and also click-to-dial. First, the phone number is filtered according to the prefilter. Anything that matches the prefilter is removed from the digit string being considered. Then, the digit string is tested with each pattern in order until a match is found. Each pattern must result in at least one named match for the following values: •CC—Country code •AC—Area code •EX—Exchange •ST—Station •EXT—Extension •SN—Generic "subscriber number" The subscriber number may or may not follow the typical definition of a subscriber number; this value is more of a generic container. After a pattern is found that matches the digit string, and it is divided into its parts, one of two things occurs: •If the number is being processed for click-to-dial, the style of the phone number is determined by specific rules. The phone number is then dialed as specified in the "How to dial..." section. •If the number is being processed for searching Cisco Unified CallConnector for Microsoft Dynamics CRM, it is formatted and searched according to the patterns specified in the "Search Formats" area.
Search Formats	Search formats allows the administrator to maximize efficiency and accuracy when searching Cisco Unified CallConnector for Microsoft Dynamics CRM. After a phone number is processed by the pattern recognizers, the list of search formats is processed in order until one is found in which all components of the search format can be provided. Each search format component is a code that matches the named match values detected by the pattern recognizers. Each matching value is then replaced with that portion of the phone number. There are two formats for each search component, using AC as an example: •{ac}—Replaces the "{ac}" with the area code detected from the phone number. •{%ac%}—Replaces the "{%ac%}" with the area code detected from the phone number with "%" symbols between each digit. The first format provides the most accurate searching, however, in some cases, may not find the correct records if there are other characters interspersed in the text stored in Cisco Unified CallConnector for Microsoft Dynamics CRM. This will not occur if Cisco Unified CallConnector for Microsoft Dynamics CRM users are diligent about how they enter phone numbers into the Cisco Unified CallConnector for Microsoft Dynamics CRM system. When other characters are interspersed in the text in Cisco Unified CallConnector for Microsoft Dynamics CRM, the "{%ac%}" format can help because it will still recognize those values, but probably also produces some results that are not true matches.

The Cisco Unified CallConnector for Microsoft Dynamics CRM Server Service is now installed and starts automatically, as shown in Figure 18.

Step 23

Next, the installation of the Cisco Unified CallConnector for Microsoft Dynamics CRM server component prompts you to choose which website to install the Independent Software Vendor (ISV) customizations into. Choose the Microsoft CRM 3.0 website from the drop-down list, as shown in Figure 19.

Step 24

After selecting the Microsoft CRM website, the installer displays a notification message, which advises you that the ISV customizations are installed, as shown in Figure 20, but you must manually remove the default customizations. Otherwise, you may receive unwanted buttons in the Cisco Unified CallConnector for Microsoft Dynamics CRM GUI, such as the Test button.

Installing the Cisco Unified CallConnector for Microsoft Dynamics CRM Client

Note For maximum ease of configuration, install and verify the operation of the Cisco Unified CallConnector for Microsoft Dynamics CRM Server Service before installing clients.

Install the following software for the Cisco Unified CallConnector for Microsoft Dynamics CRM Client.

–

Cisco Unified Communications Manager Telephony Application Programming Interface (Cisco Unified Communications Manager TAPI) Client (if integrating with Cisco Unified Communications Manager, with or without Cisco Unified IPCC Express integration)

–

Cisco Unified Communications Manager Express IOS TAPI Service Provider (Cisco IOSTSP) Client (if integrating with Cisco Unified Communications Manager Express). Obtain the latest version of this file from:

Perform the following steps to install the Cisco Unified CallConnector for Microsoft Dynamics CRM Client with Cisco Unified Communications Manager, Cisco Unified Communications Manager Express, and Cisco Unified IPCC Express.

Step 2

Locate and double-click the Setup.exe file for the Cisco Unified CallConnector for Microsoft Dynamics CRM Client installer (see Figure 21).

Figure 21 Cisco Unified CallConnector for Microsoft Dynamics CRM Client Installer Extracted Files

The Cisco Unified CallConnector for Microsoft Dynamics CRM Client Setup Wizard appears (see Figure 22).

Figure 22 Client Setup Wizard: Cisco Unified CallConnector for Microsoft Dynamics CRM

Figure 23 License Agreement Window: Cisco Unified CallConnector for Microsoft Dynamics CRM Client

Figure 24 Select Installation Folder Window: Cisco Unified CallConnector for Microsoft Dynamics CRM Client

Step 7

Click Next to accept the default installation folder and confirm the installation.

Figure 25 Confirm Installation Window: Cisco Unified CallConnector for Microsoft Dynamics CRM Client

The installation begins copying files. After the files are copied, the Cisco Unified CallConnector for Microsoft Dynamics CRMClient Configuration window appears, as shown in Figure 26.

Figure 26 Client Configuration Window —TAPI Configuration Tab: Cisco Unified CallConnector for Microsoft Dynamics CRM

The TAPI Configuration tab allows you to specify the line to monitor for incoming and outgoing calls (see Figure 26). You can also specify to completely ignore either inbound or outbound calls (or both).

The TAPI Lookup timeout field specifies a value in milliseconds, after which time the Cisco Unified CallConnector for Microsoft Dynamics CRM client manually asks the provider for caller ID information if the TAPI client does not provide it. If the client frequently reports the wrong phone number (such as the internal voice-mail pilot extension), increasing this value may eliminate this.

The Client Configuration window's Ignore List tab appears as shown in Figure 27.

The Ignore List tab allows you to specify phone numbers that the Cisco Unified CallConnector for Microsoft Dynamics CRM client should ignore when processing inbound and outbound phone numbers from the client side. The first four boxes allow you to specify numbers to ignore when the phone number either begins with, ends with, is exactly, or contains the specified digit strings. Only digits are allowed. The fifth box, "Custom/Advanced," allows you to specify regular expressions of phone number digit strings to ignore.

Figure 27 Client Configuration Window—Ignore List Tab: Cisco Unified CallConnector for Microsoft Dynamics CRM

The Client Configuration window's CRM Configuration tab appears, as shown in Figure 28.

The CRM Connector Configuration tab allows you to specify server and login information for both the Cisco Unified CallConnector for Microsoft Dynamics CRM server and the Microsoft CRM server.

Figure 28 Client Configuration Window—CRM Configuration Tab: Cisco Unified CallConnector for Microsoft Dynamics CRM

Step 12

In the Cisco Unified CallConnector for Microsoft Dynamics CRM Server field, enter the hostname on which the Cisco Unified CallConnector for Microsoft Dynamics CRM server is installed. After initial configuration, when you change the value in this field, the value in the Cisco Unified CallConnector for Microsoft Dynamics CRM Server Web Path will be updated with the same value. Change this if the Cisco Unified CallConnector for Microsoft Dynamics CRM server Web components were installed on a different server or have a different access URL. The value in the Cisco Unified CallConnector for Microsoft Dynamics CRM Web Path must be a complete URL that points to the directory in which the C4Dial.aspx and C4Stub.aspx files are located.

Note You must also include the port number the website is running on if it is not the default port 80. In the example shown in Figure 28, the hostname of the Microsoft CRM Server is "triton" and the Microsoft CRM website is running on port 5555. Failure to provide the custom port number (except port 80) will cause problems with the screen pops.

Step 13

Configure the Login Domain, Login Name, and Login Password fields with your Microsoft CRM login information and click Connect.

If the connection is successful, the status will show Connected and the Dial Plan Configuration drop-down box will become enabled.

Step 14

Select the appropriate Dial Plan Configuration (Phone Number Processor Configuration) based on geographic location and as provided for by the Cisco Unified CallConnector for Microsoft Dynamics CRM Server Service administrative configuration.

The Logging tab allows you to configure how the client logs system events. Logging levels available include:

Each level includes messages from all previous levels. The "Critical Errors" level produces virtually no output, while the "Debug4" level produces copious output. We recommend using the setting "Warnings" for normal operation. Some messages (primarily relating to TAPI events) do not currently have message levels associated with them, and they are always logged.

You can collect the logging information in eiher a file or in a logging window. If you select Log to File, additional options relating to the filename and file aging become available. If you select Enable Log to Window, one additional option to control how many messages to display is available..

Figure 29 Client Configuration Window—Logging Tab: Cisco Unified CallConnector for Microsoft Dynamics CRM

Figure 30 Client Installation Complete Window: Cisco Unified CallConnector for Microsoft Dynamics CRM

Table Of Contents

Installing Cisco Unified CallConnector for Microsoft Dynamics CRM 3.0

Contents