Configuring the Cisco Unified Personal Communicator

This chapter is from the book 

Configuring Advanced Features for CUPC

The advanced features available to the CUPC client consist of Unity voicemail, MeetingPlace conferencing, video, and LDAP integration. The following sections describe the configuration of these advanced features in greater detail.

Voicemail Configuration for CUPC

CUPC has the capability to access Unity voicemail directly through the client interface. This is useful to the end user by providing a visual interface to the Unity voicemail system, enabling the user to prioritize voicemails by name, timestamp, duration, and so on without having to listen to the messages first.

Two primary prerequisites must be completed before integrating CUPS to Unity:

• Implement a supported version of Unity or Unity Connection, which are the only two supported messaging platforms for CUPS integration.
• Complete the integration of CUCM and Unity/Unity Connection, and make sure all voice ports are working properly.

The sections that follow discuss how to satisfy these prerequisites in more detail.

Cisco Unity Connection

The following steps describe the Cisco Unity Connection (CUC) provisioning steps for CUPC users. Use Figure 5-10 with the following steps.

• Step 1. Configure a class of service in CUC with IMAP enabled:

  1. Select Class of Service in the left navigation pane.
  2. Select or add the desired class of service in the list.
  3. Check the Allow Users to Use Unified Client to Access Voice Mail box. This allows access to port 7993 and TLS for the CUPC client support.
  4. For IMAP client support as well, check the Allow Users to Access VoiceMail Using an IMAP Client box and select the Allow Users to Access Message Bodies button.
  5. Click Save.
• Step 2. Create a CUC user account and voicemail box for each CUPC user.
• Step 3. Make sure the web application password is set for the user.

Use Figure 5-11 with the following steps to enable secure messaging:

• Step 1. Enable secure messaging:

  1. Select Class of Service using the navigation panel; then click the Class of Service the CUPC users are a part of.
  2. Under the Message Options section of the Class of Service; select the type of secure messaging next to the Require Secure Messaging option:
     • Always: Messages will always be marked secure.
     • Never: Messages will never be marked secure. (Users can still mark messages as private, and they will be secure.)
     • Ask: Users will be prompted from the Special Delivery Options menu to select if the message is marked secure or not.
     • Private: Messages are marked secure only when the user makes them a private message. This is the system default.

• Step 2. Configure unidentified caller message security settings, as shown in Figure 5-12:

  1. Select Users in the navigation panel.
  2. Select the desired user.
  3. Select Edit > Message Settings.
  4. Check Mark Secure in the Unidentified Callers Message Security section.

Cisco Unity

The next steps cover the configuration requirements for Unity as the message platform for the CUPC user:

• Step 1. Configure the Microsoft Exchange server to use IMAP by enabling the IMAP Connector. Refer to Chapter 9, "Troubleshooting Cisco Unified Presence," for step-by-step guidance.
• Step 2. Configure the port and encryption type. Ensure that SSL is the only encryption type being used and not TCP. This setting is manually done in Exchange 2003 but on Exchange 2007, SSL is the default.
• Step 3. Configure the user in Unity.
• Step 4. Create the exchange mailbox for the users. This step might not be necessary, depending on whether the user was added in Unity or AD first. If users were imported from AD into Unity, the mailbox should already be there as a result of the import process. For purposes of brevity, it is assumed that this is the case.

The following steps are necessary only if secure messaging is implemented with Cisco Unity:

• Step 1. Enable secure messaging through the Cisco Unity System Admin Page, as shown in Figure 5-13:

  1. Select Subscribers > Subscribers > Features.
  2. Select the desired option in the Message Security When Sending a Message list.
  3. Select Save.
  

  Figure 5-13 Enabling Secure Messaging in Unity

• Step 2. Configure unidentified caller message security settings, as shown in Figure 5-14.:

  1. Select System > Configuration > Message Security Settings.
  2. Select an option from the list on how messages should be secured from unidentified callers.
  3. Select Save.
  

  Figure 5-14 Enabling Secure Messaging in Unity Continued

Configuring Voicemail Servers in CUPS

