[cisco-voip] Persistent Chat

[Parker Pearson - Donoma]

If you are interested, one StoneScribe solution (https://www.donomasoftware.com/donoma-stonescribe/)  will manage this.

StoneScribe will manage those chats to the end of their lifecycle and then not only delete them – they are file-shredded.  There’s a lot StoneScribe does… but for your problem here, I’ve limited my comments to that issue.

We sell through Cisco resellers around the world, so you can either reach out to them – or you can start with contacting us direct and we can loop in your integrator of choice.

Cheers,

Parker Pearson


Parker 
Pearson
Vice President, Marketing & Business Development
Donoma Software
1750 Kraft Dr. Suite 1200 Blacksburg, VA 24060
t: 540.443.3577
e: parker at donomasoftware.com
w: www.donomasoftware.com

The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.
From: cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of Erick Wellnitz <ewellnitzvoip at gmail.com>
Date: Wednesday, February 13, 2019 at 10:37 AM
To: Anthony Holloway <avholloway+cisco-voip at gmail.com>
Cc: Cisco VoIP Group <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Persistent Chat

If I ever find out what the customer does I'll definitely update everyone.  I may even write something in the lab to share if I ever get some time.

I'd imagine a python script on a small linux host could run every night to clean up old entries.




________________________________

The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.
On Tue, Feb 12, 2019 at 10:05 AM Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway%2Bcisco-voip at gmail.com>> wrote:
Oh I see.  Well, since Cisco does mention the following:

"We recommend that you maintain the external database according to the best practice guidelines described in the product documentation. If you do not properly maintain the external database, and you allow the external database to fill up, this causes performance problems in the IM and Presence Service cluster."

It stands to reason that you could just use the method you described initially, which is to have your SQL admin write the procedure to delete records older than X days.

Good luck, and I'd be curious to know which route you take.

On Tue, Feb 12, 2019 at 8:56 AM Erick Wellnitz <ewellnitzvoip at gmail.com<mailto:ewellnitzvoip at gmail.com>> wrote:
That works for what loads in Jabber  but they're concerned with the messages existing in the database which makes them fair game for legal discovery.

On Mon, Feb 11, 2019 at 7:59 PM Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway%2Bcisco-voip at gmail.com>> wrote:
Is it not just the setting labeled  Maximum number of messages that can be retrieved from the archive?

On Mon, Feb 11, 2019 at 11:12 AM Erick Wellnitz <ewellnitzvoip at gmail.com<mailto:ewellnitzvoip at gmail.com>> wrote:
All,

With the introduction of WebEx Teams the request for persistent chat isn't so common anymore.

I have a client asking about it and how we can limit how long messages are kept in persistent chat.

I can't find a native way to do that but was thinking if IM&Presence doesn't index the database independently an SQL admin could write a procedure to remove entries older than x days.

Any thoughts?
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190213/d882c823/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image183372.png
Type: image/png
Size: 737 bytes
Desc: image183372.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190213/d882c823/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image421177.png
Type: image/png
Size: 762 bytes
Desc: image421177.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190213/d882c823/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image846049.png
Type: image/png
Size: 706 bytes
Desc: image846049.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190213/d882c823/attachment-0002.png>