continue to see
> the messages past the purge date. CSCvk74438
>
> ~Chris
>
> -Original Message-
> From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of
> Pawlowski, Adam
> Sent: Thursday, February 14, 2019 11:05 AM
> To: 'cisco-voip@p
Chris
-Original Message-
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of
Pawlowski, Adam
Sent: Thursday, February 14, 2019 11:05 AM
To: 'cisco-voip@puck.nether.net'
Subject: Re: [cisco-voip] Persistent Chat
When we evaluated the cleanup jobs when 12.0 came
6:48 PM
To: Pawlowski, Adam
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Persistent Chat
Is this the white paper you are talking about?
https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cucm/im_presence/database_setup/BestPractices/Cisco_IMP_ExtDB_WP.pdf
On Thu, Feb 14, 2019
Is this the white paper you are talking about?
https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cucm/im_presence/database_setup/BestPractices/Cisco_IMP_ExtDB_WP.pdf
On Thu, Feb 14, 2019 at 11:05 AM Pawlowski, Adam wrote:
> When we evaluated the cleanup jobs when 12.0 came out, it didn't
When we evaluated the cleanup jobs when 12.0 came out, it didn't actually work.
It may now in a SU but 12.0 is sort of the stepchild and didn't get much
attention so we're ignoring it.
The best practices whitepaper explains the tables and sample jobs to clean it
up, so we just added cleanup jo
is*
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Erick Wellnitz
> *Sent:* Wednesday, February 13, 2019 9:36 AM
> *To:* Anthony Holloway
> *Cc:* Cisco VoIP Group
> *Subject:* Re: [cisco-voip] Persistent Chat
>
>
>
> If I ever f
>
> *~Chris*
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Erick Wellnitz
> *Sent:* Wednesday, February 13, 2019 9:36 AM
> *To:* Anthony Holloway
> *Cc:* Cisco VoIP Group
> *Subject:* Re: [cisco-voip] Persistent Chat
>
database-setup-guide-1201_chapter_0110.html
~Chris
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Erick
Wellnitz
Sent: Wednesday, February 13, 2019 9:36 AM
To: Anthony Holloway
Cc: Cisco VoIP Group
Subject: Re: [cisco-voip] Persistent Chat
If I ever find out
any copies of this information.
From: cisco-voip on behalf of Erick
Wellnitz
Date: Wednesday, February 13, 2019 at 10:37 AM
To: Anthony Holloway
Cc: Cisco VoIP Group
Subject: Re: [cisco-voip] Persistent Chat
If I ever find out what the customer does I'll definitely update everyone. I
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 <
a
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, th
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-v...@gmail.com> wrote:
> Is it not just the setting labeled Maximum number of
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
wrote:
> All,
>
> With the introduction of WebEx Teams the request for persistent chat isn't
> so common anymore.
>
> I have a client asking abou
That's pretty slick. Thank you!
On Mon, Feb 11, 2019 at 2:44 PM Ryan Huff wrote:
> Erick,
>
> Here is a web front end I wrote for the compliance dB.
>
> If you’re handy with PHP, you could add a delete / prune function fairly
> easy. Or perhaps the easier thing in your case, is to just reverse
Erick,
Here is a web front end I wrote for the compliance dB.
If you’re handy with PHP, you could add a delete / prune function fairly easy.
Or perhaps the easier thing in your case, is to just reverse engineer the
script and grab the queries and pass those along to your customer’s SQL admin..
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 i
16 matches
Mail list logo