Voicemail servers are defined in CUPS to allow for required interactions between CUPS and the specified voicemail server. Voice message web service (VMWS) is the service on a Cisco Unity or CUC server that enables deleted voicemails to be moved to their correct location in the mail store and also provides encryption service for secure messaging environments. The IP address of the voicemail server and the peer Microsoft Exchange server (if using Unity) is needed prior to the following steps:

• Step 1. Navigate to Application > Cisco Unified Personal Communicator > Voicemail Server in the CUPS administration page, as shown in Figure 5-15.
  

  Figure 5-15 Configuring the CUPC Voice Mail Server in CUPS

• Step 2. Click Add New.
• Step 3. Select Unity or Unity Connection in the server type menu.
• Step 4. Define the voicemail server name.
• Step 5. Define the FQDN hostname or IP address.
• Step 6. For Cisco Unity Servers, define 443 for Web Service Port. For Cisco Unity Connection Servers, define 143 for the Port.
• Step 7. For Cisco Unity Servers, select HTTPS for Web Service Protocol. For Cisco Unity Connection Servers, select TCP, UDP, TLS, or SSL. The default is UDP.
• Step 8. If enabling Secure Messaging (optional), define the Secure Port and Secure Protocol Type. For Cisco Unity Servers, choose HTTP or HTTPS for Protocol Type. For Cisco Unity Connection Servers, choose TCP, SSL, or TLS as the Protocol Type.
• Step 9. Click Save.

Configuring Mailstore Server in CUPS

Defining a mailstore in CUPS is required for the CUPC client to access the voicemail messages on the voicemail server. Figure 5-16 shows the CUPS Mailstore page. The FQDN hostname or IP address of the mailstore server is necessary to complete the following tasks.

• Step 1. Navigate to Application > Cisco Unified Personal Communicator > Mailstore in the CUPS administration site.
• Step 2. Click Add New.
• Step 3. Define the mailstore server name.
• Step 4. Define the FQDN hostname or IP address.

• Step 5. Define the IMAP port number for CUPC to use in connecting to the mailstore server.

  Unity Connection options follow:

  • TCP: port 143
  • SSL: port 993
  • TLS: port 143 or 7993

  Unity with Exchange options are the same as Unity Connection except TLS is supported only on port 143.

• Step 6. Click Save.

Configuring Voicemail Profiles in CUPS

The voicemail profile is required in CUPS to enable the CUPC client to access the correct voicemail resources for the end user. The following steps are necessary to configure the voicemail profile:

• Step 1. Navigate to Application > Cisco Unified Personal Communicator > Voicemail Profile in the CUPS administration page, as shown in Figure 5-17.
  

  Figure 5-17 Configuring the CUPC Voicemail Profile in CUPS

• Step 2. Click Add New.
• Step 3. Define the profile name.
• Step 4. Select the Voice Message Pilot number for the correct voicemail server of the CUPC end user.

When the voicemail profile configuration is complete, CUPC end users are now ready to log in and access the voicemail services through the desktop client.

Conferencing Configuration for CUPC

One of the major benefits of using the CUPS and the CUPC client is that application integrations allow for consolidated user functionality into other applications, such as video and conferencing. These integrations are at the touch of a button and easy to use from an end-user perspective. Initiating a conversation through an IM window and then escalating that conversation to an audio or video call at the touch of a button and then further enhancing that conversation into a collaboration conference is compelling for end users and has a dramatic effect on their productivity. This functionality begins to bring the true value of CUPS and the CUPC client to the user.

CUPC can be configured to support ad-hoc web conference sessions with the following products:

• Cisco Unified MeetingPlace
• Cisco Unified MeetingPlace Express
• Cisco Unified MeetingPlace VT
• Cisco Webex Meeting Center

MeetingPlace Express and Meeting Place Express VT

MeetingPlace Express and MeetingPlace Express VT can both provide web and audio conferencing functionality to CUPC. MeetingPlace Express VT provides video conferencing resources to provide the capability for CUPC to escalate a point-to-point video call to a multipoint video call.

Several things need to be completed before integrating the MeetingPlace Express (VT) platform into the CUPS solution:

