We upgraded VCS's to X8.2.1 for vulnerability remediation. When I look at Status->Calls->Calls the Duration appears to be calculated using the UTC time as the start time and not the local TZ offset. When I have been connected for 7 secs the Duration shows 5 hours 7 secs (the system is using valid NTP servers and is set at CST6CDT). Has anybody else experienced or noticed this?
I wondered if there has been a resolution to this as we seem to be seeing a similar issue under x8.2.2.
We set the VCS to 'GB' which should account for daylight savings, however, the time clock now shows an hour ahead of where it should be (i.e. BST (GMT+1) rather than GMT), the the call timers show calls as existing for an additional hour.
Obviously all the log are out as well.
We could force these back to GMT, but of course next spring we will find that the daylight offset will not be applied.
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...