Voicemail Pro Not Connecting 1

[jcallen03]

I have an IP Office 500V2 with a VM Pro server. Everything worked fine until I changed the IP on the VM Pro server. I changed the IP on the System VM tab in Manager to reflect the changed IP. Now the VM Pro client does not see the IP Office. I changed the System VM tab in Manager to the broadcast address and it didn't make a difference. What am I missing?

 

[DigitelD]

Have you rebooted the server?

SHK Certified (School of Hard Knocks)
NCSS, ATSP/IP

 

[tlpeter]

No need to reboot.
I did this yesterday and worked straight away.
You must have done something wrong.
Do you have the right default gateway?
Can you ping the IPO from the VMPro server?
Can you ping the VMPro server from SSA?


BAZINGA!

I'm not insane, my mother had me tested!

 

[jcallen03]

I didn't change the gateway. The IP was 192.168.200.209 and it changed to 192.168.200.198 so it is still on the same subnet. I can connect to the IPO from the VM Pro server. I have Manager loaded and I connected with no problem. I did not ping the VM Pro server from SSA. I will try that. Thanks for the suggestions.

 

[acollard83]

Also, is DNS running on that server? If so, stop the DNS service, restart the VM Pro service then restart the DNS service.

 

[GhostZman]

When you changed the IP address on the IPO, did it reboot? I haven't tried it, but I could have sworn that changing the IP address on anything forces a reboot.

 

[jcallen03]

You do have to reboot if you change the Voicemail IP in Manager.

I think the DNS idea might be worth checking out but you put the IP in Manager and not the name so you would think DNS would not be a factor. I also tried the broadcast IP. I am willing to try anything though.

 

[jcallen03]

It turned out to be a windows firewall issue. There is an Avaya batch file that fixed it.

 

[hairlessupportmonkey]

Hahahaha - lesson 1 - check for firewalls first ;-)

ACSS - SME
General Geek