Requirement for voicemails to be marked read in order to archive

[Lee Cramman]

I'm hitting a problem in an instance whereby only email is ever used to handle voicemails (never the app) so the voicemails are never marked as read and so never get archived. The voicemail directory just balloons until it hits quota.

There are strict legal reasons why they can't use send and delete on those voicemails and must archive them instead.

Has anyone else hit this issue and found a solution?

Any advice on an easy, non-manual way of marking >490,000 voicemails as read in one go (that's on a single extension)?

Thanks

PS - devs, a feature to send voicemail via email and archive (rather than send by email and delete) might be a useful and lightweight development

 

[Lee Cramman]

Managed to bulk set the existing ones (so don't need to manually go through one by one) but the issue remains going forward.

 

[Charles_3CX]

Regarding your question, please note that, as you have noticed, currently, the only way emails will be archived is when they have been heard and set to listen.

 

[Lee Cramman]

Thanks @Charles_3CX - just wondering if anyone has found an alternative approach to this. I did see a suggestion online of having a simple script that modifies the metadata, but I'm not keen on that idea as it makes the install non-standard.

 

[SteveITS]

I know you can bulk delete in the web GUI, via impersonation, not sure about marking them read.

 

[SweetAction]

Marking them as read is something you can do in the web ui and anything you can do in the webui can be done via the API as well.
I'd likely grab a Raspberry Pi or whatever and setup a script to login and mark all vmails are read once a day as needed. Certainly something built in would be good, I wonder if I could code a CFD to execute the script even.

Food for thought

 

[Lee Cramman]

Marking them as read is something you can do in the web ui and anything you can do in the webui can be done via the API as well.
I'd likely grab a Raspberry Pi or whatever and setup a script to login and mark all vmails are read once a day as needed. Certainly something built in would be good, I wonder if I could code a CFD to execute the script even.

Food for thought

That is a great idea, thanks - I'll dig in.