ipo rls 8.1.67 - no recording after message left in mailbox 3

[Wallysworld]

Hi All;

I've got an odd issue, well I have many but this one relates to v/m pro.

Have a user who's voicemail says it was never accessed (in voice mail pro client -> users tab). Not that strange you say... initialize it!
That's where the odd issue comes into play. This user has been using their mailbox for 5 months! Now the mailbox says it's never been accessed.
I tried several different tests and finally deleted the user (saved it) and recreated the same user. It was removed out of the voice mail pro client and then returned.
The mailbox has been initialized, the password has been changed, the greeting has been recorded, you can leave a message... but the message does not light up the phone and there's no message when you access the mailbox. Plus, the mailbox still says it has never been accessed.
No duplication of name/extension #?

I'm stumped, has anyone else ever had this?

Thanks, as always.

 

[amriddle01]

Do you have a space in the name in programming? This isn't supposed to be an issue anymore... but Avaya love bringing back old bugs

 

[Westi]

mostly a space behind the last letter in the name field

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

“This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[Wallysworld]

There is no space after (or before the user name/full name).

 

[Wallysworld]

SORRY, I'm not sure if it's relevant, but full disclosure it's a UC Module.

It is not one of the defective group.

 

[amriddle01]

The replacements are hardly trouble free, you could test with an external instance of VM Pro to at least rule it out

 

[Wallysworld]

Just a follow up:

created a SR with Avaya, they accessed the uc module using Putty, and found 2 old names in that list that were not showing up on the user list in System Manager.
He deleted those 2, we recreated the user, and tested it. Tested good.
His suggestion was that the corruption was created due to changing the user's name (not deleting it and recreating the user).
So, that's what I'll do from now on.

 

[amriddle01]

Thanks for the follow up, perhaps he should also suggest to is bosses that they fix their shit, changing names is a common procedure and shouldn't ever cause corruption....