I am using the Schmoozecom endpoint manager. I am in Utah which should be +07:00 and since it's 3/30/2014 Daylight Saving Time is in effect.
Actual time right now is: 08:00 MDT
However here is what I get when I provision my T22P's (the only model I have so I don't know if others have the same issue.)
+7 DST Enabled 9:00 AM
+7 DST Disabled 9:00 AM
It doesn't seem to make a difference. I am rebuilding configs after editing the template and rebooting the phones after the rebuild.
Allen maybe it was just a typo but Mountain time should be -7:00 as opposed to +7:00. What firmware version are your phones on?
Rick
(03-31-2014 01:29 AM)rlsabin Wrote: [ -> ]Allen maybe it was just a typo but Mountain time should be -7:00 as opposed to +7:00. What firmware version are your phones on?
Rick
Yes, sorry -7:00.
Firmware is SIP-T22P 7.72.0.30
I dumped the Schmoozecom Endpoint manager and went back to the stock PIAF OSS Endpoint manager. Not only does it solve this problem, but it also solved provisioning issues with a couple of phones as well.
(03-31-2014 10:34 AM)ccwtech Wrote: [ -> ]I dumped the Schmoozecom Endpoint manager and went back to the stock PIAF OSS Endpoint manager. Not only does it solve this problem, but it also solved provisioning issues with a couple of phones as well.
Could you post the "local_time" settings from one of your working yealink configuration files? I'm seeing the same issue. Have you had any other trouble/limitations with the OSS Endpoint manager? Seems like that might not be developed any more.
Hmm, this really seems like a problem with the phone's firmware. I have a T21 with 34.72.0.20. If I set the zone to -7 Canada(Edmonton,Calgary) via the phone's gui I get the right time. If I change to -7 United States-Mountain Time, it slow by one hour (like DST is not applied). And, in fact I see that Offset(minutes) is blank with Mountain Time, but shows 60 with the other DST observing time zones. Can't change it though as it is greyed out.
(03-31-2014 10:34 AM)ccwtech Wrote: [ -> ]I dumped the Schmoozecom Endpoint manager and went back to the stock PIAF OSS Endpoint manager. Not only does it solve this problem, but it also solved provisioning issues with a couple of phones as well.
I have reported this to Schmoozecom and they have acknowledged this is a bug.
Their Endpoint manager is a Beta product so issues like this are expected. There isn't an ETA but I know it's on the tracker to fix.
My calendar is working well and correct to my time zone and date/time. However, the problem is that it is in 2555 not 2012. I try to set the year to 2012 manually, but it automatically runs up to 2500s again. Could anyone tell me how to fix it ?? Thanks.
(11-10-2014 06:24 PM)Jackiefouch Wrote: [ -> ]My calendar is working well and correct to my time zone and date/time. However, the problem is that it is in 2555 not 2012. I try to set the year to 2012 manually, but it automatically runs up to 2500s again. Could anyone tell me how to fix it ?? Thanks.
Since your issue is different, you should create a different thread rather than use this thread.
I used the autodst.xml file which isn't well documented but works great. then update your provision template so that it uses it instead of the settings from the phone system.