1. Install a release of MeetingPlace Express (VT) supported by the CUPC client. The release notes for the CUPC client will specify the specific supported software versions. You can find current CUPC 7.x release notes at http://tinyurl.com/y9dephh.
2. Configure CUCM to integrate with MeetingPlace Express (VT).
3. Determine the number of web, audio, and video ports required for the solution. A good rule of thumb for the average user population is 1:40 (ports:client) for web and video and 1:20 for audio.

The next steps cover the necessary configuration to integrate MeetingPlace Express (VT) with CUPC:

• Step 1. Configure the MeetingPlace Express (VT) conferencing capabilities:

  1. Install the following licenses:
     • adhocsystemsoftware
     • webconf
     • maxadhoc
     • maxweb
  2. Configure MeetingPlace Express (VT) for adhoc conferencing. You can find detailed documentation for this feature at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Express,_Release_2.x.
  3. Configure MeetingPlace Express for the reservationless feature to support full web meetings initiated by MeetingPlace Express and the web meetings initiated by CUPC. You can find specific details on configuring user profiles, call control, and such on MeetingPlace Express at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace_Express,_Release_2.x.
• Step 2. Enable Secure Sockets Layer (SSL) encryption. This is optional; however, if it is not completed, passwords sent between CUPC and MeetingPlace Express will be sent in clear text, creating a potential security vulnerability.
• Step 3. Configure a user profile for each CUPC user that is going to initiate web conferences from the CUPC client.

  NOTE

  This is not required for all CUPC users and is needed only for the users that will initiate the web conferences.

• Step 4. Ensure that the Presenter add-in is installed on each CUPC user's computer. This can be done remotely by downloading the install package from Cisco Connection Online, or the user can download it by navigating to the MeetingPlace Express server's main page using a web browser.
• Step 5. Configure the voice network so that inbound calls from the PSTN to the CUPC user support RFC2388. This allows an inbound call from MeetingPlace Express to the CUPC user to use the CUPC key pad for DTMF instead of key press markup language (KPML). This is required only for DTMF support on inbound calls to CUPC, which supports both KPML and DTMF for outbound calls. This will be done on the CUCM configuration page for the SIP Trunk configured to CUPS (see Figure 5-18).
  

  Figure 5-18 Configuring RFC 2388 DTMF Support

When these configurations are made, CUPS configuration will take place to define a conferencing server and profile. Those steps come later in this chapter, after the MeetingPlace and Webex configurations are covered.

Configuring MeetingPlace

The following steps configure MeetingPlace to support the CUPC client:

• Step 1. Install the web and audio conferencing user licenses.
• Step 2. Enable SSL encryption. This is optional; however, if not completed, passwords sent between CUPC and MeetingPlace Express will be sent in clear text, creating a potential security vulnerability.
• Step 3. Configure user authentication on the web conference server. The following methods are supported:
  • MeetingPlace
  • LDAP
  • HTTP Basic
  • LDAP, then MeetingPlace
• Step 4. Configure user profiles for each CUPC user on the MeetingPlace server.

When these configurations are made, CUPS configuration takes place to define a conferencing server and profile. Those steps come later in this chapter, after the Webex configurations are covered.

Configuring WebEx Meeting Center

Integration for CUPC into WebEx Meeting Center is a new integration available with CUPS version 7.0(3) and CUPC version 7.0(2). The WebEx Meeting Center conferencing server must be installed prior to configuration. You can find documentation on how to set up this server on the provisioned WebEx site that is being integrated. Create a user profile on the WebEx Meeting Center for each CUPC user that needs access to initiate web conferencing meetings.

The previous three integration options outline the steps required to provision a CUPC user to have access to the conferencing features that the client provides. This provisioning, so far, has only taken place on the conferencing servers. The next section covers the steps to define these conferencing servers and the conferencing profiles in the CUPS for the CUPC client to leverage these resources.

Configuring Conference Servers in CUPS

This section covers the configuration of the conferencing server in CUPS so that the CUPC client can access the available resources. The configuration steps are done through the CUPS administration web pages.

