I have a customer that allows email alerts, but does not want to have a copy or forward the voicemail to email. They would like to go to visual voice, but the owner doesn't want their users to be able to change the mode. Is there any way I can lock in the email alert option and still use visual voice? Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can I limit email options for customers with Visual Voice ? 1
- Thread starter dthszn
- Start date
- Thread starter
- #2
amriddle01
Programmer
That stuff is hard coded into the system, it can't be changed 
- Thread starter
- #4
It is bit Draconian to dictate to a user exactly how they use their Voicemail and these features can still be enabled without Visual voice anyway.
However an old fashioned written memo of "Do Not Enable VM Forward or Copy on your mailbox or else" should be sufficient ;-)
A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
-
1
- #6
DrDrayAvaya
Programmer
IT dept could setup rule for ditching emails from the IP address of the IPO that has attachments perhaps? they'll always come from same IP and sender address...
that would allow "Alert" emails, and not clog their exchange database with mass amounts of .wav files that likely never get cleared.
?
that would allow "Alert" emails, and not clog their exchange database with mass amounts of .wav files that likely never get cleared.
?
- Thread starter
- #7
IPGuru- I agree with you 100% and that was my suggestion, but the owner is trying to protect his business. He has people leaving personal information on voicemails that should not be left in a voicemail. And as we all know, employees always listen to their supervisors. He will deal with the "or else", but you can't undo the damage.
- Thread starter
- #8
IPGuru,
Normally I would agree with you but in this case there are issues with Avaya's design that would justify the need to restrict the user's options.
The Exchange Server integration requires you to configure the user to have Voicemail Email set to Forward. In theory the user then accesses and manages all their voicemails through Outlook. But by having to enable the feature using the Voicemail Email settings, all the user's other IP Office interfaces now provide them with access to their voicemail email settings which, if changed by mistake or curiosity, break their Exchange Server integration.
Nothing fatal but not the best user experience in the world to have to tell the user "re this option on your phone/prompt in your mailbox, don't use it".
On Avaya's part its a classic "did enough to get it working in the first build but never revisited it to smooth the rough edges".
Normally I would agree with you but in this case there are issues with Avaya's design that would justify the need to restrict the user's options.
The Exchange Server integration requires you to configure the user to have Voicemail Email set to Forward. In theory the user then accesses and manages all their voicemails through Outlook. But by having to enable the feature using the Voicemail Email settings, all the user's other IP Office interfaces now provide them with access to their voicemail email settings which, if changed by mistake or curiosity, break their Exchange Server integration.
Nothing fatal but not the best user experience in the world to have to tell the user "re this option on your phone/prompt in your mailbox, don't use it".
On Avaya's part its a classic "did enough to get it working in the first build but never revisited it to smooth the rough edges".
Sizbut
I think its even works
IMS didnt work so they introduced the IMAP server in VMPro (A Sensible Idea) then tried to re-integrate it with exchange again (Once again putting reliability in the hands of Microsoft).
however in this case I don't think the customers requirements have anything to do with exchange limitations they just do not want the users forwarding messages as emails.
it would be the customer telling its staff they are not to use a certain feature (Just like telling them they are not to phone the MD direct)
A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
I think its even works
IMS didnt work so they introduced the IMAP server in VMPro (A Sensible Idea) then tried to re-integrate it with exchange again (Once again putting reliability in the hands of Microsoft).
however in this case I don't think the customers requirements have anything to do with exchange limitations they just do not want the users forwarding messages as emails.
it would be the customer telling its staff they are not to use a certain feature (Just like telling them they are not to phone the MD direct)
A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
- Status
Similar threads
- Locked
- Question