Exchange 2007 move voice messages to folder (Cisco Unity)

We are attempting to deploy Cisco Unity for our voice messages on an Exchange 2007 Enterprise system. We are running into an issue because we have a significant number of users that use POP3 clients. When the POP3 clients check for new email, it either:

1) Marks the voice messages as read; thereby removing the new VM light on their Cisco phones. This also means the messages are not marked as new when manually checking the voice messages via the phone. This occurs when the POP3 clients is set to keep the messages on the server.
2) Removing the voice messages completely (not even accessible via the phone). This occurs when they do not save the messages on the server in the POP3 client.

Unfortunately, this is not acceptable to our users. They need to be able to reach their vice messages via their phone. Also, it is not feasible at this time to convert all users to OWA or Outlook in Exchange mode.

One possible solution that was thrown out there was to place the voice messages in a folder (i.e. a managed folder called Voicemail). However, we did not see a way to have Unity place the messages in this folder directly. We also looked at the Exchange side of things and could not figure out a way to move messages to a folder, except via a server-side rule on each user's mailbox. I saw some scripting with MAPI that made it sound possible to add a rule to all accounts, although very ugly, was for Exchange 2000/2003 only, and unmanageable long-term.

We don't know if any of these options are possible and we just missed something, or if there is another option we didn't think of yet. Anything an expert can provide to guide us in the right path would be a huge help. Also, I deal with the Exchange side of things, not the phone system or Unity, so please be very descriptive and patient with anything involving that area.

Thanks experts.
LVL 12
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Glen KnightCommented:
Unfortunately what your seeing is the behaviour of POP3 that is how it is designed to work.

From what I remember if cisco unity there is no way to specify the folder for the voicemail message and the only way you would achieve this would be to use a serverside rule for each user.

I would just turn off email delivery of voicemail for these users until you have migrated them over to using exchange services rather than POP3

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
geowrianAuthor Commented:
Thanks, demazter. I'll wait a bit to see if anybody else has something else to add or try. Or even a script to add the server rule for users to at least make it feasible in some manner.

Unfortunately, that's what we've been seeing as well. As for migrating everybody, that likely won't be for a couple years - we have over 5,000 mailboxes. Our users use clients ranging from Outlook (in POP3 mode) to Thunderbird to Eudora to Pegasus to Incredimail to Mac Mail & Entourage to others. Getting everybody to one system is going to be difficult in both possible push back as well as training and migration.
Glen KnightCommented:
You can create server side rules via script.

I have to tell you I have never done it but you might want to have a look at the following:
geowrianAuthor Commented:
Thanks again. I'll keep that in mind. I was hoping for more of a script to run on the server to add it to mailboxes. Those seem to be a script that runs on each computer via Outlook (although it still sets a server-side rule if in Exchange mode). Most of the people using POP3 clients are not using Outlook.
geowrianAuthor Commented:
Thanks much. I played around with some EWS API coding and MAPI scripting, but it's useless until we get Exchange 2010.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.