[WXC/VFX] Time on phone 1 hour out (WRTP54G)

Forums › Vodafone New Zealand (including Vodafone, WxC, Farmside) › [WXC/VFX] Time on phone 1 hour out (WRTP54G)

dolsen

1392 posts

Uber Geek

Trusted

Lifetime subscriber

#34164 20-May-2009 11:13

Hi All,

The time on my cordless phone is an hour out. If I set the time to be correct on the phone, it ends up resetting itself to be 1 hour out (I think after it rings, or a message is left, I haven't really taken notice what triggers the change in time).

What I think is happening is the phone is picking up the time from the ATA, which is a Linksys WRTP54G.

Looking at the pages in the router, I can not see any option for time zone displayed. There is a page that says "current time", but, it is shown as unknown.

The wrtp54g is connected to a dynalink rta1320 in half bridge mode. The router picks up the primary dns correctly (but not the secondary dns).

Any ideas?

Norton Secure VPN

Affiliate link

Affiliate link: Norton Secure VPN helps secure private information using bank-grade encryption when using public Wi-Fi on your PC, Mac, or mobile device.

chchmjr

60 posts

Master Geek

ID Verified

Lifetime subscriber

#216303 20-May-2009 12:54

I think the problem started at the last daylight saving change. The time is included in the caller ID data that arrives between the 1st and 2nd ring cycles. Many phones set their internal clock to that time data. The data comes from the VFX switch so I guess the problem lies there.

Michael

grant_k

3539 posts

Uber Geek

Trusted

#216383 20-May-2009 16:29

I am also running a WRTP54G router and have noticed the same issue. WxC were never able to get this sorted and in previous years, Phil. aka Maverick would manually reset all the affected profiles so they would be downloaded a day or two later. Apparently, there is some bug in the Linksys firmware that doesn't cope with NZDT.

Because WxC rarely participate in these forums now, this issue has been ignored since Daylight Saving finished a month or so back. It would be really nice if this could be fixed once and for all, but I'm not holding my breath. It doesn't seem worth complaining to their Tech. Support over such a minor issue which in all probability still cannot be fixed and will rear its head again in September when Daylight Saving starts again. At least if they leave things alone, our phone clocks will be correct during summer...

dolsen

1392 posts

Uber Geek

Trusted

Lifetime subscriber

#216396 20-May-2009 16:58

grant_k:
<snip>
Because WxC rarely participate in these forums now, this issue has been ignored since Daylight Saving finished a month or so back. It would be really nice if this could be fixed once and for all, but I'm not holding my breath. <snip>

Hopefully, they are watching... and, even if they don't post, perhaps something will be done...

geek4me

843 posts

Ultimate Geek

Trusted

Lifetime subscriber

#216450 20-May-2009 20:03

I have a WRP400 wireless router which had the same problem - the time went (stayed) one hour ahead of the current time after daylight saving finished. This would happen regardless of what random time the phone was set to by me manually.

Once a call arrived it would change the time to 1 hour ahead of the correct time after the second ring of an incoming call. It did this on 2 different phones at home.

After several emails Xnet/Vfx staff did a "custom config" that fixed the issue for me about 1 week ago.

grant_k

3539 posts

Uber Geek

Trusted

#216462 20-May-2009 20:48

geek4me: After several emails Xnet/Vfx staff did a "custom config" that fixed the issue for me about 1 week ago.

Yeah, that's what they did for most of us who were having this problem. Which was great, except that the "custom config." needs to be modified twice every year. After the 3rd or 4th time, I decided it wasn't worth the bother.

My Uniden 5.8GHz cordless system actually doesn't reset its clock according to the Caller ID. It is just the records in the CID memory that are 1 hour out. So in my case, it isn't such a big deal. However, I used to have a Uniden Desk Phone which did reset its clock on every incoming Caller ID, and that used to annoy me more.

geek4me

843 posts

Ultimate Geek

Trusted

Lifetime subscriber

#216689 21-May-2009 15:11

Perhaps now that they see it is a common problem affecting many customers across many routers which affects several phone types, in my case both a Uniden FP099 and a Uniden 3315, they may do something about it so we won't need to call them twice a year to "fix" it.

dolsen

1392 posts

Uber Geek

Trusted

Lifetime subscriber

#217056 22-May-2009 21:22

dolsen:

Hopefully, they are watching... and, even if they don't post, perhaps something will be done...

And... now it's fine :-)

grant_k

3539 posts

Uber Geek

Trusted

#217068 22-May-2009 22:03

Yeah, I noticed that this morning here too.

Cheers WxC.

nossi

25 posts

Geek

#221148 3-Jun-2009 00:07

I express daylight rules the other way around because NZ is ahead of GMT or UTC, unlike the rest of the world which is behind.

Time Zone: GMT+13:00
Daylight Saving Time Rule: start=4/1/7/3;end=9/-1/7/2;save=-1

This results in GMT+12 (save=-1) in winter between 1st Sun Apr 3am and last Sun Sep 2am; and
GMT+13 (0 hour offset) in summer.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#221167 3-Jun-2009 06:42

nossi: I express daylight rules the other way around because NZ is ahead of GMT or UTC, unlike the rest of the world which is behind.

Time Zone: GMT+13:00

Daylight Saving Time Rule: start=4/1/7/3;end=9/-1/7/2;save=-1

This results in GMT+12 (save=-1) in winter between 1st Sun Apr 3am and last Sun Sep 2am; and

GMT+13 (0 hour offset) in summer.

The problem is there were issues in earlier Linksys firmware that prevented DST rules from working properly if DST ended in a different year to the one it started - ie it worked fine in the Northern Hemisphere where it starts and ends in the same calendar year. In the Southern Hemisphere where it starts in one calendar year and finishes in the next the DST rule did not work properly.

I believe this is now fixed.