installation and configuration guide for cisco unified ... unified communications manager...

Installation and Configuration Guide for Cisco Unified Personal Communicator Release 7.0December 2008

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Installation and Configuration Guide for Cisco Unified Personal Communicator Release 7.0 ©2006—2008 Cisco Systems, Inc. All rights reserved.

Installatio

C O N T E N T S

C H A P T E R 1 Planning to Install Cisco Unified Personal Communicator 1-1

About Interactions With Servers and Applications 1-1

How Cisco Unified Personal Communicator Interacts With Servers at Startup 1-3

Network Settings That Are Retrieved from Servers 1-4

User Settings That Are Retrieved from Servers 1-5

Portable User Preferences That Are Stored on Cisco Unified Presence 1-5

Gathering Information to Configure Servers 1-6

Installing Servers 1-7

Application Dialing Rule Changes Required for Plus Dialing 1-10

Example of Application Dialing Rule Changes 1-11

C H A P T E R 2 Configuring Required Servers for Cisco Unified Personal Communicator 2-1

How to Configure Cisco Unified Communications Manager 2-1

Adding Desk Phones to the Cisco Unified Communications Manager Database 2-1

Completing the Cisco Unified IP Phone Configuration 2-3

Associating Cisco Unified IP Phones With Users and Adding Users to a Group 2-3

Adding Cisco Unified Personal Communicator as a Phone Type 2-5

Associating Lines, Users, and Directory Numbers 2-8

Do Not Disturb Behavior in Cisco Unified Personal Communicator 2-8

Configuring Extension Mobility 2-10

How to Configure Dialing Rules 2-11

Application Dialing and Directory Lookup Rules 2-11

How Cisco Unified Personal Communicator Transforms Dialed Numbers 2-11

Configuring Application Dialing Rules 2-12

Configuring Directory Lookup Rules 2-12

How to Configure Licensing in Cisco Unified Communications Manager 2-13

Licensing Options for Cisco Unified Personal Communicator 2-13

Obtaining a License File 2-14

Uploading a License File 2-14

Assigning Capabilities to Users 2-15

Viewing Licensing Information 2-16

Configuring the LDAP Server 2-16

How to Configure Cisco Unified Presence 2-17

Configuring Nodes 2-17

iiin and Configuration Guide for Cisco Unified Personal Communicator Release 7.0

Contents

How to Select the Proxy Listener 2-18

Selecting the Proxy Listener in Release 7.0 2-18

Selecting the Proxy Listener and Creating Proxy Profiles in Release 6.x 2-19

Specifying TFTP Server Addresses 2-20

How to Configure LDAP Settings 2-22

Configuring the LDAP Attribute Map 2-22

Rules for a Displayed Contact Name 2-23

Fetching Contact Pictures from a Web Server 2-23

Specifying LDAP Server Names and Addresses 2-24

Creating LDAP Profiles 2-26

How to Configure CTI Gateway Settings 2-28

Desk-Phone Mode Failover and Recovery 2-28

CTI Connection Failures and Recovery When No Calls Are Present 2-28

CTI Connection Failures and Recovery When Calls Are Present 2-29

Specifying CTI Gateway Server Names and Addresses 2-29

Creating CTI Gateway Profiles 2-30

How to Change Application Profiles 2-31

Changing Application Profiles for a Single User 2-32

Changing Application Profiles for Multiple Users 2-32

Disabling Instant Messaging Globally 2-33

Configuring the Maximum Contact List Size 2-33

Configuring Firewalls to Pass Cisco Unified Personal Communicator Traffic 2-34

Configuring Users for Point-to-Point Video Calls and for Multipoint Videoconferencing 2-34

C H A P T E R 3 Configuring Recommended Servers for Cisco Unified Personal Communicator 3-1

How to Configure Voice-Mail Servers 3-1

Configuring Cisco Unity Connection Servers 3-2

Configuring Cisco Unity Servers 3-4

Specifying Voice-Mail Server Names and Addresses in Cisco Unified Presence Administration 3-6

Configuring Secure Messaging in Cisco Unified Presence Administration 3-7

Specifying Mailstore Server Names and Addresses in Cisco Unified Presence Administration 3-9

Creating Voice-Mail Profiles in Cisco Unified Presence Administration 3-11

How to Configure Conferencing Servers 3-12

Configuring Cisco Unified MeetingPlace Express and Cisco Unified MeetingPlace Express VT Servers 3-12

Configuring Cisco Unified MeetingPlace Servers 3-15

Specifying Conferencing Server Names and Addresses in Cisco Unified Presence Administration 3-17

Creating Conferencing Profiles in Cisco Unified Presence Administration 3-18

ivInstallation and Configuration Guide for Cisco Unified Personal Communicator Release 7.0

Contents

Configuring Videoconferencing Resources 3-19

C H A P T E R 4 Deploying and Updating Cisco Unified Personal Communicator 4-1

How to Deploy the Application 4-1

Installer Package Names 4-1

Localized Installer Packages and Three-Letter Language Locales 4-2

Software Download Site 4-3

Deploying the Application in a Mac OS Environment 4-4

Deploying the Application and the Camera Drivers in a Microsoft Windows Environment 4-4

Installing the Application 4-5

Updating the Application 4-6

Installation and Configuration of Headsets and Other Audio Devices 4-6

Use of Third-Party Headsets with Cisco Unified Personal Communicator 4-7

Information to Provide to Users 4-7

C H A P T E R 5 Adding a New User After Deploying Cisco Unified Personal Communicator 5-1

Configuring a New User for Full Cisco Unified Personal Communicator Functionality 5-1

IN D E X

vInstallation and Configuration Guide for Cisco Unified Personal Communicator Release 7.0

Contents

viInstallation and Configuration Guide for Cisco Unified Personal Communicator Release 7.0

Installation and Configuration Guide fo

C H A P T E R 1
Planning to Install Cisco Unified Personal Communicator
December 2008

• About Interactions With Servers and Applications, page 1-1

• Gathering Information to Configure Servers, page 1-6

• Installing Servers, page 1-7

• Application Dialing Rule Changes Required for Plus Dialing, page 1-10

Note For details about new features in this release, see the “New and Changed Information” section in the release notes: http://www.cisco.com/en/US/products/ps6844/prod_release_notes_list.html

About Interactions With Servers and ApplicationsCisco Unified Personal Communicator interacts with these servers and applications as shown in Figure 1-1 on page 1-3:

• Cisco Unified Communications Manager call-processing system (formerly known as Cisco Unified CallManager) provides telephony features, video, and voice-over-IP capabilities to Cisco Unified Personal Communicator. Through the interaction with Cisco Unified Communications Manager, Cisco Unified Personal Communicator offers integrated soft-phone capabilities (audio and video) and computer telephony interface (CTI) control of the physical Cisco Unified IP Phone. You administer Cisco Unified Personal Communicator as a phone device by using the Cisco Unified Communications Manager Administration Phone Configuration window.

• Cisco Unified Presence delivers a Session Initiation Protocol (SIP) presence engine and a SIP proxy server functionality to Cisco Unified Personal Communicator. The presence engine provides Cisco Unified Personal Communicator with the infrastructure for user and device status information (for example, available, away, do not disturb) by using SIP Instant Messaging and Presence Leveraging Extensions (SIMPLE).

The presence engine stores information about the preferred communication method (instant message, e-mail, voice, video) and the contact list for each user. Cisco Unified Presence also maintains login authentication for, and provides configuration information to, Cisco Unified Personal Communicator by using Simple Object Access Protocol (SOAP) over HTTP and HTTPS.

1-1r Cisco Unified Personal Communicator Release 7.0

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

Chapter 1 Planning to Install Cisco Unified Personal CommunicatorAbout Interactions With Servers and Applications

The proxy server provides both registration and routing support for its clients, all of which are SIP-based. The Cisco Unified Personal Communicator sends SIP messages to and receives SIP messages from this proxy server. These SIP messages are for presence information and database change notifications. Cisco Unified Personal Communicator also sends SIP messages (via the proxy) to other Cisco Unified Personal Communicator clients for instant messaging.

• Corporate Lightweight Directory Access Protocol (LDAP) version 3 directories interact 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 the contact list.

• Cisco Unity Connection or Cisco Unity enable users to effectively manage communications messages (view, play back, sort, and delete) from within the Cisco Unified Personal Communicator application.

• Web conferencing servers:

– Cisco Unified MeetingPlace Express provides access to a private, reservationless, web conferencing sessions for users who are in a Cisco Unified Personal Communicator conversation. Users can start a web conferencing session at any time to share content, such as presentations, and to facilitate collaboration with others. Cisco Unified MeetingPlace Express does not reserve voice ports for web meetings initiated through Cisco Unified Personal Communicator.

– Cisco Unified MeetingPlace Express VT extends Cisco Unified Communications Manager video telephony capabilities. Users can add video to existing voice communication, move from point-to-point to multiparty voice and video calls, and can add web conferencing to their voice and video communications.

– Cisco Unified MeetingPlace provides a more extensive feature set (such as scheduled and reservationless rich-media conferencing) and allows more concurrent users than Cisco Unified MeetingPlace Express. With this product, a Cisco Unified Personal Communicator user can start a web conferencing session or a video conferencing session.

• Cisco Unified Videoconferencing and Cisco Unified MeetingPlace Express VT provide audio and video support for merged conference calls (three or more parties) placed through Cisco Unified Personal Communicator.

For information about supported releases for the applications and servers that interact with Cisco Unified Personal Communicator, see the release notes:


1-2Installation and Configuration Guide for Cisco Unified Personal Communicator Release 7.0



Figure 1-1 Cisco Unified Personal Communicator Interactions with Network Servers

• How Cisco Unified Personal Communicator Interacts With Servers at Startup, page 1-3

• Chapter 2, “Configuring Required Servers for Cisco Unified Personal Communicator”

How Cisco Unified Personal Communicator Interacts With Servers at Startup When Cisco Unified Personal Communicator starts, the application performs the following operations:

1. It makes a secure (encrypted) connection to Cisco Unified Presence and downloads the contact list, network settings, user settings, and portable user preferences for each user.

2. Once the user logs in to the Cisco Unified Presence home node, Cisco Unified Personal Communicator uses the TFTP server address retrieved from Cisco Unified Presence to download the UPCusername.cnf.xml configuration file from Cisco Unified Communications Manager. For details about the configuration file, see the “Specifying TFTP Server Addresses” section on page 2-20.

3. The application registers to receive presence information from Cisco Unified Presence. After it is registered, the application subscribes to receive live presence information for each user in the contact list.

SIMPLE andSOAP/HTTP(S)

27

08

94

IP

Cisco UnifiedCommunications Manager

M

M

M

M

M

LDAP

SIPandCTI

IMAP

Cisco UnifiedPersonal

Communicator

Microsoft Outlookclick-to-dial plug in

Cisco UnifiedPresence

Cisco Unity orCisco Unity Connection

LDAPDirectoryServer

Cisco UnifiedVideoconferencing

Cisco UnifiedMeetingPlace or

Cisco UnifiedMeetingPlace Express

HTTP(S)

SCCPSCCPor SIP

MicrosoftExchange

WebDAV

MicrosoftLCS/OCS

InterdomainFederations



4. If soft-phone mode is enabled for the user, the application starts the soft-phone module and registers with Cisco Unified Communications Manager for call processing.

If configured, Cisco Unified Personal Communicator establishes a connection with Cisco Unified Communications Manager for desk-phone control. Otherwise, if phone-association mode is enabled for the user through the extension mobility feature in Cisco Unified Communications Manager and if the user did not specify a preferred device in Cisco Unified Personal Communicator, Cisco Unified Personal Communicator chooses the first CTI-enabled phone that is associated to the user in Cisco Unified Communications Manager.

5. The application connects to the voice-mail server (if deployed), provides the credentials for the user, and retrieves the headers of any currently stored voice-mail messages. Cisco Unified Personal Communicator stores the call history locally and records missed calls only if it is running.

6. The application attempts to look up directory information for call records, contact information for each contact in the contact list, and for the voice-mail messages that have been retrieved. The application presents the directory results to the user in the Recent pane.

7. When all directory searches are complete, the application stores the contact information for presence and voice mail in memory.

Related Topics

• Network Settings That Are Retrieved from Servers, page 1-4

• User Settings That Are Retrieved from Servers, page 1-5

• Portable User Preferences That Are Stored on Cisco Unified Presence, page 1-5

Network Settings That Are Retrieved from ServersYou must configure network settings so that users can access network resources. You configure the network settings in Cisco Unified Presence Administration unless noted otherwise. Cisco Unified Personal Communicator retrieves the following settings:

• List of servers (Cisco Unified Communications Manager, LDAP, voice-mail servers, and web conferencing servers) and their addresses, ports, and transport types

• LDAP schema mapping (data definition for the directory)

• LDAP user common name (cn) attribute (for limiting the LDAP search to names)

• LDAP search base (the location where all LDAP users exist) and recursive search flag (specifies whether to perform a recursive search of the directory starting at the search base)

• Bind anonymously to LDAP (specifies whether to use the credentials of the user to log in to this LDAP server or to use an anonymous login for read-only access)

• Presence domain name (used for SIP registration in the form of user@domainname)

• Application dialing rules and directory lookup dialing rules (configured through the Cisco Unified Communications Manager Administration)

• Voice-mail pilot number (redirects an incoming call to voice mail)

These settings are read only; Cisco Unified Personal Communicator cannot modify them and write them to the server.



Related Topics





User Settings That Are Retrieved from ServersYou configure certain settings specific to each user in Cisco Unified Presence Administration and in Cisco Unified Communications Manager Administration. Similar to the network settings, the application retrieves the user settings from the server, but it can neither modify the configuration nor write it to the server.

The application retrieves the following user settings:

• The phone line or number to control when the application operates in CTI mode

• Licensing information, including what capabilities are enabled

Related Topics




Portable User Preferences That Are Stored on Cisco Unified PresenceThe application stores portable user-preference information on Cisco Unified Presence so that the user can log in from any computer and retain various application settings. The application writes preference information to, and retrieves preference information from, the server. This preference information includes:

• The LDAP directory username and password (required only if non-anonymous bind is configured in Cisco Unified Presence Administration)

• Cisco Unified Presence digest password (not visible in the web administration but it is synchronized from Cisco Unified Communications Manager user configuration)

• Username and password for voice-mail server access

• Username and password for conferencing server access

• User preference information configured through the Preferences window in Cisco Unified Personal Communicator

The contact list is stored on and downloaded from Cisco Unified Presence. The recent communication records (missed, received, and sent calls, but not voice mail) are stored on the file system of the client computer and are not stored on Cisco Unified Presence.


Chapter 1 Planning to Install Cisco Unified Personal CommunicatorGathering Information to Configure Servers

Preference information is stored at this location:

• For Windows XP: drive:\Documents and Settings\username\Application Data\Cisco\Unified Personal Communicator

• For Windows Vista: drive:\Users\username\AppData\Local\Cisco\Unified Personal Communicator

where drive is the local hard drive and username is the login name of the logged in user.

All data in the Application Data directory is designed to follow the user around if you configure the Windows Roaming Profile option for the user. If the Windows user profile type is roaming, these settings will apply whenever the user logs in under the same Windows account on any other computer. For details about roaming profiles, see the Microsoft website.

Preference information for Mac OS systems is stored at this location, where ~ is the home folder for the user:

• ~/Library/Preferences/Cisco/UnifiedPersonalCommunicator/

• ~/Library/Preferences/com.cisco.CiscoUPC.plist

Related Topics




Gathering Information to Configure ServersThe table lists the information you need to gather to complete the server configuration tasks.

Procedure

Task Where needed...

Information Needed for Cisco Unified Communications Manager Configuration

Whether the plus character in dialed numbers is enabled or supported in your Cisco Unified Communications Manager installation

Application Dialing Rule Changes Required for Plus Dialing, page 1-10

Cisco Unified IP Phone MAC address for each user Adding Desk Phones to the Cisco Unified Communications Manager Database, page 2-1

Directory numbers for each user Adding Desk Phones to the Cisco Unified Communications Manager Database, page 2-1

Cisco Unified Communications Manager usernames Adding Cisco Unified Personal Communicator as a Phone Type, page 2-5

Cisco Unified Communications Manager MAC address How to Configure Licensing in Cisco Unified Communications Manager, page 2-13

Cisco Unified Videoconferencing MCU MAC address Configuring Videoconferencing Resources, page 3-19

