IP Office 500V2 R10 UCM Voicemail Pro No Go

[nzgordini]

Hi Guys - I have recently upgraded one of our IPO 500V2 to R10.0.0.2.0(10). This all went well and has been running quite happily for a couple of weeks.
I then installed a new UC Module(V2)with exactly the same version of software and it all appeared to go well with no errors during the install or ignition process. But the Vmail Pro will not play with the IPO.
I changed the voicemail password in both the IPO system security settings and through the voicemail pro client, the ip addresses of the IPO Lan1 and UCM are in the same subnet and share the same gateway information, the IPO voicemail typr is set as voicemail pro on UC Module and the IP address shows correctly as 169.254.0.2 (automatically populated), the correct licences are installed in the IPO (Essential and Preferred - VM Pro, plus office worker licences), the SSA shows the UCM as operational and web manager shows all the UCM services as running.
When I try to ring the voicemail the call fails and the monitor shows that VM Pro is not operational ?? Also when I login to the voicemail pro client the server displays as "No Name" and the IP address as 0.0.0.0

Anything else you can see that I may have overlooked?

Thanks

 

[joe2938]

try to power down the uc module and then power back up

 

[nzgordini]

Joe, if only it were that easy.....

Thanks though

 

[teletechman]

Check the System voicemail tab to make sure it is going to vm pro on UCM and not VM pro had this is before. also if this doesn't work try to do a security reset to default and see if it connects.
Mike

 

[joe2938]

when you say system status show the voicemail as operational, does it say voicemail pro?

 

[nzgordini]

Hi Joe

Yes, SSA recognises it as Voicemail pro and shows the variant as UCM V2 with the correct software load displayed

Gordini

 

[nzgordini]

Teletechman - yes IPO is set as VmailPro on UCM

Gordini

 

[joe2938]

Have you tried to reboot IP Office then as everything seems to check out

 

[CarGoSki]

Usually when SSA shows VMPro is active and voicemail does not respond then the voicemail security password and the password entered into vmpro client no longer match.
Why does the address show as 169.254.0.2? Have you connected and changed the address?

 

[nzgordini]

Hi CarGoSki

The address of 169.254.0.2 automatically populates even though the actual address of the UCM is a 192.168.x address - This is quite normal

Gordini

 

[joe2938]

I agree mine says the same and works great

 

[nzgordini]

Hi Joe,

Yes, a complete power down of the system was one of the first things I tried when I discovered things weren't working....

Gordini

 

[NYSTECH]

Was there an old UC module you replaced or was this a new Install of UC Module?

 

[joe2938]

Knowing everything you have done other than redoing the ignition process, I would power everything down and reseat the uc module and test again

 

[nzgordini]

Nystech - no, completely new UCM V2 install

Joe - Not a bad suggestion. I guess it's all getting a bit confused with all the changes I have been doing to get this sorted. I am just off to visit the site shortly - only 72 miles away....

Gordini

 

[CarGoSki]

OK if you say so.
I am looking at a 9.0 UC Module now and SSA and Manager show the UC Module address as the configured address and not the other "hidden" address.
I recall see that address in early UC Modules but not lately. Perhaps this is r10 behavior.

 

[nzgordini]

Hi CarGoSki

I'll let you know when I get it going. It does seem as though this may be R10 behaviour as it is well documented in the latest UCM install write up.

Gordini

 

[intrigrant]

Set a VM Pro password in security settings and the same password in the VM Client.
R10 requires you to set a password.

 

[joe2938]

he already did that

 

[intrigrant]

Default security settings and reconfigure.
In Manager > voicemail must display : VM Pro on UC Module with the ipadress of the UCM greyed out.
Look in the logs to see what error is shown.