Roggers, PG and AW keep going back an hour. We have manually changed the time to correct this issue but sit there and watch it fallback an hour again. Has anyone seen this issue? Currently running ICM 7.2(1)
Sounds like you have NTP (network time..) synchronization. This is managed by your Call Manager.
here is some info from one of the guides:
The Disable ICM time synchronization checkbox in the MDS and DMP Properties dialogaffects time synchronization between systems. Since the Windows operating system uses itsown integrated time service--making it unnecessary for the ICM to perform a separate timesynchronization--the box is checked by default. The ICM software documentation states thatyou should accept this default, except in cases where the PG is configured as a workgroupmachine (that is, not a domain).
In most enterprises it's managed by a Stratum 2 NTP source - generally a router or a Unix box. Normally there are several of these - three is better than 2. Some large enterprises have their own Stratum 1 source, external clock and all - but that's big bickies.
The conventional ICM implementation is to point the PDC emulator on the ICM DC (typically the secondary DC where the FSMO roles have been moved) at the Stratum 2 box. That provides the NTP source for the domain. All members of the domain get their time synchronization from the DC.
You are correct about disabling ICM time sync. On boxes not in the domain (CVP, Media Stores, PGs) point the NTP source directly at the Stratum 2.
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...