Desktop: Client's system clock should be synchronized to the Finesse server system clock. - Revision history

Dosproul: 1 revision

2013-01-10T20:33:16Z

1 revision

← Older revision

Revision as of 20:33, 10 January 2013

Lobruce at 21:13, 4 December 2012

2012-12-04T21:13:09Z

← Older revision		Revision as of 21:13, 4 December 2012
Line 11:		Line 11:
	! '''Possible Cause'''		! '''Possible Cause'''
	\|		\|
-	For fields that display a duration, such as the Time in State field in the Team Performance gadget and the Max Time field in the Queue Statistics gadget, Finesse server publishes a time stamp in UTC format. The time stamp is then converted to a time stamp in the local time zone of the agent or supervisor desktop and duration is computed by comparing it with the current local time.	+	For fields that display a duration, such as the Time in State field in the Team Performance gadget and the Max Time field in the Queue Statistics gadget, Finesse server publishes a time stamp in UTC format. The time stamp is then converted to a time stamp in the local time zone of the agent or supervisor desktop and duration is computed by comparing it with the current local time.

	If the system clock on the agent or supervisor desktop is not synchronized with the system clock on the Finesse server, the duration will be incorrect.		If the system clock on the agent or supervisor desktop is not synchronized with the system clock on the Finesse server, the duration will be incorrect.
Line 25:		Line 25:
	\|-		\|-
	! '''Release'''		! '''Release'''
-	\| Release 9.0(1)	+	\| Release 9.0(1), Release 9.1(1)
	\|-		\|-
	! '''Associated CDETS #'''		! '''Associated CDETS #'''
-	\| ~~N/A~~	+	\| None
	\|}		\|}

	<br>		<br>

-	[[Category:Cisco_Finesse,_Release_9.0]]	+	[[Category:Cisco_Finesse,_Release_9.0]]  [[Category:Cisco Finesse, Release 9.1]]

Dosproul: 1 revision

2012-09-25T17:47:51Z

1 revision

← Older revision

Revision as of 17:47, 25 September 2012

Lobruce at 14:58, 24 September 2012

2012-09-24T14:58:41Z

← Older revision		Revision as of 14:58, 24 September 2012
Line 4:		Line 4:
	\|-		\|-
	! '''Problem Summary'''		! '''Problem Summary'''
-	\| Fields that display a duration on the Finesse gadgets will have incorrect values unless the system clock on the agent or supervisor desktop is synchronized with the Finesse server system clock~~. This does not apply to different~~ time ~~zones~~ between ~~machines - only when~~ the ~~minutes/seconds are different~~.	+	\| Fields that display a duration on the Finesse gadgets will have incorrect values unless the system clock on the agent or supervisor desktop is synchronized with the Finesse server system clock, accounting for the time zone difference between the server and the agent or supervisor desktop.
	\|-		\|-
	! '''Error Message'''		! '''Error Message'''
Line 10:		Line 10:
	\|-		\|-
	! '''Possible Cause'''		! '''Possible Cause'''
-	\| For fields that display a duration, such as the Time in State field in the Team Performance gadget and the Max Time field in the Queue Statistics gadget, Finesse server publishes a time stamp ~~which gets~~ converted to a ~~duration on~~ the agent or ~~the~~ supervisor desktop~~, based on~~ the current time ~~minutes on the agent or supervisor desktop~~. ~~Therefore, if~~ the system clock on the agent or supervisor desktop is not synchronized with the system clock on the Finesse server, the duration will be incorrect.	+	\|
-	The ~~server publishes the timestamps in UTC format and the client converts it into the local time zone and then computes the duration based on the current local time. The server and client need~~ not be in the same time zone~~. The~~ clocks must be synchronized ~~i.e~~., if the server ~~is 3pm~~ in ~~CA then~~ the agent ~~PCs~~ in ~~NY should be 6pm,~~ not 6:~~03pm~~ or 6:~~05pm~~.	+	For fields that display a duration, such as the Time in State field in the Team Performance gadget and the Max Time field in the Queue Statistics gadget, Finesse server publishes a time stamp in UTC format. The time stamp is then converted to a time stamp in the local time zone of the agent or supervisor desktop and duration is computed by comparing it with the current local time.
		+
		+	If the system clock on the agent or supervisor desktop is not synchronized with the system clock on the Finesse server, the duration will be incorrect.
		+
		+	Note: The desktops do not need to be in the same time zone as the Finesse server but the clocks must be synchronized. For example, if it is 3:00 P.M. on the Finesse server in California, it must be 6:00 P.M. on the agent's PC in New York (not 6:03 P.M. or 6:05 P.M.).
		+
	\|-		\|-
	! '''Recommended Action'''		! '''Recommended Action'''
