Voicemail Pro Stopped Working 1

[chazzmanbm]

Hi Folks,

One of my clients has an IP Office 500v2 (R9.1) with Voicemail Pro server (9.1) and all of a sudden their AA and all voicemails stopped working. The PBX and server have IP connectivity, and Manager, VM Pro and other tools are installed on the same server (Windows 2003). All the files are in tact on the server and the IPO is configured for Voicemail Lite/Pro (with the correct IP address). I have verified that the VMPro service is running on the server but still, I get no communication between the two. Both the PBX and VM server have been rebooted (last resort) but still no joy.

All calls to VM, *17 (standard config of Voicemail Collect and "?"U) and *90 (Voicemail Node and AA script) just ring out.

I'm all out of ideas and next moves. Can anyone offer any advice?

Thanks.

 

[amriddle01]

If it's not just a standalone VM server and it's running DHCP/DNS etc it's probably had a reboot after an update or something and used the VM Pro ports for the other services, seen it many times

 

[teletechman]

with VM pro if you dial *17 it will give you a wave off with a message on the phone unobtainable if the VM pro is down or the service is stopped. Double check the IP address then on the VM pro server runt the firewall batch file again. Make sure that AV is off when you test.
Mike

 

[chazzmanbm]

Thanks guys. The server does not run DNS or DHCP and the IP addresses are still in tact. *17 and *90 just give 486 busy and no announcements. I had a look at the Windows firewall and can see the vmprov5svc is in the allowed list.

 

[sizbut]

So what happens when you access the voicemail server with the Voicemail Pro client? What appears on the Help | About menu.

Stuck in a never ending cycle of file copying.

 

[Telecomboy]

If this is a new install, make sure the licenses are valid. If it is not a new install, run the firewall batch even if you see it listed in firewall exceptions. It will open the needed ports for them to talk to each other properly.

 

[holdmusic34]

Also try reserving your ports in the registry.

No dns I know I know.

faq940-7374


You haven't lived until you've been affected by a lack of gratuitous arp.

 

[chazzmanbm]

So what happens when you access the voicemail server with the Voicemail Pro client? What appears on the Help | About menu."

I can log in no problem, and my scripts are there. I can't see any users when I am logged in though (see attached image). .....and a pic of the help -> about screen.

I ran the batch file and still no change. I haven't run the hotfix file yet since it's for win 2k8 and I'm running Windows 2011 server. Anybody know if the hotfix will work for 2011 Small Business Server?

 

[amriddle01]

It's not supported on an SBS server btw

 

[chazzmanbm]

amriddle, when you say "it's not supported on an SBS server" do you mean the hotfix is not supported or that VoicemailPro server isn't supported on an SBS server?

 

[chazzmanbm]

It looks like the netshell command to exclude the ports is unsupported. The only options after add (netsh interface add ....) is as follows:

netsh>interface ipv4 add ?

The following commands are available:

Commands in this context:
add address - Adds a static IP address or default gateway to the specified interface.
add dnsservers - Adds a static DNS server address.
add neighbors - Adds a neighbor address.
add route - Adds a route over an interface.
add winsservers - Adds a static WINS server address.
netsh>

 

[chazzmanbm]

...so what next? Any ideas how I can reserve ports on Windows Small Business Server 2011?

 

[amriddle01]

You need to establish that's the issue first, load VM Pro on another machine for testing and see if it connects, but VM Pro isn't supported on SBS..for this very reason I imagine

 

[chazzmanbm]

I just ran netstat -a on the VM Pro Server notice the following:

There are two active connections between the VM Pro Server (10.248.42.253) and the IPO (10.248.42.2)

TCP 10.248.42.253:49925 10.248.42.2:50814 ESTABLISHED
TCP 10.248.42.253:62585 10.248.42.2:50808 ESTABLISHED

The ports to exclude as referenced in the Microsoft support fix, are as follows.

UDP 0.0.0.0:50790 *:*
UDP 0.0.0.0:50791 *:*
UDP 0.0.0.0:50792 *:*
UDP 0.0.0.0:50793 *:*
UDP 0.0.0.0:50794 *:*
UDP 0.0.0.0:50795 *:*
UDP 0.0.0.0:50796 *:*
UDP 0.0.0.0:50797 *:*
UDP 0.0.0.0:50798 *:*
UDP 0.0.0.0:50799 *:*
UDP 0.0.0.0:50800 *:*
UDP 0.0.0.0:50801 *:*

There is some communication happening anyway. ....but it's still not working.

 

[amriddle01]

Reset the security settings in the system, then enter a VM password there and also in the VM Pro client/settings to match

 

[chazzmanbm]

Turns out that DNS was running after all. I disabled the DNS service, rebooted the server and voila! Voicemail started working again. Thanks everybody for your help and suggestions.

 

[amriddle01]

Typical