Information needed for Cisco Unified Presence Configuration

TFTP server (primary and backup) addresses How to Select the Proxy Listener, page 2-18

LDAP attribute mapping schema Configuring the LDAP Attribute Map, page 2-22

LDAP server addresses Specifying LDAP Server Names and Addresses, page 2-24


Chapter 1 Planning to Install Cisco Unified Personal CommunicatorInstalling Servers

Related Topics

• Installing Servers, page 1-7


• Chapter 3, “Configuring Recommended Servers for Cisco Unified Personal Communicator”

Installing ServersThis section 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 usernames and passwords. Although passwords do not need to match across all servers, it is 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 computer requirements that are described in the release notes:


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 Communications Manager.

Cisco Unified Communications Manager manages the Cisco Unified IP Phones associated with Cisco Unified Personal Communicator and routes and processes calls. Cisco Unified Communications Manager 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 Communications Manager System Guide and the instructions in the Cisco Unified Communications Manager Administration Guide (or in the Cisco Unified Communications Manager Administration online help).

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

LDAP server password Creating LDAP Profiles, page 2-26

Computer telephony interface (CTI) gateway server addresses

Specifying CTI Gateway Server Names and Addresses, page 2-29

Voice-mail server addresses (Cisco Unity Connection or Cisco Unity)

Specifying Voice-Mail Server Names and Addresses in Cisco Unified Presence Administration, page 3-6

Web conferencing server addresses (Cisco Unified MeetingPlace Express VT, Cisco Unified MeetingPlace Express, or Cisco Unified MeetingPlace)

Specifying Conferencing Server Names and Addresses in Cisco Unified Presence Administration, page 3-17

Task Where needed...





Step 3 Install and configure the 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 the contact list for a user.

You must configure Cisco Unified Presence to interact with the LDAP server.

Step 4 Install and configure Cisco Unified Presence.

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

See the Cisco Unified Presence installation and upgrade guide and the deployment guide:

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

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

Step 5 (Optional) For full functionality of Cisco Unified Personal Communicator, install and configure these products:

• Cisco Unity Connection or Cisco Unity to provide voice-mail retrieval and playback

– See the Cisco Unity Connection install and upgrade guides, and the maintain and operate guides:

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

– See the Cisco Unity install and upgrade guides, and the maintain and operate guides:

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

You must configure Cisco Unified Presence to interact with the voice-mail server.

• Cisco Unified MeetingPlace Express VT, Cisco Unified MeetingPlace Express, or Cisco Unified MeetingPlace to provide web conferencing or voice and video conferencing

– See the Cisco Unified MeetingPlace Express VT and the Cisco Unified MeetingPlace Express install and upgrade guides, and the maintain and operate guides:


– See the Cisco Unified MeetingPlace install and upgrade guides, and the maintain and operate guides:

http://www.cisco.com/en/US/products/sw/ps5664/ps5669/tsd_products_support_series_home.html

You must configure Cisco Unified Presence to interact with the web conferencing server.

• Microsoft Exchange Calendar server integration with Cisco Unified Presence to include the status of meetings from the Outlook calendar into Cisco Unified Personal Communicator user availability status.

You must integrate the Exchange server with Cisco Unified Presence so that Cisco Unified Personal Communicator users can import the status of meetings from their calendars into their availability status. This means that if a user has a meeting scheduled, the meeting status is used to update the availability of the Cisco Unified Personal Communicator user. When calendar integration is enabled, meetings scheduled in the Exchange calendar impact Cisco Unified Personal Communicator user availability in these ways:

– Scheduled meetings cause the availability status of the user to display as Busy for that time period.







http://www.cisco.com/en/US/products/sw/ps5664/ps5669/tsd_products_support_series_home.html


– Meetings marked as Out-of-the-Office cause the availability status to display as Away for that time period.

– Meetings marked as Free or Tentative cause the availability status to display as Free for that time period.

For details about how to integrate and configure Cisco Unified Presence with Microsoft Exchange Server, see the integration note:


• Microsoft Office Communications Server (OCS) or Microsoft Live Communications Server (LCS) integration with Cisco Unified Presence to provide inter-domain presence and instant messages exchange.

When you configure federations, Cisco Unified Presence users in one domain can interact with Microsoft Office Communicator (MOC) users and/or Cisco Unified Presence users in another domain to exchange presence and instant messages.

Inter-domain presence and instant messaging federations are supported in these configurations:

– Cisco Unified Personal Communicator to Cisco Unified Personal Communicator in different Cisco Unified Presence domains

Cisco Unified Personal Communicator is registered to one Cisco Unified Presence/Cisco Unified Communications Manager domain, and another Cisco Unified Personal Communicator is registered to another Cisco Unified Presence/Cisco Unified Communications Manager domain.

– Cisco Unified Personal Communicator to a deskphone controlled by MOC in different Cisco Unified Presence domains

Cisco Unified Personal Communicator is registered to one Cisco Unified Presence domain and a deskphone controlled by MOC is registered to another Cisco Unified Presence domain.

– Cisco Unified Personal Communicator to MOC device registered to OCS or LCS

Cisco Unified Personal Communicator is registered to one Cisco Unified Presence domain, and the MOC device is registered with OCS or LCS.

The result of the federation is that contact lists in Cisco Unified Personal Communicator will contain foreign and internal usernames.

Note Any external user who does not have a domain cannot be in a federated domain. There will be no presence available for this contact.

For details about how to integrate and configure Cisco Unified Presence with Microsoft OCS/LCS, see the integration note:


• 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:

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

You must configure Cisco Unified Communications Manager to interact with the MCU.





Chapter 1 Planning to Install Cisco Unified Personal CommunicatorApplication Dialing Rule Changes Required for Plus Dialing

Step 6 Configure the servers in this procedure for use with Cisco Unified Personal Communicator.

Related Topics

• Gathering Information to Configure Servers, page 1-6


• Chapter 3, “Configuring Recommended Servers for Cisco Unified Personal Communicator”

Application Dialing Rule Changes Required for Plus DialingThe E.164 standard defines an international numbering plan for public phone systems. In the E.164 standard, each number contains a country code, an area code, and a subscriber number. Each phone user has a globally unique number.

If a phone number has a plus character (“+”) at the start, the number is in E.164 format. Phone numbers in LDAP directories can have a plus character prefix. Typically, when you dial an international number, you replace the plus character with the correct international access code for the locale from which you make the call. For example, in the United States, you replace the plus character with 011, in France you replace the plus character with 00, and so on. However, some phone systems allow you to dial the plus character directly.

You can configure Cisco Unified Communications Manager Release 7.0 to support the plus character in dialed numbers. Cisco Unified Personal Communicator Release 7.0 does not remove the plus character from dialed numbers. Releases of Cisco Unified Personal Communicator earlier than Release 7.0 do remove the plus character from dialed numbers.

You might only need to configure application dialing rules for numbers that users enter manually, if all of the following conditions are true:

• Your system uses only Cisco Unified Communications Manager Release 7.0 and Cisco Unified Personal Communicator Release 7.0.

• You have configured translation patterns in Cisco Unified Communications Manager to accommodate numbers that begin with a plus character.

• Your LDAP directory contains phone numbers that are only in full E.164 format and begin with a plus character.

You must configure the application dialing rules in Cisco Unified Communications Manager to remove the plus character from dialed numbers, if both of the following conditions are true:

• Support for the plus character is not enabled or supported in your Cisco Unified Communications Manager installation.

• Your LDAP directory contains phone numbers formatted with the plus character.

You do not need to reconfigure the application dialing rules if you reconfigure Cisco Unified Communications Manager to process the plus character correctly. However, in this case you might need to reconfigure the application dialing rules to support both Cisco Unified Personal Communicator Release 7.0, and releases earlier than Release 7.0.



Example of Application Dialing Rule ChangesThe LDAP number of a user is +1 408 555 1212. Other users can dial this user at 85551212. Users within the same Cisco Unified Communications Manager cluster can dial the user at 51212. The following table shows sample application dialing rules for this scenario for Cisco Unified Personal Communicator Release 7.0, and for releases earlier than Release 7.0:

Release Application Dialing Rules

Earlier than 7.0

Outbound

Any one of the following rules is suitable:

numDigits 11 beginsWith 1408 remove 4 prefixWith 8

numDigits 11 beginsWith 1408 remove 3 prefixWith <nothing>

numDigits 11 beginsWith 1408555 remove 6 prefixWith <nothing>

Inbound


numDigits 8 beginsWith 8555 remove 1 prefixWith +1408


7.0 Outbound

Any one of the following pairs of rules is suitable. Each pair of rules supports both Cisco Unified Personal Communicator Release 7.0, and releases earlier than Release 7.0.

numDigits 11 beginsWith 1408 remove 4 prefixWith 8 numDigits 12 beginsWith +1408 remove 5 prefixWith 8

numDigits 11 beginsWith 1408 remove 3 prefixWith <nothing> numDigits 12 beginsWith +1408 remove 4 prefixWith <nothing>

numDigits 11 beginsWith 1408555 remove 6 prefixWith <nothing> numDigits 12 beginsWith +1408555 remove 7 prefixWith <nothing>

Inbound






C H A P T E R 2
Configuring Required Servers for Cisco Unified Personal Communicator
December 2008

• How to Configure Cisco Unified Communications Manager, page 2-1

• How to Configure Licensing in Cisco Unified Communications Manager, page 2-13

• Configuring the LDAP Server, page 2-16

• How to Configure Cisco Unified Presence, page 2-17

• Configuring Firewalls to Pass Cisco Unified Personal Communicator Traffic, page 2-34

• Configuring Users for Point-to-Point Video Calls and for Multipoint Videoconferencing, page 2-34

How to Configure Cisco Unified Communications Manager • Adding Desk Phones to the Cisco Unified Communications Manager Database, page 2-1

• Completing the Cisco Unified IP Phone Configuration, page 2-3

• Associating Cisco Unified IP Phones With Users and Adding Users to a Group, page 2-3

• Adding Cisco Unified Personal Communicator as a Phone Type, page 2-5

• Associating Lines, Users, and Directory Numbers, page 2-8

• Do Not Disturb Behavior in Cisco Unified Personal Communicator, page 2-8

• Configuring Extension Mobility, page 2-10

• How to Configure Dialing Rules, page 2-11

Adding Desk Phones to the Cisco Unified Communications Manager DatabaseYou can enable users to control their desk phones from Cisco Unified Personal Communicator. For each user, you can add a Cisco Unified IP Phone or another Cisco-supported phone supported for use with Cisco Unified Personal Communicator to the Cisco Unified Communications Manager database. You can then configure the phone.

Before You Begin

• Make sure you are using a supported Cisco Unified Communications Manager release. See the release notes:


Chapter 2 Configuring Required Servers for Cisco Unified Personal CommunicatorHow to Configure Cisco Unified Communications Manager


• Decide how you want to add phones to the Cisco Unified Communications Manager database:

– Automatically, through auto-registration

– Manually, through the Phone Configuration windows

For details, see the online help topic “Configuring Cisco Unified IP Phones” in Cisco Unified Communications Manager Administration.

• Make sure that you add one of the Cisco Unified IP Phone products. Alternatively, you can add another Cisco-supported phone. Make sure that you add a phone that is supported for use with Cisco Unified Personal Communicator. See the release notes:


Procedure

Step 1 Select Device > Phone.

Step 2 Add one of the Cisco Unified IP Phone products for the user. Alternatively, add another Cisco-supported phone for the user. Configure the phone for your environment.

Step 3 Configure the phone to interoperate with Cisco Unified Personal Communicator, as follows:

a. Allow control of the Cisco Unified IP Phone from the computer telephony interface (CTI).

b. Check Allow Control of Device from CTI.

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.

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

Note In the Directory Number Configuration window, in the Line Settings for All Devices section, you can configure the Hold Reversion Ring Duration and the Hold Reversion Notification Interval settings, but they are not functional for Cisco Unified Personal Communicator.

Troubleshooting Tips

For detailed instructions, use the Cisco Unified Communications Manager Administration online help or the Cisco Unified Communications Manager Administration Guide:


Related Topics

• Completing the Cisco Unified IP Phone Configuration, page 2-3









Completing the Cisco Unified IP Phone ConfigurationYou can configure a Cisco Unified IP Phone with optional features by following the tasks in the table. However, these configuration steps are not necessary to run Cisco Unified Personal Communicator.

For a list of supported Cisco Unified Personal Communicator features, see the data sheet:

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

Procedure

Associating Cisco Unified IP Phones With Users and Adding Users to a GroupAfter you add Cisco Unified IP Phones to the Cisco Unified Communications Manager database and configure them to be controlled from CTI, you must perform the following tasks:

• Modify user credentials (required if integrating with Cisco Unified Communications Manager Release 6.0 and later)

• Set up user accounts, and associate directory numbers (primary extensions) to users.

• Associate phones with users.

Task For details, see...1

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

Configure telephony features and settings, including DND2 or extension mobility for environments where users are not permanently assigned to physical phones3.

2. DND = Do Not Disturb

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

Cisco Unified Communications Manager Administration Guide

Cisco Unified Communications Manager Features and Services Guide

Do Not Disturb Behavior in Cisco Unified Personal Communicator, page 2-8

Configuring Extension Mobility, page 2-10

Modify phone button templates (softkeys). Cisco Unified Communications Manager Administration Guide

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


Cisco Unified Communications Manager Features and Services Guide

Set up directories for Quick Search and Dialing Rules features.


Add users to Cisco Unified Communications Manager, and associate users with device IDs for access to the User Options web pages.



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


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


• Add users to the CTI users group.

• Add users to a Cisco Unified Communications Manager user group.

Before You Begin

To avoid interoperability problems with Cisco Unified Personal Communicator, use care when you specify the usernames in the End User Configuration window. You must take care to create usernames that do not cause two users to have the same soft-phone device name. If Cisco Unified Personal Communicator cannot derive the soft-phone device name, the application does not properly register and function as expected. You convert the username into a soft-phone device name when you add Cisco Unified Personal Communicator as a phone type.

Procedure

Step 1 Select User Management > Credential Policy Default.

To modify user credentials, edit all entries (Application User Password, End User Password, and End User PIN):

a. Uncheck User Must Change at Next Login.

b. Check Does Not Expire.

c. Click Save.

Step 2 Select User Management > End User to provision users.

a. Click Add New to add a new user.

b. Enter information for this user in the End User Configuration window.

c. Enter values into the fields in the User Information section.

For details about these fields, see the online help topic “End User Configuration Settings” in Cisco Unified Communications Manager Administration.

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

e. Select the primary extension, or primary directory number, for this user from the drop-down list in the Directory Number Associations section.

f. Click Save.

Step 3 Click Device Association in the Device Associations section to associate a Cisco Unified IP Phone with this user.

a. Enter the MAC address of the phone for this user, prefixed with SEP, in the User Device Association window.

b. Click Find.

c. Select the phone for the user from the list.

d. Click Save.

e. Select the primary extension for the newly-associated phone.

f. Click Save.

Step 4 Select Device > Phone to associate the user with a line.

a. Click the phone to associate with the user.

b. Click the directory number link.



c. Click Associate End Users at the bottom of the Directory Number Configuration window.

d. Select the user to associate to this device.

e. Click Add Selected.

f. Click Save.

Step 5 Add the user to the CTI users group.

a. Select User Management > User Group.

b. Enter Standard CTI Enabled in the search field of the Find and List User Groups window.

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

c. Click Find.

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

e. Click Add End Users to Group.

f. Search for a user in the Find and List Users window.

g. Select the user.

h. Click Add Selected.

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

Step 7 Click Save.

Related Topics



Adding Cisco Unified Personal Communicator as a Phone TypeTo enable Cisco Unified Personal Communicator soft-phone features, you must manually create a new soft-phone device for each user.

Restrictions

• The auto-registration features in Cisco Unified Communications Manager are not supported for use with Cisco Unified Personal Communicator.

• With Cisco Unified Communications Manager Release 6.0(1) and later, you can associate a secondary soft-phone device with a primary device and consume only one device license per device (also known as secondary licensing or adjunct licensing). For releases prior to Cisco Unified Communications Manager Release 6.0(1), three device licenses are consumed.

• Adjunct licensing has these restrictions:

– You can associate up to two secondary soft-phone devices to a primary phone.

– You cannot delete the primary phone unless you remove the associated secondary soft-phone devices.

