In the spring of 2007, the start date and end date for daylight saving time (DST) change in order to comply with the Energy Policy Act of 2005. DST dates for 2007 in the United States and Canada start three weeks earlier, 2:00 A.M. on the second Sunday in March, and end one week later, 2:00 A.M. on the first Sunday in November.
Due to these changes, the Cisco CallManager, the IP Phones and the Cisco Unity can have issues with time zone.
Review the requirements listed for the appropriate product in order to make the Cisco CallManager, the IP Phones and the Cisco Unity accept the changes to DST in 2007.
This issue is tracked in Cisco bug ID CSCsf07523 for the Cisco CallManager 4.x and earlier. Manually reset the time on the servers in order to workaround this issue.
In order to resolve this issue on a Cisco CallManager that runs on a Microsoft Windows version of the operating system (OS) 4.x and earlier, apply these DST fixes:
·the IP Phone load
Cisco recommends the application of the OS patch first. Then, during a separate maintenance window, apply the appropriate Engineering Special (ES) version of
Cisco CallManager, as mentioned in the First Fixed-in Version:
All the Cisco CallManager versions 4.x and earlier run on the Cisco IP Telephony (IPT) operating system, which is the Cisco version of the Windows 2000 build.
Therefore, in order to obtain the 2007 DST changes required for the operating system, apply either of these versions, which are available from Cisco Downloads:
Cisco Third Generation IP Phones (7941/7961/7971):
This issue is documented in Cisco bug ID CSCse47164 for the Cisco third generation IP Phones, which require a Sun Java Patch in order to accept the U.S. DST changes. These IP Phone loads incorporate the DST fix for the Cisco third generation IP Phones:
·8.0(4) ES06 (00.01)
The DST fixes for the correct Cisco CallManager version must also be applied in order to support this change.
Cisco Third Generation IP Phones (7970/7971/7961/7941/7911/7906):
The time change for Daylight Savings time may not take affect automatically for a third-generation IP Phone that runs SCCP or SIP loads older than 8.2(2).
This issue is documented in Cisco bug ID CSCsh12444.
These are the third-generation IP Phones:
After the phone is upgraded to 8.2(1) or 8.0(4)SR3 in order to get the fix for the 2007 DST changes, this issue can appear.
In order to workaround this issue, reset the IP Phone from the Cisco CallManager Administration (CCMAdmin) in order for the phone to obtain the correct time. A power cycle of the phone does not fix the time.
The conditions required for the phone to update the time zone are the root cause of the bug. Without this fix, the only time the phone updates the time zone is if the clock drifts more than 10 seconds off of the NTP server time.
If the phone is power cycled after it has the correct time, the time returns to the wrong time, off by an hour.
The fix for this bug is available in these phone loads and later:
Media Convergence Servers (MCSs):
This issue is documented in Cisco bug ID CSCsf07541 and CSCsh20360 for the MCS. These Cisco MCS OS versions include the Microsoft Hotfix KB924840 for the Windows 2000 based operating systems:
These versions are available from Cisco Downloads. Upgrade to one of those OS versions in order to get the fix.
Cisco Unity/Cisco Unity Bridge:
The potential problem with the Cisco Unity relates to Inbox timestamps, which can be incorrect by an hour for three weeks in the spring and one week in the fall for the year of 2007 and beyond. In other words, the Cisco Unity voicemail timestamps can be off by one hour during the periods when the new DST begins or ends. This can impact any event correlation activities that are performed as a part of normal operations, troubleshooting, or monitoring.
If the patches to Windows and the Cisco Unity are not applied, adjust the time manually through the Windows operating system.
In order to resolve this issue, apply these fixes and patches:
The features and version that are used dictate the specific patches needed. Some systems can require patches to the operating system, the Java Runtime Engine and a specific Cisco Unity Engineering Special (ES). Other systems only require the operating system patch. A single downloadable file, available from Cisco Downloads, bundles all the patches necessary for the Cisco Unity and the Cisco Unity Bridge. Complete these steps in order to resolve the timestamp issue:
Download the ZIP file.
Extract the contents into a folder on the Cisco Unity or Cisco Unity Bridge system.
Locate and open the ReadMe.txt file within the folder that the ZIP extraction created.
Complete the instructions provided in the ReadME.txt file.
Refer to Cisco bug ID CSCsh63361 for more information.
This table lists the Cisco Unity and Cisco Unity Bridge versions to which each patch applies. If a version of the Cisco Unity is not listed, no patch is necessary.
Hello, I am a final user who´s traying to find out some source of knowledge for some issues I am facing with my new Cisco 8845 3PCC connected to an Issabel PBX/Asterisk. I am coming from a “yeahlink” user experience, so It´s been quite a change in ab...
Hello, I have about 15 remote sites and 2 data centers. The data-centers both have CUBES that connect to the PSTN via provider SIP trunks. Each remote site also has an SRST. I have always assigned MTP via the MRG list for each site ...
Hi Peeps, I'm running a 12.0 cluster, and using solarwinds to monitor it. We constantly get "alerts" for phone registration rejected. I've argued with management to disable this useless alert, but they believe it to be valid. So I'm...
Hi,My question today is for the different version of roomkits, room kit pro, room kit plus and MX700. Each of these have dual monitors. These devices are all registered to webex portal hub. Currently during a webex, the first monitor dis...