Hello, we had the same issue yesterday. We were running 4.1(3)sr5b and upgraded to 4.1(3) sr5d and it fixed the issue. It seemed to be a combination of the phones having their own DST calculator in them and whatever else the patch did. Check out this link:
Ginger thanks for the link! We performed the reboot on the Unity yesterday and believe that solved the problem. Now our Exchange 2000 SP3 (which was manually adjusted) has to be set 1 hour behind in order for the time stamp to be correct. Has anyone heard of a fix for this issue?
HAve you reviewed MS for issues regarding the change in handling of Daylight Savings time? They have a number of articles about that, and whether the local absolute time has been shifted by the automatic DST time changer. If the problem goes away next week (when we now switch to DST), then that's your issue. the solution may be found in a combination of MS and Cisco patches, depending on local system settings (is your widnows box set to automatically adjust for daylight saving time, etc.)
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...