-	\| Synchronize the system clock on agent and supervisor desktops to the Finesse server system clock. Use a common NTP server between server and client.	+	\|
		+	*Synchronize the system clock on agent and supervisor desktops to the Finesse server system clock.
		+	*Use a common NTP server between server and client.
		+
	\|-		\|-
	! '''Release'''		! '''Release'''
Line 23:		Line 31:
	\|}		\|}

-	<br>	+	<br>

	[[Category:Cisco_Finesse,_Release_9.0]]		[[Category:Cisco_Finesse,_Release_9.0]]

Ginod: /* Client's system clock should be synchronized to the Finesse server system clock */

2012-09-21T22:56:05Z

Client's system clock should be synchronized to the Finesse server system clock

← Older revision		Revision as of 22:56, 21 September 2012
Line 4:		Line 4:
	\|-		\|-
	! '''Problem Summary'''		! '''Problem Summary'''
-	\| Fields that display a duration on the Finesse gadgets will have incorrect values unless the system clock on the agent or supervisor desktop is synchronized with the Finesse server system clock.~~ ~~	+	\| Fields that display a duration on the Finesse gadgets will have incorrect values unless the system clock on the agent or supervisor desktop is synchronized with the Finesse server system clock. This does not apply to different time zones between machines - only when the minutes/seconds are different.
	\|-		\|-
	! '''Error Message'''		! '''Error Message'''
Line 10:		Line 10:
	\|-		\|-
	! '''Possible Cause'''		! '''Possible Cause'''
-	\| For fields that display a duration, such as the Time in State field in the Team Performance gadget and the Max Time field in the Queue Statistics gadget, Finesse server publishes a time stamp which gets converted to a duration on the agent or the supervisor desktop, based on the current time on the agent or supervisor desktop. Therefore, if the system clock on the agent or supervisor desktop is not synchronized with the system clock on the Finesse server, the duration will be incorrect.	+	\| For fields that display a duration, such as the Time in State field in the Team Performance gadget and the Max Time field in the Queue Statistics gadget, Finesse server publishes a time stamp which gets converted to a duration on the agent or the supervisor desktop, based on the current time minutes on the agent or supervisor desktop. Therefore, if the system clock on the agent or supervisor desktop is not synchronized with the system clock on the Finesse server, the duration will be incorrect.
		+	The server publishes the timestamps in UTC format and the client converts it into the local time zone and then computes the duration based on the current local time. The server and client need not be in the same time zone. The clocks must be synchronized i.e., if the server is 3pm in CA then the agent PCs in NY should be 6pm, not 6:03pm or 6:05pm.
	\|-		\|-
	! '''Recommended Action'''		! '''Recommended Action'''
-	\| Synchronize the system clock on agent and supervisor desktops to the Finesse server system clock.	+	\| Synchronize the system clock on agent and supervisor desktops to the Finesse server system clock. Use a common NTP server between server and client.
	\|-		\|-
	! '''Release'''		! '''Release'''

Dosproul: 1 revision

2012-06-28T16:05:49Z

1 revision

← Older revision

Revision as of 16:05, 28 June 2012

Vijsharm: /* Client's system clock should be synchronized to the Finesse server system clock */

2012-04-16T21:57:24Z

Client's system clock should be synchronized to the Finesse server system clock

New page

== Client's system clock should be synchronized to the Finesse server system clock ==

{| border="1"
|-
! '''Problem Summary'''
| Fields that display a duration on the Finesse gadgets will have incorrect values unless the system clock on the agent or supervisor desktop is synchronized with the Finesse server system clock. 
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| For fields that display a duration, such as the Time in State field in the Team Performance gadget and the Max Time field in the Queue Statistics gadget, Finesse server publishes a time stamp which gets converted to a duration on the agent or the supervisor desktop, based on the current time on the agent or supervisor desktop. Therefore, if the system clock on the agent or supervisor desktop is not synchronized with the system clock on the Finesse server, the duration will be incorrect.
|-
! '''Recommended Action'''
| Synchronize the system clock on agent and supervisor desktops to the Finesse server system clock.
|-
! '''Release'''
| Release 9.0(1)
|-
! '''Associated CDETS #'''
| N/A
|}

<br>

[[Category:Cisco_Finesse,_Release_9.0]]