– The primary phone must be the device that consumes the most licenses. You cannot make the soft-phone device the primary phone and associate a Cisco Unified IP Phone as the secondary device.



– Secondary soft-phone devices are limited to Cisco IP Communicator, Cisco Unified Personal Communicator, and Cisco Unified Mobile Communicator.

Procedure

Step 1 Select Device > Phone.

Step 2 Click Add New in the Find and List Phones window.

Step 3 Select Cisco Unified Personal Communicator.

Step 4 Click Next.

Step 5 Specify the soft-phone device name in the Device Name field. The soft-phone device name must conform to the following guidelines:

– Derives from the username.

– Starts with UPC.

– Contains only uppercase letters, or numerals.

– Contains no more than 12 additional characters after UPC.

See Table 2-1 for examples.

Note As shown in Table 2-1, 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 do 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 cannot properly register and cannot function as expected. You might have to reconfigure a user to use a name other than their normal username to avoid this problem.

a. Enter a descriptive name for the phone in the Description field. For example, enter Richard–soft phone.

b. Configure all required fields for your environment.

c. Select the user ID from Owner User ID.

d. Select the device name of the Cisco Unified IP Phone to associate with Cisco Unified Personal Communicator from Primary Phone.

e. Uncheck Allow Control of Device from CTI to disable the ability of CTI to control and monitor this device.

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

Cisco Unified Communications Manager Username Associated Soft-Phone Device Name

jjackson UPCJJACKSON

johnnie_jackson UPCJOHNNIEJACKS

johnniejackson UPCJOHNNIEJACKS

john.jackson UPCJOHNJACKSON



Step 6 Enter information in the Protocol Specific Information section, as follows:

Step 7 Click Save.

Step 8 Verify that the status shown at the top of the page indicates a successful save.

Step 9 Click the Add a New DN link in the Association Information pane that displays on the left side of the window.

Step 10 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 in the Directory Number Information section.

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

Step 11 Enter the caller ID in Display (Internal Caller ID), in the Line 1 on Device Device-Name section.

Step 12 Enter information in the Multiple Call/Call Waiting Settings on Device section, as follows:

a. Enter 6 to specify the maximum number of calls that can be presented to Cisco Unified Personal Communicator in Maximum Number of Calls.

b. Specify the trigger after which an incoming call receives a busy signal in Busy Trigger.

This setting works with the Maximum Number of Calls setting. For example, if the maximum number of calls is set to 6 and the busy trigger is set to 6, incoming call 7 receives a busy signal.

Step 13 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 Communications Manager 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 running at the time of the modifications.

Related Topics


• Configuring Extension Mobility, page 2-10

• Licensing Options for Cisco Unified Personal Communicator, page 2-13

• Configuring Videoconferencing Resources, page 3-19

Field Setting

Presence Group Select Standard Presence Group.

Device Security Profile

Select Cisco Unified Personal Communicator - Standard SIP Non-Secure Profile.

This security profile is installed with Cisco Unified Communications Manager.

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.

Digest User Select the user ID. This is the same user ID as the one you selected for Owner User ID.



Associating Lines, Users, and Directory NumbersTo ensure that the availability status in Cisco Unified Personal Communicator is accurately displayed, you must make sure there is an association between the user and the line that is configured for the user in Cisco Unified Communications Manager, Release 6.x.

Procedure

Step 1 Select Device > Phone, and find the directory number.

Step 2 Click the link for the line in the Association Information section on the left side of the window.

Step 3 Scroll to the bottom of the page and make sure the user is associated with the line on the Directory Number Configuration window.

Step 4 Make sure you associate the line and user for all the phones used by the user for that directory number.

Note You can also associate lines, users, and directory numbers by using the Bulk Administration Tool (BAT).

Related Topics

• Adding Desk Phones to the Cisco Unified Communications Manager Database, page 2-1



Do Not Disturb Behavior in Cisco Unified Personal CommunicatorThe Do Not Disturb (DND) feature in Cisco Unified Personal Communicator is always available in the user interface and is supported in both soft-phone and desk-phone modes as described in Table 2-2.



Apart from Cisco Unified Personal Communicator, other devices might be associated with a particular user. For example, devices such as IP Phone Messenger or Cisco Unified IP Phone that are registered to Cisco Unified Communications Manager might be associated with a particular user.

Table 2-2 DND Behavior in Cisco Unified Personal Communicator

Configuration Behavior

Cisco Unified Personal Communicator in soft-phone mode and set to DND by the user

Rejects calls.

• User cannot answer incoming calls from Cisco Unified Personal Communicator.

• Incoming call notifications are not displayed.

• Incoming calls do not display in the Recent pane of Cisco Unified Personal Communicator.

• Unanswered calls are diverted to the call forward no answer (CFNA) target. The default setting for CFNA is voicemail in Cisco Unified Communications Manager.

If the CFNA target is not configured, incoming calls are rejected by Cisco Unified Communications Manager, and the caller hears a busy tone.

• (Shared line) If Cisco Unified Personal Communicator shares the line appearance with other devices, the endpoints that are not set to DND call reject are alerted to the incoming call, and the caller hears the ringing tone. If all endpoints sharing the line appearance are set to DND call reject, incoming calls are forwarded to the CFNA target.

Cisco Unified Personal Communicator in desk-phone mode with DND Call Reject configured in Cisco Unified Communications Manager

The DND behavior for Cisco Unified Personal Communicator is the same as the controlled Cisco Unified IP Phone:

• User cannot answer calls from either Cisco Unified Personal Communicator or from the desk phone.

• Incoming call notifications are not displayed.

• Incoming calls do not display in Recent pane of Cisco Unified Personal Communicator.

• (Shared line) If Cisco Unified Personal Communicator shares the line appearance with other devices, the endpoints that are not set to DND call reject are alerted to the incoming call, and the caller hears the ringing tone. If all endpoints sharing the line appearance are set to DND call reject, incoming calls are forwarded to the call forward busy (CFB) target.

Cisco Unified Personal Communicator in desk-phone mode with DND Ringer Off configured in Cisco Unified Communications Manager

The DND behavior for Cisco Unified Personal Communicator is the same as the controlled Cisco Unified IP Phone:

• User can answer incoming calls from Cisco Unified Personal Communicator or from the desk phone. In both cases, Cisco Unified Personal Communicator displays a call progress window with the connected call status.

• An incoming call notification displays without an audio alert on the Cisco Unified IP Phone under Cisco Unified Personal Communicator desk-phone control, and Cisco Unified Personal Communicator displays the incoming call notification. If the call is not answered, it is diverted to the CFNA target. If CFNA is not configured, the call is rejected, and the caller hears a busy tone.

• Incoming calls display in both Cisco Unified Personal Communicator and the desk phone communication histories.



If the DND status is set on other devices, Cisco Unified Personal Communicator displays the DND status. Similarly, Cisco Unified Presence passes the DND setting from Cisco Unified Personal Communicator to other devices associated with this Cisco Unified Personal Communicator user.

If a user clears the DND status, Cisco Unified Presence clears DND from all endpoints associated with this user even if the endpoint is shared by other users.

Related Topics

• For details about configuring the Cisco Unified IP Phone for DND, see the Cisco Unified Communications Manager Features and Services Guide:


• For details about which Cisco Unified IP Phone models support the DND feature, see the administration guide for the specific phone model:

http://www.cisco.com/en/US/products/hw/phones/ps379/prod_maintenance_guides_list.html

Configuring Extension MobilityUse the extension mobility feature to allow users to log in to and configure a Cisco Unified IP Phone as their own, on a temporary basis,. After a user logs in, the phone adopts the default device profile information for that user, 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, the directory numbers, services, speed dials, and other properties for that user display on that phone. But when user B uses the same desk at a different time, information for user B displays. The extension mobility feature dynamically configures a phone according to who is currently logged into the phone.

By using extension mobility, Cisco Unified Personal Communicator users can associate this application with one of several desk phones that have the same directory number on the primary line as their default desk phone in Cisco Unified Communications Manager Administration.

Procedure

Step 1 Select Device > Phone, and access the Directory Number Configuration window.

Step 2 Make sure to remove all devices from the phone association list (if any) of the user.

Step 3 Follow the Cisco Unified Communications Manager extension mobility configuration information in the Cisco Unified Communications Manager Features and Services Guide:


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

Step 5 When you add the Cisco Unified IP Phone to Cisco Unified Communications Manager (Device > Phone), make sure that is controllable by CTI.

Related Topics

• Adding Desk Phones to the Cisco Unified Communications Manager Database, page 2-1



http://www.cisco.com/en/US/products/hw/phones/ps379/prod_maintenance_guides_list.html



How to Configure Dialing Rules • Application Dialing and Directory Lookup Rules, page 2-11

• How Cisco Unified Personal Communicator Transforms Dialed Numbers, page 2-11

• Configuring Application Dialing Rules, page 2-12

• Configuring Directory Lookup Rules, page 2-12

Application Dialing and Directory Lookup Rules

Based on the dial plan for your company and the information stored in the LDAP directory (telephone number for the user), you might need to define application dialing rules and directory lookup rules through the Cisco Unified Communications Manager routing information administration pages. Cisco Unified Presence queries Cisco Unified Communications Manager 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.

You can configure Cisco Unified Communications Manager Release 7.0 to support the plus character in dialed numbers. Cisco Unified Personal Communicator Release 7.0 does not remove the plus character from dialed numbers. Releases of Cisco Unified Personal Communicator earlier than Release 7.0 do remove the plus character from dialed numbers.

You might need to configure the application dialing rules in Cisco Unified Communications Manager to remove the plus character from dialed numbers, in particular circumstances.

Related Topics

• Application Dialing Rule Changes Required for Plus Dialing, page 1-10




How Cisco Unified Personal Communicator Transforms Dialed Numbers

Before Cisco Unified Personal Communicator places a call through contact information, the application removes everything from the phone number to be dialed, except for letters and digits. The application transforms the letters to digits and applies the dialing rules from Cisco Unified Presence. 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 the numbers. If there is a problem with the dialed number because of mistransformations, you must correct the dialing rules.

For detailed conceptual and task-based information on dialing rules, see the Cisco Unified Communications Manager Administration online help or the Cisco Unified Communications Manager Administration Guide:





Related Topics

• Application Dialing and Directory Lookup Rules, page 2-11



Configuring Application Dialing Rules

Application dial rules automatically strip numbers from, or add numbers to, phone numbers that the user dials. For example, you can configure a dialing rule in Cisco Unified Communications Manager Administration that automatically adds the digit 9 at the start of a 7-digit phone number to provide access to an outside line. Application dialing rules are used to manipulate numbers that are dialed from Cisco Unified Personal Communicator.

Procedure

Step 1 Select Call Routing > Dial Rules > Application Dial Rules.

Step 2 Configure the dialing rules by following the online help for this page or see the Cisco Unified Communications Manager Administration Guide:


Related Topics




Configuring Directory Lookup Rules

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 initial digits and the length of the number. For example, you can create a directory lookup rule in Cisco Unified Communications Manager Administration that automatically removes the area code and two prefix digits from a 10-digit telephone. This rule transforms 4089023139 into 23139.

Procedure

Step 1 Select Call Routing > Dial Rules > Directory Lookup Dial Rules.

Step 2 Configure the rules by following the online help for this page or see the Cisco Unified Communications Manager Administration Guide:


Related Topics






Chapter 2 Configuring Required Servers for Cisco Unified Personal CommunicatorHow to Configure Licensing in Cisco Unified Communications Manager


How to Configure Licensing in Cisco Unified Communications Manager

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

• Licensing Options for Cisco Unified Personal Communicator, page 2-13

• Obtaining a License File, page 2-14

• Uploading a License File, page 2-14

• Assigning Capabilities to Users, page 2-15

• Viewing Licensing Information, page 2-16

Licensing Options for Cisco Unified Personal CommunicatorCisco Unified Communications Manager 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 contact list, directory searching, instant messaging, and the ability to control a Cisco Unified IP Phone for click-to-dial and incoming call notification through desk-phone mode in Cisco Unified Personal Communicator. Users can also use web conferencing and voice-mail features if they are licensed for these products. For a list of supported servers, see the release notes:


These licenses are required:

– One Cisco Unified Personal Communicator software license. The Cisco Unified Personal Communicator license comes with one Cisco Unified Communications Manager device user license.

– One Cisco Unified Presence user feature license. This license is also known as a Cisco Unified Communications Manager phone device license.

• Base functionality and soft phone—In addition to the base capabilities, you can configure Cisco Unified Personal Communicator as a video-enabled soft phone to allow the user to use Cisco Unified Personal Communicator in soft-phone mode.

These licenses are required:

– One Cisco Unified Personal Communicator software license. The Cisco Unified Personal Communicator license comes with one Cisco Unified Communications Manager device user license.

– One Cisco Unified Presence user feature license. This license is also known as a Cisco Unified Communications Manager phone device license.




– Three Cisco Unified Communications Manager phone device licenses to register as a Cisco Unified Communications Manager soft phone.

Note In Cisco Unified Communications Manager Release 6.0(1), you can associate a secondary device with a primary device and consume only one device license per device. This is also known as adjunct licensing. You can configure adjunct licensing manually through the Phone Configuration window, through AXL, or through the BAT.

Related Topics




Obtaining a License FileWhen 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.

Before You Begin

• Obtain the MAC address of Cisco Unified Communications Manager for which you are requesting the licenses and a valid e-mail ID.

• Decide the number of device licenses that you need. You can use the license unit calculator in Cisco Unified Communications Manager Administration. Select System > Licensing > License Unit Calculator.

Procedure

Step 1 Obtain the license files for Cisco Unified Personal Communicator. Follow the instructions in the Cisco Unified Communications Manager Administration online help or the Cisco Unified Communications Manager Administration Guide:


Step 2 Enter the MAC address of Cisco Unified Communications Manager for which you want the licenses.

Step 3 Enter a valid e-mail address to which you want the license file document sent.

Step 4 Enter the number of nodes and devices for which you want licenses.

Step 5 Assign capabilities to users after the license is uploaded.

Related Topics


Uploading a License FileAfter you obtain the license file, you must copy it to your local computer and then upload it to the server.




Procedure

Step 1 Upload the Cisco Unified Personal Communicator license file to Cisco Unified Communications Manager Administration (System > Licensing > License File Upload).

Step 2 Follow the instructions in the Cisco Unified Communications Manager Administration online help or the Cisco Unified Communications Manager Administration Guide:



License files must have a .lic suffix.

Related Topics

• Assigning Capabilities to Users, page 2-15

Assigning Capabilities to UsersAfter the Cisco Unified Personal Communicator license files are uploaded, you must assign the capabilities to existing users in the Cisco Unified Communications Manager database. Use the first procedure to assign capabilities to a single user. Use the second procedure to assign capabilities to multiple users.

Before You Begin

You must upload the license file before you can assign capabilities to users.

Procedure

Step 1 Select System > Licensing > Capabilities Assignment.

Step 2 Click Find in the Find and List Capabilities Assignments window to display a list of all users.

Step 3 Click the link for the user in the search results section to display the Capabilities Assignment Configuration window.

Alternatively, select multiple users and click Bulk Assignment.

Step 4 Check Enable CUP to enable the user to log in to Cisco Unified Presence. This consumes one device license.

Step 5 Check Enable CUPC to enable Cisco Unified Personal Communicator to obtain presence information for the contact list from Cisco Unified Presence. This consumes one device license.

If you added Cisco Unified Personal Communicator as a phone type, three device licenses are consumed for each user for soft-phone capabilities.

Step 6 Click Save.

Related Topics





Chapter 2 Configuring Required Servers for Cisco Unified Personal CommunicatorConfiguring the LDAP Server

• Viewing Licensing Information, page 2-16

Viewing Licensing Information

Procedure

Related Topics



Configuring the LDAP ServerThe LDAP directory interacts with Cisco Unified Personal Communicator to provide contact information through directory searches.

Before You Begin

• Purchase a supported LDAP directory server. For information about supported LDAP directory servers, see the release notes:


• Make sure the LDAP server is installed before you attempt LDAP-specific configuration in Cisco Unified Presence Administration.

If You Want To... Then...

Display the license report. In Cisco Unified Communications Manager Administration, select System > Licensing > License Unit Report.

The report lists the number of authorized, used, and remaining licenses.

Determine the number of license units that are required for Cisco Unified Personal Communicator.

