Instant Messaging Compliance Guide for Cisco Unified Presence Release 8.0, 8.5 and 8.6
Planning for IM Compliance
Downloads: This chapterpdf (PDF - 344.0KB) The complete bookPDF (PDF - 855.0KB) | Feedback

Planning for IM Compliance

Table Of Contents

Planning for IM Compliance

About Cisco Unified Presence IM Compliance

Cisco Unified Presence IM Compliance Components

Sample Topologies and Message Flow for IM Compliance

Single Cluster Configuration

Intercluster or Federated Network Configuration

Prerequisite Configuration Tasks

Support for PostgreSQL 9.1.1


Planning for IM Compliance


Revised: April 30, 2013

About Cisco Unified Presence IM Compliance

Prerequisite Configuration Tasks

About Cisco Unified Presence IM Compliance

Cisco Unified Presence IM Compliance Components

Sample Topologies and Message Flow for IM Compliance

Many industries require that instant messages adhere to the same regulatory compliance guidelines as are all other business records. To comply with these regulations, your system must log and archive all business records, and the archived records must be retrievable.

Cisco Unified Presence provides support for instant messaging (IM) compliance by collecting data for the following IM activities in single cluster, intercluster, or federated network configurations:

Point-to-point messages

Group chat - This includes ad-hoc, or temporary chat messages, and permanent chat messages.

Cisco Unified Presence IM Compliance Components

Cisco Unified Presence IM compliance includes these components:

Cisco Unified Presence server, Release 8.0 or higher—Cisco Unified Presence uses the Message Archiver component for logging messages to the external database.

External database—For information on supported external databases, see the Database Setup Guide for Cisco Unified Presence.

IM Client—Supported clients include Cisco clients such as Cisco Jabber; third-party XMPP clients, and other third-party clients used in federated networks.


Note The Cisco Unified Presence IM compliance provides a basic IM logging solution. If you require a more granular logging solution, for example logging based on policy, use the third-party compliance solution, see the appendix module for details.


Related Topics

Database Setup Guide for Cisco Unified Presence

Integrating with Third-Party Compliance Servers

Sample Topologies and Message Flow for IM Compliance


Note The external database requirements defined in this section depend on the capacity of your servers.


Cisco Unified Presence IM Compliance provides logging of all compliance related data to an external database. All IM traffic passes through the Cisco Unified Presence Server (via the Message Archiver component) and is simultaneously logged to the external database. Each IM log contains the sender and recipient information, the timestamp, and the message body.

For ad-hoc group chat messages, by default Cisco Unified Presence logs multiple copies of the same message to the external database, one copy for each recipient. This identifies what users in the ad-hoc group chat received the message.

Depending on the XMPP client you deploy, you may also notice this behavior:

Cisco Unified Presence may log an incoming message to the external database twice. This occurs because some XMPP clients do not support the ability to 'learn' the full JID, or address, of the other party in the conversation. Consequently the XMPP client forks the message to all active clients for the user (all clients that the user is currently signed into), and Cisco Unified Presence then logs all forked messages to the external database.

Cisco Unified Presence may log the first message in a chat to the external database twice. This occurs until the XMPP client `learns' the full JID, or address, of the other party in the conversation.

If Cisco Unified Presence loses its connection to the external database, it continues to send and deliver IMs to users, and users can still create (ad-hoc) chat rooms. However with no connection to the external database, Cisco Unified Presence does not log any of these IMs so it does not support permanent group chat. Cisco Unified Presence raises an alarm if the connection to the external database is lost.

Single Cluster Configuration

When using Cisco Unified Presence IM Compliance in a single cluster, we highly recommend that you deploy one external database per cluster to which all incoming messages sent to users in the cluster are logged.


NoteFor IM Compliance, we highly recommend that you deploy one external database per cluster. However, depending on your requirements, you can configure more than one external database per cluster, or share an external database between clusters.

If you deploy the Group Chat feature, you require one external database per node in a cluster. See the Database Setup Guide for Cisco Unified Presence.


Figure 1-1 highlights these components and message flow. By default Cisco Unified Presence IM Compliance logs inbound messages to the external database, however you can configure the feature to also log outgoing messages.

Figure 1-1 Cisco Unified Presence IM Compliance for a Single Cluster

Intercluster or Federated Network Configuration

When using Cisco Unified Presence IM Compliance in an intercluster or federated network configuration, you must configure an external database per cluster. Additionally, you should configure the Cisco Unified Presence server to log both incoming and outgoing messages. Otherwise, each database will retain only half of the conversation. Figure 1-2 highlights these components and message flow.

Figure 1-2 Cisco Unified Presence IM Compliance for a Multiple Clusters

Prerequisite Configuration Tasks

Before you use this guide to configure IM compliance, make sure that you have performed the following tasks:

Install the Cisco Unified Presence servers as described in the Installation Guide for Cisco Unified Presence.

Configure the Cisco Unified Presence servers as described in the Deployment Guide for Cisco Unified Presence.

Set up the external database as described in the Database Setup Guide for Cisco Unified Presence.

Support for PostgreSQL 9.1.1

To deploy PostgreSQL version 9.1.1 as the external database, you must set the following values in the postgresql.conf file:

escape_string_warning = off
standard_conforming_strings = off
 
   

After you configure these parameters, you must restart PostgreSQL. For more information about how to configure the postgresql.conf file and restart PostgreSQL, see the Database Setup Guide for Cisco Unified Presence.

Related Topics

Installation Guide for Cisco Unified Presence:

http://www.cisco.com/en/US/products/ps6837/prod_installation_guides_list.html

Deployment Guide for Cisco Unified Presence:

http://www.cisco.com/en/US/products/ps6837/products_installation_and_configuration_guides_list.html

Database Setup Guide for Cisco Unified Presence:

http://www.cisco.com/en/US/products/ps6837/products_installation_and_configuration_guides_list.html