cbennett912

IP403, 2.1.24, VM Pro Latest under Windows Server 2003 -or- Windows 200 Pro. I am new to VM Pro, but have a good data background. I am trying to get VM messages to copy to an email account. I have all the fields filled out right, but I must be missing something. I setup MAPI client on server, all that. Is IMS required for this?

I have tried Exchange, and half-dozen other email server apps, and messge never gets delivered. I only have one server, so I guess I can't install VMpro and IMS on the same server. Any ideas?

Cephas

This can be tricky. What windows account did you install VMPro under? There is an Avaya job aid to assist in this, be sure to follow it (on the docs CD or at support.avaya.com). In a nutshell, you should create a windows login named "voicemail" with admin priveleges, login as voicemail and install VMPro. Then in your VMPro control panel item, in the first tab you would put voicemail@youremaildomain.com

Peter

PBXtech.info

 

corhavelaar

I use VM Pro e-mail notification with a SMTP enabled server.
All i did was on the VM Pro server go to start -> configuration -> VM pro and fill in the ip adress of the SMTP server and, if necessery the username and password.
After this you must enter a valid e-mail adres on the Voicemail tab of a user.
You can check the SMTP server with a telnet session, you can find information on the microsoft site, it is supported in MS Exchange.

James-c

I have a very similar system, and exactly the same problem. I have VM Pro 2.1.24 on Windows 2003 Standard Edition with another maching running Exchange on SBS 2003, and even though I have created a "voicemail" account in Exchange and also tried the SMTP option, nothing happens. I will try running the VM Pro software while logged in as "Voicemail" and see what happens.

**Update** Logging in as "Voicemail" and re-installing VM Pro under this user login has got it working, Voicemail now goes to e-mail! It must be some exchange permission issue. Thanks Cephas

On another note, I am also having problems in VM Pro in general on this machine. We want to use it as a backup for our receptionist, so that if she is busy or the phone exceeds the set number of rings the caller goes to auto attendant queue, but this doesn't seem to work properly. I am going to try reinstalling again to see what happens.

I have heard that many of these issues are related to Windows Server 2003.

Cephas

How are you going about this? I know of 2 ways, each with ups and downs but both work:

1 - direct incoming calls to the receptionist, turn her voicemail option on, but create a custom user leave mail start point for her that does a goto to your AA callflow. downside = can't simply transfer callers to her phone and expect it to go to her mailbox if no answer, must use assisted transfer/leave mail combo

2 - direct incoming calls to AA callflow first, and use assisted transfer token immediately to ring reception phone - on timeout, proceed with callflow. downside = heavier use of VMS ports.

Peter

James-c

Had it working originally using this method: Incoming Call Route to VM:Reception -VM module "Reception" uses this flow: Start Point - Route by Call Status - Default (transfer to reception group), Busy (transfer to AA queue), No Answer (transfer to AA queue) and Out of Hours (to Voicemail leave message). If reception phone is available, call goes and all is ok, but if phone is busy or is unanswered it goes bad. Unanswered calls just keep ringing, and if the phone is busy the system just drops the call instantly.

This actually worked quite well at first, but after uninstall/re-install to rectify the voicemail to e-mail problems, this aspect stopped working. Everything else appears to be the same though. Other call flow conditions work ok, just not route by call status.

I appreciate your help.
James

PBXtech.info

 

Cephas

What version of firmware/VMPro are you running. Assisted transfer was broken in 2.1.15/2.1.6, had never tried route by call status but can only assume it relies on the same broken code as the feature is quite similiar.

You should either be on 2.1.248901 with VMPro 2.1.10, or 2.0.18 with VMPro 2.0.17 or .20

Peter

PS If in USA or Canada, I recommend 2.1.248901

James-c

Thanks Peter,
I am in Australia.
The IP403 build rev shows only 2.1.24 (no sub revision shown).
VM Pro is 2.1.10.

It did appear to work earlier but is now not behaving as we want. I don't really want to format and reinstall the machine (Server 2003) but this appears to be what I will have to do.

The Telephony Techs here have been unable to make any inroads to the faults we are experiencing either.

Cephas

2.1.24 is subject to TFTP lockup, which causes all manner of problems. Use 2.1.248901 instead, you can get it through your support channel.

What kind of sets do you use in Aussie-land? DS or DT? I know they have no end of problems with 2.1.anything in the UK, haven't heard feedback from down under yet.

Peter

James-c

We have now got 2.1.27, and some things appear better than before. We still had a total system lockup just before Christmas, with all incoming calls receiving a busy signal. No update for VM Pro 2.1.10 was available though, although I have heard of 2.1.12 being out there. 2.1.27 appears to have improved the performance of VM Pro as well so far.
I asked about version 3 upgrade and was told that all field trials in Australia failed, and we will have to wait some time for upgrades.

We now have a new company providing Avaya support and the guy who is helping us appears far more competent than the techs from the previous company. He is also more customer focussed.

Not sure on the DS or DT question, how would we tell?

James