cupc_ig_1_1
Preparing to Deploy Cisco Unified Personal Communicator
Downloads: This chapterpdf (PDF - 491.0KB) The complete bookPDF (PDF - 1.23MB) | Feedback

Preparing to Deploy Cisco Unified Personal Communicator

Table Of Contents

Preparing to Deploy Cisco Unified Personal Communicator

Predeployment Overview

Information to Gather Before Configuring Servers

Cisco Unified CallManager Configuration

Adding Cisco Unified IP Phones to the Cisco Unified CallManager Database

Associating the Cisco Unified IP Phone to an End User and Adding the End User to a Group

Creating a SIP Phone Security Profile for Cisco Unified Personal Communicator

Adding Cisco Unified Personal Communicator as a Phone Type

Configuring Extension Mobility

Configuring Videoconferencing Resources

Configuring Dialing Rules

Licensing

Obtaining a License File

Uploading a License File

Assigning Capabilities to Users

Viewing the License Report

LDAP Server Configuration

Configuring Microsoft Active Directory for Anonymous Queries

Assigning Permissions

Inheriting Permissions from the Parent Object

Configuring Additional Information for Microsoft Active Directory 2003

Verifying Permissions for Microsoft Active Directory

Configuring Cisco Unified Presence Server LDAP Settings for Microsoft Active Directory

Cisco Unity Connection Configuration

Cisco Unified MeetingPlace Express Configuration

Cisco Unified Presence Server Configuration

Configuring the LDAP Attribute Map

Rules for Mapping the UserID Attribute

Rules for a Displayed Contact Name

Photo Attributes and Format

Specifying LDAP Server Names and Addresses

Creating LDAP Server Profiles

Specifying Cisco Unity Connection Server Names and Addresses

Creating Cisco Unity Connection Server Profiles

Specifying Cisco Unified MeetingPlace Express Server Names and Addresses

Creating Cisco Unified MeetingPlace Express Server Profiles

How Participants Join the Web-Only Meeting

Participant Privileges and Meeting Controls

Specifying CTI Gateway Server Names and Addresses

Creating CTI Gateway Server Profiles

Creating SIP Proxy Server Profiles

Changing Application Profiles on a Per-User Basis

Firewall Configuration

Video Telephony Camera Configuration

Headsets and Other Audio Devices Configuration

Use of Third-Party Headsets with Cisco Unified Personal Communicator


Preparing to Deploy Cisco Unified Personal Communicator


This chapter describes how to prepare your network before deploying Cisco Unified Personal Communicator.

Topics in this section include:

Predeployment Overview

Information to Gather Before Configuring Servers

Cisco Unified CallManager Configuration

LDAP Server Configuration

Cisco Unity Connection Configuration

Cisco Unified MeetingPlace Express Configuration

Cisco Unified Presence Server Configuration

Firewall Configuration

Video Telephony Camera Configuration

Headsets and Other Audio Devices Configuration

Use of Third-Party Headsets with Cisco Unified Personal Communicator

Predeployment Overview

This topic provides a high-level overview of the tasks that need to be completed before you deploy Cisco Unified Personal Communicator.


Note Use care when setting user names and passwords. Although passwords do not need to match across all servers, it will be easier for users to correctly configure the Cisco Unified Personal Communicator client if they do. Users cannot change passwords from Cisco Unified Personal Communicator; instead users must follow the password change instructions specific to each server.


Procedure


Step 1 Comply with the network, server, and the client PC requirements that are described in the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

a. Make sure to use the correct software release for the supported servers.

b. Make sure that you read and understand the system requirements before you proceed with the installation.

Step 2 Install and configure Cisco Unified CallManager.

Cisco Unified CallManager manages the Cisco Unified IP Phones associated with Cisco Unified Personal Communicator and routes and processes calls. Cisco Unified CallManager provides licensing information to Cisco Unified Personal Communicator and provides controls for video conferencing when the Cisco Unified Videoconferencing Multipoint Control Unit (MCU) is installed.

Follow the system configuration overview instructions in the Cisco Unified CallManager System Guide and the instructions in the Cisco Unified CallManager Administration Guide (or in the Cisco Unified CallManager Administration online help).

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html

Step 3 Install and configure the Lightweight Directory Access Protocol (LDAP) server by following the instructions that shipped with the server.

The LDAP directory interacts with Cisco Unified Personal Communicator to provide additional contact information (first name, last name, phone numbers, and so forth) through directory searches for each contact in a user's contact list.

Step 4 Install and configure Cisco Unified Presence Server.

Cisco Unified Presence Server provides the client configuration and presence information to Cisco Unified Personal Communicator.

Follow the installation and configuration information at this URL:

http://www.cisco.com/en/US/products/ps6837/prod_installation_guides_list.html

