65533 new message on VMPro 6.0 (22)

[Mlck]

Hi


I got that problem with some users but not always the same, I can see those message in the VMPRO Client under Specific Start Point/Users/New

When they have that problem, they can't use visual voice.

Somebody else ever live that issue

thanks

IPO 6.0.(8)
vmpro 6.0(22)
ccr 1.2.2.78

 

[Bas1234]

Disable and delete the Voicemails of that mailbox of that user thru the VMPro client > User > right click on the user.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Mlck]

Yeah I did that couple of time but I would like to fix that.

Maybe there a patch?

 

[Bas1234]

Turn vm off on the user, in the manager > user > voicemail unticked

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Mlck]

I turn off voice mail box (disable and clear with a right clic)

I unchek Voicemail in the user and nothing, I delete the user and the extension of that user, merge. recreate the user and the extension,,,same thing.

I'll reboot the VMPro and the IPO toninght, will see.

thanks

 

[h382]

Reboot should fix it.. A few of us had that issue, and a reboot fixed it for me.

 

[Bas1234]

How is the system setup?

One VMPRO server and more then one IPO in a SCN network using Hotdesking and User rights?

If so;
User Right is not supported over SCN, to solved it just copy the user rights from site 1 in to site 2.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[h382]

Title is misleading, but here is another topic on it.

http://www.tek-tips.com/viewthread.cfm?qid=1606513&page=2

 

[Mlck]

Yes but I know the issue will come back for that user or an other one, since I have this problem, I reboot many times. I think I will open a ticket with Avaya

thanks

 

[myalias09]

This is a known issue and should be fixed in the next 6.0 release due out soon.