The IM and Presence centralized deployment allows you to deploy your IM and Presence deployment and your telephony deployment in separate clusters. The central IM and Presence cluster handles IM and Presence for the enterprise, while the remote Cisco Unified Communications Manager telephony cluster handles voice and video calls for the enterprise.
The Centralized Deployment option provides the following benefits when compared to standard deployments:
The Centralized Deployment option does not require a 1x1 ratio of telephony clusters to IM and Presence Service clusters–you can scale your IM and Presence deployment and your telephony deployment separately, to the unique needs of each.
Full mesh topology is not required for the IM and Presence Service
Version independent from telephony–your IM andh Presence central cluster can be
running a different version than your Cisco Unified Communications
Manager telephony clusters.
Can manage IM and Presence upgrades and settings from the
Lower cost option, particularly for large deployments with many Cisco Unified Communications Manager clusters
Easy XMPP Federation with third parties.
With a 25K OVA template, and a six-node cluster with High Availability enabled, the IM and Presence Service central deployment supports up to 75,000 clients. To support 75K users with 25K OVA, default trace level for XCP router needs to be changed from Info to Error.
Interclustering for Centralized Deployment
Interclustering is supported between two Centralize cluster. Intercluster is tested with one cluster with 25K ( with 25K OVA) and another with 15K (with 15K OVA) devices and no performance issues were observed.
Centralized Deployment Setup vs Standard Deployments
The following table discusses some of the differences in setting up an IM and Presence Centralized Cluster Deployment as opposed to standard deployments of the IM and Presence Service.
Differences with Standard Deployments
The installation process for an IM and Presence central deployment is the same as for the standard deployment. However, with central deployments, the IM and Presence central cluster is installed separatelyfrom your telephony cluster, and may be located on separate hardware servers. Depending on how you plan your topology, the IM and Presence central cluster may be installed on separate physical hardware from your telephony cluster.
For the IM and Presence central cluster, you must still install
Cisco Unified Communications Manager and then install the IM and
Presence Service on the same servers. However, the Cisco Unified
Communications Manager instance of the IM and Presence central
cluster is for database and user provisioning primarily, and does
not handle voice or video calls.
Compared to standard deployments, the following extra configurations are required to set up the IM and Presence Service central deployment:
Users must be synced into both the telephony cluster and the IM
and Presence Service central cluster so that they exist in both
In your telephony clusters, end users should not be enabled for
IM and Presence.
In your telephony clusters, the Service Profile must include the
IM and Presence Service and must point to the IM and Presence
In the IM and Presence central cluster, users must be enabled
for the IM and Presence Service.
In the IM and Presence central cluster's database publisher node, add your remote Cisco Unified Communications Manager telephony cluster peers.
A DNS SRV that points to the publisher node of the connected telephony cluster is required. If you have an ILS network deployed, the SRV should point to the telephony hub cluster.
The following configurations, which are used withstandard
deployments of the IM and Presence Service, are not required with
Presence Gateway is not required.
SIP Publish trunk is not required.
A Service Profile is not required on the IM and Presence central
cluster–the Service Profile is configured on the telephony cluster
to which the central cluster connects
The following diagram highlights the cluster architecture for this deployment option. Cisco Jabber clients connect to multiple Cisco Unified Communications Manager clusters for voice and video calling. In this example, the Cisco Unified Communications Manager telephony clusters are leaf clusters in a Session Management Edition deployment. For Rich Presence, Cisco Jabber clients connect to the IM and Presence Service central cluster. The IM and Presence central cluster manages instant messaging and presence for the Jabber clients.
Your IM and Presence cluster still contains an instance for Cisco Unified Communications Manager. However, this instance is for handling shared features such as database and user provisioning–it does not handle telephony.
Figure 1. IM and Presence Service Centralized Cluster Architecture
Centralized Cluster Use Case
To connect your telephony and IM and Presence clusters, a new system for exchanging access keys is introduced. This diagram shows the flow for SSO logins:
-: Query DNS to get SRV record.
-: Query UDS to get the Home Cisco Unified Communications Manager cluster.
-: Get Access Token and Refresh Token from Cisco Unified Communications Manager cluster through SAML SSO.
: Read UC Service Profile. The service profile contains an IM and Presence profile and points to the IM and Presence central cluster.
: Client registers to the IM and Presence cluster using the same Access Token through SOAP and XMPP interfaces.
: The token is validated and a response is sent back to Jabber client.
Figure 2. IM and Presence Service Centralized Cluster Use Case
Centralized Deployment Prerequisites
The following prerequisites are required for the IM and Presence
Service centralized deployment:
In the telephony cluster, Cisco Unified Communications Manager must be running Release 9.1(x) or higher.
The telphony cluster cannot not have any IM and Presence Service cluster nodes. You cannot mix an IM and Presence Centralized Deployment with a Standard Deployment (IM and Presence Service on Cisco Unified Communications Manager) within the same cluster.
Cisco Jabber must be running Release 9.4 or higher.
The IM and Presence central cluster must have a DNS SRV record that points to the publisher node of the Cisco Unified Communications Manager telephony cluster. If your telephony deployment includes an ILS network, the DNS SRV must point to the hub cluster.
The Cisco AXL Web Service feature service must be running in all clusters. This service is enabled by default, but you can confirm that it is activated from the Service Activation window of Cisco Unified Serviceability.
Centralized Deployment Configuration Task Flow
Complete these tasks if you want to configure an IM and Presence centralized cluster deployment.
Enable IM and Presence Services on your centralized cluster. If you have an LDAP directory sync configured, you can use the Feature Group Template to enable IM and Presence Services for users.
If your deployment does not use an LDAP sync, you can use a csv file and the Bulk Administration Tool to enable Presence for end users. For details on how to use the Bulk Administration Tool, see the Bulk Administration Guide for Cisco Unified Communications Manager.
Log into the Cisco Unified CM Administration interface of the IM and Presence centralized cluster. This server should have no telephony configured.
Choose User Management > User Phone/Add > Feature Group Template.
Do one of the following:
Click Find and select an existing template
Click Add New to create a new template
Check both of the following check boxes:
Enable User for Unified CM IM and
Complete the remaining fields in the Feature Group Template
Configuration window. For help with the fields and their settings,
refer to the online help.
What to Do Next
To propagate the setting to users, you must complete an LDAP sync.
Use this procedure in your remote telephony clusters to create a service profile that points to the IM and Presence central cluster. Cisco Jabber clients will use this profile to find the IM and Presence central cluster.
Update Presence User Settings in Telephony Cluster
If you've already completed an LDAP sync in your telephony deployment, use the Bulk Administration Tool to edit user settings in the Telephony cluster for IM and Presence users. This configuration will point Presence users to the Central Cluster for the IM and Presence Service.
This procedure assumes that you have already completed an LDAP sync in your telephony cluster. However, if you haven't yet completed the initial LDAP sync, you can add the Central Deployment settings for
Presence users into your initial sync. In this case, do the following in your telephony cluster:
Configure a Feature Group Template that includes the Service
Profile that you just set up. Make sure that have the Home Cluster option selected and the Enable User for Unified
CM IM and Presence option unselected.
In LDAP Directory Configuration, add the Feature Group Template to your LDAP Directory sync.
Complete the initial sync.
For additional details on configuring Feature Group Templates and LDAP Directory, see the "Configure End Users" part of the System Configuration Guide for Cisco Unified Communications Manager.
From Cisco Unified CM Administration, choose QueryBulk Administration > Users > Update Users > Query.
From the Filter, select Has Home Cluster Enabled and click
Find. The window displays all of the end users for whom this is their Home Cluster.
Click Next. In the Update Users Configuration window, the check boxes on the far left indicate whether you want to edit this setting with this query. If you don't check the left check box, the query will not update that field. The field on the right indicates the new setting for this field. If two check boxes appear, you must check the check box on the left to update the field, and in the right check box, enter the new setting.
Under Service Settings, check the left check box for each of the following fields and then in the right check box or drop-down, edit the field settings as follows:
Home Cluster—Check the right check box to enable the telephony cluster as the home cluster.
Enable User for Unified CM IM and Presence—Leave the right check box unchecked. Presence users will use the IM and Presence central cluster for IM and Presence rather than the telephony cluster.
UC Service Profile—From the drop-down, select the service profile that you configured in the previous task.
Complete any remaining fields that you want. For help with the fields and their settings, see the online help.
For IM and Presence centralized clusters where there are more than one
remote telephony clusters, you can use the Intercluster Lookup
Service (ILS) to provision remote telephony clusters for the IM and
Presence central cluster. ILS monitors the network and propagates
network changes such as new clusters or address changes to the
This task flow focuses on ILS requirements around IM and Presence centralized cluster deployments. For additional ILS configuration around telephony, such as configuring Global Dial Plan Replication or URI Dialing, see the "Configure the Dial Plan" section of the System Configuration Guide for Cisco Unified Communications Manager.
Before You Begin
If you are deploying ILS, make sure that you have done the following:
Plan your ILS network topology. You must know which telephony clusters will be hubs and spokes.
The telephony cluster to which the IM and Presence central cluster connects must be a hub cluster.
You must configure a DNS SRV record that points to the publisher node of the hub cluster.
Log into Cisco Unified CM Administration on the publisher node of your telephony cluster.
Choose Advanced Features > ILS Configuration.
From the Role drop-down list box, select Hub Cluster or Spoke Cluster depending on which type of cluster you are setting up.
Check the Exchange Global Dial Plan Replication Data with Remote
Clusters check box.
Configure ILS Authentication Details.
If you want to use TLS authentication between the various clusters, check the Use TLS Certificates check
If you use TLS, you must exchange CA-signed certificates
between the nodes in your cluster.
If you want to use password authentication (regardless of
whether TLS is used), check the Use Password check box and enter
the password details.
In the ILS Cluster Registration popup, configure your registration details:
In the Registration Server text box, enter the publisher node IP address or FQDN for the hub cluster to which you want to connect this cluster. If this is the first hub cluster in your network, you can leave the field blank.
Make sure that the Activate the Intercluster Lookup Service on the
publisher in this cluster check box is checked.
Repeat this procedure on the publisher node of each telephony cluster that you want to add to the ILS network. Depending on the sync values that you configured, there may be a delay while the cluster information propagates throughout the network.
If you chose to use Transport Layer Security (TLS) authentication between clusters, you must exchange Tomcat certificates between the publisher node of each cluster in the ILS network. From Cisco Unified Operating System Administration, use the Bulk Certificate Management feature to:
Export certificates from the publisher node of each cluster to a central location
Consolidate exported certificates in the ILS network
Import certificates onto the publisher node of each cluster in your network
For details, see the "Manage Certificates" chapter of the Administration Guide for Cisco Unified Communications Manager.
Use this procedure to confirm that your ILS network is up and running.
Log in to the publisher node on any of your telephony
From Cisco Unified CM Administration choose Advanced Features > ILS Configuration.
Check the ILS Clusters and Global Dial Plan Imported Catalogs
section. Your ILS network topology should appear.
Centralized Deployment Field Descriptions
From Cisco Unified CM IM and Presence Administration, choose System > Centralized Deployment to access the Centralized Deployment window. If you are deploying the IM and Presence Centralized Cluster deployment, you can create connections to your remote Cisco Unified Communications Manager clusters in this configuration window.
Click the Add New button to add a Cisco Unified Communications Manager cluster. Click Synchronize Selected to synchronize access keys with the remote cluster.
Table 2 Centralized Deployment Field Descriptions
The FQDN, hostname, IPv4 address, or IPv6 address of the remote Cisco Unified Communications Manager cluster publisher node.
The Peer Address cannot point to any IM and Presence Service node or to the Cisco Unified Communications Manager instance of another IM and Presence Service central cluster.
Peer AXL Username
The login username for the AXL account on the remote cluster.
Peer AXL Password
The password for the AXL account on the remote cluster.
Displays the current sync status with the remote cluster.
Displays the last time a sync occurred with the remote cluster.
Save and Synchronize
After you have entered your details, click this button to save your settings and to sync access keys with the remote cluster.
Centralized Deployment Interactions and Restrictions
ILS Hub Cluster
If the ILS hub cluster is down, and more than one telephony cluster exists, the Central Cluster feature does not work.