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.
Contact Center users dial out/call customers from their computers via a desktop based application like Cisco Finesse Agent / CAD (Cisco Agent Desktop) application or any other 3rd party application.As per organizational process the requirement is ...
i want share with you my setup, how i configure TMS 15.6.0 with SQL 2012:
-first of all this deployment design in LAB just for practice, my deployment contain SQL and TMS in same server if you need to install TMS in another server yo...