Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Daylight Savings "Time" is wrong

    Happy daylight savings time!
    Came in this morning and the time on my phone was not changed to daylight savings time.
    Checked the time on server. It hadnít updated so i fixed that.
    Sent out a request to reset all the phones.
    Most of them still have the wrong time.
    Some of them have the wrong date & time.

    I am checking the shoretel.com & finding things like this...

    This is because the time display of IP phones and switches didnít sync up with server, the time will be updated when next event occurs, one work around to force the time update:

    1. In Director, go to the Edit Sites page and change the "time zone" for each affected site and save.

    2. Change the time zone under sites back to what it should be and save. This forces the server to update the time on the switches.

    3. Reset my phones still showing wrong date & time.

    Any Ideas would be appreciated.

  • #2
    I changed the time zone to eastern on our system for a temporary fix, which set all the clocks ahead one hour. Back when the system was setup a few months ago, the only way I could get the phones to display the correct time was to add a working NTP server IP address into the DHCP server. NTP servers always seem to be overloaded, so I just had to find a list of servers and check each server individually until I found one that was working well. Then I entered that IP into the DHCP server.

    Comment


    • #3
      Did you run the DST patch on the server???http://support.microsoft.com/kb/928388

      Comment


      • #4
        LonnieBear is right, the phones get their time from the NTP server defined by DHCP. It has nothing to do with the time on the ShoreTel server. You can to a MUTE-I-N-F-O-# on a phone to see what the NTP server they are talking to is.

        If the time on the NTP server is wrong, the time on everything that relies on it will be wrong as well.

        Comment


        • #5
          I meant DST update on NTP server as well.

          He stated that the time hadn't been updates on the server as well. Is his ST server the DST source? It's been known to happen.

          Comment


          • #6
            Same problem here...

            Hello Ironhart,

            I don't have any ideas for you but I want to say that I'm in the same boat.

            I found the same problem and after doing the same 3 steps you did it still did not resolve the problem. Infact, after reseting my desktop phone the time was even more out of wack. Any phone that I reset will start with the time 2am Sun Feb 6th.

            My vendor, SmartIP, asked me to hard code an SNTP IP in one phone to see if it made a change. I tried using the IP for time.windows.com but after entering and saving it I did a mute info # and I could see that the change did not stick.

            I checked my windows voice mail server (w2k3) and I found that it didn't even have SP2 installed. So I'm currently running the updates in hopes that this will help.


            Originally posted by ironhart
            Happy daylight savings time!
            Came in this morning and the time on my phone was not changed to daylight savings time.
            Checked the time on server. It hadn’t updated so i fixed that.
            Sent out a request to reset all the phones.
            Most of them still have the wrong time.
            Some of them have the wrong date & time.

            I am checking the shoretel.com & finding things like this...

            This is because the time display of IP phones and switches didn’t sync up with server, the time will be updated when next event occurs, one work around to force the time update:

            1. In Director, go to the Edit Sites page and change the "time zone" for each affected site and save.

            2. Change the time zone under sites back to what it should be and save. This forces the server to update the time on the switches.

            3. Reset my phones still showing wrong date & time.

            Any Ideas would be appreciated.

            Comment


            • #7
              sp2

              It probably did not have SP2 because until recently shoretel did not support SP2 on the Vmail Server.

              Comment


              • #8
                update on this.
                someone had installed a second time service because the windows time service wasnt working.
                all my attempts to fix it failed so i ran the 2003 SP2 update and then a million more patches.
                that fixed the time server service.
                the phones got the updated time and are doing fine now.
                oddly enough the shoreware director security was then messed up.
                The Directory wouldnt display names, couldnt move phones, one HG didnt work, and a few other odd issues.
                I ran the ShoreWare repair (from the install disk start the install the choose repair) and things are back to "normal".
                thank you all for your sugestions.
                Ironhart

                Comment


                • #9
                  Clarification on Shoretel Daylight Savings Time

                  Through a couple of simple experiments, it has become clear that while the Shoretel phones get their TIME from the NTP server they are assigned to, they get the Daylight Savings Time calculation from their Shoretel server, not the NTP server. Therefore, if you are having Daylight Savings Time issues like I did until a few minutes ago, load the Cumulative Daylight Savings Time patch MS KB955839 on the Shoretel server and it will be instantly fixed. The phones will recalc the correct time within seconds of loading the patch.

                  Comment


                  • #10
                    Doesnt the time change in America next weekend?

                    Comment


                    • #11
                      Yes it does. Nov 1st.

                      Comment


                      • #12
                        Well, FYI...This just happened to me, friggin Monday Morning lateness and IRATE client. To make a long story short. Download the patch and update your time. If you try to update it without the patch, it wont work. So the answer is....download the patch Daylight Saving Time Help and Support Center

                        400Degreez....take two of these and walk it out!

                        Comment


                        • #13
                          Time issue...

                          27Oct09
                          All phones were on Standard time, checked all issues in DHCP and correct.
                          Noticed comment about phone getting DST dates from ShoreTel server.
                          Checked for patch and was installed, retried patch and was told later version existed. Did MS updates as of 27Oct09 and restarted server and phones now indicate correct time. Let's see what happens when we go to Standard time in a few days.

                          Uisng 8.1 on Server 2003 R2 with SP2 and latest patches to date.
                          Roy :dots:

                          Originally posted by 400degreez View Post
                          Well, FYI...This just happened to me, friggin Monday Morning lateness and IRATE client. To make a long story short. Download the patch and update your time. If you try to update it without the patch, it wont work. So the answer is....download the patch Daylight Saving Time Help and Support Center

                          400Degreez....take two of these and walk it out!

                          Comment


                          • #14
                            After verifying that the phones are in the correct site, and that the site has the correct time zone set. Please try reinstalling the following Daylight Savings Time patches from Microsoft.

                            Download details: Update for Windows Server 2003 (KB970653)

                            Download details: Update for Windows Server 2003 (KB970653)

                            Comment

                            Working...
                            X