Suggestions on quick VM archiving process?

[jhloaded]

A part of our terminated employee exit process now includes the archiving of voicemail files. Currently, I am loading up the user's ShoreTel user into the Personal Call Manager and opening the VM manager to export each VM one by one.

Does anyone have a suggestion on a quicker way of doing this?

[Palitto Consulting]

You could just grab the folder of wave files for that user from under Shoreline Data. If you want something more advanced, we could write a bulk VM mover or exporter for you fairly easily.

[jhloaded]

Perhaps the way they are being stored changed in 8.x. We are currently using 7.5 so the extension folders only contain the .dat file and greeting .wav's.

All of the voicemails sit in a folder above that level and have a generated file name so there isn't a way to tell who the voicemail belongs to.

[Palitto Consulting]

Right, sorry, I knew there was a folder for each extension but now I remember that those just store greetings. It is the same on 8.1.

[Palitto Consulting]

Please see this application. It must be run on a machine having Call Manager installed.

http://web.palittoconsulting.com/Pub...rder-1.0.0.zip

(We provide no warranty or liability, and have tested it against Shoretel 8.1 only)

[The Conman]

Does anyone have a particular process in place for newer versions of ShoreTel? We're running 14.x. I'm curious what others may be doing.

[tekkyn00b]

I just finished writing this.

http://pastebin.com/ienjPfjY

Definitely read through it first and customize it the way you need for your environment, but after testing, this is SUPER handy. Just tested on our Help Desk workgroup mailbox, and I exported about 40 voicemails in maybe 2 seconds, with each WAV renamed to the date the message was left, as well as the caller ID if available. (ex. 2016-0301_+11234567890.wav).

Naturally our VAR is hesitant to give the okay to use this, but after lots of testing on my own mailbox, my co-workers', and our WorkGroup, I'm confident in it enough to use in our environment. Obviously make sure you're taking snaps of your HQ/DVS or have backups ahead of time, but there's nothing in there that makes any modifications to HQ/DVS. Basically, it's just copying the WAVs to a folder on your Desktop, and then it renames the WAVs that are now on your local computer.

I wrote it for running on my Mac, but you can run it on linux if you need. But again, customize it for your environment. I'm sure there's a way to adapt some of this to PowerShell, but *shrug*.

And yeah, you assume all risks and responsibilities associated with running this. This works in our environment, but as it is currently written, there's a strong chance it will not work in yours without customizing the paths and such.

Oh, and we're on 14.2.