Overview of IM Logging and Archiving
Cisco WebEx Messenger allows you to log and archive Instant Messages (IMs) that users in your organization exchange with each other or with users outside your organization. IM logging and archiving allows your organization to monitor and review IM exchanges. In most cases, this is done to comply with the enterprise's information audit processes.
You can enable IM logging and archiving for users in your Cisco WebEx Messenger organization. Cisco WebEx Messenger can send the logged messages for archival to the following archival solutions:
HP Autonomy DRC-CM and Global Relay Message Archiver are Saas-based message archiving services.
Information logged in an IM session
The following is logged in an IM session:
Restrictions for logged IM users
The following restrictions are applicable for logged IM users:
IMs are temporarily stored in Cisco data centers before they are transmitted to the customer's servers over a secure channel. Once the transmission is complete, these IMs are permanently deleted from Cisco data centers. The following graphic shows the IM logging and archiving process.
IM archiving notifications
By setting up IM archiving notifications you can choose whether or not to notify users that their IMs are being archived. This notification is sent by the system, and the the default message text is shown below.
All instant messages sent in this session to and from this account, as well as the initiation and termination of any other communication modes (e.g. voice call, video call) will be logged and are subject to archival, monitoring, or review and/or disclosure to someone other than the recipient.
However, you can choose to override the default message text to suit your organization’s requirements. For more information, see Setting up IM archiving notifications.
When one or more IM logged users are engaged in a one-to-one or group chat, the system sends a notification message to all users involved that their conversation is being logged and archived by one or more of the user’s organizations.
IM logging and archiving notification frequency
Notifications are sent to all users in a conversation, one for each logged user in the conversation. For example, if five users are in a group chat where three are logged, three notifications are sent to all five users. The exceptions to this are as follows:
The system does not send notifications for specific conversations more than once an hour. However, there are cases where notifications are sent more often. For example, if users leave and rejoin a group chat, are on multiple IM applications simultaneously, or sign out and back in again.
If a logged user signs out and back in, all notification tracking timeouts are reset for that user.
After a notification timeout expires, no new notifications are sent unless there is new activity, such as the exchange of IM's or users joining group chats.
Defining an IM archiving endpoint
Setting up IM archiving for your Cisco WebEx Messenger organization involves configuring the archiving endpoint in Cisco WebEx Messenger Administration Tool. The IM archiving endpoint is the place to which the logged IM data is sent. You can configure multiple endpoints.
Endpoint configuration involves specifying the following parameters:
To learn how to set up IM archiving endpoints, see Setting up IM Archiving.
After configuring IM archiving endpoints, you need to assign users in your Cisco WebEx Messenger organization to be logged. There are several provisioning methods that allow you to assign users to be logged as listed below:
Enabling IM Logging and Archiving for your organization
IM Archiving is a separate solution that you need to get provisioned from Cisco WebEx. For information on how get IM Archiving provisioned for your organization, contact your Cisco WebEx Customer Success Manager.
Provisioning information is displayed in Cisco WebEx Administration Tool under Resource Management in the Configuration tab. IM Archiving will not work for users over and above the number of users your Cisco WebEx Messenger organization has been provisioned with. For more information, see Specifying resource management information.
|Top of Page|