Instant Messaging Compliance for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1)
Integration with third-party compliance servers
Downloads: This chapterpdf (PDF - 472.0KB) The complete bookPDF (PDF - 2.32MB) | Feedback

Integration with third-party compliance servers

Integration with third-party compliance servers

About Third-Party IM compliance

As an alternative to IM compliance, you can integrate IM and Presence with a third-party compliance server. With this solution, IM and Presence only delivers messages to users after it successfully logs the message to a third-party compliance server. If the compliance server is unavailable, IM and Presence does not deliver the message to the recipient.

Third-party IM compliance requires these components:

  • IM and Presence Service Release 9.0(1) - IM and Presence uses the Event Broker component to send messages to the third-party compliance server.
  • Third-party compliance server - You require a third-party compliance server for each node in the cluster.
  • 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 IM and Presence Service does not provide a secure TLS/SSL connection between IM and Presence and the third-party compliance server.


To use the third-party compliance solution you must configure a third-party compliance server for each node in the cluster. IM and Presence passes all messages that are sent to or from any users associated with a node to the designated third-party compliance server for that node. The third-party compliance server applies any relevant policy or filtering to the message, and then passes the message back to IM and Presence. IM and Presence delivers the message to the recipient. Note that you may potentially experience performance delays in your network because of the volume of messages that pass between IM and Presence and the third-party compliance server. If IM and Presence loses its connection to the third-party server, all IM traffic stops. The following figure highlights these components and message flow.

Figure 1. Third-Party IM Compliance



Configure third-party IM compliance server on IM and Presence

Before You Begin
  • Install and configure the third-party compliance server(s)
  • Install the IM and Presence servers as described in Installing Cisco Unified Communications Manager .
  • Configure the IM and Presence servers as described in the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager .
Procedure
    Step 1   Select Cisco Unified CM IM and Presence Administration > External Server Setup > Third-Party Compliance Servers.
    Step 2   Select Add New.
    Step 3   Enter the server details.
    Step 4   Enter a value for the Restart Interval. If you want to restart the connection to the third-party compliance component if it should fail, enter the number of seconds at smaller or larger restart intervals as required. If you change this setting, you must restart the Cisco XCP Router service.
    Step 5   (Optional) Select Enable Packet Size Limits to restrict amount of data transferred to the third-party server.
    Step 6   Click Save.
    Step 7   Restart the Cisco XCP Router Service.

    Troubleshooting Tip

    Use caution when changing these settings. If you save any changes, you will lose all previous configuration settings.


    Related References

    Assign third-party compliance server to IM and Presence node

    Before You Begin

    Configure a third-party IM compliance server on IM and Presence.

    Procedure
      Step 1   Select Cisco Unified CM IM and Presence Administration > Messaging > Compliance.
      Step 2   Select Third-Party Compliance Server from the Compliance Server Selection.
      Step 3   Assign a third-party IM compliance server to a IM and Presence node in the Third-Party Server Assignment window.
      Step 4   Select Save.
      Step 5   Restart the Cisco XCP Router Service.

      Troubleshooting Tips

      If you switch between IM compliance deployment options (for example, switch from the Message Archiver option to the Third-Party Compliance Server option), you must restart the Cisco XCP Router Service.