[cisco-voip] Persistent Chat

[Chris Clouse]

Starting in IM&P 12.0, there is a External Database Cleanup Utility on the IM&P server to allow for a retention policy/purging to occur for those databases.

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/database_setup/12_0_1/cup0_b_database-setup-guide-1201/cup0_b_database-setup-guide-1201_chapter_0110.html

~Chris

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Erick Wellnitz
Sent: Wednesday, February 13, 2019 9:36 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.

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<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip&d=DwMFaQ&c=PzM68gSF_5r1R7BCE75oeA&r=Mtd_oRs0XS4YUZQRBEtJXoqyA13HyCrRFFUpCucX5ZI&m=HJh4qJQdNtGVKg-Y13gZJ0_R5b-pXRUKOA-5PMBYor8&s=_CyAQbqVesAOioe8mqM2m_sucXi1pWn83aJPag0-FZs&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190213/c620c7b2/attachment.html>