Also follow the instructions in the administration guide (or in the online help in the Cisco Unified Presence Server Administration at this URL:

http://www.cisco.com/en/US/products/ps6837/prod_maintenance_guides_list.html

Step 5 For full functionality of Cisco Unified Personal Communicator, you need to have these products installed and operational:

Cisco Unity Connection to provide voice-mail retrieval and playback

See the install and upgrade guides, and the maintain and operate guides at this URL:

http://www.cisco.com/en/US/products/ps6509/tsd_products_support_series_home.html

You must configure the Cisco Unified Presence Server to interact with the Cisco Unity Connection server.

Cisco Unified MeetingPlace Express to provide web conferencing

See the install and upgrade guides, and the maintain and operate guides:

http://www.cisco.com/en/US/products/ps6533/tsd_products_support_series_home.html

You must configure the Cisco Unified Presence Server to interact with the Cisco Unified MeetingPlace Express server.

Cisco Unified Videoconferencing MCU for video conferencing support when Cisco Unified Personal Communicator is used in soft-phone mode

See the install and upgrade guides, and the maintain and operate guides at this URL:

http://www.cisco.com/en/US/products/hw/video/ps1870/tsd_products_support_series_home.html

You must configure Cisco Unified CallManager to interact with the MCU.

Step 6 Configure each of the servers for use with Cisco Unified Personal Communicator by following the instructions in this chapter.


Related Topics

How Cisco Unified Personal Communicator Fits into Your Network, page 1-2

Information to Gather Before Configuring Servers

Information to Gather Before Configuring Servers

Table 2-1 lists the information you need to gather to complete the server configuration tasks in this chapter.

Table 2-1 Information to Gather 

Task
Where needed...
Information needed for Cisco Unified CallManager Configuration

Cisco Unified IP Phone MAC address for each user

Adding Cisco Unified IP Phones to the Cisco Unified CallManager Database

Directory numbers for each user

Adding Cisco Unified IP Phones to the Cisco Unified CallManager Database

Cisco Unified CallManager user names

Adding Cisco Unified Personal Communicator as a Phone Type

Cisco Unified Videoconferencing MCU MAC address

Configuring Videoconferencing Resources

Cisco Unified CallManager MAC address

Licensing

Information needed for Cisco Unified Presence Server Configuration

LDAP attribute mapping schema

Configuring the LDAP Attribute Map

LDAP server addresses

Specifying LDAP Server Names and Addresses

LDAP server password

Creating LDAP Server Profiles

Cisco Unity Connection server addresses

Specifying Cisco Unity Connection Server Names and Addresses

Cisco Unified MeetingPlace Express server addresses

Specifying Cisco Unified MeetingPlace Express Server Names and Addresses

Computer telephony interface (CTI) gateway server addresses

Specifying CTI Gateway Server Names and Addresses


Cisco Unified CallManager Configuration

This section describes the Cisco Unified CallManager configuration. Topics in this section include:

Adding Cisco Unified IP Phones to the Cisco Unified CallManager Database (required)

Associating the Cisco Unified IP Phone to an End User and Adding the End User to a Group (required)

Creating a SIP Phone Security Profile for Cisco Unified Personal Communicator (required)

Adding Cisco Unified Personal Communicator as a Phone Type (required for video soft-phone support)

Configuring Extension Mobility (optional)

Configuring Videoconferencing Resources (required for video conferencing support)

Configuring Dialing Rules (required)

Licensing (required)

For information about the supported Cisco Unified CallManager releases, see the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

Adding Cisco Unified IP Phones to the Cisco Unified CallManager Database

You must add and configure a Cisco Unified IP Phone supported for use with Cisco Unified Personal Communicator to the Cisco Unified CallManager database.

You complete these steps from Cisco Unified CallManager Administration through the Device > Phone menu:


Note You can automatically add phones to the Cisco Unified CallManager database by using auto-registration or by manually adding them through the Phone Configuration windows. For more information, see the online help topic "Configuring Cisco Unified IP Phones" in Cisco Unified CallManager Administration.


Add a Cisco Unified IP Phone (if none exists) for the user. Configure the phone for your environment.

Configure the phone to interoperate with Cisco Unified Personal Communicator by allowing control of the Cisco Unified IP Phone from the computer telephony interface (CTI). Verify that the Allow Control of Device from CTI check box is checked (the default setting).

If this option is not provided in the Device Information section of the Phone Configuration window, the phone is not supported for use with Cisco Unified Personal Communicator.

Assign a directory number, and associate this number with the phone.

For detailed instructions, use the Cisco Unified CallManager Administration online help or the Cisco Unified CallManager Administration Guide at this URL:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html

For information about phones supported for use with Cisco Unified Personal Communicator, see the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

You can configure a Cisco Unified IP Phone with the optional features listed in Table 2-2, but these features are not used with Cisco Unified Personal Communicator. For a list of supported phone features, see the "Features and Benefits" section on page 1-1.

Table 2-2 Optional Cisco Unified IP Phones Features 

Task
For details, see... 1

Configure telephony features and settings, including extension mobility for environments where users are not permanently assigned to physical phones2 (optional).

Cisco Unified CallManager Administration Guide

Cisco Unified CallManager Features and Services Guide

"Configuring Extension Mobility" section

Modify phone button templates (softkeys) (optional).

Cisco Unified CallManager Administration Guide

Configure Cisco Unified IP Phone services, such as access to stock quotes and weather reports (optional).

Cisco Unified CallManager Administration Guide

Cisco Unified CallManager Features and Services Guide

Set up directories for Quick Search and Dialing Rules features (optional).

Cisco Unified CallManager Administration Guide

Add users to Cisco Unified CallManager, and associate users with device IDs for access to the User Options web pages (optional).

Cisco Unified CallManager Administration Guide

1 Cisco Unified CallManager documentation is available from the Help menu in the Cisco Unified CallManager Administration and at this URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html

2 When you configure extension mobility, Cisco Unified Personal Communicator users can select the associated desk phone in Cisco Unified Personal Communicator. For more information, see the Cisco Unified Personal Communicator user guide at this URL: http://www.cisco.com/en/US/products/ps6844/products_user_guide_list.html


Related Topics

Associating the Cisco Unified IP Phone to an End User and Adding the End User to a Group

Creating a SIP Phone Security Profile for Cisco Unified Personal Communicator

Associating the Cisco Unified IP Phone to an End User and Adding the End User to a Group

After you add the Cisco Unified IP Phone to the Cisco Unified CallManager database and configure it to be controlled from CTI, you must perform these tasks (described in this section):

Set up the user account, and associate the directory number (primary extension) to the user.

Associate the phone to the end user.

Add the end user to the CTI users group.

Add the end user to a Cisco Unified CallManager user group.

Procedure

Complete these steps from Cisco Unified CallManager Administration:


Step 1 Choose User Management > End User.

Step 2 In the Find and List Users window, click Add New to add a new user.

Step 3 In the End User Configuration window, enter information for this user.

a. In the User Information section, enter values into the fields.

For details about these fields, see the online help topic "End User Configuration Settings" in Cisco Unified CallManager Administration.

Make sure to configure a digest credential for the user. Any value will work, but do not leave this field blank.


Note To avoid interoperability problems with Cisco Unified Personal Communicator, use care when specifying the username. You will convert it into a soft-phone device name in the "Adding Cisco Unified Personal Communicator as a Phone Type" section. For more information, see Table 2-3.


b. In the Directory Number Associations section at the bottom of the window, select the primary extension (primary directory number) for this user from the drop-down list.

c. Click Save.

Step 4 In the Device Associations section, associate a Cisco Unified IP Phone with this end user by clicking the Device Association button.

a. In the User Device Association window, enter the MAC address of the phone for this user prefixed with SEP, and click Find.

b. Select the user's phone from the list (should be the only phone returned), and click Save Selected/Changes at the bottom of the page.

Step 5 Add the end user to the CTI users group:

a. Choose User Management > User Group.

b. In the search field of the Find and List User Groups window, enter Standard CTI Enabled, and click Find.

This is a standard group that is created when Cisco Unified CallManager installs.

c. Click the Standard CTI Enabled group to open the User Group Configuration window.

d. Click the Add End Users to Group button.

e. In the Find and List Users window, search for a user by using the search options, select the user's check box, and click Add Selected.

Step 6 Follow the instructions in Step 5, but search for the Standard CCM End Users group, and add the end user to this group.

Step 7 Click Save.


Related Topics

Creating a SIP Phone Security Profile for Cisco Unified Personal Communicator

Adding Cisco Unified Personal Communicator as a Phone Type

Creating a SIP Phone Security Profile for Cisco Unified Personal Communicator

Because the Cisco Unified Personal Communicator does not support Transport Layer Security (TLS) in Cisco Unified CallManager, you must configure a SIP security profile and then associate this profile when you add Cisco Unified Personal Communicator as a phone type.

Procedure

Complete these steps from Cisco Unified CallManager Administration:


Step 1 Choose System > Security Profile > Phone Security Profile.

Step 2 In the Find and List SIP Phone Security Profiles window, click Add New.

Step 3 In the Phone Security Profile Information section, enter settings for these fields:

a. In the Name field, enter a name for this security profile.

To ensure that you apply the correct profile to the device, include the device model in the security profile name.

b. In the Description field, enter a security profile description.

c. In the Nonce Validity Time field, enter the number of seconds that the nonce is valid.

The default value equals 600 (10 minutes). When the time expires, Cisco Unified CallManager generates a new value.

A nonce value is a random number that supports digest authentication and is used to calculate the MD5 hash of the digest authentication password.

d. For Device Security Mode, choose Non Secure.

No security features except image authentication exist for the phone. A TCP connection opens to Cisco Unified CallManager.

e. For Transport Type, choose TCP + UDP, TCP, or UDP.

Choose TCP + UDP if you want to use a combination of TCP and UDP.

Choose TCP to ensure that packets are received in the same order that they are sent. This protocol ensures that no packets get dropped.

Choose UDP to ensure that packets are received quickly. This protocol, which can drop packets, does not ensure that packets are received in the order that they are sent.

None of these settings provides security.

f. Check Enable Digest Authentication to enable SIP authentication.

Check this box if you want Cisco Unified CallManager to challenge the identity of the phone when it sends a request to Cisco Unified CallManager. After Cisco Unified CallManager challenges the identity, the phone responds with a MD5 checksum, and Cisco Unified CallManager verifies the information based on the credentials that you configured in Cisco Unified CallManager Administration. If the credentials match, digest authentication of the phone is successful.

You specified the digest authentication credentials in the End User window in Cisco CallManager Administration in the "Associating the Cisco Unified IP Phone to an End User and Adding the End User to a Group" section. To associate the credentials with the phone after you configure the user, you choose a Digest User and an end user in the Phone Configuration window.

g. None of the settings in the Phone Security Profile CAPF Information section apply to Cisco Unified Personal Communicator. You can use any value.

h. For Phone Port, enter the port number that you want Cisco SIP IP Phones to use to listen for SIP messages from Cisco Unified CallManager. The default is 5060.

Step 4 Click Save.

Step 5 If you want this user to have only a presence-enabled directory with desk phone control through Cisco Unified Personal Communicator, skip these configuration sections:

"Adding Cisco Unified Personal Communicator as a Phone Type" section

"Configuring Videoconferencing Resources" section

"Video Telephony Camera Configuration" section

Proceed to the "Configuring Dialing Rules" section.


Adding Cisco Unified Personal Communicator as a Phone Type

To enable Cisco Unified Personal Communicator soft-phone features, you must manually create a new soft-phone device per user. The auto-registration features in Cisco Unified CallManager are not supported for use with Cisco Unified Personal Communicator. Completing this procedure causes three device licenses to be consumed.

Procedure

Complete these steps from Cisco Unified CallManager Administration:


Step 1 Choose Device > Phone.

Step 2 In the Find and List Phones window, click Add New.

Step 3 In the Add a New Phone window, in the Phone Type drop-down list, select Cisco Unified Personal Communicator, and click Next.

Step 4 In the Phone Configuration window, in the Device Information section, perform these steps:

a. In the Device Name field, specify the soft-phone device name according to these guidelines:

It must match the user name.

It must start with UPC.

It must contain the letters A through Z and numerals 0 through 9, ignoring all other characters.

It can contain 12 additional characters after UPC.

See Table 2-3 for examples.

Table 2-3 Username Conversion for Cisco Unified Personal Communicator Soft-Phone Device 

Cisco Unified CallManager Username
Associated Soft-Phone Device Name

jjackson

UPCJJACKSON

johnnie_jackson

UPCJOHNNIEJACKS

johnniejackson

UPCJOHNNIEJACKS

john.jackson

UPCJOHNJACKSON



Note As shown in Table 2-3, the usernames johnnie_jackson and johnniejackson translate to the same soft-phone device name and are said to collide. You must take care to create usernames that will not result in a collision when the soft-phone device name is configured. If Cisco Unified Personal Communicator is unable to derive its soft-phone device name, it will not be able to properly register and will not function as expected. You might have to reconfigure a user to use a name other than their normal username to avoid this problem.


b. In the Description field, enter the purpose of the phone; for example, Richard's soft phone.

c. Configure all required fields for your environment.

d. For Owner User ID, select the user ID from the drop-down list.

e. Make sure to uncheck Allow Control of Device from CTI to disable CTI to control and monitor this device.

Step 5 In the Protocol Specific Information section, perform these steps:

a. For Presence Group, select Standard Presence Group.

b. For SIP Phone Security Profile, select the security profile from the drop-down list that you created in the "Creating a SIP Phone Security Profile for Cisco Unified Personal Communicator" section.

c. For SIP Profile, select Standard SIP Profile to specify the default SIP profile. SIP profiles provide specific SIP information for the phone such as registration and keepalive timers, media ports, and do-not-disturb control.

d. For Digest User, select the user ID. It should be the same as that selected for the Owner User ID.

Step 6 Click Save.

The Phone Configuration window redisplays with the new information. Verify that the status shown at the top of the page indicates a successful save. If an error is displayed, the most common problems result from incorrectly formatted device names or the failure to specify a mandatory parameter.

Step 7 In the Association Information pane that displays on the left side of the window, click the Add a New DN link.

Step 8 In the Directory Number Information section, enter the directory number and route partition for the Cisco Unified Personal Communicator that are the same as the ones used by the Cisco Unified IP Phone for this user.

This configuration causes the Cisco Unified Personal Communicator to share the line with the Cisco Unified IP Phone for this user.

Step 9 For the Line 1 on Device Device-Name section, for the Display (Internal Caller ID), enter a string (20 characters maximum) as the callerID; for example, Richard Jonnes. This string is displayed as the callerID on phones that are called.

Step 10 In the Multiple Call/Call Waiting Settings on Device section, perform these steps:

a. In the Maximum Number of Calls field, type 2 to specify the maximum number of calls that can be presented to Cisco Unified Personal Communicator.

b. In the Busy Trigger field, type 2 to specify the number after which an incoming call receives a busy signal.

For example, if you answer a call and then receive another call, you can put the first call on hold and answer the second. If a third person tries to call you, Cisco Unified CallManager enforces the busy limit; it sees that there are already two calls in process and responds to the third caller with a busy signal.

Step 11 Click Save.

Ensure that the status shown at the top of the page indicates a successful save and that the resulting status is Ready.

Cisco Unified CallManager reminds you that changes to line or directory number settings require a restart. However, a restart is required only when you edit lines on Cisco Unified IP Phones that are up and running at the time of the modifications.


Related Topics

Configuring Videoconferencing Resources

Configuring Videoconferencing Resources

Video Telephony Camera Configuration

Configuring Extension Mobility

Use the extension mobility feature to allow users to configure a Cisco Unified IP Phone as their own, on a temporary basis, by logging in to that phone. After a user logs in, the phone adopts the user individual user default device profile information, including line numbers, speed dials, services links, and other user-specific phone properties.

For example, when user A occupies a desk and logs in to the phone, that user's directory numbers, services, speed dials, and other properties appear on that phone. But when user B uses the same desk at a different time, user B's information appears. The extension mobility feature dynamically configures a phone according to the current user.

By using extension mobility, Cisco Unified Personal Communicator users can associate this application with one of several desk phones.

Procedure


Step 1 Make sure to remove all devices from the user's phone association list (if any) in Cisco Unified CallManager Administration (choose Device > Phone and access the Directory Number Configuration window).

This action also removes the Preferred CTI Device selection in Cisco Unified Presence Server Administration (Application > Unified Personal Communicator > User Settings window).

Step 2 Follow the Cisco Unified CallManager extension mobility configuration information in the Cisco Unified CallManager Features and Services Guide at this URL:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html

When you create the device user profile (Device > Device Settings > Device Profile), make sure that it is controllable by CTI (along with the line).

When you add the Cisco Unified IP Phone to Cisco Unified CallManager (Device > Phone), make sure that is controllable by CTI as described in "Adding Cisco Unified IP Phones to the Cisco Unified CallManager Database" section.


Configuring Videoconferencing Resources

You can enable Cisco Unified Personal Communicator soft-phone users to have merged conference calls (three or more parties) with audio and video support.

Procedure

Complete these tasks:


Step 1 Install a supported videoconferencing server.

For information about the servers supported for use with Cisco Unified Personal Communicator, see the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

For installation information, see this URL:

http://www.cisco.com/en/US/products/hw/video/ps1870/tsd_products_support_series_home.html

Step 2 In Cisco Unified CallManager Administration, configure the media resources:

Add the video conference bridge to Cisco Unified CallManager by choosing the Media Resources > Conference Bridge menu.

You need the MAC address of the videoconference bridge to complete this task.

Create a media resource group list, and add the video conference bridge to it by choosing the Media Resources > Media Resource Group List menu.

Create a media resource group, and add a media resource to it by choosing the Media Resources > Media Resource Group menu.

For detailed configuration instructions, use the Cisco Unified CallManager Administration online help or the Cisco Unified CallManager Administration Guide at this URL:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html


Related Topics

Adding Cisco Unified Personal Communicator as a Phone Type

Video Telephony Camera Configuration

Configuring Dialing Rules

Based on your company's dial plan and the information stored in the LDAP directory (telephone number for the end user), you might need to define application dialing rules and directory dialing rules through the Cisco Unified CallManager routing information administration pages. The Cisco Unified Presence Server queries Cisco Unified CallManager to obtain these dialing rules for the Cisco Unified Personal Communicator.

These rules define how Cisco Unified Personal Communicator can reformat the inbound call ID to be used as a directory lookup key and how to transform a phone number retrieved from the LDAP directory for outbound dialing.

Application dial rules automatically strip numbers from or add numbers to telephone numbers that the user dials. For example, you can configure a dial rule that automatically adds the digit 9 in front of a 7-digit telephone number to provide access to an outside line. Application dial rules are used to manipulate numbers that are dialed from Cisco Unified Personal Communicator. You configure these dial rules through Cisco Unified CallManager Administration from the Call Routing > Dial Rules > Application Dial Rules menu.

Directory lookup rules transform caller identification numbers into numbers that can be looked up in the directory from Cisco Unified Personal Communicator. Each rule specifies which numbers to transform based on the beginning digits and length of the number. For example, you can create a directory lookup rule that automatically removes the area code and two prefix digits from a 10-digit telephone, which would transform 4089023139 into 23139. You configure these dial rules through Cisco Unified CallManager Administration from the Call Routing > Dial Rules > Directory Lookup Dial Rules menu.

Before Cisco Unified Personal Communicator places a call through contact information, it removes everything from the phone number to be dialed except for letters and digits. It transforms the letters to digits and applies the dialing rules it obtains from Cisco Unified Presence Server. The letter-to-digit mapping is locale specific and corresponds to the letters found on a standard telephone keypad for that locale (for example, for an US English locale, 1800-GOTMILK transforms to 18004686455).

Users cannot view or modify transformed numbers before Cisco Unified Personal Communicator places them. If there is a problem with the dialed number because of mistransformations, you must correct the dialing rules so that the attempted dialed number will work.

For detailed conceptual and task-based information on dial rules, see the Cisco Unified CallManager Administration online help or the Cisco Unified CallManager Administration Guide at this URL:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html

For dial-plan details, deployment, and installation of these dial plans for certain countries other than North America, see this URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/5_0/idp/dpdep502.htm

You can download Cisco Unified CallManager Dial Plan applications at this URL:

http://www.cisco.com/cgi-bin/tablebuild.pl/IDP50

Licensing

Cisco Unified CallManager Administration tracks the number of Cisco Unified Personal Communicator devices that are connected to it and compares it with the number of device licenses that have been purchased.

You can configure Cisco Unified Personal Communicator in these ways:

Base functionality—This configuration provides a user with a presence-enabled directory with desk phone control.

Two devices licenses are required: one for Cisco Unified Personal Communicator user enablement and one for Cisco Unified Presence Server enablement.

Base plus soft-phone functionality—In addition to the base capabilities, you can configure Cisco Unified Personal Communicator as a video soft phone.

Five device licenses units are required: one for Cisco Unified Personal Communicator user enablement, one for Cisco Unified Presence Server enablement, and three for the soft-phone enablement.

Topics in this section include:

Obtaining a License File

Uploading a License File

Assigning Capabilities to Users

Viewing the License Report

Obtaining a License File

When you place an order for Cisco devices, Cisco provides a Product Authorization Key (PAK). The PAK provides the software activation key and the license file.

To obtain the license files for Cisco Unified Personal Communicator, follow the instructions in the Cisco Unified CallManager Administration online help or the Cisco Unified CallManager Administration Guide at this URL:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html

After you enter the MAC address of the Cisco Unified CallManager server for which you are requesting the licenses and a valid e-mail ID, enter the number of nodes and devices for which you want licenses.

To determine the number of device licenses that you need, use the license unit calculator in Cisco Unified CallManager Administration (System > Licensing > License Unit Calculator).

After the license is uploaded, assign capabilities to users. See the "Assigning Capabilities to Users" section.

Related Topics

Uploading a License File

Assigning Capabilities to Users

Uploading a License File

After you obtain the license file, you must copy it to your local machine and then upload it to the server.

To upload the Cisco Unified Personal Communicator license file to Cisco Unified CallManager, use the System > Licensing > License File Upload menu, and follow the instructions in the Cisco Unified CallManager Administration online help or the Cisco Unified CallManager Administration Guide at this URL:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html

License files must have a .lic suffix.

Related Topics

Obtaining a License File

Assigning Capabilities to Users

Assigning Capabilities to Users

After the Cisco Unified Personal Communicator license files are uploaded, you must assign the capabilities to existing users in the Cisco Unified CallManager database.


Note You must upload the license file before you can assign capabilities to users. For more information, see the "Uploading a License File" section.


Procedure

Complete these steps from Cisco Unified CallManager Administration:


Step 1 Choose System > Licensing > Capabilities Assignment.

Step 2 In the Find and List Capabilities Assignments window, click Find to display a list of all users.

Step 3 In the search results section, click the user's link to display the Capabilities Assignment Configuration window.


Tip To assign capabilities to more than one user, select multiple user check boxes, and click Bulk Assignment.


Step 4 Check Enable UPS to enable the user to log in to Cisco Unified Presence Server. (One device license is consumed.)

Step 5 Check Enable UPC to enable Cisco Unified Personal Communicator to obtain presence information for the contact list from Cisco Unified Presence Server. (One device license is consumed.)

If you completed the "Adding Cisco Unified Personal Communicator as a Phone Type" section, three device licenses are consumed per user for video soft-phone capabilities.

Step 6 Click Save.


Related Topics

Viewing the License Report

Viewing the License Report

You can display the license report from Cisco Unified CallManager Administration by choosing System > Licensing > License Unit Report. The report lists the number of authorized, used, and remaining licenses.

To determine the number of license unit that are required for Cisco Unified Personal Communicator, choose System > Licensing > License Unit Calculator.

Related Topics

Obtaining a License File

Uploading a License File

LDAP Server Configuration

The LDAP directory interacts with Cisco Unified Personal Communicator to provide contact information through directory searches.


Note Make sure the LDAP server is installed before attempting LDAP-specific configuration on the Cisco Unified Presence Server.


Procedure


Step 1 Purchase a supported LDAP directory server.

For information about the supported LDAP directory servers, see the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

Step 2 Install the server and software according to the manufacturer's instructions.

For Microsoft Active Directory, see the "Configuring Microsoft Active Directory for Anonymous Queries" section. See the Microsoft Active Directory documentation for complete information.

Step 3 Perform the LDAP-specific configuration on the Cisco Unified Presence Server:

Configuring the LDAP Attribute Map (required)

Specifying LDAP Server Names and Addresses (required)

Creating LDAP Server Profiles (required)


Configuring Microsoft Active Directory for Anonymous Queries

This section describes how to configure Microsoft Active Directory 2000 and 2003 for anonymous queries.

By default, anonymous LDAP operations are not permitted in Active Directory. This means that an attempt to perform anonymous search in Active Directory results in the server requesting authenticated connection to LDAP and refusing the query. Therefore, some additional configuration on the Active Directory server and the Cisco Unified Presence Server are required to make anonymous queries work.

Topics in this section include:

Assigning Permissions (required)

Inheriting Permissions from the Parent Object (required)

Configuring Additional Information for Microsoft Active Directory 2003 (required)

Verifying Permissions for Microsoft Active Directory (required)

Configuring Cisco Unified Presence Server LDAP Settings for Microsoft Active Directory (required)

Assigning Permissions

To enable anonymous queries, you must grant Anonymous Logon access to user objects that need to be located by anonymous search. Table 2-4 lists the rights that must be given to all user objects to enable anonymous search.

Table 2-4 Anonymous Permissions 

User Object
Permissions
Inheritance
Permission Type

ANONYMOUS LOGON

List Contents

This object and all child objects

Object

ANONYMOUS LOGON

Read name

This object and all child objects

Property

ANONYMOUS LOGON

Read Name

This object and all child objects

Property

ANONYMOUS LOGON

Read objectClass

This object and all child objects

Property



Note The strings and images are specific to the Windows 2000 server. There might be minor GUI changes for other Windows servers.


Procedure

To assign permissions for Active Directory 2000 and 2003, complete these steps:


Step 1 Launch ADSIEDIT (from Start > Run, enter ADSIEDIT.msc).

If ADSIEDIT is not installed on your server, manually install it from the Windows server CD.

Step 2 In the left panel, navigate to the user container, right-click it, and view properties.

Normally, in the CN=Users Properties window, the user container is CN=Users, DC=domain name, DC=com. If the user objects are present in different containers, repeat the procedure on each of the containers.

Step 3 Click the Security tab, and then click the Advanced button.

Step 4 In the Access Control Settings for Users window, click Add.

Step 5 If this is a Windows 2000 server, a User List window displays. Select Anonymous Logon, and click OK.

or

If this is a Windows 2003 server, a Select User window displays, prompting you to enter the object name. Enter Anonymous Logon, and click OK.

Step 6 In the Permission Entry for Users window, click the Object tab, and set these values:

For Apply Onto, select This Object and All Child Objects.

In the Permissions list, check Allow for List Contents.

Step 7 Click the Properties tab, and set these values:

For Apply Onto, select This Object and All Child Objects.

Click Clear All to clear permissions (if any are already set).

In the Permissions list, check Allow for Read name, Read Name, and Read objectClass.

Check Apply These Permissions to Objects and/or Containers Within this Container Only.

Step 8 Click OK to close the Permission Entry for Users window.

The Access Control Settings for Users window now has four Anonymous Logon permissions.

Step 9 Click Apply, then OK twice to close the Properties window.


Related Topics

Inheriting Permissions from the Parent Object

Inheriting Permissions from the Parent Object

The permissions applied for the user container affect all the user objects within that container. But some users, especially administrator users, might not inherit these permissions. In this situation, you must explicitly configure those users to inherit permissions from the parent object.

Procedure

To make the user inherit permissions from parent object in Active Directory 2000 and 2003, complete these steps:


Step 1 Launch the ADSIEDIT (from Start > Run, enter ADSIEDIT.msc), and navigate to the user container.

Step 2 Select the user, right-click, and view properties.

The Properties window displays.

Step 3 In the Properties window, click the Security tab, and then click the Advanced button.

Step 4 Check Allow Inheritable Permissions from Parent to Propagate to this Object.

Step 5 Click Apply and then OK to close the windows.


Related Topics

Configuring Additional Information for Microsoft Active Directory 2003

Verifying Permissions for Microsoft Active Directory

Configuring Additional Information for Microsoft Active Directory 2003

Windows 2003 servers require certain additional configuration to enable anonymous queries.

Procedure

To enable anonymous queries on Windows 2003 servers, complete these additional steps:


Step 1 Launch ADSIEdit (from Start > Run, enter ADSIEDIT.msc).

Step 2 Navigate to CN=Directory Service, CN= Windows NT, CN = Services, CN= Configuration, DC=domain name, DC=com.

Step 3 Right-click the CN=Directory Service container, click Properties, and scroll to the dsHeuristics attribute.


Note The Properties window varies for various Windows 2003 servers. On certain servers, you might see a list box for properties instead of a selection box.


Step 4 In Edit Attribute field, enter 0000002 if the dsHeuristics attribute is not already set.

The seventh character (2) controls the way you can bind to the LDAP service.

If, instead of 2, the character is 0 or absent, it means that anonymous LDAP operations are disabled. Setting the seventh character to 2 permits anonymous operations.


Note If the attribute already contains a value, make sure you are changing only the seventh character from the left. This is the only character that needs to be changed to enable anonymous binds.


For example, if the current value is 0010000, change it to 0010002.
If the current value is less than 7 characters, add zeros followed by 2; for example, 001 becomes 0010002.

Step 5 Click Apply and then OK to close the window.


Related Topics

Verifying Permissions for Microsoft Active Directory

Configuring Cisco Unified Presence Server LDAP Settings for Microsoft Active Directory

Verifying Permissions for Microsoft Active Directory

After you complete the permission configuration, you should verify it.

Procedure

To verify permissions for Microsoft Active Directory 2000 and 2003, complete these steps.


Step 1 Launch ADSIEDIT (from Start > Run, enter ADSIEDIT.msc).

Step 2 In the left panel, navigate to the user container, find the user name. Right click to view the Properties window.

Step 3 On the Properties window, select the Security tab, and then click the Advanced button.

The Access Control Settings for the user appear.

Step 4 On the Permissions tab, sort by name.

You should see four Anonymous Logon entries. The first entry should have the List Contents permission, and the other three entries should have the Read Property permissions.

If this is not the case, check Allow Inheritable Permissions to Propagate to this Object.

Step 5 Click Apply and then OK to close the windows.


Related Topics

Configuring Cisco Unified Presence Server LDAP Settings for Microsoft Active Directory

Configuring Cisco Unified Presence Server LDAP Settings for Microsoft Active Directory

After you configure Microsoft Active Directory for anonymous queries, you must complete other LDAP-specific configuration on the Cisco Unified Presence Server.

Procedure

Complete these tasks from Cisco Unified Presence Server Administration:


Step 1 Set up the LDAP attribute map with this mapping:

LastName = SN

UserID = sAMAccountName

For more information, see the "Configuring the LDAP Attribute Map" section.

Step 2 Follow the instructions in the "Specifying LDAP Server Names and Addresses" section and include these steps:

a. Match the port number setting in Cisco Unified Presence Server with that used on the Active Directory LDAP server. The default is 389.

If the server is Global Catalogue, enter 3268 as the port number.

b. For protocol, select TCP if the Global Catalogue server is used.

Step 3 In Cisco Unified Presence Server Administration, configure the LDAP server profile.

Follow the instructions in the "Creating LDAP Server Profiles" section and include these steps:

a. In the LDAP Directory Information section, make sure to:

Leave the Bind Distinguished Name field blank.

Leave the Password field blank.

Check Anonymous Bind.

b. In the LDAP Search Context Information section, specify the search context. Set O and OU (OU must contain users; for example, ou=users,dc=cisco,dc=com).

For Microsoft Active Directory, cn=users,DC=EFT-LA,DC=cisco,DC=com.

The search base should include all users of Cisco Unified Personal Communicator.

c. In the LDAP Server Information section, select the primary and backup servers that you configured in the "Specifying LDAP Server Names and Addresses" section.


Cisco Unity Connection Configuration

Cisco Unity Connection provides the voice-mail features described in the "Features and Benefits" section on page 1-1 to Cisco Unified Personal Communicator.

Procedure


Step 1 Install a supported release of Cisco Unity Connection.

For information about the supported releases, see the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

Step 2 In Cisco Unity Connection Administration, enable Internet Mail Access Protocol (IMAP) client access to voice messages for users associated with a class of service.

a. Expand Class of Service in the left pane, and then click Class of Service.

b. On the Search Class of Service window, in the Search Results table, click the display name of the applicable class of service.

c. On the Edit Class of Service window, under Licensed Features, check Allow Users to Access Voice Mail Using an IMAP Client.

d. Select Allow Users to Access Message Bodies so that users have access to the entire voice mail.

e. Click Save.

For more information, see the Cisco Unity Connection User Moves, Adds, and Changes Guide at this URL:

http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html

Step 3 Set up an account on the Cisco Unity Connection server for each Cisco Unified Personal Communicator user with a voice mailbox.

Make sure that the user ID and the password used for logging in to Cisco Unity Connection are the same as the ones you created in the Cisco Unified CallManager for each Cisco Unified Personal Communicator user.

For information about setting up the account, see the Cisco Unity Connection User Moves, Adds, and Changes Guide at this URL:

http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html

Step 4 Configure a new e-mail account to enable Cisco Unified Personal Communicator users to access Cisco Unity Connection voice messages from their IMAP client application. For more information, see the Cisco Unity Connection User Setup Guide at this URL:

http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html

Step 5 Perform the Cisco Unity Connection server-specific configuration on the Cisco Unified Presence Server:

Specifying Cisco Unity Connection Server Names and Addresses

Creating Cisco Unity Connection Server Profiles


Cisco Unified MeetingPlace Express Configuration

Cisco Unified MeetingPlace Express provides Cisco Unified Personal Communicator users with the ability to escalate to a web-only meeting from within an existing audio or video communication session. Cisco Unified MeetingPlace Express does not reserve voice ports for web-only meetings initiated through Cisco Unified Personal Communicator.

For detailed Cisco Unified MeetingPlace Express-specific information for the integration with Cisco Unified Personal Communicator, managing certificates, creating user profiles, and for call-control integration, see the configuration and maintenance guide at this URL:

http://www.cisco.com/en/US/products/ps6533/prod_maintenance_guides_list.html

Procedure

Complete these tasks to enable web-only meetings to be initiated from Cisco Unified Personal Communicator:


Step 1 Install a supported release of Cisco Unified MeetingPlace Express.

For information about the supported releases, see the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

Step 2 Through Cisco Unified MeetingPlace Express Administration Center, install enough web-conferencing licenses on Cisco Unified MeetingPlace Express to accommodate both the full web meetings that are initiated from Cisco Unified MeetingPlace Express and the web-only meetings that are initiated from Cisco Unified Personal Communicator.

Step 3 If not already enabled, enable the Secure Sockets Layer (SSL) encryption technology on the Cisco Unified MeetingPlace Express server by obtaining and uploading the required certificates from a trusted certificate authority (CA).

The certificate is required for secure communications between Cisco Unified Personal Communicator and Cisco Unified MeetingPlace Express.

Step 4 Set up a user profile on the Cisco Unified MeetingPlace Express server for each Cisco Unified Personal Communicator user who might initiate web-only meetings from a Cisco Unified Personal Communicator conversation.

Make sure to set the Method of Attending to I'll Call In for users who might initiate web-only meetings; otherwise, the Cisco Unified MeetingPlace Express system will try to contact the user who clicked the Escalate to Web Conference button in Cisco Unified Personal Communicator. Make sure to tell users not to change this Cisco Unified MeetingPlace Express setting.

You do not need to create a Cisco Unified MeetingPlace Express profile for Cisco Unified Personal Communicator users who attend web meetings. They join the web meeting as guests, and a password is not needed.


Tip As an alternative, you can configure the Administrative XML Layer Simple Object Access Protocol (AXL SOAP) authentication on Cisco Unified CallManager to simplify Cisco Unified MeetingPlace Express user profile administration. With this configuration, the Cisco Unified Personal Communicator meeting initiator needs a Cisco Unified CallManager profile instead of a Cisco Unified MeetingPlace Express user profile. With AXL authentication, when the initiator requests a meeting for the first time through Cisco Unified Personal Communicator, a Cisco Unified MeetingPlace Express profile is automatically created for the initiator.


Step 5 Change the network configuration so that inbound calls from the public switched telephone network (PSTN) to Cisco Unified Personal Communicator support RFC2833.

For inbound calls, Cisco Unified Personal Communicator requires RFC2833 support if these calls require dual tone multifrequency (DTMF) digit collection. Inbound calls to the client will not be answered with key press markup language (KPML) support.

A typical inbound call scenario is when Cisco Unified MeetingPlace calls the user as a conference is being set up. In this situation, if the inbound call from the PSTN supports RFC2833, the Cisco Unified Personal Communicator user can join the meeting by using the session dial pad.

For outbound calls, Cisco Unified Personal Communicator supports both KPML and RFC2833 digit collection.

Step 6 Perform the Cisco Unified MeetingPlace Express server-specific configuration on the Cisco Unified Presence Server:

Specifying Cisco Unified MeetingPlace Express Server Names and Addresses

Creating Cisco Unified MeetingPlace Express Server Profiles


Cisco Unified Presence Server Configuration

This section describes the Cisco Unified Presence Server configuration needed for Cisco Unified Personal Communicator. Cisco Unified Presence Server provides client configuration and presence information to Cisco Unified Personal Communicator. For information about the supported Cisco Unified Presence Server releases, see the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

Topics in this section include:

Configuring the LDAP Attribute Map (required)

Specifying LDAP Server Names and Addresses (required)

Creating LDAP Server Profiles (required)

Specifying Cisco Unity Connection Server Names and Addresses (required)

Creating Cisco Unity Connection Server Profiles (required)

Specifying Cisco Unified MeetingPlace Express Server Names and Addresses (required)

Creating Cisco Unified MeetingPlace Express Server Profiles (required)

Specifying CTI Gateway Server Names and Addresses (required)

Creating CTI Gateway Server Profiles (required)

Creating SIP Proxy Server Profiles (required)

Changing Application Profiles on a Per-User Basis

Configuring the LDAP Attribute Map

You must configure the LDAP attribute map through the Cisco Unified Presence Server. You enter LDAP attributes for your environment, which map to the given Cisco Unified Personal Communicator attribute names.

Procedure

Complete these steps from Cisco Unified Presence Server Administration:


Step 1 Choose Application > Unified Personal Communicator > Settings to display the Cisco Unified Personal Communicator Settings window.

Step 2 In the LDAP Attribute Map section, for each Cisco Unified Personal Communicator attribute name (contact schema), enter the corresponding LDAP user object attribute into the LDAP field. Table 2-5 lists the Cisco Unified Personal Communicator attribute names, the default LDAP attribute names, and provides a place for you to enter the corresponding attributes for your directory.

Change any default LDAP attribute name if it does not match with your LDAP directory. Ensure that an LDAP attribute is paired to only one Cisco Unified Personal Communicator attribute.

For information on LDAP settings for Microsoft Active Directory, see the "Configuring Microsoft Active Directory for Anonymous Queries" section.

Table 2-5 LDAP Attribute Map 

UPC Attribute Name
LDAP Attribute Name (default)
Your LDAP Attribute Name

UID

employeenumber

 

LastName1

sn

 

Nickname1

nickname

 

Photo

jpegPhoto

 

DisplayName

displayName

 

NameSuffix

   

BusinessEMail

mail

 

BusinessPhoneNumber1

telephoneNumber

 

BusinessMobilePhone

mobile

 

BusinessFax

facsimileTelephoneNumber

 

HomeEMail

   

HomeFax

   

FirstName1

givenName

 

MiddleName

initials

 

UserID1

uid

 

Title

title

 

NamePrefix

   

Gender

   

IM

   

BusinessVoiceMail

voicemail

 

BusinessPager

pager

 

BusinessOtherPhone

   

HomeMobilePhone

   

URL

labeledURI

 

1 For maximum performance (faster LDAP searches in Cisco Unified Personal Communicator), make sure to index these attributes. For information on how to enable indexing, see your LDAP server documentation.


For information about mapping the UserID attribute, see the "Rules for Mapping the UserID Attribute" section.

The values are global to all LDAP server hosts.

Step 3 Click Save.


Related Topics

Rules for Mapping the UserID Attribute

Rules for a Displayed Contact Name

Photo Attributes and Format

Specifying LDAP Server Names and Addresses

Rules for Mapping the UserID Attribute

The UPC UserID attribute in the LDAP attribute map in Table 2-5 must match the Cisco Unified CallManager user ID.

This mapping is required for a contact in LDAP to be added to the Contact list in Cisco Unified Personal Communicator. This field associates the LDAP user with the associated user on Cisco Unified CallManager and Cisco Unified Presence Server.

Rules for a Displayed Contact Name

These rules determine how a name is displayed as a contact in Cisco Unified Personal Communicator:

If the end user edits a contact name in Cisco Unified Personal Communicator (Actions > Edit Contact Nickname), display this name.

If you configured an LDAP attribute for DisplayName, display this name.

If you configured an LDAP attribute for Nickname, display this name with the last name.

Otherwise, display the configured LDAP attributes for the first and last names in the Contact pane.

If you did not configure LDAP attributes for the FirstName and LastName, display the LDAP UserID or the Cisco Unified Presence Server user ID in the Contact pane.

Photo Attributes and Format

By default, Cisco Unified Personal Communicator uses the jpegPhoto LDAP attribute, which is present in the Windows 2003 Active Directory schema. By contrast, the Windows 2000 Active Directory uses the thumbnailPhoto attribute. You can change the field in which Cisco Unified Personal Communicator looks for the photo through the LDAP attribute map in Cisco Unified Presence Server administration described in the "Configuring the LDAP Attribute Map" section.

You cannot configure the Cisco Unified Presence Server, Cisco Unified Personal Communicator, or the Windows Active Directory with image URLs because the image data must be stored in Active Directory as a base-64 encoded JPEG binary object.

You can use any application that supports storing photos to LDAP servers; for example, http://phpldapadmin.sourceforge.net/.

For the photo to be displayed in the contact details in Cisco Unified Personal Communicator, the user must have permission to read it; that is, the Read/List All attributes on the subtree must be correct. You set this through the AD Directory Administrator tool or through ADSI EDIT.

Specifying LDAP Server Names and Addresses

You must specify the LDAP server names, addresses ports, and protocol types on Cisco Unified Presence Server so that Cisco Unified Personal Communicator can interact with them.

Procedure

Complete these steps from Cisco Unified Presence Server Administration:


Step 1 Choose Application > Unified Personal Communicator > LDAP Server.

Step 2 In the Find and List LDAP Hosts window, click Add New to add a new server.

Step 3 In the LDAP Host Configuration window, enter information into the fields:

a. For the Name field, enter the name of the server. It is limited to 128 characters.

b. (Optional) For the Description field, enter a description of the server. It is limited to 128 characters. You can enter alphanumeric characters, spaces, and these characters: !#$'()*+,./:;=?@^_`{|}~-

c. For the Hostname/IP Address field, enter an IP address or a fully qualified domain name for the server.

d. For the Port field, enter 389 as the port number used by the LDAP server.

Check the LDAP server documentation or the LDAP server configuration for this information.

e. For the Protocol Type drop-down list, select TCP as the protocol to use when contacting this server.

Step 4 Click Save.

You can add more servers, select all servers, delete selected servers, clear all selections, and adjust the number of rows displayed on the page.


Related Topics

Creating LDAP Server Profiles

Creating LDAP Server Profiles

You must create an LDAP server profile on the Cisco Unified Presence Server to configure primary and backup servers for redundancy and to add users to the profile. The LDAP server profile also has LDAP directory configuration settings and search context information.

Procedure

Complete these steps from Cisco Unified Presence Server Administration:


Step 1 Choose Application > Unified Personal Communicator > LDAP Profile.

Step 2 In the Find and List LDAP Profiles window, click Add New to add a new profile and to display the LDAP Profile Configuration window.

Step 3 In the LDAP Profile Information section, enter information into the fields:

a. In the Name field, enter the profile name limited to 128 characters.

b. (Optional) In the Description field, enter a description limited to 128 characters. You can enter alphanumeric characters, spaces, and these characters: !#$'()*+,./:;=?@^_`{|}~-

Step 4 In the LDAP Directory Information section, enter information into the fields:

a. In the Bind Distinguished Name field, enter the administrator-level account information limited to 128 character s in the form useraccount@domain.com.

This is the distinguished name with which you bind for authenticated bind.

b. In the Password field, enter the LDAP bind password (the password for the administrator-level account that you provided in the Bind Distinguished Name string) so users can access this LDAP server.

Enter the same password in the Confirm Password field. The password is limited to 128 characters.

c. After configuring Cisco Unified Presence Server for authenticated bind with the LDAP server, you must configure the LDAP server for anonymous permissions and anonymous login so that all directory information (name, number, mail, fax, home number, and so forth) is passed to the Cisco Unified Personal Communicator client. For more information, see the "Configuring Microsoft Active Directory for Anonymous Queries" section.

d. (Optional) Select Anonymous Bind so that users can log in anonymously to this LDAP server for read-only access.

Deselect this check box to use the user credentials to log in to this LDAP server.

Step 5 In the LDAP Search Context Information section, enter information into the fields:

a. (Optional) In the Search Context field, enter the location where all LDAP users exist. This location is a container or directory. The name is limited to 256 characters.

b. (Optional) Select Recursive Search to perform a recursive search of the directory starting at the search base.

Step 6 In the LDAP Server Information section, select the primary LDAP server and optional backup servers from the drop-down lists.

Only servers you specified in the "Specifying LDAP Server Names and Addresses" section appear in the primary and backup server drop-down lists.

Step 7 Click Add Users to Profile.

Step 8 In the Find and List Users window, click Find to populate the search results fields, or search for a specific user, and then click Find.

Step 9 Select users by clicking their check boxes, and add them to this profile by clicking Add Selected.

You can add more users, select all users, delete selected users, clear all selections, and adjust the number of rows displayed on the page.

Step 10 Click Save to save the profile.

If you want to create another profile, click Add New. If you want to delete the profile, click Delete.


Related Topics

Changing Application Profiles on a Per-User Basis

Specifying Cisco Unity Connection Server Names and Addresses

You must specify Cisco Unity Connection server names, addresses, ports, and protocol types on the Cisco Unified Presence Server so that Cisco Unified Personal Communicator can interact with them.

Procedure

Complete these steps from Cisco Unified Presence Server Administration:


Step 1 Choose Application > Unified Personal Communicator > Unity Connection Server.

Step 2 In the Find and List Unity Connection Hosts window, click Add New to add a new server.

Step 3 In the Unity Connection Host Configuration window, enter information into the fields:

a. For the Name field, enter the name of the server. It is limited to 128 characters.

b. (Optional) For the Description field, enter a description of the server. It is limited to 128 characters. You can enter alphanumeric characters, spaces, and these characters: !#$'()*+,./:;=?@^_`{|}~-

c. For the Hostname/IP Address field, enter an IP address or a fully qualified domain name for the server.

d. For the Port field, specify the port number configured for the server. Enter 143.

e. For the Protocol Type drop-down list, select TCP as the protocol to use when contacting this server.

Step 4 Click Save.

You can add more servers, select all servers, delete selected servers, clear all selections, and adjust the number of rows displayed on the page.


Related Topics

Creating Cisco Unity Connection Server Profiles

Creating Cisco Unity Connection Server Profiles

You must create a Cisco Unity Connection server profile on the Cisco Unified Presence Server to configure primary and backup servers for redundancy and to add users to the profile.

Procedure

Complete these steps from Cisco Unified Presence Server Administration:


Step 1 Choose Application > Unified Personal Communicator > Unity Connection Profile.

Step 2 In the Find and List Unity Connection Profiles window, click Add New to add a new profile.

Step 3 In the Unity Connection Profile Configuration window, enter information into the fields.

a. For the Name field, enter the profile name limited to 128 characters.

b. (Optional) For the Description field, enter a description of the profile limited to 128 characters. You can enter alphanumeric characters, spaces, and these characters: !#$'()*+,./:;=?@^_`{|}~-

c. (Optional) Select an option from the Voice Messaging Pilot drop-down list.

With this setting, the software obtains the directory number (pilot number) for the voice-mail system (if any) to which unanswered calls are redirected.

Number—Use the default voice-mail pilot for the system per the configuration in Cisco Unified CallManager Administration from the Voice Mail > Voice Mail Pilot menu.

The voice-mail pilot number is the directory number that a user dials to access their voice messages. Cisco Unified CallManager automatically dials the voice-messaging number when a user presses the Messages button on their phone. Each pilot number can belong to a different voice-messaging system.

No Voice Mail—Disable sending an unanswered incoming call to voice mail.

d. From the Primary Unity Connection Server and the Backup Unity Connection Server drop-down lists, select a primary server and backup servers.

Only servers you specified in the "Specifying Cisco Unity Connection Server Names and Addresses" section appear in the primary and backup server drop-down lists.

Step 4 Click Add Users to Profile.

Step 5 In the Find and List Users window, click Find to populate the search results fields, or search for a specific user, and then click Find.

Step 6 Select users by clicking their check boxes, and add them to this profile by clicking Add Selected.

You can add more users, select all users, delete selected users, clear all selections, and adjust the number of rows displayed on the page.

Step 7 Click Save to save the profile.

If you want to create another profile, click Add New. If you want to delete the profile, click Delete.


Related Topics

Changing Application Profiles on a Per-User Basis

Specifying Cisco Unified MeetingPlace Express Server Names and Addresses

You must specify the Cisco Unified MeetingPlace Express server names, addresses, ports, and protocol types on the Cisco Unified Presence Server so that Cisco Unified Personal Communicator can interact with them.

Procedure

Complete these steps from Cisco Unified Presence Server Administration:


Step 1 Choose Application > Unified Personal Communicator > MeetingPlace Express Server.

Step 2 In the Find and List MeetingPlace Express Hosts window, click Add New to add a new server.

Step 3 In the MeetingPlace Express Host Configuration window, enter information into the fields:

a. For the Name field, enter the name of the server. The limit is 128 characters.

b. (Optional) For the Description field, enter a description of the server. The limit is 128 characters. You can enter alphanumeric characters, spaces, and these characters: !#$'()*+,./:;=?@^_`{|}~-

c. For the Hostname/IP Address field, enter an IP address or a fully qualified domain name for the server.

d. For the Port field, specify the port number configured for the server. Enter 80 for HTTP, and enter port 443 for HTTPS.

e. For the Protocol drop-down list, specify the protocol to use when contacting this server.

HTTP: selects Hypertext Transfer Protocol as the standard method for transferring data between the server and the browser. Choose this option if the Cisco Unified MeetingPlace Express server does not have SSL enabled.

HTTPS: selects Hypertext Transfer Protocol over SSL as the method for securely transferring data between the server and the browser. Choose this option if the Cisco Unified MeetingPlace Express server has SSL enabled.

Step 4 Click Save.

You can add more servers, select all servers, delete selected servers, clear all selections, and adjust the number of rows displayed on the page.


Related Topics

Creating Cisco Unified MeetingPlace Express Server Profiles

Creating Cisco Unified MeetingPlace Express Server Profiles

You must create a Cisco Unified MeetingPlace Express server profile on the Cisco Unified Presence Server to configure primary and backup servers for redundancy and to add users to the profile.


Note By contrast, a profile in Cisco Unified MeetingPlace Express defines the privileges and preferences configured for a specific user in this application.


Procedure

Complete these steps from Cisco Unified Presence Server Administration:


Step 1 Choose Application > Unified Personal Communicator > MeetingPlace Express Profile.

Step 2 In the Find and List MeetingPlace Express Profiles window, click Add New to add a new profile.

The MeetingPlace Express Profile Configuration window redisplays.

Step 3 In the MeetingPlace Express Profile Configuration window, enter information into the fields.

a. For the Name field, enter the profile name limited to 128 characters.

b. (Optional) For the Description field, enter a description of the profile limited to 128 characters. You can enter alphanumeric characters, spaces, and these characters: !#$'()*+,./:;=?@^_`{|}~-

c. From the Primary MeetingPlace Express Server and the Backup MeetingPlace Express Server drop-down lists, select a primary server and backup servers.

Only servers you specified in the "Specifying Cisco Unified MeetingPlace Express Server Names and Addresses" section appear in the primary and backup server drop-down lists.

Step 4 Click Add Users to Profile.

Step 5 In the Find and List Users window, click Find to populate the search results fields, or search for a specific user, and then click Find.

Step 6 Select users by clicking their check boxes, and add them to this profile by clicking Add Selected.

You can add more users, select all users, delete selected users, clear all selections, and adjust the number of rows displayed on the page.

Step 7 Click Save to save the profile.

If you want to create another profile, click Add New. If you want to delete the profile, click Delete.


Related Topics

Changing Application Profiles on a Per-User Basis

How Participants Join the Web-Only Meeting

For information about how participants add web conferencing to their conversation sessions (join the web-only meeting), see the User Guide for Cisco Unified Personal Communicator at this URL:

http://www.cisco.com/en/US/products/ps6844/products_user_guide_list.html

Related Topics

Participant Privileges and Meeting Controls

Participant Privileges and Meeting Controls

Cisco Unified Personal Communicator meeting participants join the web meeting as guests. Guests do not require a Cisco Unified MeetingPlace Express profile or a password to attend web meetings that are initiated from Cisco Unified Personal Communicator.

All participants have presenter privileges and can share data if the Cisco Unified MeetingPlace Express Presenter Add-In is installed.

For information about installing the Presenter Add-In, see the user guide for Cisco Unified MeetingPlace Express at this URL:

http://www.cisco.com/en/US/products/ps6533/products_user_guide_list.html

For information about supported and unsupported Cisco Unified MeetingPlace Express meeting controls, see the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

For a description of the characteristics of a web conference that you add to a Cisco Unified Personal Communicator conversation, see the user guide for Cisco Unified Personal Communicator at this URL:

http://www.cisco.com/en/US/products/ps6844/products_user_guide_list.html

For an overview of the meeting room (and what users can expect to see in a web-only meeting) and for information about presenting and working with shared content, see the user guide for Cisco Unified MeetingPlace Express at this URL:

http://www.cisco.com/en/US/products/ps6533/products_user_guide_list.html

Related Topics

How Participants Join the Web-Only Meeting

Specifying CTI Gateway Server Names and Addresses

The CTI gateway, which is the CTIManager component of Cisco Unified CallManager, provides desk phone control (phone-association mode) to Cisco Unified Personal Communicator users. The CTIManager program is installed when Cisco Unified CallManager is installed.

You must specify CTI gateway server names, addresses, ports, and protocol types on the Cisco Unified Presence Server so that the information for reaching the CTI gateway server can be downloaded when the end user logs in to Cisco Unified Personal Communicator.

Cisco Unified Presence Server dynamically creates a TCP-based CTI gateway host profile based on the hostname of Cisco Unified CallManager. Before using this profile, verify that the Cisco Unified Presence Server and Cisco Unified Personal Communicator clients can ping Cisco Unified CallManager by its DNS name. If they cannot reach the server, you need to add a new server based on the IP address of Cisco Unified CallManager as described in the next procedure. You do not need to delete the automatically created host profiles.

As an alternative, if you configure Cisco Unified CallManager with an IP address through the Cisco Unified CallManager Administration System > Server menu, Cisco Unified Presence Server will dynamically create a TCP-based CTI gateway host profile for that address. The fields in Cisco Unified Presence Server Administration (Application > Unified Personal Communicator > CTI Gateway Server) are automatically populated, and you do not need to perform this procedure. Proceed to the "Creating CTI Gateway Server Profiles" section to add users to this profile.

Procedure

Complete these steps from Cisco Unified Presence Server Administration:


Step 1 Choose Application > Unified Personal Communicator > CTI Gateway Server.

Step 2 In the Find and List CTI Gateway Hosts window, click Add New to add a new server.

Step 3 In the CTI Gateway Host Configuration window, enter information into the fields:

a. For the Name field, enter the name of the server. The limit is 128 characters.

b. (Optional) For the Description field, enter a description of the server. The limit is 128 characters. You can enter alphanumeric characters, spaces, and these characters: !#$'()*+,./:;=?@^_`{|}~-

c. For the Hostname/IP Address field, enter an IP address or a fully qualified domain name of the Cisco Unified CallManager server that is running the CTI service.

d. For the Port field, enter 2748 as the port number configured for the server.

e. For the Protocol Type drop-down list, select TCP as the protocol to use when contacting this server.

Step 4 Click Save.

You can add more servers, select all servers, delete selected servers, clear all selections, and adjust the number of rows displayed on the page.


Related Topics

Creating CTI Gateway Server Profiles

Creating CTI Gateway Server Profiles

You must create a CTI gateway server profile on the Cisco Unified Presence Server to configure primary and backup servers for redundancy and to add users to the profile.

Cisco Unified Presence Server dynamically creates a TCP-based CTI gateway server profile based on the hostname of Cisco Unified CallManager. Before using this profile, verify that Cisco Unified Presence Server and Cisco Unified Personal Communicator clients can ping Cisco Unified CallManager by its DNS name. If they cannot reach the server, you need to add a new server based on the IP address of Cisco Unified CallManager as described in the next procedure. You do not need to delete the automatically created host profiles.

As an alternative, if you configure Cisco Unified CallManager with an IP address through the Cisco Unified CallManager Administration System > Server menu, Cisco Unified Presence Server dynamically creates a TCP-based CTI gateway server profile based on that address. The fields in Cisco Unified Presence Server Administration (Application > Unified Personal Communicator > CTI Gateway Profile) are automatically populated, and you need only to add users to the default CTI TCP profile that is created (see Step 4).

Procedure

Complete these steps from Cisco Unified Presence Server Administration:


Step 1 Choose Application > Unified Personal Communicator > CTI Gateway Profile.

Step 2 In the Find and List CTI Gateway Profiles window, click Add New to add a new profile.

Step 3 In the CTI Gateway Profile Configuration window, enter information into the fields.

a. For the Name field, enter the profile name limited to 128 characters.

b. (Optional) For the Description field, enter a description of the profile limited to 128 characters. You can enter alphanumeric characters, spaces, and these characters: !#$'()*+,./:;=?@^_`{|}~-

c. From the Primary CTI Gateway Server and the Backup CTI Gateway Server drop-down lists, select a primary server and backup servers.

Only servers you specified in the "Specifying CTI Gateway Server Names and Addresses" section appear in the primary and backup server drop-down lists.

Step 4 Click Add Users to Profile.

Step 5 In the Find and List Users window, click Find to populate the search results fields, or search for a specific user, and then click Find.

Step 6 Select users by clicking their check boxes, and add them to this profile by clicking Add Selected.

You can add more users, select all users, delete selected users, clear all selections, and adjust the number of rows displayed on the page.

Step 7 Click Save to save the profile.

If you want to create another profile, click Add New. If you want to delete the profile, click Delete.


Related Topics

Changing Application Profiles on a Per-User Basis

Creating SIP Proxy Server Profiles

You must create a SIP proxy server profile on the Cisco Unified Presence Server to configure primary and backup servers for redundancy and to add users to the profile. The Cisco Unified Personal Communicator sends SIP messages to and receives SIP messages from this proxy server, which communicates with Cisco Unified CallManager or other servers.

Procedure

Complete these steps from Cisco Unified Presence Server Administration:


Step 1 Choose Application > Unified Personal Communicator > Proxy Profile.

Step 2 In the Find and List Proxy Profiles window, click Add New to add a new profile.

Step 3 In the Proxy Profile Configuration window, enter information into the fields.

a. For the Name field, enter the profile name limited to 128 characters.

b. (Optional) For the Description field, enter a description of the profile limited to 128 characters. You can enter alphanumeric characters, spaces, and these characters: !#$'()*+,./:;=?@^_`{|}~-

c. For Proxy Listener, select Default Cisco SIP Proxy TCP Listener from the drop-down list.

With this setting, Cisco Unified Personal Communicator uses TCP to communicate with the proxy server.

Do not select Default Cisco SIP Proxy UDP Listener. For more information, see the "Important Notes" section in the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

d. For the Primary Proxy Server and the Backup Proxy server (optional), select a primary and a backup server from the drop-down lists.

These servers were configured during the Cisco Unified Presence Server installation from the System > Server menu.

Step 4 Click Add Users to Profile.

Step 5 In the Find and List Users window, click Find to populate the search results fields, or search for a specific user, and then click Find.

Step 6 Select users by clicking their check boxes, and to add them to this profile by clicking Add Selected.

You can add more users, select all users, delete selected users, clear all selections, and adjust the number of rows displayed on the page.

Step 7 Click Save to save the profile.

If you want to create another profile, click Add New. If you want to delete the profile, click Delete.


Related Topics

Changing Application Profiles on a Per-User Basis

Changing Application Profiles on a Per-User Basis

You can change individual application profiles on a per-user basis. Application profiles are not required; it is possible that some Cisco Unified Personal Communicator users might not have a Cisco Unity Connection or a Cisco Unified MeetingPlace Express profile. In this situation, the drop-down selection displays None.

Prerequisites

You must first create the server profile before you can modify the user settings as described in these sections:

Creating LDAP Server Profiles

Creating Cisco Unity Connection Server Profiles

Creating Cisco Unified MeetingPlace Express Server Profiles

Creating CTI Gateway Server Profiles

Creating SIP Proxy Server Profiles

Procedure

Complete these steps from Cisco Unified Presence Server Administration:


Step 1 Choose Application > Unified Personal Communicator > User Settings.

Step 2 In the Unified Personal Communicator User Settings Find and List window, click Find to populate the search results fields, or search for a specific user, and then click Find.

Step 3 Select the user by clicking their link.

Step 4 In the CTI Control Information section, assign the preferred CTI device from the drop-down list to this user.

The preferred CTI device is the MAC address of the user's primary desk phone in the form of SEPxxxxxxxxxxxx. You must select this address whether or not the user intends to use the application only in soft-phone mode. The preferred CTI device is the device that the end user wants to control when in phone-association (desk phone) mode.

If the user does not specify a preferred device in Cisco Unified Personal Communicator, the one you specify as the preferred CTI device in Cisco Unified Presence Server is used.

Step 5 In the Application Profile Information section, decide which application profile to change for this user.

If you change a user application profile in this window (for example, change from Unity Profile 1 to Unity Profile 2), the change is reflected in Application > Unified Personal Communicator > Unity Connection Profile window.

If a user does not have an application profile for a specific server, select None.

Step 6 Click Save.


Firewall Configuration

Frequently used by corporations and educational institutions for increased security, firewalls work by blocking certain Internet traffic from entering or leaving a network.

Internet traffic moves through a firewall based on service identification numbers that are known as ports. Certain ports must be open for Cisco Unified Personal Communicator to work. Network administrators typically open a minimal number of network ports, allowing the traffic for approved applications to enter and leave the network while blocking other network traffic.

If users have a software firewall installed on their PCs or if there is a hardware firewall in the network between the Cisco Unified Presence Server and Cisco Unified Personal Communicator, you must configure the firewall to pass Cisco Unified Personal Communicator traffic. Failure to do so will result in missing, incorrect, or intermittent reachability status displayed in Cisco Unified Personal Communicator. For information about the network ports used by Cisco Unified Personal Communicator, see the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

Video Telephony Camera Configuration

You can configure users for point-to-point and for multipoint videoconferencing support.

Procedure


Step 1 Distribute video telephony (VT) cameras supported for use with Cisco Unified Personal Communicator to users. For more information, see the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

Step 2 Configure users for soft-phone use. For more information, see the "Adding Cisco Unified Personal Communicator as a Phone Type" section.

Step 3 Set up videoconferencing resources in Cisco Unified CallManager. For more information, see the "Configuring Videoconferencing Resources" section.

Step 4 Provide end users with the appropriate documentation to complete the installation:

Cisco VT Camera Quick Start Guide (for use with Windows-based PC clients)

http://www.cisco.com/en/US/products/sw/voicesw/ps5662/prod_installation_guides_list.html

iSight User Guide (for use with Macintosh-based PC clients)

http://www.apple.com/support/manuals/

See the "Providing Information to End Users" section on page 3-4.


Headsets and Other Audio Devices Configuration

You or the end user should install and configure any audio devices that require drivers, such as sound cards or USB headsets. Follow the headset instructions that are supplied with the headset.

For information on establishing the audio device and the control panel settings, see the user guide for Cisco Unified Personal Communicator at this URL:

http://www.cisco.com/en/US/products/ps6844/products_user_guide_list.html

For information about supported headsets and other audio devices, see the release notes at this URL:

http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

Related Topics

Use of Third-Party Headsets with Cisco Unified Personal Communicator

Use of Third-Party Headsets with Cisco Unified Personal Communicator

While Cisco does perform basic testing of third-party headsets for use with the Cisco Unified Personal Communicator application, it is ultimately the customer's responsibility to test this equipment in their own environment to determine suitable performance. Because of the many inherent environmental and hardware inconsistencies in the locations where this application is deployed, there is not a single best solution that is optimal for all environments.

Before customers begin deploying any headsets (especially deployment in quantity) in their production network, Cisco recommends thorough testing at the customer site to check for voice quality issues, especially hum and echo.

The primary reason that support of a headset would be inappropriate for an installation is the potential for an audible hum. This hum can either be heard by the remote party or by both the remote party and this application user. Causes for this humming sound range from electrical lights near the PC to the PC power source itself. In some cases, a hum heard on a headset plugged directly into the PC Universal Serial Bus (USB) port might be reduced or eliminated by using a powered USB hub.

In some instances, the mechanics or electronics of various headsets can cause remote parties to hear an echo of their own voice when they speak to Cisco Unified Personal Communicator users. The application user will not be aware of this echo.

Finally, some analog headsets do not match the electrical characteristics for which some soundcards are designed. The microphones on such headsets are frequently too sensitive, even when the input levels in Cisco Unified Personal Communicator are reduced to their lowest values. The users of such headsets will sound distorted to remote parties.

It is important to ask Cisco Unified Personal Communicator users whether a particular headset sounds good to them. In addition, remote parties should be queried as to the reception from this application when using a particular headset.

Related Topics

Headsets and Other Audio Devices Configuration