The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter provides information about the following topics:
Complete the following tasks, in sequence, on each server that you install in an IM and Presence Service cluster.
Caution | Ensure that you complete this post-installation checklist on the IM and Presence Service database publisher node before you install IM and Presence Service subscriber nodes. |
After you install IM and Presence, check to see if Cisco has released software updates, critical patches or Service Updates.
Software upgrades contain fixes that were unavailable at the time of the original release. They often include service updates, security fixes, firmware updates, critical patches or other software fixes that can improve operation.
Complete the following procedure to check for software upgrades.
Step 1 | Browse to www.cisco.com. |
Step 2 | Select . |
Step 3 | Navigate to . |
Step 4 | If there are any software upgrades, follow the instructions to download the software. |
Configure the Cisco Unified Communications Manager as a Presence Gateway.
Failover - Occurs in a presence redundancy group when one or more critical services fails on an IM and Presence Service node in the group or a node in the group fails. Clients automatically connect to the other IM and Presence Service node in that group.
Fallback - Occurs when a fallback command is issued from the Command Line Interface (CLI) or Cisco Unified Communications Manager during either of these conditions:
The failed IM and Presence Service node comes back into service and all critical services are running. The failed over clients in that group reconnect with the recovered node when it becomes available.
The backup activated IM and Presence Service node fails due to a critical service failure, and the peer node is in the Failed Over state and supports the automatic recovery fallback.
A critical service on Node A fails—A critical service (for example, the Presence Engine) fails on Node A. Automatic failover occurs and all users are moved to Node B. Node A is in a state called "Failed Over with Critical Services Not Running". When the critical service recovers, the node state changes to "Failed Over." When this occurs Node B tracks the health of Node A for 30 minutes. If no heartbeat is missed in this timeframe and the state of each node remains unchanged, automatic fallback occurs.
Node A is rebooted—Automatic failover occurs and all users are moved to Node B. When Node A returns to a healthy state and remains in that state for 30 minutes automatic fallback will occur.
Node A loses communications with Node B—Automatic failover occurs and all users are moved to Node B. When communications are re-established and remain unchanged for 30 minutes automatic fallback will occur.
You can manually initiate a node failover, fallback, and recovery of IM and Presence Service nodes in the presence redundancy group. A manual fallback operation is required unless the automatic fallback option is set.
You are required to change the default domain name for non-DNS deployments. Changing the domain name is optional for DNS deployments.
If your IM and Presence Service deployment does not use DNS, the domain name for the IM and Presence Service node is set to DOMAIN.NOT.SET during installation. Cisco recommends that you change this value to the enterprise domain value after installation is complete.
You must stop the following services on all nodes in the cluster before you change the domain name, and then restart those services after the changes are made:
For information about how to change the default domain name, see the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager.
For information about using domain names with Cisco Unified Communications Manager and system managed components, see the Cisco Unified Communications System Solution Reference Network Design (SRND) guide for your release.
Note | The IM address scheme that you choose must be consistent across all IM and Presence Service clusters. |
For more information about setting the IM address scheme for the IM and Presence Service cluster and Directory URI requirements, see the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager.
The UserID@Default_Domain IM address scheme is the default option when you perform a fresh install or upgrade IM and Presence Service from an earlier version. To configure the default domain, choose .
The Directory URI address scheme aligns a user's IM address with their Cisco Unified Communications Manager Directory URI.
Multiple domain support. IM addresses do not need to use a single IM and Presence Service domain.
Alignment with the user's email address. The Cisco Unified Communications Manager Directory URI can be configured to align with a user's email address to provide a consistent identity for email, IM, voice and video communications.
Alignment with Microsoft SIP URI. The Cisco Unified Communications Manager Directory URI can be configured to align with the Microsoft SIP URI to ensure that the user's identity is maintained when migrating from Microsoft OCS/Lync to IM and Presence Service.
Synchronize the Directory URI from the LDAP directory source.
If you add an LDAP directory source in Cisco Unified Communications Manager, you can set a value for the Directory URI. Cisco Unified Communications Manager then populates the Directory URI when you synchronize user data from the directory source.
Note | If LDAP Directory Sync is enabled in Cisco Unified Communications Manager, you can map the Directory URI to the email address (mailid) or the Microsoft OCS/Lync SIP URI (msRTCSIP-PrimaryUserAddress). |
Manually specify the Directory URI value in Cisco Unified Communications Manager.
If you do not add an LDAP directory source in Cisco Unified Communications Manager, you can manually enter the Directory URI as a free-form URI.
Caution | If you configure the node to use Directory URI as the IM address scheme, Cisco recommends that you deploy only clients that support Directory URI. Any client that does not support Directory URI will not work if the Directory URI IM address scheme is enabled. Cisco recommends that you use the UserID@Default_Domain IM address scheme and not the Directory URI IM address scheme if you have any deployed clients that do not support Directory URI. |
See the Cisco Unified Communications Manager Administration Guide for more information about setting up the LDAP directory for Directory URI.
Observe the following conditions when using the Directory URI IM address scheme:
All users have a valid Directory URI value configured on Cisco Unified Communications Manager.
All deployed clients must support Directory URI as the IM address.
The IM address scheme must be consistent across all IM and Presence Service clusters.
See the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager for detailed Directory URI IM address requirements and interactions.
During installation, if you select not to use DHCP, you must enter a hostname and IP address for the IM and Presence server. The hostname cannot be null, localhost, or an IP address. The IM and Presence node name gets its value by concatenating the DNS domain to this hostname value to form a fully qualified domain name (FQDN). This FQDN must be resolvable. If you do not use DNS in your deployment, then the IM and Presence node name, which is set to the server's hostname by default, is not resolvable. To overcome this, you must change the IM and Presence node name to be the server's IP address after installation is complete.
For information about how to change the IM and Presence node name, see Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager.
Note | You must complete this task on each server that you install in an IM and Presence cluster. |
You must configure Cisco Unified Communications Manager as a Presence Gateway on IM and Presence to enable the SIP connection that handles the availability information exchange between Cisco Unified Communications Manager and IM and Presence.
For more information about how to configure a Presence Gateway on IM and Presence, see the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager .
Configure a SIP Trunk on a Cisco Unified Communications Manager.
After you configure Cisco Unified Communications Manager as a Presence Gateway, you must configure a SIP PUBLISH trunk on Cisco Unified Communications Manager. See the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager for more information.
When you have configured the SIP PUBLISH trunk on Cisco Unified Communications Manager, you must then enable SIP PUBLISH on IM and Presence.
See the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager for more information.
The User Assignment Mode enterprise parameter is set to Balanced by default after an initial installation of IM and Presence Service. In balanced mode, users are automatically assigned to IM and Presence Service servers that are configured in a presence redundancy group when users are added to the cluster. No manual user assignment is required when the User Assignment Mode enterprise parameter is set to Balanced.
Note | For end users to receive the availability and Instant Messaging (IM) services of IM and Presence Service, use Cisco Unified CM Administration to assign end users to IM and Presence Service servers on your nodes and clusters. |
For more information about balanced and manual user assignments, and to set up IM and Presence Service servers for users, see the Cisco Unified Communications Manager Administration Guide .
You must activate the following services:
To activate the services, select
in Cisco Unified Serviceability.Note | You must complete this task on each server that you install in an IM and Presence cluster. |