-
Cisco IP Communicator Administration Guide (2.0)
-
Preface
-
An Overview of Cisco IP Communicator
-
Preparing to Deploy Cisco IP Communicator
-
Deploying and Updating Cisco IP Communicator
-
Configuring the Application
-
Configuring Features and Services
-
Customizing Cisco IP Communicator
-
Viewing Operational Information
-
Troubleshooting Cisco IP Communicator
-
Providing Information to Users Via a Website
-
Index
-
PDF of the Entire Book
-
Table Of Contents
Preparing to Deploy Cisco IP Communicator
Cisco Unified CallManager Configuration Requirements
Installing a Hotfix for USB Audio Devices
Deployment and Configuration Checklist
Adding Devices to the Cisco Unified CallManager Database
Adding Devices with Auto-Registration
Adding Devices with Auto-Registration and TAPS
Adding Devices with Cisco Unified CallManager Administration
Collecting Device Names Before Adding Devices
Running the Cisco IP Communicator Administration Tool
Preparing to Deploy Cisco IP Communicator
This chapter outlines the required and recommended tasks involved in deploying Cisco IP Communicator, and provides instructions for adding Cisco IP Communicator devices to the Cisco Unified CallManager database.
This chapter includes the following topics:
•
Deployment and Configuration Checklist
•
•
Tip
http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html
Installation Prerequisites
Before deploying the Cisco IP Communicator application to users, read the requirements in these sections:
•
Network Requirements
For Cisco IP Communicator to successfully operate as an endpoint in your network, your network must meet the following requirements:
•
•
•
If you want Cisco IP Communicator to auto-locate its TFTP server, you also need an IP network that supports DHCP with Cisco Option 150 configured with the address of your TFTP servers.
If you want to use Cisco Emergency Responder (CER), you need an available ethernet port on a Cisco ethernet switch. For details, see the Cisco Emergency Responder Administrator Guide.
Note
Related Topics
•
•
•
Cisco Unified CallManager Configuration Requirements
Cisco IP Communicator requires Cisco Unified CallManager to handle call processing. Before you deploy Cisco IP Communicator to users, see the the Cisco Unified CallManager Administration Guide or context-sensitive help in the Cisco Unified CallManager Administration web application to ensure that Cisco Unified CallManager is set up properly to manage Cisco IP Communicator devices and to route and process calls.
For an overview of configuration and deployment tasks involving Cisco Unified CallManager, see the "Deployment and Configuration Checklist" section.
Note
Related Topics
•
Client PC Requirements
Personal computers (PCs) on which you want to install Cisco IP Communicator should meet the requirements outlined in these sections:
Platform Requirements
Cisco IP Communicator has certain minimum requirements of the PC and operating system on which it runs. In the minimum configuration, Cisco IP Communicator consumes a substantial portion of the PC's CPU during calls. With additional CPU and RAM, the application will be more responsive and launch faster. See Table 2-1 and Table 2-2 for details.
Note
•
Table 2-1 Cisco IP Communicator Only
Table 2-2 Cisco IP Communicator Interoperating with Cisco VT Advatage.
Related Topics
•
•
Hardware Requirements
Cisco IP Communicator requires the following of the client PC and its peripherals:
•
•
•
•
Related Topics
•
Installing a Hotfix for USB Audio Devices
Caution
You must install a Microsoft Windows hotfix if you use Cisco IP Communicator with both of the following:
•
•
To get the hotfix for your locale, access the file called cipc-Admin-ffr.1-1-1.zip from this website:
http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-comm
Unzip the W2KUSBHotfix.zip file to access the appropriate locale folder.
If you are installing the English version of Cisco IP Communicator Release 1.1(5), then run the Windows2000-KB832339-x86-ENU.EXE file.
If you are installing the French version of Cisco IP Communicator Release 1.1(5), then run the Windows200-KB832339-x86-FRA.EXE file.
Deployment and Configuration Checklist
Table 2-3 is designed to give you an overview all of the administrative tasks involved in preparing for, deploying, and configuring Cisco IP Communicator.
The table is broken into three sections:
•
•
•
Some of the tasks in the table are not specific to Cisco IP Communicator, but apply to any Cisco Unified CallManager-supported phone device. Required tasks are noted.
Note
Table 2-3 Pre-Deployment and Configuration Checklist
1.
•
•
•
•
Optional. You can use this information to configure devices in Cisco Unified CallManager Administration web application.
The Device Information fields in the Device Configuration page will auto-populate if information is relevant and available. Edit fields only if you want to override system settings on a per-device basis.
•
•
•
2.
•
•
•
•
Adding devices is required. The method that you use to add devices to Cisco Unified CallManager determines how the directory number is assigned and whether you need to obtain a MAC address from a network interface, or you need to use a free-form device name. Note that if you want to use a free-form device name, you must be registered with at least version 5.0(1) of Cisco Unified CallManager.
If you do not use auto-registration or TAPS to add a devices, you must add the device to Cisco Unified CallManager before deploying the application.
•
•
•
•
3.
Not necessary if you use auto-registration or TAPS.
1.
As needed. Provides enhanced telephony functionality.
•
•
•
2.
As needed. Provides softkeys.
3.
Recommended. Gives users access to information such as stock quotes and weather reports, which are displayed on the phone as interactive content with text and graphics.
•
•
4.
You must run the tool in order to install the Directory Wizard (used to configure the Quick Search and Dialing Rules features). Additionally, you must select the option to enable HTTP access if any users in your network rely on unsupported VPN clients (the tool sets up an IP reflector web page to resolve audio IP auto-detection problems). Enabling HTTP access also improves AutoUpdate performance for remote users.
•
•
•
5.
Recommended. Quick Search can search both corporate and personal directories; use Dialing Rules to apply a dialing plan. If you are integrating with a Cisco Unified CallManager directory, you can use the Directory Wizard to set up configuration files. First, run the Administration Tool (see the previous step).
•
•
•
6.
Recommended. Associates users with device IDs to enable access to the User Options web pages; includes users and their phone numbers in relevant Quick Search results (when integrating with a Cisco Unified CallManager directory).
•
•
1.
•
•
•
Users must have administrative privileges on their PCs in order for you to deploy software using the first option.
If you use a Microsoft Windows installer package, you can provide command line options to specify values during deployment. See the topic at right for details.
2.
Recommended. Providing users with this information can improve their success with the product.
3.
You or the user will need to install audio devices that rely on drivers such as a USB headset and USB handset. Ideally, this task should be performed before the application is installed on the client PC.
•
4.
Some configuration tasks may be required before the application will function at initial startup.
Related Topics
•
•
•
•
Adding Devices to the Cisco Unified CallManager Database
Before installing the Cisco IP Communicator application, you must decide how you want to add devices to the Cisco Unified CallManager database.
Choose one of the methods described in the sections below:
•
•
•
Table 2-4 provides an overview of your options for adding devices to the Cisco Unified CallManager database. These options are described in detail in the topics listed above.
Adding Devices with Auto-Registration
You can use this method without first gathering device names from client PCs.
When auto-registration is enabled, Cisco Unified CallManager provides a directory number as soon as you run the Cisco IP Communicator application after installation. During auto-registration, Cisco Unified CallManager automatically assigns the next available sequential directory number to the device.
You can use auto-registration to quickly submit devices into the Cisco Unified CallManager database. You can then modify settings, such as the directory numbers, from Cisco Unified CallManager. Additionally, you can move auto-registered devices to new locations and assign them to different device pools without affecting their directory numbers.
For information about enabling and configuring auto-registration, see the Cisco Unified CallManager Administration Guide.
Related Topics
•
•
•
Adding Devices with Auto-Registration and TAPS
You can use this method without first gathering MAC addresses from client PCs.
TAPS, the Tool for Auto-Registered Phones Support, works in conjunction with the Bulk Administration Tool (BAT) to update devices that were previously added to the Cisco Unified CallManager database using dummy device names. Use TAPS to update MAC addresses and download pre-defined configurations for Cisco IP Communicator devices.
To implement TAPS, you or the user dial a TAPS directory number and follow voice prompts. When the process is complete, the Cisco IP Communicator device downloads its directory number and other settings, and the device is updated in Cisco Unified CallManager Administration with the correct device name.
You must make sure that Auto-registration is enabled in Cisco Unified CallManager Administration (System > Cisco Unified CallManager) for TAPS to function.
See the the Bulk Administration Tool User Guide for Cisco Unified CallManager for detailed instructions about both BAT and TAPS.
Using a Version of TAPS that is Included with Cisco CallManager 3.3.3
If you want to use a version of TAPS that is included with Cisco CallManager 3.3.3 to add a Cisco IP Communicator device to the database for a user who already has a hardware Cisco IP Phone, and if the Cisco IP Communicator device will use the same phone number as the hardware phone, then you need to take the following steps:
1.
2.
Related Topics
•
•
•
Adding Devices with Cisco Unified CallManager Administration
Use this method to add devices individually to the Cisco Unified CallManager database using Cisco Unified CallManager Administration web pages.
To do so, you need to first collect the appropriate device name for each client on which you want the Cisco IP Communicator application installed. You may use the MAC address form the network interface on the client PC. Alternatively, if you are connecting to Cisco Unified CallManager 5.0(1) or later, you may use a free-form device name instead of the MAC address. See the "Collecting Device Names Before Adding Devices" section for more information.
After you have collected device names, choose Device > Add a New Device in Cisco Unified CallManager Administration. For complete instructions and conceptual information about Cisco Unified CallManager, see the the Cisco Unified CallManager Administration Guide and the Cisco Unified CallManager System Guide.
Tip
Related Topics
•
•
•
Adding Devices with BAT
The Cisco Bulk Administration Tool (BAT) is a plug-in application for Cisco Unified CallManager that enables system administrators to perform batch operations, including registration, on large numbers of devices, including Cisco IP Phones and Cisco IP Communicator devices.
To add devices using BAT only (meaning, not in conjunction with TAPS), you need to first collect the appropriate device name for each client on which you want the Cisco IP Communicator application installed. See the "Collecting Device Names Before Adding Devices" section for more information.
For detailed instructions about using BAT, see the Cisco Unified CallManager Administration Guide and the Bulk Administration Tool User Guide for Cisco Unified CallManager.
Related Topics
•
•
•
•
Collecting Device Names Before Adding Devices
You need to collect device names before adding devices to the database individually, using Cisco Unified CallManager Administration, or in bulk, using BAT only (not in conjunction with Tool for Auto-Registered Phones Support).
You do not need to collect device names before adding devices with auto-registration only or when using BAT in conjunction with TAPS.
There are two ways to collect Device Names. The first is to use the MAC address of one of the network interfaces on the client PC. The second way is to use a free-form device name. In order to use a free-form device name, you must be connecting to Cisco Unified CallManager version 5.0(1) or later. If you choose to use a MAC address, you need to get it from the network interface of the client PC on which you want the Cisco IP Communicator application installed.
If there is more than one network interface on the client PC, use the MAC address from the interface that is most likely to provide permanent connectivity, or from the interface that is always enabled—even if it is inactive. (For example, use the integrated Ethernet card rather than the wireless card, docking station, or PC card.)
This criteria also pertains to choosing a network interface to associate with the application during initial startup (if such a choice is necessary.) For more information about choosing an interface if prompted at startup, see the "Selecting a Device Name" section. If you choose to use a free-form device name, you must be connecting to a Cisco Unified CallManager version 5.0(1) or later. You may choose any device name you want as long as it is unique across the Cisco Unified CallManager cluster. The maximum number of characters in the string is 15 and the string is limited to ASCII characters only.
Related Topics
•
•
Running the Cisco IP Communicator Administration Tool
As part of your deployment preparations, it is highly recommended that you:
•
•
You can get the Administration Tool from the same Cisco IP Communicator software download web site:
http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-comm
Table 2-5 summarizes the benefits of running the Administration Tool.
Tip
•
Table 2-5 Using the Cisco IP Communicator Administration Tool
Install the Directory Wizard on your server
Run the Administration Tool on the Cisco Unified CallManager publisher.
The Administration Tool installs DirectoryWizard.exe and LdapDirectories.README.txt in this folder: <TFTPPath>\Communicator.
Running the Tool on the Cisco Unified CallManager publisher allows the Directory Wizard to auto-detect configuration values. See the "How to Configure Quick Search Using the Directory Wizard" section for details.
Use the Directory Wizard to configure Quick Search and Dialing Rules. See the "Configuring Corporate and Personal Directories" section.
Enable HTTP access
Run the Administration Tool and select the Enable HTTP Access setting.
Enabling HTTP access can:
•
Note that users must have administrator privileges on their PCs to use AutoUpdate. See the "Updating the Application" section on page 3-10.
•
Note that if you are enabling HTTP for this purpose, you also need to specify the URL of getIP.asp web page in Cisco Unified Cisco IP Communicator Administration Guide for Cisco Unified CallManager Administration. See the "Resolving Audio IP Address Auto-Detection Problems" section.
Access the Directory Wizard and the Administration Tool ReadMe file
Run the Administration Tool and select the appropriate check boxes.
Alternately, you can launch the Directory Wizard and ReadMe file from the Cisco IP Communicator program group.
Related Topics
•
•