Before beginning the configuration, you must complete the following prerequisite tasks:

• Get the IP address and the port number of the conferencing server.
• Integrating to a WebEx Meeting Center solution requires the Site ID and the Partner ID assigned to your WebEx site. If you do not know these IDs, you can get them from your WebEx administrator.

The following configuration steps are necessary to complete the integration:

• Step 1. Go to Application > Cisco Unified Personal Communicator > Conferencing Server in the CUPS administration page, as shown in Figure 5-19.
  

  Figure 5-19 Configuring the CUPC Conferencing Server in CUPS

• Step 2. Click Add New.
• Step 3. Define the Name of the conference server.
• Step 4. Define an optional description of the conference server.
• Step 5. Enter the IP address or a hostname of the conference server. The hostname needs to be a Full Qualified Domain Name (FQDN) that can be resolved by the DNS server used by CUPS.
• Step 6. Define the port that the conference server is configured for. The options are for 80 (HTTP) or 443 (HTTPS).
• Step 7. Select the protocol used when CUPS communicates with the conferencing server. The current supported protocols are HTTP and HTTPS.
• Step 8. Select the conferencing server being integrated.
• Step 9. If WebEx were selected, enter the Site ID and the Partner ID for the WebEx site being integrated.

Configuring Conferencing Profiles in CUPS

This section covers the final step for CUPC users accessing conferencing resources on the network. Prior to this section, the steps covered addressed the conferencing server provisioning of the CUPC user and configuring the conference server in CUPS. There can be more than one conference server defined in CUPS as required by end-user feature/functionality, migration from one platform to another, increased capacity requirements, and so on. Conference profiles enable the capability to have different CUPC end users configured for different conferencing server resources. The following steps are needed to configure conferencing profiles and assign CUPC users:

• Step 1. Navigate to Application > Cisco Unified Personal Communicator > Conferencing Profile in the CUPS administration page, as shown in Figure 5-20.
  

  Figure 5-20 Configuring the CUPC Conferencing Profile in CUPS

• Step 2. Click Add New.
• Step 3. In the name section, define the name of the conferencing profile.
• Step 4. Select the Primary Conferencing Server as defined in the system.
• Step 5. You can add up to two backup conferencing servers defined in the system.
• Step 6. Check the Make This the Default Conferencing Profile for the System box if this is the default system.
• Step 7. Click the Add Users to Profile.
• Step 8. Select the users for this voicemail profile.
• Step 9. Click Add Selected.
• Step 10. Click Save.

This section completes the required tasks necessary to configure full conferencing features for CUPC users. This feature will allow for ad-hoc web conferencing leveraging Meeting Express, Meeting Place Express VT, MeetingPlace, and WebEx Meeting Center. Conferencing can be a conversation escalated to a point-to-point web sharing portal or a full-service web conference with the ability to invite other users to the conference via a click to add, e-mail, or IM.

Configuring Video for CUPC

Video is relatively simple for a CUPC deployment. The main thing to note here is that video with CUPC is supported only when the client is in softphone mode. To configure video for CUPC, complete the following tasks:

• Step 1. Configure the CUPC client for softphone use if it is not the user's primary device.
• Step 2. Confirm that video use is enabled for the CUPC device in CUCM. This is done within the Region settings of CUCM and assigned to the device through the device pool.
• Step 3. Distribute supported video cameras for the CUPC users.
• Step 4. If three or more parties are required in a video call, the media resource group defined for those users must have a conference bridge configured with video resources available. The supported options are MeetingPlace Express VT, MeetingPlace with video, and Cisco Unified Videoconferencing solution that leverages the 3500 series Multipoint Control Units (MCU).

Configure LDAP for CUPC

This section covers LDAP integration for the purposes of user lookup in the CUPC client. This enables CUPC users to search for and add contacts from a defined LDAP directory. The section does not cover LDAP directory integration for purposes of user provisioning and authentication with CUCM. Detailed LDAP integration for those purposes can be found in the "Configuring CUPC Users in CUCM" section of this chapter. Cisco strongly recommends having CUCM integrated to LDAP for user provisioning and authentication and configuring CUPC for LDAP integration on CUPS for user lookup functionality.

