Cisco Bug: CSCte10783 - TCT remote browse & collect files get wrong timestamp of files
Mar 19, 2015
- Cisco Unified Communications Manager (CallManager)
- Cisco Unity Connection Version 7.1
- Cisco Unified Communications Manager Version 7.1
Known Affected Releases
Symptom: RTMT get wrong timestamps in some specific timezone because of Java API use 3-letter-abbreviation can not differentiate if CST means "China Standard Time" or U.S. "Central Standard Time", hence if Auto DST on RTMT (windows XP/Windows 2003) disabled before using a Non-DST applicable timezone, it will consider CST as U.S. "Central Standard Time" even the CCM server's actual timezone is "China Standard Time". As a result, all log files listed by TCT remote browse or downloaded by TCT are having a timestamp which are 14 hours ahead of actual time by comparison with the timestamp of the log's content. Conditions: Choose RTMT machine(windows XP/2003)'s timezone to any DST timezone but disable auto adjust, apply the setting, then choose non-DST one. In this case, we choose GMT+8 perth, disable DST, apply, then choose GMT+8 Beijing and apply again.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases