Deploying Availabilty and IM Functionality
Back to configuration example overview page: Sample Configuration Workflow for Deploying Cisco Unified Presence with Cisco Unified Personal Communicator
In this module , we will demonstrate how to set up and verify a basic availability and IM deployment. This will allow your CUPC users to add contacts, view user availability, receive incoming IMs, initiate outgoing IMs and participate in group chat rooms. Assumptions:
- CUP is installed
- CUCM is installed
- Active Directory is installed
- Postgres is installed and configured as per....
Creating your Users on Active Directory
Create the users Charles Holland, Sue Miller and Neena Patel on the Active Directory server.
The steps below show you how to create the user Charles Holland. Repeat these steps to create users Sue Miller and Neena Patel.
Before You Begin: Create the Example.com branch in Active Directory, and create an ExampleUsers folder.
Right-click on the ExampleUsers folder in the Example.com branch, and select New > User.
Create the user Charles Holland.
Define a password for the user Charles Holland.
Select Finish to save the user data for Charles Holland.
Right-click on the user Charles Holland to edit the user properties.
In the General tab, define a telephone number and email address for user Charles Holland.
In the Telephones tab, define a mobile number for Charles Holland (if required).
In the Organization tab, define the organizational details for user Charles Holland.
Repeat the steps above to create users Sue Miller and Neena Patel on Active Directory.
Creating the LDAP Search Account on Active Directory
You must create an LDAP search account in Active Directory. This is a basic user account which the CUPC client uses to authenticate when searching the AD server using LDAP.
Right-click on the Users folder in the Example.com branch, and select New > User.
Create the LDAP search user.
Create a password for the LDAP search user.
When you save the LDAP search user, the new user entry will appear in the main Users folder.
Activating and Verifying Services on Cisco Unified Communication Manager
On Cisco Unified Communication Manager, select Tools > Service Activation in the Serviceability GUI. Activate the service indicated below.
Select Tools > Control Center - Feature Services. Verify that these services are now running.
Select Tools > Control Center - Network Services. Verify that these services are now running.
Configuring LDAP Integration on Cisco Unified Communications Manager
Enable LDAP Synchronization on Cisco Unified Communications Manager to sync your users from Active Directory. On Cisco Unified Communications Manager, select System > LDAP > LDAP System in the Administration GUI.
Configure your LDAP Directory. On Cisco Unified Communications Manager, select System > LDAP > LDAP Directory in the Administration GUI. Select Add New. Accept the information messages that display.
Configure the LDAP server credentials.
Configure the LDAP synchronization settings.
Configure the LDAP server information, and then save your configuration.
Select Perform Full Sync Now to synchronize the user information from Active Directory to CUCM.
Enable LDAP Authentication for the users you sync from Active Directory. Select System > LDAP > LDAP Authentication, and check Use LDAP Authentication for End Users.
Enabling Users Capabilities on CUCM
Select System > Licensing > Capabilities Assignment, and select a user.
Assign CUP and CUPC capabilities to the selected user. Perform this procedure for each user.
Starting the Directory Sync Service on CUCM
Select Tools > Service Activation in the Serviceability GUI, and activate the Cisco DirSync service.
Verify that the Cisco DirSync service is running. Select Tools > Control Center – Feature Services.
Verify that the Cisco DirSync service has a status of 'Activated'.
Adding CUP as an Application Server on CUCM
Select System > Application Server in the Administration GUI, and select Add New.
Select Cisco Unified Presence Server as the application server type.
Define the application server entry details as shown below, and save your configuration.
Activating Services on CUP
In the Serviceability GUI on CUP, select Tools > Service Activation. Activate the services shown below.
Configuring the External Database on CUP
In order to support the Compliance and/or Persistent Chat functionality in your deployment, you must have deployed an external PostgresSQL database. You must configure the external database details on CUP. In the Administration GUI, select Messaging > External Database Setup > External Databases, and select Add New.
Note! In the Example Solutions Inc lab deployment, the PostgresSQL database is installed on the same server as Active Directory.
Configure and save an external database called ‘tcmadb’ as shown below.
Configuring the Compliance Settings on CUP
In the Administration GUI, select Messaging > Compliance. Select Message Archiver as the compliance server type, and assign the external database ‘tcmadb’ to your CUP node.
Configuring Group and Persistent Chat Settings on CUP
In the Administration GUI, select Messaging > Group and Persistent Chat. Check Enable Persistent Chat, and configure the chat settings as shown below.
Assign the external database ‘tcmadb’ (that you configured previously) as the chat database.
Restarting the Chat Services on CUP
Click on the service notification in the Administration GUI.
Select a server from the menu.
In the Serviceability GUI, restart the XCP Router and XCP Message Archiver services.
Select Tools > Control Center - Network Services.
Restart the Cisco XCP Router service.
Configuring LDAP Server and Profile on CUP
You need to configure the Active Directory details (LDAP server) on CUP. In the Administration GUI, select Application > Cisco Unified Personal Communicator > LDAP Server. Select Add New.
Configure the Active Directory server information as shown below, and save your configuration.
Select Applications > Cisco Unified Personal Communicator > LDAP Profile.
Select Add New.
Configure the LDAP Profile as shown below.
Check Make this the default LDAP Profile for the system.