The first thing to understand before configuring LDAP servers in CUPS is the rules for how contacts are displayed in CUPC. This is important to understand because there will be attributes that need to be mapped for displaying names, and these rules determine how names are displayed:

• If a user edits a contact name retrieved from LDAP in CUPC, display that name. This is the Nickname attribute in CUPS.
• If the LDAP user field DisplayName is configured, display that name.
• If the LDAP user field Nickname is configured, display that name with the last name.
• If none of the preceding are configured, display the LDAP user field of the FirstName and LastName. If there is no last name, display only the first name. If there is no first name, display only the last name.
• If no LDAP user fields are configured, display the LDAP UserID or the CUPS user ID.
• If a non-LDAP contact is added, the user can define the Display As name, first name, and last name.

The first thing you need to do is to configure an LDAP attribute map for the supported LDAP server and the CUPC client attributes. Several attribute mappings available enable you to manipulate information between the LDAP server and the CUPC client, but only one is required at the start to provide the functionality of adding users retrieved in an LDAP search to the CUPC client contact list. The following are the steps necessary to accomplish that task:

• Step 1. Navigate to Application > Cisco Unified Personal Communicator > Settings in the CUPS administration page, as shown in Figure 5-21.
  

  Figure 5-21 Configuring the User ID Format in CUPS

• Step 2. Select the type of LDAP server you want to configure in the drop-down menu.
• Step 3. Define the UserID field under the UPC User Fields to one of the following:
  • Microsoft Active Directory - sAMAccountName
  • Sun ONE - uid
• Step 4. Click Save.

After you correctly set the attributes, you can configure the LDAP server. The steps necessary to configure an LDAP server in CUPS are as follows:

• Step 1. Navigate to Application > Cisco Unified Personal Communicator > LDAP Server, as shown in Figure 5-22.
  

  Figure 5-22 Configuring the CUPC LDAP Server in CUPS

• Step 2. Click Add New.
• Step 3. Define the name of the LDAP server.
• Step 4. Define the FQDN hostname or the IP address.
• Step 5. Define the port number used by the LDAP server; 389 is the default.
• Step 6. Select the protocol to use. The default is TCP.
• Step 7. Click Save.

The final required configuration is the LDAP Profile. The required steps to configure an LDAP profile in CUPS follows:

• Step 1. Navigate to Application > Cisco Unified Personal Communicator > LDAP Profile in the CUPS administration page, as shown in Figure 5-23.
  

  Figure 5-23 Configuring the CUPC LDAP Profile in CUPS

• Step 2. Click Add New.
• Step 3. Define the name of the profile.
• Step 4. It is optional but recommended to define the Bind Distinguished Name field using an administrator-level account. Anonymous bind is available if wanted. The syntax can vary depending on the LDAP server used. Table 5-2 provides a guide to the syntax for Microsoft Active Directory and Sun ONE.
• Step 5. Define the LDAP bind password.
• Step 6. Define the search context to be used for LDAP user searches by the CUPC client. A single OU search context is supported. For example (Microsoft AD): CN=users,DC=cisco,DC=com
• Step 7. Check to perform a recursive search of the directory.
• Step 8. Select the primary LDAP server.
• Step 9. Select any backup LDAP servers.
• Step 10. Click Add Users to Profile.
• Step 11. Select the users for this voicemail profile.
• Step 12. Click Add Selected.
• Step 13. Click Save.

Table 5-2. Supported LDAP Directory Types and Naming Syntax

LDAP Server Type	Distinguished Name Syntax
Microsoft Active Directory	CN=Michael Popovich, CN=Users, DC=Contoso, DC=com
Sun ONE	cn=Michael Popovich, ou=Operations, o=Example Corp, st=CA, c=US

Upon completion of these steps, the CUPC users can search for contacts in the client and leverage the defined LDAP directory. When the search is completed on the client, the user has the option to IM, place an audio and video call to LDAP-defined contact numbers, initiate a web conference, and add the LDAP contact to the CUPC contact list.