PSA R11.1.1.0 requires a 31 digit voicemail password and lets you enter a password that isnt valid 10

[critchey]

Just upgraded a system to R11.1.1.0 along with installing an app server same version. Things went well but when I went to add a voicemail password in the security settings it required an exactly 31 digit password to work... what a pain! Just figured Id pass along this "great news"...

The truth is just an excuse for lack of imagination.

 

[dsm600rr]

Avaya pulling another release off support.avaya.com/downloads/

ACSS

 

[critchey]

Oh it got even better! It let me set a password that it turned around and rejected when trying to connect the IPO. I couldn't for the life of me figure out why SSA reported it was a bad voicemail password not allowing the app server to connect to the IPO when I was copying and pasting it. I finally decided to go online, generate a random 31 digit password with all the needed characters, use that and poof up it went. So the security settings were allowing me to set this as the password but was then saying I was entering the incorrect password... when in reality it didn't like the password and should of never let me set it to that in the first place.

The truth is just an excuse for lack of imagination.

 

[dsm600rr]

Id go ahead and roll that one back

ACSS

 

[Daniel Barnett]

We just upgraded to the latest application server with 11.1 VMpro.
We entered a password around 14 char long and it worked just fine.

I read that as (not more than) 31 char long. - The update.

Our IP office is 11.1.0.1.0 build 95
Seems as if it's the IP office upgrade making that change, not the app server.

 

[critchey]

Ya this is specifically R11.1.1 (feature pack 1) not R11.1.0.1 (service pack 1).

This is in the manual:
"For IP Office R11.1 FP1 and higher, the password for voicemail connection is enforced to 31 characters with
restriction on repeated characters and enforcement of characters from different character types (lower case,
upper case, numbers, extended characters)."

It is not a huge deal but it sure would be nice if it didn't let you set the password to something it will turn around and reject.

The truth is just an excuse for lack of imagination.

 

[budbyrd]

Password requires eight characters one number one special character and a capitol... I use SnowWhite&The7DawrvesSacramento It is a total of 31 characters...

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[critchey]

I think the issue I ran into was they used the word "voicemail". It is not stated anywhere but Im guessing it won't actually let you change to a voicemail password containing that word just like you can't (anymore on R11.1) change the Administrator password to contain Administrator in it.

The truth is just an excuse for lack of imagination.

 

[BFG9K]

I've just upgraded our Lab system and everything is working except for VMPro. I've changed it to use an exactly 31-digit long password with Uppercase, Lowercase, Numbers and Specials in it, however it is still showing Voicemail None.

Any other bright ideas here?

I swear Avaya have not had a normal IPOSE release for at least 2 years now.

 

[budbyrd]

Watch it in monitor. Turn on ping-pong. It may give you a clue why it isn't connecting.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[JayNEC]

After upgrading to 11.1.1.1.0 build 18 I had SSL errors showing up in the Monitor trace for Voicemail Pro, and of course system status said NONE for voicemail.
stared at various logs for a while then enabled verbose logging and noted "Voicemail Pro Server running with disableVulnerableTLSSupport :Y" showing up in the debug log.

So I looked for that line in the /etc/vmpro_settings.ini and changed it to N
restarted, then had password error showing in system status. blanked those out and it came up.


New England Communications

http://www.necomm.com

 

[qtelcom]

So I looked for that line in the /etc/vmpro_settings.ini and changed it to N
restarted, then had password error showing in system status. blanked those out and it came up.

This fixed my issue also, anyone know why? Initially I tried setting the voicemail password to exactly 31 characters and still show none in system status. After changing that string JayNEC mentioned in the vmpro_settings.ini to N it worked right away.

Is there a setting on the IPO side that could be changed instead of having to WinSCP and edit this vmpro_settings.ini?
(IPO500v2 to virtual App server)

 

[JayNEC]

I was unable find any reference to this setting in the Avaya KB

New England Communications

http://www.necomm.com

 

[BFG9K]

@JayNEC, I actually raised an SR with Avaya and they weren't able to figure it out. Your post fixed the issue and Avaya told me they haven't heard of any other issues in the field yet with this release.

Just wanted to say thank you, I love when the community is better at the product than the actual vendor is