Customer has a new Unity Connection 8.6.3 cluster. One site is in Los Angeles, and the other in Phoenix. The publisher (in Los Angeles) is set to use LA Time. The subscriber, located in Phoenix (which incidentally doesn't observe DST, but is not available as an option), is set to Denver.
All the users are in PST. The timestamps of all the messages are showing up one hour ahead.
Both servers using the same NTP and are synced. Both systems set to their timezones.
Each user is set to the Los Angeles time on the first page of the user account.
Messages retrieved are all coming up one hour ahead.
Thanks guys. I wasn't aware of this particular little issue.
I spoke with TAC about it. I'm kind of puzzled as I'd think messages would be stored with UTC date time stamps, and then read out based on the setting of the individual user. TAC indicated that their was a documentation defect bug about this, but there are currently no plans to change the behavior.
The 2021 IT Blog Awards, hosted by Cisco, is now open for submissions. Submit your blog, vlog or podcast by Friday, December 3.
To learn what's new in this year's competition or to gain insights into the judging considerations, check out t...
Greetings, Wanted to share a few lessons learned while migrating from a distributed to centralized IMP deployment. Our current setup included many CUCM/IMP distributed clusters with centralized Expressway server for MRA login. We did not wish to perf...
Parsec's Cisco UCCE/PCCE CC Connector application for CRM works as a bridge between the CRM and Cisco UCCE/PCCE CC solution.The CRM can be any cloud based CRM like Salesforce (SFDC), ServiceNow ,MS Dynamics or a 3rd party CRM.The CRM user/Agent will have ...
It’s a feature which allows CUCM to determine whether the phone is in its home location or a roaming station.By enabling this feature users can roam from one site to another site and acquire the site-specific settings such as Codecs, MRGL, Call rout...