if someone has any experience with this issue please let me know what you found.
I'm getting frequent reports from users that they get prompted that they have a new voicemail message (MWI comes on and VM message in their email inbox) but cant access it. I have verified this is the case.
When they log in to VM through the phone Unity says "you have one new voice message", user presses "1" to hear new messages, Unity says you have no new voice messages". Message is not accessible from new or old/saved messages. Most of teh time though the message can be played back from Viewmail for outlook (which calls the phone for playback through a voicemail port).
these messages are still "new" in the user inbox, meaning unread/untouched. I know when you click on or move a VM message from the inbox it becomes marked read by Unity. this is not the case here.
Upgrade to newest Unity TSP, still having the issue. Actually may have worsened it! But it did exist before TSP upgrade.
Going to run DBWalker utility tonight to see if there's any database errors.
I believe blowing out teh mailbox and recreating it will fix it however thats not a "fix" IMO, its a band aid.
Thnaks in advance for any input.
I'm getting frequent reports from users that they get prompted that they have a new voicemail message (MWI comes on and VM message in their email inbox) but cant access it. I have verified this is the case.
When they log in to VM through the phone Unity says "you have one new voice message", user presses "1" to hear new messages, Unity says you have no new voice messages". Message is not accessible from new or old/saved messages. Most of teh time though the message can be played back from Viewmail for outlook (which calls the phone for playback through a voicemail port).
these messages are still "new" in the user inbox, meaning unread/untouched. I know when you click on or move a VM message from the inbox it becomes marked read by Unity. this is not the case here.
Upgrade to newest Unity TSP, still having the issue. Actually may have worsened it! But it did exist before TSP upgrade.
Going to run DBWalker utility tonight to see if there's any database errors.
I believe blowing out teh mailbox and recreating it will fix it however thats not a "fix" IMO, its a band aid.
Thnaks in advance for any input.