In Cisco Unified Communications Manager Administration, select System > Licensing > License Unit Calculator.

Obtain system information. In Cisco Unified Presence Administration, select this menu:

• Release 7.0: Diagnostics > System Status

• Release 6.x: System > Status

The status window provides the following information:

• Number of licensed Cisco Unified Presence and Cisco Unified Personal Communicator users synchronized from the Cisco Unified Communications Manager database.

• User IDs and the primary extension, number of devices, and the number of contacts associated with users.

• Which users are licensed to use Cisco Unified Personal Communicator.



Chapter 2 Configuring Required Servers for Cisco Unified Personal CommunicatorHow to Configure Cisco Unified Presence

Procedure

Step 1 Install the server and software according to the instructions from the manufacturer.

Step 2 Perform the LDAP-specific configuration in Cisco Unified Presence Administration.

Related Topics

• How to Configure LDAP Settings, page 2-22

How to Configure Cisco Unified Presence • Configuring Nodes, page 2-17

• How to Select the Proxy Listener, page 2-18

• Specifying TFTP Server Addresses, page 2-20

• How to Configure LDAP Settings, page 2-22

• How to Configure CTI Gateway Settings, page 2-28

• How to Change Application Profiles, page 2-31

• Disabling Instant Messaging Globally, page 2-33

• Configuring the Maximum Contact List Size, page 2-33

Note For information about configuring Cisco Unified Presence for voice-mail and web-conferencing functionality, see Chapter 3, “Configuring Recommended Servers for Cisco Unified Personal Communicator.”

Configuring NodesCisco Unified Presence servers scale beyond the two-node cluster limit in previous releases and provide presence services for all users within a single Cisco Unified Presence cluster. If you use nodes, you can use the following functionality:

• Automatic failover from the primary to the secondary node—If Cisco Unified Personal Communicator cannot reach the primary node for the user, the client software automatically uses the secondary Cisco Unified Presence server as the failover node.

• Automatic redirect if the user tries to log in to a nonhome node—If a Cisco Unified Personal Communicator user tries to log in to a nonhome node, the Cisco Unified Presence nonhome node sends a redirect response that includes the correct home-node address. Cisco Unified Personal Communicator automatically logs in to the primary node for the user.

• Rehome a user to a different subcluster while the user is offline. Cisco Unified Personal Communicator switches to the new node in the home subcluster without user intervention.

• Rehome a user that is logged in. Cisco Unified Personal Communicator registers, publishes, and subscribes to the new home subcluster. During the transition, instant message capability, user status, and contact list status might be temporarily unavailable.



Procedure

Step 1 Create a subcluster and associate a primary and secondary node to that subcluster in Cisco Unified Presence Administration (System > Topology).

For details about installing the first and secondary nodes, see the Cisco Unified Presence installation and upgrade guide:


Step 2 Assign each Cisco Unified Personal Communicator user to a node in the subcluster as the home or primary node for the user. The other node in the subcluster becomes the failover node for redundancy. This subcluster pairing provides load sharing/balancing and redundancy for the partition.

For details about completing the node and system topology configuration, see the Cisco Unified Presence configuration and maintenance guide:

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

How to Select the Proxy Listener Cisco Unified Personal Communicator sends SIP messages to, and receives SIP messages from, a proxy server, which communicates with Cisco Unified Communications Manager or other servers.

There are two different procedures depending on which release of Cisco Unified Presence you are using:

• Selecting the Proxy Listener in Release 7.0, page 2-18

• Selecting the Proxy Listener and Creating Proxy Profiles in Release 6.x, page 2-19

Selecting the Proxy Listener in Release 7.0

You must select a SIP proxy listener in Cisco Unified Presence Administration, Release 7.0.

Procedure

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

Step 2 Select Default Cisco SIP Proxy TCP Listener for Proxy Listener.

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

Note Do not select Default Cisco SIP Proxy UDP Listener because availability information for contacts in the Cisco Unified Personal Communicator contact list might not be available for large contact lists. Also, availability information might not be available when connected through a moderately lossy networks such as VPN over the Internet.

Step 3 Click Save.





Step 4 Make sure that all availability-related messages between Cisco Unified Personal Communicator and Cisco Unified Presence use TCP.

a. Select System > Service Parameters.

b. Select a Cisco Unified Presence server from Server.

c. Select Cisco UP SIP Proxy as the service on the Service Parameter Configuration window.

d. Set Use Transport in Record-Route Header to On in the SIP Parameters (Clusterwide) section.

This forces the Proxy to use the transport parameter in the record-route header.

e. Click Save.

Related Topics


Selecting the Proxy Listener and Creating Proxy Profiles in Release 6.x

Before You Begin

• You must create the SIP proxy server profile in Cisco Unified Presence Administration Release 6.x, before you can add Cisco Unified Personal Communicator licensed users to the application profile. You create the SIP proxy server profile when you change an application profile for a single user.

• Make sure you configure the SIP proxy server address during the Cisco Unified Presence installation from the System > Server menu. You need this address for this procedure.

Procedure

Step 1 Select Application > Cisco Unified Personal Communicator > Proxy Profile.

Step 2 Click Add New in the Find and List window to add a new profile.

Step 3 Enter information into the fields.

Field Setting

Name Enter the server name.

Description (Optional) Enter a profile description.

Proxy Listener Select Default Cisco SIP Proxy TCP Listener.

Note Do not select Default Cisco SIP Proxy UDP Listener because availability information for contacts in the Cisco Unified Personal Communicator contact list might not be available for large contact lists. Also, availability information might not be available when connected through a moderately lossy networks such as VPN over the Internet.

Primary Proxy Server

Select a primary server.



Step 4 Click Save.

Step 5 Make sure that all availability-related messages between Cisco Unified Personal Communicator and Cisco Unified Presence use TCP.


b. Select a Cisco Unified Presence server from Server.

c. Select Cisco UP Presence Engine from Service.

d. Specify the string to insert into the Contact header field of the SIP message in Enterprise Presence Server Contact Name, in the Presence Engine Configuration section.

Use this format: ipaddress:port;transport=tcp.

e. Click Save.

f. Select Cisco UP SIP Proxy from Service.

g. Set Use Transport in Record-Route Header to On in the SIP Parameters (Clusterwide) section.

This forces the Proxy to use the transport parameter in the record-route header.

h. Click Save.

Related Topics



• Changing Application Profiles for a Single User, page 2-32

Specifying TFTP Server Addresses You must specify TFTP server addresses in Cisco Unified Presence Administration. Cisco Unified Personal Communicator connects to the primary TFTP server (whose address is retrieved from Cisco Unified Presence) at startup, for suspend and resume operations, and for the re-establishment of dropped network connections. When the connection is established, Cisco Unified Personal Communicator downloads the UPCusername.cnf.xml configuration file from Cisco Unified Communications Manager for each user.

The configuration file contains the list of Cisco Unified Communications Manager primary and failover server addresses and the transport protocol for Cisco Unified Personal Communicator to use in soft-phone mode to connect to Cisco Unified Communications Manager.

After the file is successfully downloaded, the configuration information is made available to other Cisco Unified Personal Communicator subsystems, and Cisco Unified Personal Communicator disconnects from the TFTP server.

Backup Proxy Server

(Optional) Do not select anything; redundant SIP proxy servers are not supported in Cisco Unified Personal Communicator.

Add Users to Profile Click this button, then use the Find and List Users window to find and select users. Click Add Selected to add users to the profile.

Field Setting



Each time Cisco Unified Personal Communicator tries to download the configuration file, the application attempts to contact the primary TFTP server. If the primary TFTP server does not respond, Cisco Unified Personal Communicator fails over to the backup TFTP servers, if any exist. Cisco Unified Personal Communicator fails over to the backup TFTP servers in the order specified in Cisco Unified Presence Administration,.

If all TFTP server connections fail, Cisco Unified Personal Communicator tries to load the last valid downloaded configuration from the following locations:

• For Windows XP: drive:\Documents and Settings\username\Application Data\Cisco\Unified Personal Communicator

• For Windows Vista: drive:\Users\username\AppData\Local\Cisco\Unified Personal Communicator

• For Mac OS: ~/Library/Preferences/Cisco/UnifiedPersonalCommunicator/

If the loading of the local file is successful, Cisco Unified Personal Communicator updates the Server Health window with a warning notification (yellow indicator). If the file transfer fails and the file does not exist, Cisco Unified Personal Communicator updates the Server Health window with a failure notification and switches to Disabled mode.

Before You Begin

• Make sure that you are using a supported Cisco Unified Presence release. See the release notes:


• Obtain the hostnames or IP addresses of the TFTP servers.

Restrictions

The following Cisco Unified Communications Manager failover restrictions apply to Cisco Unified Personal Communicator:

• Auto-registration is not supported.

• Cisco Unified Personal Communicator fails over to a configured TFTP server when it tries to download the configuration file. The application also tries to download the file from the backup TFTP servers.

• AutoUpdate and upgrades through TFTP are not supported for Cisco Unified Personal Communicator software.

Procedure


Step 2 Assign the primary (required) and backup (optional) TFTP server addresses in the fields provided. You can enter an IP address or a fully-qualified domain name.

Step 3 Click Save.

Troubleshooting Tip

You can see the TFTP server addresses in the server health window in Cisco Unified Personal Communicator (Help > Show Server Health on Windows and Help > Show System Diagnostics on Mac OS).




How to Configure LDAP Settings • Configuring the LDAP Attribute Map, page 2-22

• Rules for a Displayed Contact Name, page 2-23

• Fetching Contact Pictures from a Web Server, page 2-23

• Specifying LDAP Server Names and Addresses, page 2-24

• Creating LDAP Profiles, page 2-26

Configuring the LDAP Attribute Map

You must configure the LDAP attribute map through in Cisco Unified Presence Administration. You enter LDAP attributes for your environment and map them to the given Cisco Unified Personal Communicator attributes.

Before You Begin

• Make sure you install and set up the LDAP server before configuring the LDAP attribute map in Cisco Unified Presence Administration.

• 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.

Restrictions

• The UPC UserID setting in the LDAP attribute map must match the Cisco Unified Communications Manager 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 Communications Manager and Cisco Unified Presence.

• You can pair an LDAP field to only one Cisco Unified Personal Communicator field.

Procedure


Step 2 Select a supported LDAP server from Directory Server Type. The LDAP server populates the LDAP attribute map with Cisco Unified Personal Communicator user fields and LDAP user fields.

Step 3 If necessary, make modifications to the LDAP field to match your specific LDAP directory. The values are global to all LDAP server hosts.

Step 4 If you are integrating with Microsoft Active Directory, set up the LDAP attribute map with the following mapping:

• LastName = SN

• UserID = sAMAccountName

Step 5 Click Save.




• If you want to stop using the current attribute mappings and use the factory default settings, click Restore Defaults.

• You can see the LDAP attribute mappings in the server health window in Cisco Unified Personal Communicator (Help > Show Server Health on Windows and Help > Show System Diagnostics on Mac OS).

• For information on faster LDAP searches, see the Cisco Unified Personal Communicator troubleshooting guide:

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

Related Topics

• Configuring the LDAP Server, page 2-16

• Configuring the LDAP Attribute Map, page 2-22

• Fetching Contact Pictures from a Web Server, page 2-23


Rules for a Displayed Contact Name

The following rules determine how names are displayed as contacts in Cisco Unified Personal Communicator:

• If the user edits a contact name in Cisco Unified Personal Communicator, display this name. This is the Nickname LDAP attribute in Cisco Unified Presence.

• If you configured an LDAP user field for DisplayName, display this name.

• If you configured an LDAP user field for Nickname, display this name with the last name.

• Otherwise, display the configured LDAP user fields for the first and last names in the Contact pane. If there is a first name but no last name, display the first name. If there is a last name but no first name, display the last name.

• If you do not configure LDAP user fields for the FirstName and LastName, display the LDAP UserID or the Cisco Unified Presence user ID in the Contact pane.

• If a user adds a non-LDAP contact, the contact details in Cisco Unified Personal Communicator allow the user to edit the Display As name, the first name, and the last name.

Related Topics



Fetching Contact Pictures from a Web Server

You can configure a parameterized URL in the Photo field in the LDAP attribute map in Cisco Unified Presence Administration so that Cisco Unified Personal Communicator can fetch pictures from a web server instead of from the LDAP server.

Before You Begin

• Use %%uid%% as the substitution string.




You can use any LDAP attribute whose query value contains a piece of data that uniquely identifies the photo of the user. For example:

– http://wwwin.cisco.com/photo/std/%%uid%%.jpg

– http://wwwin.cisco.com/photo/std/%%sAMAccountName%%.jpg (for ActiveDirectory)

• The double percent symbols are required, and they must enclose the name of the LDAP attribute to substitute.

Restrictions

• The URL length is limited to 50 characters in Cisco Unified Presence Administration. To work around this issue, obtain a shortened URL from http://tinyurl.com. For example, http://wwwin.cisco.com/dir/photo/std maps to http://tinyurl.com/2rwkf9. This saves 11 characters so that you can enter http://tinyurl.com/2rwkf9/%%sAMAccountName%% into Cisco Unified Presence Administration.

