Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MCD 4.1SP2 delayed vmail using Embedded

Status
Not open for further replies.

chrisgoff

Technical User
Jan 3, 2012
14
US
I have 2 users who are complaining about delayed voicemails, not just MWI's, but the vm's themselves. They check their vmail at say 9am when they get to the office, go through their box, and an hour or so later they get a MWI and check again..but the message is time stamped before 9am. It is a 4.1SP2 3 system cluster, all sites using their own embedded voice mail, all in the same time zone.

I have tried deleting and rebuilding the boxes, but it didn't resolve the issue.

Any other suggestions?

-Chris
 
Not sure if it is the issue but check under the form VM Network Servers for the time zone setting. There used to be an issue where the system would time stamp messages incorrectly because this setting was incorrect.
 
Caknfd

I just checked the VM Network Servers form, and it is blank for all three systems, Their time zones are set in the Date and Time form under System Properties.

-Chris
 
As a test can you leave a message for a user (test mailbox) and then log into the mailbox and check and timestamp the message and see if it is correct.

What area of the country are these systems? (Time Zone Wise)

Craig
 
I left a message in a test mailbox, the timestamp is correct.

I did notice something a little weird about the timezones, they are all GMT -5, but they are set differently...one says America/New York, and the other two say US Eastern Time.

I'm not sure this is causing an issue as they are both GMT -5 timezones and the offending voicemail's system isn't involved in this issue...but you never know...I'm going to change the one that's different and reboot the whole cluster tonight.

 
It was a shot in the dark. if you add a system in the VM Network Servers (you use to have to add your local system) there is a time zone setting there that caused issues in the past.
Sorry I can't be more help

Craig
 
Thanks, I do appreciate it, if the reboots don't fix it, I'm going to call Mitel tomorrow.
 
The network voicemail time zone if not set correctly affects VPIM (voicemail to email) time stamps where the delivered voicemail will show the time and date of the timezone programmed.
So it should be set to the same time zone if you are using smtp forwarding.

Share what you know - Learn what you don't
 
There can often be a preception of delayed messages as well. This was mostly on the Nupoint voicemails and was sometimes just user actions. Haven't really heard of the issue on the embedded but a reboot seems like a good start. All your settings look ok so make sure the users check that they really have gone through all their messages at 9 AM. You would think if its an issue you would think more then 2 people would experience the problem.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
I suppose you could also stop and start the voicemail service first rather than reboot

either connect to the maint port directly or connect a SSH session to the controller and enter the following

iPVM_Stop (stops voicemail)
iPVM_Start (starts voicemail

Share what you know - Learn what you don't
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top