VM requires user to reset pass and deletes VM's??

[placidsolace]

Hey Everyone,

So I have one user that has been having strange stuff going on with their voicemail. Voicemail Pro gets a message for said user and the users phone lights up, at random the user will all of a sudden need to create a new voicemail password after the login prompt at which point all the voicemails in the users voicemail are deleted. What could be happening? If you need more information please ask and any help folks can provide is greatly appreciated.

~placidsolace

 

[Westi]

is there a PC that makes changes and has a configuration open for a long time?
or worse not closing the config. when uploading changes?

Check the Audit trail who made changes and when as soon as this happens.
That requires different logins for different people to really be a good help so if everybody has the default login then you can just guess but at least you see that someone was making changes.

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Interrupt the silence only if you improve it by saying something, otherwise be quiet and everybody will be grateful.

 

[placidsolace]

Thanks Westi, that kept us busy for a bit but I ended up stumbling upon more info that makes me think its something else.

We rebuilt the users extension from the ground up, and all seemed well, but then later today it was happening again. No one left the config open on this one, and I found that the voicemails are being saved in the correct directory but the only way to access them are by using the users old extension. We had to move the user due to job changes from DID 4844 to DID 4885 so, not sure if this changes the advice but truly at a loss of where to go from here. Is there a place that the voicemails are controlled other than the voice recording tab in the configuration? Any help is appreciated.

~placidsolace

 

[placidsolace]

Additionally the extension 4844 no longer exists at the user level - also forwards at the extension level to the department manager

 

[tlpeter]

Why did you change the extension and not just point the DID to the old extension number?
There is no need for those to match (it only looks cleaner)


BAZINGA!

I'm not insane, my mother had me tested!

 

[amriddle01]

This sounds like it's caused by some questionable practices. If you are moving people around by re numbering extensions and deleting those extension etc instead of just changing the DDI/DID routing I am not surprised this is happening



"No problem monkey socks

 

[IPGuru]

+ remember VM works on user name not extn number, nay change to a name will create a new mailbox.


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[placidsolace]

Makes sense, thanks for the further advice everyone. In this case we did have to change the extension per corporate policy, there is a certain range of DID's that are specifically for inside sales and this individual was moving from there to a purchasing position at our sister company. I am curious if there is a way to address this. If it is outside best practices then what do other companies do when this is necessary? I can't be the only person needing to do this. Also if the old user and new user were completely removed, including the VM directories, then how is it still associating with the old user? It was completely removed and rebuilt ?? All help is greatly appreciated and thank you everyone for your input. Hopefully I can get to the bottom of this with the forums assistance

 

[IPGuru]

deleting a user from the IPO will not necessarily cause the VM pro to remove the Name & greeting recordings for that user.
if you then create a new user with the same name it will pickup the old greetings & continue to use them.

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[placidsolace]

@IPGuru - thank you for the comment, but how do I edit that? Everyone has mentioned this but no fix has been expressed. Like I expressed, I removed everything for both extensions just two days ago and the issue still exists, including removing the actually VM directories. Please provide advice on how to correct this issue if you're compelled to comment.