Carl Johnson Posted March 19, 2009 Report Share Posted March 19, 2009 Upgraded to 3.3.0.3163 of the PBX, removed my custom polycom XML templates from /html so it uses the system ones. Now the phone time is wrong as the DST start date is MIA .. tcpIpApp.sntp.daylightSavings.start.date="" this should have a value of "8" (second instance in the month) Please fix this so the variable to get that populated works. ** FROM POLYCOM ADMIN GUIDE ** tcpIpApp.sntp.daylightSavings.start.date 1-31 8 If fixedDayEnable is set to 1, use as day of the month to start DST. If fixedDayEnable is set to 0, us the mapping: 1 = the first occurrence of a given day-of-the-week in a month, 8 = the second occurrence of a given day-of-the-week in a month, 15 = the third occurrence of a given day-of-the-week in a month, 22 = the fourth occurrence of a given day-of-the-week in a month Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 19, 2009 Report Share Posted March 19, 2009 Upgraded to 3.3.0.3163 of the PBX, removed my custom polycom XML templates from /html so it uses the system ones. Now the phone time is wrong as the DST start date is MIA .. tcpIpApp.sntp.daylightSavings.start.date="" this should have a value of "8" (second instance in the month) Please fix this so the variable to get that populated works. ** FROM POLYCOM ADMIN GUIDE ** tcpIpApp.sntp.daylightSavings.start.date 1-31 8 If fixedDayEnable is set to 1, use as day of the month to start DST. If fixedDayEnable is set to 0, us the mapping: 1 = the first occurrence of a given day-of-the-week in a month, 8 = the second occurrence of a given day-of-the-week in a month, 15 = the third occurrence of a given day-of-the-week in a month, 22 = the fourth occurrence of a given day-of-the-week in a month It should be "dst_start_week_of_month" that is set to "2"... ?! Quote Link to comment Share on other sites More sharing options...
Carl Johnson Posted March 19, 2009 Author Report Share Posted March 19, 2009 I don't understand .. as noted the polycom config file is missing a value in the tcpIpApp.sntp.daylightSavings.start.date field and that is required for the phone to properly set the date/time .. also per the docs a value of 2 is not valid it would be an 8 .. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.