[WXC/VFX] Time on caller id...

Forums › Vodafone New Zealand › [WXC/VFX] Time on caller id...

astrae

254 posts

Ultimate Geek

# 100243 5-Apr-2012 23:33

Its that time if year again....

Does anyone else have the incorrect time showing on their caller ID on vfx/fusion?

1 | 2

3594 posts

Uber Geek

Trusted

WorldxChange

# 605944 6-Apr-2012 07:05

Surprising if it hasn't updated, most devices would have updated automatically , some require to pick up their configs, all devices must have DNS connectivity as well, what's your device type ?, if you send me your details I will take a look for you.

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

geek4me

841 posts

Ultimate Geek

Trusted

Lifetime subscriber

# 605974 6-Apr-2012 08:44

I have vfx on TelstraClear cable. The time on the phone display only changes after receiving an incoming call after daylight saving changes.

astrae

254 posts

Ultimate Geek

# 605976 6-Apr-2012 08:48

geek4me: I have vfx on TelstraClear cable. The time on the phone display only changes after receiving an incoming call after daylight saving changes.

I'm aware of that but it's still an hour behind.

I'm sure it changed on the old daylight savings time, but is still wrong now.

Maverick its an srp527, same username as here.

astrae

254 posts

Ultimate Geek

# 605978 6-Apr-2012 08:53

The time listed in "status" is correct. The time listed in "voice" shows the current time as one hr behind

astrae

254 posts

Ultimate Geek

# 605979 6-Apr-2012 08:53

The time listed in "status" is correct. The time listed in "voice" shows the current time as one hr behind

RunningMan

5573 posts

Uber Geek

# 606003 6-Apr-2012 09:45

Had the same issue in reverse when DST kicked in last year.

I'm seeing the same thing - voice time is behind by one hour - says 08.45 when the actual time is 09.45.

For me, cosmetic problem only, doesn't affect functionality at, so not overly worried.

grant_k

3539 posts

Uber Geek

Trusted

# 606005 6-Apr-2012 09:53

astrae: The time listed in "status" is correct. The time listed in "voice" shows the current time as one hr behind

My SRP527 is also an hour behind. My Viewbill user name has my surname as the login, although I think the Xport ID is something different.

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

# 606024 6-Apr-2012 10:30

hmm not good enough the SRP should have followed the rules set, this was tested a few times this year, let me get this checked out again, apologise for the inconvenience it's not good enough on our behalf for these devices

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

Niel

3267 posts

Uber Geek

Trusted

# 606175 6-Apr-2012 17:28

Confirm, me too, SRP voice section current time is 1h behind. Does not bother me though, but know it will get fixed.

You can never have enough Volvos!

Griven

174 posts

Master Geek

Trusted

# 607267 10-Apr-2012 08:42

Hi guys,

Sorry about this as the DST change is my responsibility, the recent firmware upgrade we pushed out has broken the implemented DST rule. Working on a fix currently but if it's urgent PM me your phone number and I can roll you back to the previous .23 firmware release that has the working DST rule.

Nicholas Cuc

Network Support
WorldxChange Communications
www.xnet.co.nz

RunningMan

5573 posts

Uber Geek

# 607271 10-Apr-2012 09:00

Griven: Hi guys,

Sorry about this as the DST change is my responsibility, the recent firmware upgrade we pushed out has broken the implemented DST rule. Working on a fix currently but if it's urgent PM me your phone number and I can roll you back to the previous .23 firmware release that has the working DST rule.

What firmware are you pushing out now? I had manually moved to .24 several months back as it seemed to provide a more stable DSL sync.

Griven

174 posts

Master Geek

Trusted

# 607293 10-Apr-2012 09:31

Its the .24 version we recently pushed out. I'll have to find why the DST rule doesn't work on this version however.

Nicholas Cuc

Network Support
WorldxChange Communications
www.xnet.co.nz

Griven

174 posts

Master Geek

Trusted

# 607884 11-Apr-2012 15:08

Update on this one.

I have been working with the vendor on a fix for the issue, we have been provided a new firmware that fixes the DST issues introduced in .24 , however we have come across a few problems with this code so its back with them. Once again if the time shown is becoming a problem PM me your details and I will arrange for your SRP to be rolled back to .23 code which correctly shows the time.

Nicholas Cuc

Network Support
WorldxChange Communications
www.xnet.co.nz

astrae

254 posts

Ultimate Geek

# 607895 11-Apr-2012 15:14

Griven: Update on this one.

I have been working with the vendor on a fix for the issue, we have been provided a new firmware that fixes the DST issues introduced in .24 , however we have come across a few problems with this code so its back with them. Once again if the time shown is becoming a problem PM me your details and I will arrange for your SRP to be rolled back to .23 code which correctly shows the time.

Doesn't bother me to much so I'm not worried about going to a different firmware. Bothers my wife more but oh well lol.

At work we run an app over citrix based in Queensland. They don't have daylight saving over there so really puzzled them. Took quite a while to implement something that worked.

RunningMan

5573 posts

Uber Geek

# 611912 19-Apr-2012 14:25

Griven: Update on this one.

I have been working with the vendor on a fix for the issue, we have been provided a new firmware that fixes the DST issues introduced in .24 , however we have come across a few problems with this code so its back with them. Once again if the time shown is becoming a problem PM me your details and I will arrange for your SRP to be rolled back to .23 code which correctly shows the time.

I take it that's the .26 that is showing some new issues? The release notes indicate it fixes the NZ DST issue. So, not a good idea to manually update to .26?

1 | 2