New Voicemail Pro issue on Windows Server

[jmarchi]

A Customer had a UC module using voicemial pro, but it died, and they didn't purchase support

We switched them to use embedded voicemail, but they recently have purchased voicemail pro so we installed the windows version.

When we switch the ip office to use the new voicemail pro on Windows, it connects, but no start points are being created for the users, and the Auto attendant modules do not pick up.

any suggestions would be appreciated

We are using 9.6.

 

[NYSTECH]

Do you have Preferred Licenses?

 

[NYSTECH]

Did you change they vm type to Voicemail Lite/pro in Manager?

 

[jmarchi]

Yes we purchased a Preferred Edition License after the UC module died.

and yes we did.

Steps we took
1. installed voicemail pro
2. configured, recorded greetings
3. changed system voicemail config to voicemail pro
4. rebooted IPO
5. the voicemail pro server changed it's name from 0.0.0.0 to the IP address of the IPO indicating it was communicating
6. changed the incoming call routes to use the Auto Attendant modules we use in voicemail pro

1. Users aren't being created
2. AA modules aren't responding to inbound calls, but everything else looks like it's connecting.

 

[intrigrant]

Set a password in security settings and the same password in VM Pro client
Reboot the VM Service and test dialling *17, if it connects you get a prompt after dialling *17

 

[DaIPOTek]

Probably the password as intrigant suggested. If you look at the voicemail type in SSA does is show Voicemail Pro/Lite or none?

 

[jmarchi]

I'll check as you suggested when i have my next window to reboot the IPO and switch it to VM Pro again.

 

[Okkie26]

Maybe firewall settings.

Did you ran the firewall batch file?

 

[Telecomboy]

Also, you did remove the UC module from the system, correct?

 

[jmarchi]

Yes the UC module was removed. And the firewall is disabled

 

[Okkie26]

try to rum the vm service as local user.

 

[IPGuru]

so we installed the windows version.

Well that was your 1st mistaek , why not install apps server?
also if the UCM had been left in the IPO the Virtual Preferred edition licence would still be present & you would not have had to have purchased one (We have done this for a customer who's UCM failed in the early days)

There is no such release as 9.6 I assume you mean 9.0.6, if so a maintenance upgrade would seem sensible (9.0 releases do seem to be very flaky).

& as previously suggested the VM Password in IP Office security setting may need to be set to match the VM Pro server


Do things on the cheap & it will cost you dear

 

[jmarchi]

Reset the passwords in IPO and on VM Pro.

No change in the situation

Also while the system was registered to voicemail pro, we created a new user, and it never created the mailbox

One thing i didn't mention before. The voicemail pro and IP Office are on different vlan's IP Office: 192.168.42.200, VM Pro 192.168.100.13. They can see each other that isn't the problem, but wondering if it may be a factor. I'm going to the customer site to move the vm pro system onto the same vlan as the ip office to try that route.

 

[derfloh]

Did you ever check the VMPro and IPO logs?