Voicemail Initializing 1

[webin]

I was asked to move our IP Office and Voicemail Pro systems off our server and host them from my workstation (which runs all the time).

After installing Voicemail, however, I can't get the thing to start working. If I pick up my phone and dial a VM shortcode, or VM:COllect, or anything VM-related, the line immediately goes dead.

I've tried every combination of installs I can think of.
-Install, followed by copying the now unused directory from the server (identical install paths and directory structure).
-Clean install, using the installation/upgrade options I've used in the past (custom settings).
-Clean install following the Install Manual to the letter.

Things I've checked:
-Voicemail services are no longer running on Server, but are running on my computer.
-License dongle is properly installed and recognized, providing a valid license.
-Voicemail IP address has been changed in Manager to point to my workstation. I also tried the broadcast IP (255.255.255.255) without success.

I can't think of anything I might be missing. Does anyone have any ideas about what magic spark I might need to bring this thing to life?

 

[gknight1]

are you getting dead air or wave off? what version are you running on ipo and voicemail?

 

[Escorthosis]

Go to the properties of the voicemail service under services and let it login using the sa account. In the same field tick "interact with the desktop".
Now you'll get window on your desktop when the service is running. If you'll start the service and then hit run (this is only to start the output to the screen) immediately in the service window you should be able to see if the VMPro is licenced and more.

But I'll bet it is the windows firewall blocking the traffic between the IPOffice and the voicemail service.
So turn off the windows firewall or make an execption for the VMPro5Service.

 

[webin]

I'm not familiar with "wave off", but I'll pick that one. Essentially, when I try to access VM, the phone returns to an idle state, as if I'd never picked up the receiver.

Our system is a 401ng,
Manager is the latest, showing as 5.2 (54)
Voicemail Pro is latest, showing as 3.2 (28)
All of which were working correctly while on the server.

What I am currently looking at:
-The server is a Wink2k3 Server, whereas my workstation is XPSp2. There may be some differences in the details there, though I don't know what. I have framework 1.1 and 2.0 installed, as per the installation manual (*Groan*)
-Perhaps there is some network setting in our LAN that is preventing my workstation from being "found" by voicemail as the server was. As of yet, I haven't found anything like that though.

 

[webin]

Escorthosis!!!

You win like a gold medal or something. I did both things you mentioned (server output and firewall), and she's alive! SHE'S ALIVE!

Sorry.. got a little excited there. Thanks a ton for the help. I agree that the windows firewall blocked it, so I'll poke a hole in that and should be good to go.

You win. Thank you.

 

[aarenot]

You should make sure that your new VMPRO server/your workstation has a static IP set, so DHCP will not chnage the IP addy, and thus lose VMPRO connectivity. You may not have hit this yet, but reboot would possibly change the vmpro server IP.

Also check power settings, andf make sure your vmpro server never hibernates, NIC card does not ever go on power save so it is always on, etc. It is now a server, so it needs all facilities to never power down, or hibernate/sleep.