Voicemail Pro Client Unable to Access after Upgrade 1

[sheldoom]

Last night I upgraded an IP500v2 from R11.0.4.4.0.6 to R11.1.3.1, the upgrade on the IP500v2 went fine, but had to run a repair on our techs Admin Suite to recreate the SD card.

We then migrated the voicemail from R11.0 Windows to 11.1.3.1 App Server on a Virtual Machine.

The strange thing that happened was that we were not able to access the new App Server using the Voicemail Pro Client. The credentials worked fine for accessing the Web Management in both 7070 and 7071. I confirmed that Enable Voicemail Pro Client was set to Yet in 7070, but no matter what I tried I could not get into Voicemail Pro Client. There was no link alarm in SSA and voicemail answered when called. I'd never seen this before.

Any ideas.

"It's all ball bearings these days" Fletch F. Fletch

 

[VinylDave]

Maybe you need a new voicemail pro client. Download it from the 7071 (I think) download section. I often had issues logging into ip500 things when using an older version. failing which, just check the 'Security - user rights' section to ensure it's enabled.

 

[sheldoom]

I tried both with the Voicemail Pro Client that can be downloaded from the App server, by the way was R11.1.3.0 not R11.1.3.1 that the system was and a fresh download of R11.1.3.1 VM Pro Client from support.avaya.com.

Thank you

"It's all ball bearings these days" Fletch F. Fletch

 

[VinylDave]

if it's just a credential thing then log onto the ip500v2 security settings - change the password there. Do the same on the app server --> manager - security - system - unsecured interfaces.

 

[sheldoom]

Tried that. It didn't help. Why do the creds work for Web Management though and not for VM Pro Client?

"It's all ball bearings these days" Fletch F. Fletch

 

[sheldoom]

I bit more info, this customer has 7 sites and we are upgrading all and replacing Windows VM Pro servers with Linux App servers. When we upgraded another site that was R10.0.0.4.0.5 we had a similar issue, but for this site we were able to access the VM Pro Client using the default password, rather than the one created during ignition. Could this be an issue just for upgrades from R10.0 to R11.1?

Do we need to default the security settings?

Thank you,

"It's all ball bearings these days" Fletch F. Fletch

 

[Ekster]

Have you enabled Voicemail Pro Client on the Application Server Web Manager and given the user "Business Partner" access in the Application Server Security Settings?

 

[IPOTS]

The password for the client is the normally the same as Manager. The 7070/7071 ports use the ignition password.

https://ipoffice-techsolutions.com/

 

[Ekster]

Also note, the account used to log into the VM Pro client is an account in the Application Server security settings not the IP500V2.

“Some humans would do anything to see if it was possible to do it.
If you put a large switch in some cave somewhere, with a sign on it saying 'End-of-the-World Switch. PLEASE DO NOT TOUCH'.
The paint wouldn't even have time to dry.”

Terry Pratchet