Voicemail Pro Server Change (IP406) 2

[mcgriff1985]

We have a server with Win Server 2003 R2 SP2, running manager 4.1 (27), and voicemail pro 3.1 (21) with a USB Dongle for licensing. The server is about 10 years old and is ready to be swapped out with a server with the same OS. I have installed vmpro 3.1 (21) and the oldest manager I could find for this system on support.avaya.com. After moving the mdb file and importing the config into vmpro with all my AA's built, I copied between servers all my recordings files and verified they were working on the new machine. I directly copied folder to folder to make sure as not to miss any files. After moving everything over and making sure the IP addresses for the USB Dongle location was updated to the new server I made live all my changes. It immediately said my licenses were invalid on the new server. I then plugged USB Dongle back into the old server and updated the IP Address to look for license back to the old Win server and it started working again. I verified a seperate account and made sure the vmpro service was working on the new server. I believe the only problem I am having is validating the licenses on the new server. Any help would be greatly appreciated.

Update: Software Build on the system config is 3.1 (65) and the manager version on the new server is 6.2 (23)

Update: After uninstalling and reinstalling both the key system software and the drivers for the usb dongle I now have a red Feature Key button in my task bar. I also now have a validated set of licenses on the phone system. I am now attempting to get the AA to answer when called but all I get is dead air. I have currently set up when you dial it goes to VM:Testing (Testing is my test vm and has a recording) but all I get is dead air (as stated above). I have rebooted both the vm server and the ip office.

 

[IPOLackey]

Okay, just a quick recap for the first issue.
If you browsed to your Avaya\IP Office folder you'll find Keyserve as a folder if you installed it correctly. Just run the Keyserve.exe in there and it will start running.

If you're getting silence on VM Pro, then you're looking at firewall. Check the in/out ports are on the wall.

 

[mcgriff1985]

I verified that the Keyserve.exe is installed and running properly. I also verified that the firewall is turned off. I made a modification to the IP Address so the new server now has the old servers IP address and all the changes to the system software has been made to reflect this. I find it a little odd that even internally the voicemail doesn't work. I can use the *17 which should take me to my local phones voicemail and all it plays is dead air as well. It says ?Name but doesn't play any recording as it should. If I go into the VMP software and click the recording to play at my phone it plays the recording over my speaker just fine. Just as with all the other recordings to their respective modules. I also setup a shortcode to test the modules to see if the system could access them and they come up ?Name when you hit the shortcode but no recording plays on these either.

It seems to me that the system simply isn't accessing the recordings even though inside the Voicemail Pro program they are there and verifiable. I even tested the system with a whole new module and voicemail build that I could use as a test set of modules and none of them pick up either. Some connection issue is causing this but I can't seem to find where.

I did notice in the old Voicemail Pro software under Preferences - General that the voicemail had a password there and the new Voicemail Pro software did not under this same menu. I went ahead and matched the passwords and rebooted. I will update on my progress.

Update: Password made no difference. Still getting open air. Call Status says (Voicemail) when calling in. When using shortcode says VM:Name but doesn't play anything. The AA even has a fallback extension in the event that the AA server is unavailable but it isnt even kicking it there. I shutdown the server and forced this to try it and it did fall back to that fallback extension.

 

[Telecomboy]

What is the new server's operating system? And what version of vmpro are you trying to run? You probably have to load R6.0 vmpro at a minimum.

 

[mcgriff1985]

System info

IP406 3.1(65)

OLD Server
Windows Server 2003 R2 SP2
Voicemail Pro 3.1 (21)
Manager 4.1(27)

New Server
Windows Server 2003 R2 SP2
Voicemail Pro 3.1 (21)
Manager 6.2(23)

I attempted to get the 4.1(27) but couldn't find my cd copy and the version of manager on the website was this one. I was assured that it would work fine and seems to be making all of my changes perfectly.

 

[Telecomboy]

I figured you updated the operating system on the server as well which could make the vmpro not work. Have you searched for and run the Avaya Batch File on the new server? this will open up all the proper ports. It sounds like maybe soming is being blocked.

http://marketingtools.avaya.com/knowledgebase/tools/firewall/

 

[mcgriff1985]

I tried the Avaya Batch File on the new server. It did it's thing, I rebooted both the server and the phone system, and I am still experiencing the same issues.

 

[mcgriff1985]

I started messing with the services again. I noticed that the VMProDBService was set to run off the assigned account that you setup for Voicemail Pro Service. I am not sure how this got to be but after double checking with the old server, I made the change for the VMProDBService to run off the Local System and then start and stopped it and it seems to be working properly now. THank you so much for all the help. Without it I probably do not get to this point and get my voicemail working.