Ooma Forums

Not to be a wet sock and drag a thread back on-topic ... but I'm gonna do just that!

I, too, am seeing incorrect timestmps on the My Ooma Voicemail list page. The times in my Call Log are correct, but that's not the case on the Voicemail list.

For what it's worth, I'm in the central time zone. On 12/2 I left myself a test message that showed as 7:46pm, which should have said 9:46pm. Two hours earlier than in reality, in this particular test. However, I just repeated this exercise at 1:50pm today, and it says 7:50pm (possibly GMT?) on the webpage. Six hours LATER than reality, in this case. So there is some variation in how the problem manifests itself.

Note however, that so far, I think all the date/times read back by the Ooma Voicemail automaton are CORRECT... so IMHO this is more likely a problem with the My Ooma webserver, and much less likely to be caused by the voicemail server itself.

Any ideas or updates on this issue? Supportive slap on the back? Bueller? Bueller??

Regards,
Mike-o

.

I see the same thing as Mike-o is mentioning above. I will put it in a picture form so powers that be can take care of this sooner. The call in question is 732-745-XXXX showing 1:17PM in call logs and 10:18AM in VM logs.

Looks like VM time is set to Pacific timezone. I cannot understand the extra minute in though

devika wrote:Looks like VM time is set to Pacific timezone. I cannot understand the extra minute in though

Perhaps the ring time difference before VM picked up?

>I, too, am seeing incorrect timestmps on the My Ooma Voicemail list page. The times in my Call Log are correct, but that's not the case on the Voicemail list.

Same here. Mine is a new installation but the test voicemails were six (or more) hours earlier than the time the same call was showing in the log.

See the same problem, only my time on the voice mail shows an 8+ hour difference ahead.

OOMA's time stamp for Voicemail is way off here as well, but worse OOMA problems prevented getting to this sooner.
Anybody come up with a solution? (I've found that waiting for OOMA usually doesn't work.....)

Unfortunately the fix from today didn't fix this problem - hopefully we can get a permanent fix for this one this week. We're tracking this internally in bug 7009.

Well, Bobby, thanks for acknowledging that you're working on it still, just the same.

As Tom Petty once said, "the waiting is the hardest part." To which I'd like to add, "the not-knowing is the second hardest part."

Can anyone verify if theirs is working correctly now?

As of today the timestamps in my voicemail are correct now.

Mine weren't looking correct as of 1:30pm Central, so I recorded another test message. It should say 1:35pm, but showed up as 11:35pm (two hours behind, ie. equivalent to Pacific time).