IM and Presence Service Overview
IM and Presence Service Administration is a web-based application that allows you to make individual, manual configuration changes to the IM and Presence Service nodes. The procedures in this guide describe how to configure features using this application.
IM and Presence Service offers a choice of either rich-featured Cisco Jabber Unified Communications clients or any third-party XMPP-compliant IM and presence client. IM and Presence Service also provides instant messaging, file transfer, and has the ability to host and configure persistent Group Chat Rooms.
In an on-premises deployment with IM and Presence Service and Cisco Unified Communications Manager, the following services are available:
-
Presence
-
Instant messaging
-
File Transfers
-
Audio Calls
-
Video
-
Voicemail
-
Conferencing
See Cisco Unified Communications Manager documentation for more.
IM and Presence Service Components
The following figure provides an overview of an IM and Presence Service deployment, including the main components and interfaces between Cisco Unified Communications Manager and IM and Presence Service.
![](/c/dam/en/us/td/i/300001-400000/350001-360000/351001-352000/351949.eps/_jcr_content/renditions/351949.jpg)
SIP Interface
You must configure the following to enable the SIP interface:
-
In Cisco Unified Communications Manager, you must configure a SIP trunk that points to the IM and Presence Service for the presence information exchange.
-
On the IM and Presence Service, configure Cisco Unified Communications Manager as a Presence Gateway so that IM and Presence Service can send SIP subscribe messages to Cisco Unified Communications Manager over the SIP trunk.
AXL/SOAP Interface
The AXL/SOAP interface handles the database synchronization from Cisco Unified Communications Manager and populates the IM and Presence Service database. To activate the database synchronization, the Cisco Sync Agent network service must be running..
By default, the Sync Agent load balances all users equally across all nodes within the IM and Presence Service cluster. However, you also have the option to manually assign users to a particular node in the cluster.
For guidelines on the recommended synchronization intervals when executing a database synchronization with Cisco Unified Communications Manager, for single and dual-node IM and Presence Service, see the IM and Presence Service SRND document.
![]() Note |
The AXL interface is not supported for application developer interactions. |
LDAP Interface
Cisco Unified Communications Manager obtains all user information via manual configuration or synchronization directly over LDAP. The IM and Presence Service then synchronizes all this user information from Cisco Unified Communications Manager (using the AXL/SOAP interface).
IM and Presence Service provides LDAP authentication for users of the Cisco Jabber client and IM and Presence Service user interface. If a Cisco Jabber user logs into IM and Presence Service, and LDAP authentication is enabled on Cisco Unified Communications Manager, IM and Presence Service goes directly to the LDAP directory for user authentication. When the user is authenticated, IM and Presence Service forwards this information to Cisco Jabber to continue the user login.
XMPP Interface
An XMPP connection handles the presence information exchange and instant messaging operations for XMPP-based clients. The IM and Presence Service supports ad hoc and persistent chat rooms for XMPP-based clients. An IM Gateway supports the IM interoperability between SIP-based and XMPP-based clients in an IM and Presence Service deployment.
CTI Interface
The CTI (Computer Telephony Integration) interface handles all the CTI communication for users on the IM and Presence node to control phones on Cisco Unified Communications Manager. The CTI functionality allows users of the Cisco Jabber client to run the application in desk phone control mode.
To configure CTI functionality for IM and Presence Service users on Cisco Unified Communications Manager, users must be associated with a CTI-enabled group, and the primary extension assigned to that user must be enabled for CTI.
To configure Cisco Jabber desk phone control, you must configure a CTI server and profile, and assign any users that wish to use the application in desk phone mode to that profile. However, note that all CTI communication occurs directly between Cisco Unified Communications Manager and Cisco Jabber, and not through the IM and Presence Service node.
Cisco IM and Presence Data Monitor Service
The Cisco IM and Presence Data Monitor monitors the IDS replication state on the IM and Presence Service. Other IM and Presence services are dependent on the Cisco IM and Presence Data Monitor so that they can delay startup until IDS replication is in a stable state.
The Cisco IM and Presence Data Monitor also checks the status of the Cisco Sync Agent sync from Cisco Unified Communications Manager. Dependent services are only allowed to start after IDS replication has set up and the Sync Agent on the IM and Presence database publisher node has completed its sync from Cisco Unified Communications Manager. After the timeout has been reached, the Cisco IM and Presence Data Monitor on the Publisher node will allow dependent services to start even if IDS replication and the Sync Agent have not completed.
On the subscriber nodes, the Cisco IM and Presence Data Monitor delays the startup of feature services until IDS replication is successfully established. The Cisco IM and Presence Data Monitor only delays the startup of feature services on the problem subscriber node in a cluster, it will not delay the startup of feature services on all subscriber nodes due to one problem node. For example, if IDS replication is successfully established on node1 and node2, but not on node3, the Cisco IM and Presence Data Monitor allows feature services to start on node1 and node2, but delays feature service startup on node3.
The Cisco IM and Presence Data Monitor behaves differently on the IM and Presence database publisher node. It only delays the startup of feature services until a timeout expires. When the timeout expires, it allows all feature services to start on the publisher node even if IDS replication is not successfully established.
The Cisco IM and Presence Data Monitor generates an alarm when it delays feature service startup on a node. It then generates a notification when IDS replication is successfully established on that node.
The Cisco IM and Presence Data Monitor impacts both a fresh multinode installation, and a software upgrade procedure. Both will only complete when the publisher node and subscriber nodes are running the same IM and Presence release, and IDS replication is successfully established on the subscriber nodes.
To check the status of the IDS replication on a node either:
-
Use this CLI command:
utils dbreplication runtimestate
-
Use the Cisco Unified IM and Presence Reporting Tool. The “IM and Presence Database Status” report displays a detailed status of the cluster.
To check the status of the Cisco Sync Agent, navigate to the Cisco Unified CM IM and Presence Administration interface and select Diagnostics > System Dashboard. You will find the Cisco Unified Communications Manager publisher node IP address as well as the sync status.