Having trouble placing or receiving calls or using your voicemail system on Ooma Telo VoIP Phones? Post your questions here.
#36356 by Mike-o-Matic
Tue Dec 08, 2009 12:05 pm
Not to be a wet sock and drag a thread back on-topic ... but I'm gonna do just that! :D

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

.
#36629 by devika
Thu Dec 10, 2009 12:24 pm
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 :?:
Attachments
VM.jpg
VM.jpg (29.84 KiB) Viewed 1738 times
Calllogs.jpg
Calllogs.jpg (45.36 KiB) Viewed 1738 times
#36648 by rcjordan
Thu Dec 10, 2009 2:43 pm
>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.
#37389 by Bobby B
Tue Dec 15, 2009 3:43 pm
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.
#37397 by Mike-o-Matic
Tue Dec 15, 2009 5:14 pm
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." :cool:
#38200 by Mike-o-Matic
Mon Dec 21, 2009 11:38 am
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).

Who is online

Users browsing this forum: Google [Bot] and 6 guests