idavies

I have an IP403 system with 5 digital extensions, and run Voicemail Lite on our server.

We make use of the email feature of Voicemail such that messages are sent out to users as an attached *.wav file. This worked absolutely fine with Windows Server 2000, however we have just upgraded to Windows Server 2003 and Exchange 2003, and now the Voicemail system crashes if this email forwarding feature is used (you can literally watch it shut down as a message is left). Switch off the function, and everything works fine - it seems to be an issue of Voicemail not interracting correctly with Exchange 2003.

We are using the latest IP manager software, and I have been informed that Avaya do not support this Voicemail function nor use on Windows 2003 Server, so there is no fix. Any similar experiences or ideas to solve this?

XseSiV

What version of Firmware are you running, V3? or V2.1? V2.1 is not neccessarily supported with 2003 machines whereas V3.0 will hum along quite nicely when there is a 2003 machine in play. what version of outlook is installed on the voicemail lite PC? outlook 2002-3 has added security restrictions that will hamper your efforts

__________________

PBXtech.info

 

idavies

I have just checked the version of the unit, and it is v. 3.0. (40). Outlook 2003 is running on the server, but naturally this is not used.

Our support Company have attempted to upgrade the SP for Exchange 2003 believeing this to be the problem. They have been unable to do this as the SP upgrade thinks that only Exchange 2000 is present, although Exchange 2003 is most definitely installed. I can only think that the upgrade from Windows Server 2000 to Windows Server 2003 (rather than a clean install) has left some remnants of the older O/S that is causing the problem with the upgrade, and VM Lite's ability to interact with Exchange and send out the *.wav files?

Maybe VM Pro using SMTP rather than MAPI might be a solution?

SteJay

IP403 with 3.0 (40)

I Had the same problem. When VM lite was installed on a windows 2k server with exchange installed, all was fine. Then my client upgraded to 2003 server and exchange and this caused vmlite to crash everytime it tried to send an email. As soon as the email notification was
stopped, vmail lite was working fine. We eventually came to the conclusion that it was because exchange 2003 and vmlite was on the same machine so moved vmlite onto a 2000 server. We then installed outlook 2003 client. This caused another problem. When vmail tried to send an email it no longer crashed but it would pop a message saying "an application is trying to access outlook. Do you want to allow it?" It appears this could be some extra security feature in outlook 2003 and as far as I know the only way bar messing with the registry is to download some 3rd party software. www.mapilab/outlook/security - seemed to work.

Anyway I have a new problem. I normally install vmlite as a service (I know its not supported) and it always seems to work ok until now. When the voicemial is run as a service it will not send emails, however as soon as you stop the service and run as an application, it works fine. I have had vmlite running as a service and sending emails before on previous levels of software (2.1) but it seems on 3.0 it will not work. Has anyone else come across this of know of any work arounds?

Cheers

S