• This substitution technique works only if Cisco Unified Personal Communicator can use the results of the query and can insert it into the template specified above to construct a working URL that fetches a JPG photo. If the web server where photos are hosted in a company requires a POST (for example, the name of the user is not in the URL) or uses some other cookie name for the photo (for example, http://www..../1234.jpg) instead of the username, this technique does not work. Cisco Unified Personal Communicator does not support authentication for this query; the photo must be retrievable from the web server without credentials.

Procedure


Step 2 In the LDAP attribute map, configure a parameterized URL in the Photo field. Use %%uid%% as the substitution string.

Step 3 Click Save.

Cisco Unified Personal Communicator removes the percent symbols and replaces the parameter inside with the results of an LDAP query for the user whose photo is to be resolved.

For example, if a query result contains the attribute “uid” with a value of “johndoe,” then a template such as http://mycompany.com/photos/%%uid%%.jpg creates the URL http://mycompany.com/photos/johndoe.jpg. Cisco Unified Personal Communicator attempts to fetch the photo.

Related Topics



Specifying LDAP Server Names and Addresses

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

Before You Begin

Obtain the hostnames or IP addresses of the LDAP servers.


http://tinyurl.com


Restrictions

If you are specifying more than one LDAP server in Cisco Unified Presence Administration for failover support in Cisco Unified Personal Communicator, the servers must all be of the same type (all Microsoft Active Directory, all Netscape, or all Sun One Directory). The LDAP attribute schema must be the same on all servers.

Procedure

Step 1 Select Application > Cisco Unified Personal Communicator > LDAP Server.

Step 2 Click Add New in the Find and List window to add a new server.


Step 4 Click Save.


• If an application dial rule is configured, to make sure that a picture displays both when you place a call to a contact and in the contact details, create proper directory lookup dialing rules in Cisco Unified Communications Manager. When you add a contact in Cisco Unified Personal Communicator, the directory lookup returns a 10-digit number (for example, 1234567890). If the user places the call by dialing only four digits (for example, 7890), the picture does not display because 7890 is not a match for 1234567890. Create the following rules to fix this problem:

– Outbound rule to remove the area code. The picture displays in the contact details.

Field Setting


Description (Optional) Enter a server description.

Hostname/IP Address

Enter an IP address or a fully qualified domain name of the server.

Port Specify the port number used by the LDAP server. The default is 389.

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

If you are integrating with Microsoft Active Directory and if the server is Global Catalog, enter 3268 as the port number.

Note The jpegPhoto attribute is not available in Microsoft Active Directory Global Catalog server, and it is not indexed (http://msdn2.microsoft.com/en-us/library/ms676813.aspx). If your LDAP configuration uses Global Catalog port 3268, the jpegPhoto is not retrievable. Instead, change the configuration in Cisco Unified Presence Administration to TCP and port 389. The photo is retrieved when you log in to Cisco Unified Personal Communicator again.

Protocol Type Select TCP.

If you are integrating with Microsoft Active Directory and if the server is Global Catalog, select TCP.


http://msdn2.microsoft.com/en-us/library/ms676813.aspx


– Inbound rule for directory lookup to prefix the area code (translate the 4-digit extension number into the 10-digit DID number stored in AD). The picture displays when you place a call.

• You can see LDAP server information in the server health window in Cisco Unified Personal Communicator (Help > Show Server Health on Windows and Help > Show System Diagnostics on Mac OS).

Related Topics



Creating LDAP Profiles

You must create LDAP profiles in Cisco Unified Presence Administration to specify LDAP directory configuration settings and context information for searching the LDAP directory. In the profile, you can assign primary and backup servers for redundancy.

Cisco Unified Personal Communicator connects to an LDAP server on a per-search basis. If the connection to the primary server fails, Cisco Unified Personal Communicator tries the first backup LDAP server, and if it is not available, it then tries the second backup server. Cisco Unified Personal Communicator also periodically tries to return to the primary LDAP server. An LDAP query that is in process when the failover to a secondary server occurs is processed on the next available server.

Connection status information is updated in the server health window (Help > Show Server Health on Windows and Help > Show System Diagnostics on Mac OS). If Cisco Unified Personal Communicator cannot connect to any of the LDAP servers, it reports the failure in the System Diagnostics window.

Before You Begin

• You must first specify LDAP server names and addresses in Application > Cisco Unified Personal Communicator > LDAP Server before you can select them in this procedure.

• You must create the LDAP profile before you can add Cisco Unified Personal Communicator licensed users to the application profile. You create the LDAP profile when you change an application profile for a single user.

Procedure

Step 1 Select Application > Cisco Unified Personal Communicator > LDAP Profile.



Field Setting

Name Enter the profile name.

Description (Optional) Enter a description.

Bind Distinguished Name

(Optional) Enter the administrator-level account information. This is the distinguished name with which you bind for authenticated bind. The following is an example bind distinguished name:

cn=administrator,cn=users,DC=cisco,DC=com

The syntax for this field depends on the type of LDAP server you deploy. For details, see the LDAP server documentation.



Anonymous Bind (Optional) Uncheck this option to use the user credentials to log in to this LDAP server.

For non-anonymous bind operations, Cisco Unified Personal Communicator receives one set of credentials. These credentials must be valid on the backup LDAP servers, if they are configured.

Note If you check Anonymous Bind, users can log in anonymously to the LDAP server with read-only access. Do not allow anonymous access on your directory server. Instead, create a user with read-only privileges on the same container where the users to be searched are located. Specify the directory number and password for Cisco Unified Personal Communicator to use in Cisco Unified Presence.

Password (Optional) Enter the LDAP bind password. This is the password for the administrator-level account that you provided in the Bind Distinguished Name string that allows users to access this LDAP server.

Confirm Password Enter the same password as the one entered in the Password field.

(Optional) After configuring Cisco Unified Presence for authenticated bind with the LDAP server, 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.

Search Context (Optional) Enter the location where all LDAP users are configured. This location is a container or directory. Only a single OU/LDAP search context is supported.

Note If integrating with Microsoft Active Directory, do the following:

• Set O and OU (OU must contain users; for example, ou=users,dc=cisco,dc=com).

For example, cn=users,DC=EFT-LA,DC=cisco,DC=com

• The searchbase must include all users of Cisco Unified Personal Communicator.

Recursive Search (Optional) Check to perform a recursive search of the directory starting at the searchbase.

Primary LDAP Server and Backup LDAP Server

Select the primary LDAP server and optional backup servers.

Make this the Default LDAP Profile for the System

(Not available in Release 6.x; optional) Check so that any new users who are added to the system are automatically placed into this default profile.

Users who are already synchronized with Cisco Unified Presence from Cisco Unified Communications Manager are not added to the default profile. However, once the default profile is created, any users synchronized after that are added to the default profile.


Field Setting



Step 4 Click Save.

Troubleshooting Tip

You can see the LDAP profile information in the server health window in Cisco Unified Personal Communicator (Help > Show Server Health on Windows and Help > Show System Diagnostics on Mac OS).

Related Topics



How to Configure CTI Gateway Settings • Desk-Phone Mode Failover and Recovery, page 2-28

• CTI Connection Failures and Recovery When No Calls Are Present, page 2-28

• CTI Connection Failures and Recovery When Calls Are Present, page 2-29

• Specifying CTI Gateway Server Names and Addresses, page 2-29

• Desk-Phone Mode Failover and Recovery, page 2-28



• Creating CTI Gateway Profiles, page 2-30

Desk-Phone Mode Failover and Recovery

If the CTI connection to Cisco Unified Communications Manager is lost while Cisco Unified Personal Communicator is operating in desk-phone mode, the application tries to re-establish the connection to the primary and then to the backup servers. Connection attempts continue on a round-robin basis, beginning again with the primary server. Successive attempts to reconnect to a server occur at intervals of 4, 8, 16, 32, and 60 seconds (maximum) until a connection is re-established.

Related Topics




CTI Connection Failures and Recovery When No Calls Are Present

When a CTI connection fails and no calls are present:

• Cisco Unified Personal Communicator attempts to reconnect to the next available CTI server.

• Until a connection is established, the Cisco Unified Personal Communicator user cannot initiate any new calls through the application. No new incoming call notifications are provided through the application.

• The user has manual control of the desk phone for making and receiving calls.



• When Cisco Unified Personal Communicator reconnects to one of the CTI servers, Cisco Unified Personal Communicator users again have the ability to control and monitor new calls through the application.

Related Topics



CTI Connection Failures and Recovery When Calls Are Present

When a CTI connection fails with one or more calls present:

• Cisco Unified Personal Communicator attempts to reconnect to the next available CTI server.

• Existing calls are unaffected, but the user no longer has control through Cisco Unified Personal Communicator and does not receive any updates or changes in the call state. Any existing Cisco Unified Personal Communicator session window closes.

• The user has manual control of the desk phone for making and receiving calls.

• When Cisco Unified Personal Communicator reconnects to one of the CTI servers, it opens a new session window for each call and shows the current state.

• Cisco Unified Personal Communicator remains connected to the current server (whether primary or backup) until the user restarts Cisco Unified Personal Communicator or when a connection failure causes it to reconnect.

Related Topics


Specifying CTI Gateway Server Names and Addresses

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

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

Before You Begin

• If you previously configured Cisco Unified Communications Manager with an IP address through the Cisco Unified Communications Manager Administration System > Server menu, Cisco Unified Presence dynamically creates a TCP-based CTI gateway host profile for that address. The fields in Cisco Unified Presence Administration (Application > Cisco Unified Personal Communicator > CTI Gateway Server) are automatically populated, and you do not need to perform this procedure.

• Obtain the hostnames or IP addresses of the CTI gateway.

Procedure

Step 1 Select Application > Cisco Unified Personal Communicator > CTI Gateway Server.





Step 4 Click Save.

Troubleshooting Tip

You can see the CTI gateway information in the server health window in Cisco Unified Personal Communicator (Help > Show Server Health on Windows and Help > Show System Diagnostics on Mac OS).

Related Topics


Creating CTI Gateway Profiles

You must create CTI gateway profiles in Cisco Unified Presence Administration and assign primary and backup servers for redundancy.

Before You Begin

• You must create the CTI gateway profile before you can add Cisco Unified Personal Communicator licensed users to the application profile.

• You must first specify CTI gateway server names and addresses in Application > Cisco Unified Personal Communicator > CTI Gateway Server before you can select them as primary or backup servers in this procedure.

• Cisco Unified Presence dynamically creates a TCP-based CTI gateway profile based on the hostname of Cisco Unified Communications Manager. Before using this profile, verify that Cisco Unified Presence and Cisco Unified Personal Communicator clients can ping Cisco Unified Communications Manager by the DNS name. If they cannot contact the server, you need to add the IP address of Cisco Unified Communications Manager in Cisco Unified Presence Administration (Application > Cisco Unified Personal Communicator > CTI Gateway Server). You do not need to delete the automatically-created host profiles.

• If you previously configured Cisco Unified Communications Manager with an IP address through the Cisco Unified Communications Manager Administration System > Server menu, Cisco Unified Presence dynamically creates a TCP-based CTI gateway profile based on that address. The fields in Cisco Unified Presence Administration (Application > Cisco 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).

Field Setting



Hostname/IP Address Enter an IP address or a fully qualified domain name of Cisco Unified Communications Manager that is running the CTI service.

Port Enter 2748.

Protocol Type Select TCP.



Procedure

Step 1 Select Application > Cisco Unified Personal Communicator > CTI Gateway Profile.



Step 4 Click Save.

Related Topics

• Desk-Phone Mode Failover and Recovery, page 2-28



• Specifying CTI Gateway Server Names and Addresses, page 2-29



How to Change Application ProfilesApplication profiles enable you to partition your Cisco Unified Personal Communicator user base for performance and scalability. You can change individual application profiles for each user.

Application profiles are not required; some Cisco Unified Personal Communicator users might not have a voice-mail or a conferencing profile. In this situation, the drop-down selection displays None.

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

• Selecting the Proxy Listener and Creating Proxy Profiles in Release 6.x, page 2-19


Field Setting



Primary CTI Gateway Server and Backup CTI Gateway Server

Select a primary server and backup servers.

Make this the Default CTI Gateway Profile for the System

(Not available in Release 6.x; optional) Check so that any new users that are added to the system are automatically placed into this default profile.

Users who are already synchronized to Cisco Unified Presence from Cisco Unified Communications Manager are not added to the default profile. However, once the default profile is created, any users synchronized after that are added to the default profile.





• Creating Voice-Mail Profiles in Cisco Unified Presence Administration, page 3-11

• Creating Conferencing Profiles in Cisco Unified Presence Administration, page 3-18

For information on how to change application profiles, see the following sections:


• Changing Application Profiles for Multiple Users, page 2-32

Changing Application Profiles for a Single User

Procedure

Step 1 Select Application > Cisco Unified Personal Communicator > User Settings.

Step 2 Click Find in the Find and List window to populate the search results fields, or search for the user, and then click Find.

Step 3 Click the link to select the user.

Step 4 (Release 6.x only; optional) Assign the preferred CTI device to the user from the drop-down list in the CTI Control Information section.

The preferred CTI device is the MAC address (in the form of SEPxxxxxxxxxxxx) of the primary desk phone that the user wants to control when in 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 Administration is used. If neither of these options are specified, Cisco Unified Personal Communicator chooses the first CTI-enabled phone that is associated with the user in Cisco Unified Communications Manager.

Step 5 Specify the profiles to change for the user in the Application Profile Configuration section.

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

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

Step 6 Click Save.

Changing Application Profiles for Multiple Users

Procedure

Step 1 Select the following menu in Cisco Unified Presence Administration:

Release 7.0: Bulk Administration > CUPC/MOC > Export

Release 6.x: Bulk Administration > Cisco Unified Presence > Export Cisco Unified Presence Users

Step 2 Click Find in the Export Users Query window to obtain current profile information by finding all users.

Step 3 Click Next at the bottom of the window.

Step 4 Specify the filename to be exported in the Export CUP Users Configuration window.



Step 5 Select Bulk Administration > Upload/Download Files.

Step 6 Find and select the file that you want to download.

Step 7 Click Download Selected.

Step 8 Add or remove profile names according to the instructions in the sample file.

Step 9 Select Bulk Administration > Upload/Download Files.

Step 10 Click Add New.


Step 12 Select Bulk Administration > CUPC/MOC > Update.

Step 13 Select the updated .csv file.

Step 14 Click Save to submit the file to update profile information in bulk.

Disabling Instant Messaging Globally You can disable instant messaging clusterwide in Cisco Unified Presence Administration. When instant messaging is disabled, the Send an Instant Message option is dimmed in Cisco Unified Personal Communicator.

Procedure


Release 7.0: Presence > Settings

Release 6.x: Cisco Unified Presence > Settings

Step 2 Deselect Enable Instant Messaging.

Step 3 Click Save.

Configuring the Maximum Contact List Size

Restriction

This configuration is not available in Cisco Unified Presence Release 6.x.

Field Setting

File Enter the name of the file to upload.

Select The Target Select the target for which you want to use the file.

Select Transaction Type Select the transaction type that the file defines.

Overwrite File if it exists Check this option if you want to overwrite an existing file with the same name.


Chapter 2 Configuring Required Servers for Cisco Unified Personal CommunicatorConfiguring Firewalls to Pass Cisco Unified Personal Communicator Traffic

Procedure

Step 1 Select Presence > Settings in Cisco Unified Presence Administration.

Step 2 Enter a number from 0 to 200 in Max Contact List Size.

This setting specifies the maximum number of contacts users can have for both Cisco Unified Personal Communicator and IP Phone Messenger.

Step 3 Click Save.

Configuring Firewalls to Pass Cisco Unified Personal Communicator Traffic

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.

Before You Begin

Read information about the network ports used by Cisco Unified Personal Communicator in the release notes:


Procedure

Step 1 Identify whether users have a software firewall installed on their computers, or if there is a hardware firewall in the network between Cisco Unified Presence and Cisco Unified Personal Communicator.

Step 2 Configure the firewall to pass Cisco Unified Personal Communicator traffic.

Failure to perform this step results in missing, incorrect, or intermittent display of availability status in Cisco Unified Personal Communicator.

Configuring Users for Point-to-Point Video Calls and for Multipoint Videoconferencing

Procedure

Step 1 (For point-to-point video calls) Configure users for soft-phone use.



Chapter 2 Configuring Required Servers for Cisco Unified Personal CommunicatorConfiguring Users for Point-to-Point Video Calls and for Multipoint Videoconferencing

Step 2 (For multipoint videoconferencing) If you want Cisco Unified Personal Communicator soft-phone users to have merged conference calls (three or more parties) with audio and video support, you must first configure videoconferencing resources.

Step 3 Distribute video telephony (VT) cameras supported for use with Cisco Unified Personal Communicator.

The camera driver installer is not provided with Cisco VT cameras. You must distribute the installer.

• For new installations:

– If users are to perform the installation, distribute the camera, the camera driver installer, and the user guide.

– If users already have a supported camera, do not distribute the driver.

• For details about supported cameras, see the release notes:


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

• User Guide for Cisco Unified Personal Communicator


• Cisco VT Camera Quick Start Guide (for use with Windows-based computers)

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

• iSight User Guide (for use with Mac OS X-based computers)

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

• Third-party USB video cameras—provide the documentation from the manufacturer

Related Topics



• Information to Provide to Users, page 4-7

• Deploying the Application and the Camera Drivers in a Microsoft Windows Environment, page 4-4





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

Chapter 2 Configuring Required Servers for Cisco Unified Personal CommunicatorConfiguring Users for Point-to-Point Video Calls and for Multipoint Videoconferencing



C H A P T E R 3
Configuring Recommended Servers for Cisco Unified Personal Communicator
December 2008

• How to Configure Voice-Mail Servers, page 3-1

• How to Configure Conferencing Servers, page 3-12


Note Make sure you first complete the tasks in Chapter 2, “Configuring Required Servers for Cisco Unified Personal Communicator.” After you complete the tasks in this chapter, Cisco Unified Personal Communicator has full feature support for voice mail, web conferencing, and videoconferencing.

How to Configure Voice-Mail Servers • Configuring Cisco Unity Connection Servers, page 3-2

• Configuring Cisco Unity Servers, page 3-4

• Specifying Voice-Mail Server Names and Addresses in Cisco Unified Presence Administration, page 3-6

• Configuring Secure Messaging in Cisco Unified Presence Administration, page 3-7

• Specifying Mailstore Server Names and Addresses in Cisco Unified Presence Administration, page 3-9



Chapter 3 Configuring Recommended Servers for Cisco Unified Personal CommunicatorHow to Configure Voice-Mail Servers

Configuring Cisco Unity Connection ServersCisco Unity Connection provides Cisco Unified Personal Communicator users with the ability to view, play, sort, and delete voice-mail messages from within the Cisco Unified Personal Communicator application.

Before You Begin

• Install and configure Cisco Unified Communications Manager. For details, see the installation and upgrade guides, and maintain and operate guides at the following URL:


• Install and configure a supported release of Cisco Unity Connection.

– For details about the server installation:


– For details about supported Cisco Unity Connection releases, see the Cisco Unified Personal Communicator release notes:


• Integrate Cisco Unified Communications Manager and Cisco Unity Connection. Both servers must be installed and running to configure voice-mail ports. For details about the voice-mail configuration, see the Cisco Unified Communications Manager Administration Guide:


Procedure

Step 1 Set up a new or existing class of service in Cisco Unity Connection Administration to enable Internet Mail Access Protocol (IMAP) client access to voice messages.

a. Expand Class of Service in the left pane.

b. Click Class of Service.

c. Click the display name of the applicable class of service in the Search Results table, in the Search Class of Service window.

d. Check Allow Users to Use Unified Client to Access Voice Mail for port 7993 and TLS, under Features.

e. For all other ports and protocols, perform the following steps:

– Check Allow Users to Access VoiceMail Using an IMAP Client under Licensed Features.

– Select Allow Users to Access Message Bodies.

– Check Allow Users to Use Unified Client to Access Voice Mail under Features.

f. Click Save.

Step 2 Configure the user:

• If the users are existing Cisco Unity Connection users, add them to the Cisco Unified Communications Manager database and to Cisco Unified Presence. Proceed to Step 4.

• If the user is a new Cisco Unified Personal Communicator user, add the user to Cisco Unified Communications Manager database, Cisco Unity Connection, and to Cisco Unified Presence.







See the administration guides for Cisco Unified Communications Manager and Cisco Unified Presence at the following URLs:

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

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

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

The user ID in Cisco Unity Connection does not need to match the user ID in Cisco Unified Presence or in Cisco Unified Personal Communicator. Cisco Unified Personal Communicator has an independent voicemail ID, which is set in the application Preference window.

For details about setting up the account, see the Cisco Unity Connection User Moves, Adds, and Changes Guide:


Step 4 (Optional) Enable secure messaging as follows:

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

b. Select an option from Require Secure Messaging in the Message Options section to enable secure messages.

Step 5 (Optional) Specify how to handle unidentified caller message security for your users as follows:

a. Expand Users in the left pane.

b. Click Users.

c. Click the alias of a user.

d. Select Edit > Message Settings.

e. Check Mark Secure in Unidentified Callers Message Security.

Step 6 If one does not already exist, specify a web application password in Cisco Unity Connection Administration for the applicable user accounts.

For details, see the Cisco Unity Connection User Moves, Adds, and Changes Guide:


Step 7 Perform the voice-mail configuration in Cisco Unified Presence Administration.


• Cisco Unified Personal Communicator users must enter their Cisco Unity Connection credentials, that is, their username and web application password, in the Cisco Unified Personal Communicator Preferences window.

• If the server can be contacted and the user credentials are correct, but voice-mail messages are not downloaded, do the following:

– Check the configuration of port 7993.

– Make sure Cisco Unified Personal Communicator is listening on port 7993.

– Check the firewall configuration. Use Telnet from a remote computer to the computer running Cisco Unified Personal Communicator, and make sure you can connect.

For details, see the Cisco Unified Personal Communicator troubleshooting guide at the following URL:









Related Topics




Configuring Cisco Unity ServersCisco Unity receives calls, plays greetings, and records and encodes voice mail. When a voice mail is received, Cisco Unity adds the .wav file to an e-mail and sends it to the configured e-mail account. Cisco Unity creates a subscriber mailbox on the Microsoft Exchange server for use as its mailstore server for message storage.

When Cisco Unified Personal Communicator users want to listen to their voice mails, they use Cisco Unified Personal Communicator to retrieve them from the mailstore server through IMAP.

Cisco Unified Personal Communicator supports both the Cisco Unity unified messaging and the Cisco Unity voice messaging configurations. With unified messaging, the Exchange server e-mail account supports both voice mail and e-mail. With voice messaging, the Exchange server e-mail account contains only voice-mail messages.

Before You Begin

• Install and configure Cisco Unified Communications Manager. For details, see the installation and upgrade guides, and maintain and operate guides at the following URL:


• Install and configure a supported release of Cisco Unity.

– For details about the server installation with Microsoft Exchange, see the following URL:


– For details about supported Cisco Unity releases, see the Cisco Unified Personal Communicator release notes at the following URL:


• Integrate Cisco Unified Communications Manager and Cisco Unity. Both servers must be installed and running to configure voice-mail ports. For details about the voice-mail configuration, see the Cisco Unified Communications Manager Administration Guide at the following URL:


• If you plan to use SSL to provide secure transmission with the mailstore server, you must set up Cisco Unity to use SSL during the installation or upgrade (or at any time after the installation or upgrade is complete). You must designate a server to act as your certificate authority, submit a certificate request, issue the certificate, and install it on the Cisco Unity server. For details, see the security guide:


Procedure

Step 1 Configure the Microsoft Exchange server to use the IMAP virtual server.








For Exchange 2003, perform the following steps:

a. Select Start > All Programs > Microsoft Exchange > System Manager.

b. In the left pane of the System Manager, expand Servers.

c. Select the server name.

d. Select Protocols > IMAP.

e. Right-click, and select Start Server.


a. Select Start > Run, enter services.msc, and click OK.

b. Select the Microsoft Exchange IMAP4 service, and click Start. This service is not started by default.

Step 2 Configure the port and encryption type.


a. Right-click IMAP Virtual Server, and select Properties.

b. Click Authentication from the Access tab.

– Verify that Requires SSL/TLS Encryption is not checked to use TCP and SSL connection.

– Verify that Requires SSL/TLS Encryption is checked to use SSL only.

c. Click OK.


a. Specify the authentication settings for the Client Access Server that is running the IMAP4 service through the Exchange Power Shell.

Select Start > Programs > Microsoft Exchange Server 2007 > Exchange Management Shell.

Exchange 2007 uses SSL by default.

b. Execute one of the following commands for the appropriate setting:

– For plain text login: set-imapsettings -LoginType PlainTextLogin

– For SSL: set-imapsettings -LoginType SecureLogin

Step 3 Configure the user:

• If the user is an existing Cisco Unity user, add the user to the Cisco Unified Communications Manager database and to Cisco Unified Presence.

• If the user is a new user, add the user to the Cisco Unified Communications Manager database, Cisco Unity (which adds the user to Exchange and to Active Directory), and to Cisco Unified Presence.

See the administration guides for Cisco Unified Communications Manager and Cisco Unified Presence at the following URLs:

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

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

Step 4 Create mailboxes for new and existing users. For details, see the documentation for your Exchange server.

Step 5 (Optional) Enable secure messaging as follows:

a. Select Subscribers > Subscribers > Features to make the change on a subscriber template.





The change you make here is not applied to currently existing subscriber accounts that were created by using this template. The setting applies only to subscriber accounts that are created by using this template after the change has been made.

b. Select an option from the Message Security When Sending a Message list to enable secure messages. For example, select Encrypt All Messages.

This setting specifies whether messages are encrypted when subscribers send messages to other subscribers.

c. Click Save.

d. Repeat these steps for additional subscribers or subscriber templates, as applicable.

Step 6 (Optional) Enable secure messaging for messages from unidentified callers:

a. Select System > Configuration > Message Security Settings.b. Specify whether messages from unidentified callers are encrypted. Select an option from the list.

c. Click Save.

Step 7 Perform the voice-mail and mailstore configuration in Cisco Unified Presence Administration.

Troubleshooting Tip

Cisco Unified Personal Communicator users must enter their Cisco Unity credentials in the Cisco Unified Personal Communicator Preferences window.

Related Topics





Specifying Voice-Mail Server Names and Addresses in Cisco Unified Presence Administration

You must configure voice-mail settings so that the Cisco Unified Presence server can interact with the voice message web service (VMWS) on Cisco Unity or Cisco Unity Connection. The VMWS service enables Cisco Unified Personal Communicator to move deleted voice-mail messages to the correct location. This service also provides message encryption capabilities to support secure messaging.

Before You Begin

• Make sure that you configure a supported server as described in the following sections:

– Configuring Cisco Unity Connection Servers, page 3-2

– Configuring Cisco Unity Servers, page 3-4

• For Cisco Unity Connection, obtain the hostname or IP address of the voice-mail server. You might need to specify more than one hostname to provide services for the number of users in your environment.



• For Cisco Unity, obtain the hostname or IP address of the Cisco Unity server. You might need to specify more than one hostname to provide services for the number of users in your environment.

• For Cisco Unity, obtain the hostnames or IP addresses of the peer Microsoft Exchange server or servers.

Procedure


Release 7.0: Application > Cisco Unified Personal Communicator > Voicemail Server

Release 6.x: Application > Cisco Unified Personal Communicator > Unity Server


Step 3 Enter information into the fields, as shown in the following table:

Step 4 Click Save.

Step 5 Click Add New, and repeat this procedure for each voice-mail server in your environment.

Related Topics




Configuring Secure Messaging in Cisco Unified Presence AdministrationTo enable users to retrieve and play secure voice-mail messages from Cisco Unified Personal Communicator, you must do the following:

• Configure secure messaging in Cisco Unified Presence Administration Release 7.0

• Configure Cisco Unity to encrypt messages

Field Setting

Release 7.0 Only

Server Type Select Unity or Unity Connection.

Name Enter the Cisco Unity Connection or Cisco Unity server name.

Hostname/IP Address Enter the hostname or the IP address of the server.

Web Service Port, Web Service Protocol

Enter 443 in Web Service Port.

Select HTTPS in Web Service Protocol.

Release 6.x Only

Name Enter the Cisco Unity Connection or Microsoft Exchange server name.

Hostname/IP Address Enter the IP address of the Exchange server.



Cisco Unity Connection

In Cisco Unity Connection, when a user sends a message, class-of-service settings determine the security level of the message. When a user marks a message as private, Cisco Unity Connection automatically marks the message as secure.

Cisco Unity Connection provides audio for secure voice-mail messages through a special IMAP port, port 7993. This port requires Transport Layer Security (TLS). Cisco Unified Personal Communicator uses this port to access, download, and play the secure message.

Cisco Unity

Cisco Unity uses public-key cryptography to send secure messages. Each Cisco Unity server in the network has a public key and a private key. The public key for each server is stored in the Cisco Unity database and is shared through Active Directory with other Cisco Unity servers in the network.

The Cisco Unity server generates new session keys daily. The server uses the session key to encrypt the voice mail, and to control the age of messages. Users cannot play messages that are encrypted with keys that are older than the age policy allows.

Cisco Unity uses Microsoft Exchange to store secure messages. You configure all subscriber mailboxes on these message store servers. Cisco Unified Personal Communicator connects to the message store and performs the following actions:

1. Uses IMAP to download the message from Exchange.

2. Determines if the message is encrypted.

3. If the message is not encrypted, Cisco Unified Personal Communicator plays the message.

4. If the message is encrypted, the following happens:

a. Cisco Unified Personal Communicator extracts the encrypted session keys from the .wav file for the message.

b. Cisco Unified Personal Communicator submits the keys to the Cisco Unity server.

c. The Cisco Unity server tries to decrypt the session keys. The server uses the private key certificates in the Cisco Unity database.

d. If the Cisco Unity server decrypts the session key, Cisco Unified Personal Communicator uses the key to decrypt the message, and plays the messages to the user.

e. If the Cisco Unity server cannot decrypt the session key, Cisco Unified Personal Communicator plays a decoy message to the user.

Before You Begin

Install and configure secure message features on the voice-mail servers, as follows:

• For Cisco Unity Connection, see the information in this guide on how to configure Cisco Unity Connection servers. See also the product online help, the system administration guide, and the user moves, adds, and changes guide at the following URL:


• For Cisco Unity, see the information in this guide on how to configure Cisco Unity servers. See also the product online help or the security guide for Cisco Unity with Microsoft Exchange at the following URL:






Restrictions

Secure message features are not available in releases of Cisco Unified Presence Administration earlier than Release 7.0.

Procedure

Step 1 Select Application > Cisco Unified Personal Communicator > Voicemail Server.

Step 2 Find and select your server.

Step 3 Perform one of the following actions, depending on what type of secure messaging you want to configure:

Related Topics

• Configuring Cisco Unity Connection Servers, page 3-2

• Configuring Cisco Unity Servers, page 3-4




Specifying Mailstore Server Names and Addresses in Cisco Unified Presence Administration

You must configure Cisco Unified Presence Release 7.0 with mailstore information so that Cisco Unified Personal Communicator can connect to the mailstore. Cisco Unified Personal Communicator uses IMAP to download messages.

Cisco Unity creates subscriber mailboxes for message storage on the Microsoft Exchange server. Cisco Unity Connection usually provides a mailstore, and hosts the mailstore on the same server.

Before You Begin

• Obtain the hostname or IP address of the mailstore server.

• If you upgrade from Release 6.x to Release 7.0, Cisco Unified Presence automatically imports the IMAP settings into the Mailstore Configuration page. In Release 6.x, these settings are on the Application > Cisco Unified Personal Communicator > Unity Server page.

Secure Messaging Type Action

SOAP Make sure that the web service port and protocol are configured. You configure the web service port and protocol when you specify the voice-mail server name and address.

IMAP Make sure that the IMAP port and protocol are configured. You configure the IMAP port and protocol when you specify the mailstore server name and address.



Restrictions

• You must provision mailstore servers before you can add the servers to the voice-mail profiles.

Procedure

Step 1 Select Application > Cisco Unified Personal Communicator > Mailstore.

Step 2 Click Add New to add a new server.

Step 3 Enter information into the fields, as follows.

The following table describes the protocols you can use, and the security features the protocols implement for voice-mail messages:

Step 4 Click Save.

Related Topics


Field Setting



Hostname/IP Address Enter the hostname or the IP address of the mailstore server.

Port, Protocol Type

Specify the IMAP port number configured for the server and the corresponding protocol to use when Cisco Unified Personal Communicator contacts this server.

Cisco Unity Connection:

• SSL = 993

• TCP = 143

• TLS = 143 or 7993

Cisco Unity with Exchange:

• SSL = 993

• TCP = 143

• TLS = 143

Protocol Description

SSL Uses a secure socket to encrypt usernames, passwords, and voice-mail messages.

TCP Sends usernames, passwords, and voice-mail messages in clear text.

TLS Uses the STARTTLS verb of IMAP to encrypt usernames, passwords, and voice-mail messages.



Creating Voice-Mail Profiles in Cisco Unified Presence Administration

Before You Begin

• You must create voice-mail profiles before you can add Cisco Unified Personal Communicator licensed users to profiles.

• Specify voice-mail server names and addresses.

• Specify mailstore server names and addresses.

Restrictions

Voice-mail server failover and mailstore server failover are not supported in Cisco Unified Personal Communicator Release 7.0(1). Do not specify backup servers in the Voicemail Profile in Cisco Unified Presence Administration.

Procedure


Release 7.0: Application > Cisco Unified Personal Communicator > Voicemail Profile

Release 6.x: Application > Cisco Unified Personal Communicator > Unity Profile

Step 2 Click Add New in the Find and List window.

Step 3 Enter information into the fields, as follows.

Note The fields in the window might be in a different order than listed in the table depending on the release Cisco Unified Presence.

Field Setting



Voice Messaging Pilot (Optional) The voice-mail pilot number is the directory number that a user dials to access their voice messages. Cisco Unified Communications Manager 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.

Select one of the following options:

• Number—Select the voice-mail pilot number for the system. This is the same as the number specified from the Voice Mail > Voice Mail Pilot menu, in Cisco Unified Communications Manager Administration.

• No Voice Mail—Select this option if you do not want to send unanswered incoming calls to voice mail.

Primary Voicemail Server Select a primary server. Select one of the mailstore servers you specified.

In Release 6.x, this field is called Primary Unity Server.

Backup Voicemail Server (Optional) Enter the name of your backup voicemail server. If you do not want a backup voicemail server, select None.

In Release 6.x, this field is called Backup Unity Server.


Chapter 3 Configuring Recommended Servers for Cisco Unified Personal CommunicatorHow to Configure Conferencing Servers

Step 4 Click Save.

Step 5 Click Add New, and repeat this procedure for each voice-mail profile you want to create.

Related Topics



• Specifying Mailstore Server Names and Addresses in Cisco Unified Presence Administration, page 3-9.


How to Configure Conferencing Servers • Configuring Cisco Unified MeetingPlace Express and Cisco Unified MeetingPlace Express VT

Servers, page 3-12

• Configuring Cisco Unified MeetingPlace Servers, page 3-15

• Specifying Conferencing Server Names and Addresses in Cisco Unified Presence Administration, page 3-17)


Configuring Cisco Unified MeetingPlace Express and Cisco Unified MeetingPlace Express VT Servers

Cisco Unified MeetingPlace Express or Cisco Unified MeetingPlace ExpressVT provide Cisco Unified Personal Communicator users with the ability to escalate to web meetings from within an existing audio or video communication session. With Cisco Unified MeetingPlace Express VT, users can move from point-to-point to multiparty voice and video calls.


Release 7.0 Only

Primary Mailstore Select the primary mailstore server. Select one of the mailstore servers you specified.

Backup Mailstore (Optional) Enter the name of your backup mailstore server. If you do not want a backup voicemail server, select None.

Make this the default Voicemail Profile for the system

(Optional) Check this option if you want new users to be automatically added to the default profile.

Users who are already synchronized to Cisco Unified Presence from Cisco Unified Communications Manager are not added to the default profile. However, any users who are synchronized after the default profile is created are added to the default profile.

Field Setting



Before You Begin

• Install a supported release of the web conferencing server (Cisco Unified MeetingPlace Express or Cisco Unified MeetingPlace Express VT). For details about the server installation:


For details about supported Cisco Unified MeetingPlace Express releases, see the release notes:


• Integrate the web conferencing server with Cisco Unified Communications Manager. Configure call control features:


• Determine the number of Cisco Unified MeetingPlace Express (or Cisco Unified MeetingPlace Express VT) user licenses that are needed to provide enough web ports for meetings initiated through Cisco Unified Personal Communicator.

Procedure

Step 1 Integrate the web conference server with Cisco Unified Personal Communicator:

For Cisco Unified MeetingPlace Express VT ad hoc conferencing functionality:

a. Install the following licenses through the Cisco Unified MeetingPlace Express Administration Center:

• adhocsystemsoftware

• webconf

• maxadhoc

This provides enough web ports for Cisco Unified Personal Communicator users. Cisco Unified Personal Communicator requires support for more than six voice, six video, and six web ports.

b. Configure Cisco Unified MeetingPlace Express VT for ad hoc conferencing by following the instructions in the configuration and maintenance guide:


For Cisco Unified MeetingPlace Express reservationless functionality:

a. Install the following licenses:

• systemsoftware

• webconf

• maxweb

This provides enough web ports for both the full web meetings that are initiated from Cisco Unified MeetingPlace Express, and the web meetings that are initiated from Cisco Unified Personal Communicator.

b. For Cisco Unified MeetingPlace Express-specific information about integrating with Cisco Unified Personal Communicator, managing certificates, creating user profiles, and configuring call-control, see the configuration and maintenance guide:









Step 2 If not already enabled, enable the Secure Sockets Layer (SSL) encryption technology on the web conference 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 the web conference server. Without SSL, clear text passwords are sent from Cisco Unified Personal Communicator to the web conferencing server and from the log-in browser to the web conferencing server.

Step 3 Set up a user profile on the web conference server for each Cisco Unified Personal Communicator user who might initiate web meetings from a Cisco Unified Personal Communicator conversation.

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

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

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

Step 4 Assist users with the Presenter Add-In installation so that desktops, documents, or computer applications can be shared. For details:


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 the web conference server 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 in Cisco Unified Presence Administration.

For details about supported and unsupported Cisco Unified MeetingPlace Express meeting controls, see the release notes:






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:



Cisco Unified Personal Communicator users must enter their Cisco Unified MeetingPlace Express credentials in the Cisco Unified Personal Communicator Preferences window.

Related Topics

• Specifying Conferencing Server Names and Addresses in Cisco Unified Presence Administration, page 3-17


Configuring Cisco Unified MeetingPlace ServersCisco Unified MeetingPlace provides a more extensive feature set (such as scheduled and reservationless rich-media conferencing) and allows more concurrent users than Cisco Unified MeetingPlace Express or Cisco Unified MeetingPlace Express VT. With Cisco Unified MeetingPlace, a Cisco Unified Personal Communicator user can escalate to a web conferencing session or to a video conferencing session from within an existing audio session.

Before You Begin

• Install a supported release of the web conferencing server. For details about the server installation:

http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html

For details about supported Cisco Unified MeetingPlace releases, see the Cisco Unified Personal Communicator release notes:


• Integrate the web conferencing server with Cisco Unified Communications Manager. Configure call control features:

Release 7.0: http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html

Release 6.x: http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_implementation_design_guides_list.html

• Determine the number of web and audio conferencing user licenses that provide enough web ports for meetings initiated through Cisco Unified MeetingPlace and through Cisco Unified Personal Communicator:

Release 7.0:


Release 6.x:

http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_implementation_design_guides_list.html


http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html









Procedure

Step 1 Install web and audio conferencing user licenses.

Step 2 If not already enabled, enable the Secure Sockets Layer (SSL) encryption technology on the web conference server. You must obtain and upload the required certificates from a trusted certificate authority (CA).

The certificate is required for secure communications between Cisco Unified Personal Communicator and the web conference server. Without SSL, clear text passwords are sent from Cisco Unified Personal Communicator to the web conferencing server and from the log-in browser to the web conferencing server.

For details about setting up SSL, see the web conferencing configuration guide (Release 6.x) or the configuration guide (Release 7.0):


Step 3 Set up a user authentication method on the web conference server.

The following authentication methods are supported for use with Cisco Unified Personal Communicator:

• MeetingPlace

• HTTP Basic Authentication (Domain)

• LDAP

• LDAP, then MeetingPlace

For details about configuring the authentication methods, see the web conferencing configuration guide (Release 6.x) or the configuration guide (Release 7.0):


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

Step 5 Perform the conferencing server configuration in Cisco Unified Presence Administration.


• Cisco Unified Personal Communicator users must enter their Cisco Unified MeetingPlace credentials in the Cisco Unified Personal Communicator Preferences window. Make sure you provide the password that is consistent with the configured authentication method. For example, if you configured MeetingPlace as the authentication method, provide the user with the MeetingPlace password. If you configured LDAP as the authentication method, provide the user with the LDAP password.

• You do not need to create Cisco Unified MeetingPlace user profiles for all Cisco Unified Personal Communicator users. Cisco Unified Personal Communicator users who do not have Cisco Unified MeetingPlace profiles can attend web conferences initiated by other Cisco Unified Personal Communicator users as guests, and passwords are not needed. However, some authentication methods, for example, HTTP Basic Authentication, do not allow Cisco Unified Personal Communicator users to log in to Cisco Unified MeetingPlace as guests.





For details about the authentication methods, see the web conferencing configuration guide (Release 6.x) or the configuration guide (Release 7.0):


• If you configure multiple web servers with different authentication methods and mismatched credentials, users might have problems when they try to log in to web conferences.

Related Topics



Specifying Conferencing Server Names and Addresses in Cisco Unified Presence Administration

You must specify conferencing server names, addresses, ports, and protocol types in Cisco Unified Presence Administration so that Cisco Unified Personal Communicator can interact with them.

Before You Begin

• Make sure you configure a supported conferencing server as described in these sections:

– Configuring Cisco Unified MeetingPlace Express and Cisco Unified MeetingPlace Express VT Servers, page 3-12.

– Configuring Cisco Unified MeetingPlace Servers, page 3-15

• Obtain the hostname or IP address of the conferencing server.

Procedure


Release 7.0: Application > Cisco Unified Personal Communicator > Conferencing Server

Release 6.x: Application > Cisco Unified Personal Communicator > MeetingPlace Server



Field Setting



Hostname/IP Address Enter an IP address or a fully qualified domain name of the server.




Step 4 Click Save.

Related Topics


Creating Conferencing Profiles in Cisco Unified Presence AdministrationYou must create conferencing profiles in Cisco Unified Presence Administration and assign each to a primary server.

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

Before You Begin

• You must create the conferencing profile before you can add Cisco Unified Personal Communicator licensed users to the application profile.

• You must first specify conferencing server names and addresses before you can select them in this procedure.

Restrictions

Conferencing server failover is not supported in Cisco Unified Personal Communicator Release 7.0(1).

Procedure


Release 7.0: Application > Cisco Unified Personal Communicator > Conferencing Profile

Release 6.x: Application > Cisco Unified Personal Communicator > MeetingPlace Profile


Port Specify the port number configured for the server.

Enter 80 for HTTP or 443 for HTTPS.

Protocol Specify the protocol to use when contacting this server:

• HTTP: Selects Hypertext Transfer Protocol as the standard method for transferring data between the server, Cisco Unified Personal Communicator, and the browser. Select this option if the Cisco Unified MeetingPlace or the Cisco Unified MeetingPlace Express does not have SSL enabled.

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

Field Setting


Chapter 3 Configuring Recommended Servers for Cisco Unified Personal CommunicatorConfiguring Videoconferencing Resources


Step 4 Click Save.

Related Topics



Configuring Videoconferencing ResourcesThrough Cisco Unified Communications Manager Administration, you can enable merged conference calls (three or more parties) with audio and video support for Cisco Unified Personal Communicator soft-phone users. Any participant in the conference call can merge other participants into the conference.

Before You Begin

• Install a supported release of the videoconferencing server. For details about the server installation:


For details about supported Cisco Unified Videoconferencing releases, see the Cisco Unified Personal Communicator release notes:


• Obtain the MAC address of the videoconference bridge.

Field Setting



Primary Conferencing Server

Select one of the conferencing servers that you specified as the primary server.

This field is called Primary MeetingPlace Server in Release 6.x.

Backup Conferencing Server

Set to None.

This field is called Backup MeetingPlace Server in Release 6.x.


Release 7.0 Only

Make this the Default Conferencing Profile for the System

(Optional) Check so that any new users who are added to the system are automatically placed into this default profile.

Users who are already synchronized to Cisco Unified Presence from Cisco Unified Communications Manager are not added to the default profile. However, once the default profile is created, any users synchronized after that are added to the default profile.




Chapter 3 Configuring Recommended Servers for Cisco Unified Personal CommunicatorConfiguring Videoconferencing Resources

Procedure

Step 1 Select Media Resources > Conference Bridge.

Step 2 Add the videoconference bridge.

Step 3 Select Media Resources > Media Resource Group List.

Step 4 Create a media resource group list.

Step 5 Add the videoconference bridge to the media resource group list.

Step 6 Select Media Resources > Media Resource Group.

Step 7 Create a media resource group.

Step 8 Add a media resource to the media resource group.

Step 9 (Optional) To enable any participant to add more participants the conference, perform the following steps:


b. Select the Cisco Unified Communications Manager server and service.

c. Set Advanced Ad Hoc Conference Enabled to True in the Clusterwide Parameter (Feature - Conference) section.

Step 10 Associate the phone with the new media resource group list:

a. Select Device > Phone in Cisco Unified Communications Manager Administration.

b. Under Search Options, search for the directory number of the phone, and when it is found, click the device name.

c. In the Phone Configuration window in the Device Information section, find the Media Resource Group List, and select the media resource group list that you just configured.

d. Select Enabled for Video Capabilities in the Product Specific Configuration Layout section.

e. Click Save.

f. Click Reset.

For detailed configuration instructions, use the Cisco Unified Communications Manager Administration online help or the Cisco Unified Communications Manager Administration Guide:


Related Topics


• Configuring Users for Point-to-Point Video Calls and for Multipoint Videoconferencing, page 2-34




C H A P T E R 4
Deploying and Updating Cisco Unified Personal Communicator
December 2008

• How to Deploy the Application, page 4-1

• Installing the Application, page 4-5

• Updating the Application, page 4-6

• Installation and Configuration of Headsets and Other Audio Devices, page 4-6

• Use of Third-Party Headsets with Cisco Unified Personal Communicator, page 4-7


Note Before deploying the application, be sure to complete the procedures in Chapter 2, “Configuring Required Servers for Cisco Unified Personal Communicator” and in Chapter 3, “Configuring Recommended Servers for Cisco Unified Personal Communicator.”

How to Deploy the Application • Installer Package Names, page 4-1

• Software Download Site, page 4-3

• Deploying the Application in a Mac OS Environment, page 4-4


Installer Package NamesYou can deploy Cisco Unified Personal Communicator by using these installer packages:


Chapter 4 Deploying and Updating Cisco Unified Personal CommunicatorHow to Deploy the Application

Related Topics

• Localized Installer Packages and Three-Letter Language Locales, page 4-2

Localized Installer Packages and Three-Letter Language LocalesIf you run the Windows non-ENU installer, the localized language and the US English language are installed. In this way, English is always available in case the configured language for the user is not available. Some log file information is in English, and Cisco TAC and other technicians can switch to English, if necessary, for troubleshooting.

For both the US English-only version and the internationalized version for the Mac OS, Cisco Unified Personal Communicator uses the operating system settings and rules to determine the correct language to present to the user at runtime. You must download and install the international version of Cisco Unified Personal Communicator to have both US English and localized languages. If you download and install the US-only version, only US English is available.

Filename Description

CiscoUnifiedPersonalCommunicatorSetupK9_XXX1.exe

1. XXX = three-letter language locale.

This executable contains the required Windows Installer engine, the Outlook plug-in, the user interface, and a set of related DLLs2 for deployment.

This package is typically used for individual users installing the application.

2. DLLs = dynamic link libraries

CiscoVTCameraDriverSetup.exe This executable contains the installer for the Cisco VT Camera and Cisco VT Camera II device drivers. The installation prompts the user to choose a language if a language other than English is available.

CiscoUnifiedPersonalCommunicatorSetupK9_XXX.msi This Microsoft Windows Installer (MSI) package contains the Outlook plug-in, the user interface, and a set of related DLLs for deployment.

This package is typically used by IT administrators with the corporate deployment tool (for example, Altiris, System Management Server (SMS), and Active Directory) to push the installation to users.

CiscoVTCameraDriverSetup.msi This MSI package contains the installer for the Cisco VT Camera and Cisco VT Camera II device drivers. For languages other than English, you associate the locale .mst file with the TRANSFORMS parameter to install a language locale.

CiscoUnifiedPersonalCommunicator-K9_ENU.dmg

CiscoUnifiedPersonalCommunicator-K9_ALL.dmg

This package is the disk image (.dmg) of the application for Mac OS X.

ENU is the US English-only package.

ALL is the US English and the localized languages.



Note Localized software and documentation for Cisco Unified Personal Communicator is released after the English release. Check the Cisco website for updates.

Use the following table to determine which non-English locale to download:

Related Topics

• Software Download Site, page 4-3

Software Download SiteYou must register for an account on Cisco.com to access the software download sit. On the download site, the installer packages are offered as .zip files. The .zip files contain all the files required to deploy the application and the camera drivers.

The software download site is at the following URL:

http://www.cisco.com/public/sw-center/sw-voice.shtml

Related Topics

• Installer Package Names, page 4-1



Language Locale Identifier

Chinese (traditional) CHT

Chinese (simplified) CHS

Danish DAN

Dutch NLD

French FRA

German DEU

Italian ITA

Japanese JPN

Korean KOR

Portuguese (Brazilian) PTB

Russian RUS

Spanish ESP

Swedish SVE




Deploying the Application in a Mac OS Environment

Procedure

Step 1 Download the disk image (.dmg) from Cisco.com in a Mac OS environment.

Step 2 Put the image on an internal server so that users can download the image from that location. Alternatively, you can burn the disk image on a CD for internal distribution.

Step 3 Ask users to complete the installation of Cisco Unified Personal Communicator by following the instructions in the Cisco Unified Personal Communicator user guide:


Related Topics




Deploying the Application and the Camera Drivers in a Microsoft Windows Environment

Restriction

Cisco Unified Personal Communicator does not support the advertising or publishing deployment in which users open an icon that the administrator places on their desktops to install the application.

Procedure

If you want to... Then...

Deploy the executable or MSI package to a shared location (such as a web server) where users can access it.

Push the installer at an elevated privilege so that users can complete the installation (run the installer and follow the installation wizard)

Deploy either the executable or the MSI package directly to the client computer.

Push the installer at an elevated privilege so that users can complete the installation (run the installer and follow the installation wizard).

or

Perform the installation operation directly on a client computer while logged in as the administrator.

Use a software deployment tool to distribute Cisco Unified Personal Communicator and camera drivers to client computers.

Push the installer at an elevated privilege so that users can complete the installation (run the installer and follow the installation wizard).



Chapter 4 Deploying and Updating Cisco Unified Personal CommunicatorInstalling the Application

Note Localized camera driver software is released after the English release. Check the Cisco website for updates.

For languages other than English, if you deploy the Cisco VT Camera driver by using the MSI package, you must install a language locale by associating the locale .mst file to the TRANSFORMS parameter. For example, to install the French locale:

msiexec /i CiscoVTCameraDriverSetup.msi /qb+ TRANSFORMS="1036.mst"

See the table for supported .mst filenames.

Related Topics




Installing the ApplicationFor detailed steps about installing the application and the camera drivers (Windows only), see the user guide:


Filename Language

1028.mst Chinese (traditional)

1030.mst Danish

1031.mst German

1034.mst Spanish

1036.mst French

1040.mst Italian

1041.mst Japanese

1042.mst Korean

1043.mst Dutch

1046.mst Portuguese

1049.mst Russian

1053.mst Swedish

2052.mst Chinese (simplified)



Chapter 4 Deploying and Updating Cisco Unified Personal CommunicatorUpdating the Application

Updating the ApplicationBefore You Begin

Register for an account on Cisco.com so that you can access the software download site.

Restrictions

In a Windows environment, command-line options are not supported on upgrades. They are supported only on new installations.

Procedure

Step 1 Download the latest available Cisco Unified Personal Communicator software from the Software Center:


Step 2 For Windows, download the Cisco VT camera drivers from the Software Center also.

Step 3 Make the updated software available for deployment.

Step 4 For Mac OS, ask users to uninstall the previous version of Cisco Unified Personal Communicator by dragging the application icon to the Trash.

Ask users to drag the address book plug-in to the Trash. For details, see the Cisco Unified Personal Communicator user guide:


Step 5 Ask users to follow the steps in the user guide to upgrade the application.


Related Topics



Installation and Configuration of Headsets and Other Audio Devices

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:


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


Related Topics

• Use of Third-Party Headsets with Cisco Unified Personal Communicator, page 4-7







Chapter 4 Deploying and Updating Cisco Unified Personal CommunicatorUse 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 responsibility of the customer 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 computer to the computer power source itself. In some cases, a hum heard on a headset plugged directly into the computer 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 speaking 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, ask remote parties about the reception from this application when they use a particular headset.

Related Topics

• Installation and Configuration of Headsets and Other Audio Devices, page 4-6

Information to Provide to UsersAfter Cisco Unified Personal Communicator is deployed, provide the information listed in the table to users.

Provide This Explanation

Give to Users Who Install

Give to Users If You Install

Information about client hardware and software requirements.

You can copy the information from the release notes:


Yes Yes

Location of Cisco Unified Personal Communicator and camera driver installers.

Provide the shared folder location or the CD with the executable files.

Yes No



Chapter 4 Deploying and Updating Cisco Unified Personal CommunicatorInformation to Provide to Users

Instructions for installing and setting up the application.

Provide the user guide for Cisco Unified Personal Communicator.


Direct users to read the first chapter for the installation and set-up information.

Yes No

Login information. Provide this information:

• Username.

• Password.

You configured the username and password in Cisco Unified Communications Manager Administration. See the “Associating Cisco Unified IP Phones With Users and Adding Users to a Group” section on page 2-3.

• Cisco Unified Presence host name or IP address.

Yes Yes

User capabilities (presence, instant messaging, video soft phone) available through Cisco Unified Communications Manager licenses.

Provide users with information about the capabilities (license) they have.

You assigned capabilities in Cisco Unified Communications Manager Administration in the “Assigning Capabilities to Users” section on page 2-15.

Yes Yes

Supported features: directory services, voice-mail retrieval and playback, access to web conferences, and Cisco Unified Communications Manager extension mobility.

Provide users with information about which Cisco Unified Personal Communicator features are supported based on the integration with the LDAP directory, voice-mail servers, and web conferencing servers. Inform users that they have the ability to initiate web conferencing sessions from a Cisco Unified Personal Communicator conversation. For details, see “Planning to Install Cisco Unified Personal Communicator” section on page 1-1.

Inform users that you configured for Cisco Unified Communications Manager extension mobility. For a description of the type of information to provide to them, see the Cisco Unified Communications Manager Features and Services Guide:


Yes Yes








Account information Provide account information to be entered into the Preferences window:

• Voice-mail server: username and web password (to use voice-mail features supported by Cisco Unified Personal Communicator)

For details, see the “How to Configure Voice-Mail Servers” section on page 3-1.

• Web conferencing server: username and password (to add web conferencing to a Cisco Unified Personal Communicator conversation)

For details, see the “How to Configure Conferencing Servers” section on page 3-12.

Yes Yes

User Options web page access information

Provide the URL (https://server-address/ccmuser), user ID, and password for accessing user options web pages on these servers:

• Cisco Unified Communications Manager

• Cisco Unified Presence

From these pages, users can control certain settings, features, and services associated with the Cisco Unified IP Phone and with Cisco Unified Personal Communicator.

See the Cisco Unified IP Phone user documentation and the Cisco IP Phone Messenger for Cisco Unified Presence:

• http://www.cisco.com/en/US/products/hw/phones/ps379/products_user_guide_list.html

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

Yes Yes

Instructions for using the application. Provide the user guide and quick start guide for Cisco Unified Personal Communicator. Remind users to use the application online help.


The user guide PDF is also available in drive:\Program Files\Cisco Systems\Cisco Unified Personal Communicator\resources\XXXX\help\CUPC-help, where XXXX represents the numbered folder that holds the documentation in your language. For example, 1033 folder holds the English-language documentation.

Yes Yes

Internal company support for the application.

Provide users with the names of people to contact for assistance and with instructions for contacting those people.

Yes Yes






http://www.cisco.com/en/US/products/hw/phones/ps379/products_user_guide_list.html




C H A P T E R 5
Adding a New User After Deploying Cisco Unified Personal Communicator
December 2008

• Configuring a New User for Full Cisco Unified Personal Communicator Functionality, page 5-1

Configuring a New User for Full Cisco Unified Personal Communicator Functionality

The table lists the required configuration steps to add a new user to various servers after the initial deployment. By completing these tasks, the new user will have full Cisco Unified Personal Communicator functionality after the initial deployment.

Procedure

Task Where to Find Information

Cisco Unified Communications Manager Configuration

Add the phone to the Cisco Unified Communications Manager database.

Allow control of the Cisco Unified IP Phone from the computer telephony interface (CTI).

Associate a directory number with the phone.

Adding Desk Phones to the Cisco Unified Communications Manager Database, page 2-1

Set up the user account, and associate the directory number with the user.

Associate the phone with the user.

Add the user to the Standard CTI Enabled group.

Add the user to the CCM End User group.

Associating Cisco Unified IP Phones With Users and Adding Users to a Group, page 2-3

Enable Cisco Unified Personal Communicator soft-phone features by manually creating a new device for each user.

Adding Cisco Unified Personal Communicator as a Phone Type, page 2-5

Make sure that availability status in Cisco Unified Personal Communicator is accurately displayed.

Associate the line of the user with the user in Cisco Unified Communications Manager.

Associating Lines, Users, and Directory Numbers, page 2-8


Chapter 5 Adding a New User After Deploying Cisco Unified Personal CommunicatorConfiguring a New User for Full Cisco Unified Personal Communicator Functionality

Obtain a license file, if necessary.

Upload the license file, if necessary.

Assign capabilities.

Obtaining a License File, page 2-14

Uploading a License File, page 2-14

Assigning Capabilities to Users, page 2-15

Voice-mail Server Configuration

Set up an account for the new user. Configuring Cisco Unity Connection Servers, page 3-2

Configuring Cisco Unity Servers, page 3-4

Web Conferencing Server Configuration

Set up a user profile for the new user. Configuring Cisco Unified MeetingPlace Express and Cisco Unified MeetingPlace Express VT Servers, page 3-12

Configuring Cisco Unified MeetingPlace Servers, page 3-15

Cisco Unified Presence Configuration

Configure the LDAP attribute map for the new user. Configuring the LDAP Attribute Map, page 2-22

Add the new user to the server profiles. Creating LDAP Profiles, page 2-26

Creating CTI Gateway Profiles, page 2-30

Creating Voice-Mail Profiles in Cisco Unified Presence Administration, page 3-11

Creating Conferencing Profiles in Cisco Unified Presence Administration, page 3-18

Assign the preferred CTI device to the MAC address of the primary desk phone for the user. (Cisco Unified Presence Release 6.x only)

Changing Application Profiles for a Single User, page 2-32

Point-to-point video calls

Multipoint videoconferencing

Video telephony camera

Configuring Users for Point-to-Point Video Calls and for Multipoint Videoconferencing, page 2-34

Configuring Videoconferencing Resources, page 3-19

Provide information to users Information to Provide to Users, page 4-7

Headset and Audio Device Information Installation and Configuration of Headsets and Other Audio Devices, page 4-6

Task Where to Find Information



I N D E X

A

Administrative XML Layer Simple Object Access Protocol

See AXL SOAP authentication 3-14

application deployment

adding new user after 5-1

deploying in Mac OS environment 4-4

deploying in Windows environment 4-4

deploying to a shared location 4-4

installer package names 4-1

software download site 4-3

updating 4-6

using a software deployment tool 4-4

using the client computer installer 4-4

application dialing rules

configuring 2-12

described 2-11

application profiles

changing for a single user 2-32

changing for multiple users 2-32

audio devices, configuration 4-6

authentication methods

Cisco Unified MeetingPlace 3-16

Cisco Unity 3-5

availability

configuring TCP as the transport 2-19, 2-20

status and firewalls 2-34

UDP restrictions 2-18, 2-19

AXL SOAP authentication 3-14

B

backup server. See redundancy

C

calendaring

effects on availability 1-8

integrating with 1-8

camera drivers

deploying in Windows environment 4-4

installer package names 4-2

updating 4-6

Cisco Unified Communications Manager

license files

obtaining 2-14

uploading 2-14

licenses

assigning capabilities to users 2-15

reports 2-16

licensing, described 2-13

Cisco Unified IP Phones

adding to database 2-1

adding user to CCM end user group 2-5

adding user to CTI users group 2-5

allowing control from CTI 2-2

associating with end user 2-4

completing the configuration 2-3

DND behavior in CUPC, described 2-8

specifying user information 2-4

Cisco Unified Personal Communicator

adding as a phone type to CUCM 2-5

configuring the contact list size 2-33

DND behavior, described 2-8

inbound calls, RFC2833 and DTMF digit collection 3-14

interaction with

IN-1r Cisco Unified Personal Communicator Release 7.0

Index

Cisco Unified Communications Manager 1-1

Cisco Unified Presence 1-1

directories 1-2

voice-mail servers 1-2, 1-4

web collaboration servers 1-2

nodes, failover and rehoming features 2-17

outbound calls, KPML and RFC2833 3-14

sharing the line with the IP Phone 2-7

soft-phone device name guidelines for CUCM 2-6

startup process, described 1-3

transformed dialed numbers, described 2-11

uninstalling

previous Mac version 4-6

updating the application 4-6

URL for downloading latest software 4-6

computer telephony interface

See CTI 2-2

conferencing servers

AXL SOAP authentication 3-14

configuring 3-12, 3-15

described 1-2

server profiles

changing 2-32

creating 3-18

specifying server names and addresses 3-17

web meetings

participant privileges 3-14, 3-16

Presenter Add-In 3-14

configuration file for soft-phone mode 1-3, 2-20

contact list size, configuring 2-33

contact name, rules for displaying 2-23

CTI

described 2-2

Standard CCM end users group 2-5

users group, Standard CTI Enabled 2-5

CTI gateway

connection failures

failover, described 2-28

with calls 2-29

IN-2Installation and Configuration Guide for Cisco Unified Personal Co

with no calls 2-28

server profiles

changing 2-32

creating 2-30

dynamically created 2-30

specifying

redundant servers 2-30

server names and addresses 2-29

CTIManager

See CTI gateway

D

desk-phone mode

and the CTI gateway 2-29

DND behavior and Call Reject 2-9

DND behavior and Ringer Off 2-9

failover and recovery 2-28

desk phones

adding to database 2-1

directory lookup rules

configuring 2-12

described 2-11

E

extension mobility, configuring 2-10

F

failover

See CTI gateway

See TFTP servers

federations

described 1-9

supported configurations 1-9

firewalls, configuring 2-34

mmunicator Release 7.0

Index

H

headsets

configuration 4-6

use of third-party 4-7

I

IMAP 3-2

inbound calls, network requirements 3-14

information needed by users 4-7

initial deployment, adding new user after 5-1

installer packages 4-1

instant messaging, disabling globally 2-33

Internet Mail Access Protocol. See IMAP

L

LDAP attributes

photo 2-22, 2-23

rules for displayed contact name 2-23

rules for mapping the UserID 2-22

settings for Microsoft Active Directory 2-22

tip for Global Catalog and retrieving jpegPhoto 2-25

LDAP server

attribute map schema 2-22

configuring 2-16

queries and contact information database 1-2

search context information 2-27

See also Microsoft Active Directory

server profiles

changing 2-31

creating 2-26

specifying

redundant servers 2-26

server names and addresses 2-24

server settings 2-24


license files

Installation and Configuration

obtaining 2-14

uploading 2-14

licenses

assigning capabilities to users 2-15

described 2-13

viewing reports 2-16

licensing, adjunct

configuring 2-6

described 2-5

restrictions 2-5

M

mailstore servers

configuring 3-10

described 3-9

ports and protocols used 3-10

media resources for videoconferencing 3-19

Microsoft Active Directory

setting LDAP search context information 2-27

settings for LDAP attribute map 2-22

setting the Global Catalog port number 2-25


Microsoft Exchange server, integrating with 1-8

N

network configuration for inbound calls 3-14

network ports and firewalls 2-34

network settings, described 1-4

new user, configuration after initial deployment 5-1

nodes

configuring 2-17

failover and rehoming features 2-17

O

outbound calls, support for KPML and RFC2833 3-14

IN-3 Guide for Cisco Unified Personal Communicator Release 7.0

Index

P

photos

fetching from a web server 2-23

LDAP attributes 2-22


point-to-point video calls

configuring device as soft phone 2-5

configuring VT camera 2-34

Presenter Add-In for Cisco Unified MeetingPlace Express 3-14

primary server. See redundancy

profiles, automatically created 2-30

proxy listener

See SIP

R

redundancy

Cisco Unified Presence nodes 2-17

CTI gateway 2-30

LDAP 2-26

TFTP server 2-21

roaming profiles 1-6

S

secondary licensing

See licensing, adjunct

secure messaging

configuring 3-7

described (Cisco Unity) 3-8

described (Cisco Unity Connection) 3-8

Secure Sockets Layer

See SLL

server configuration

Cisco Unified Communications Manager 2-1

Cisco Unified MeetingPlace 3-15

Cisco Unified MeetingPlace Express 3-12


Cisco Unified Presence 2-17

Cisco Unity 3-4

Cisco Unity Connection 3-2

gathering information 1-6

installing 1-7

LDAP 2-16

server redundancy

See redundancy

Session Initiation Protocol

See SIP

shared location deployment 4-4

SIP

presence engine, described 1-1

proxy listener

described 2-18

selecting in Release 6.x 2-19

selecting in Release 7.0 2-18

proxy server profiles

changing 2-31

creating 2-19

soft-phone device naming guidelines for CUCM 2-6

soft-phone mode

configuration file 2-20

DND behavior, described 2-9

failover, described 2-20

Software Center, URL for 4-6

software deployment tools 4-4

software download site 4-6

SSL

Cisco Unified MeetingPlace certificates 3-16

Cisco Unified MeetingPlace Express certificates 3-14

startup process 1-3

described 1-3

device configuration file for soft-phone mode 1-3

network settings 1-4

portable user preferences 1-5

retrieval of settings 1-3

user settings 1-5


Index

T

TFTP servers

addresses 2-20

failover

described 2-20

restrictions 2-21

U

UserID, rules for mapping 2-22

user information, providing 4-7

user preferences

file location (Mac OS X) 1-6

file location (Windows OS) 1-6

portable 1-5

roaming profiles 1-6

user settings, described 1-5

V

videoconferencing resources

configuring the video conferencing bridge 3-19

installing the VT camera 2-34

video telephony camera, configuring 2-34

voice-mail servers

allowing message body access 3-2

configuring

Cisco Unity Connection 3-2

Cisco Unity with Exchange 3-4

mailstore 3-10

enabling port 7993 port usage 3-2

redirecting unanswered calls 3-11

server profiles

changing 2-32

creating 3-11

setting a pilot number 3-11

setting class of service 3-2

specifying server names and addresses 3-6

Installation and Configuration

voice messaging pilot number 3-11

W

web server, fetching a photo from 2-23

Windows roaming profiles 1-6

IN-5 Guide for Cisco Unified Personal Communicator Release 7.0

Index
