Set Call Data API Request does not invoke CALL DATA UDPATE - Revision history

Dosproul: 1 revision

2012-01-04T20:56:56Z

1 revision

← Older revision

Revision as of 20:56, 4 January 2012

Lobruce: added release 8.5(3)

2011-12-15T17:59:31Z

added release 8.5(3)

← Older revision		Revision as of 17:59, 15 December 2011
Line 1:		Line 1:
-	== Set Call Data API Request does not invoke CALL_DATA_UDPATE ==	+	== Set Call Data API Request does not invoke CALL_DATA_UDPATE ==

	{\| border="1"		{\| border="1"
	\|-		\|-
-	! '''Problem Summary'''	+	! '''Problem Summary'''
	\| The Set Call Data API request returns a successful reponse, but no CALL_DATA_UPDATE is received.		\| The Set Call Data API request returns a successful reponse, but no CALL_DATA_UPDATE is received.
	\|-		\|-
-	! '''Error Message'''	+	! '''Error Message'''
-	\| None	+	\| None.
	\|-		\|-
-	! '''Possible Cause'''	+	! '''Possible Cause'''
-	\| You have sent a Set Call Data API request with one or more invalid variable parameters and ''no'' valid variable parameters. (For example, you sent the variable field as callWrapUpData instead of callWrapupData. This is invalid due to the difference in case for the letter 'u'.)	+	\| You have sent a Set Call Data API request with one or more invalid variable parameters and ''no'' valid variable parameters. (For example, you sent the variable field as callWrapUpData instead of callWrapupData. This is invalid due to the difference in case for the letter 'u'.)
	The SET_CALL_DATA_REQ must cause a change in a valid call variable. Finesse does not verify fields sent in a SET CALL DATA API request. Sending an invalid variable does not prompt a CALL_DATA_UPDATE from CTI unless other valid variables are sent along with it. A successul response indicates that the request was received, but does not mean that the request has changed the variables.		The SET_CALL_DATA_REQ must cause a change in a valid call variable. Finesse does not verify fields sent in a SET CALL DATA API request. Sending an invalid variable does not prompt a CALL_DATA_UPDATE from CTI unless other valid variables are sent along with it. A successul response indicates that the request was received, but does not mean that the request has changed the variables.
		+
	\|-		\|-
-	! '''Recommended Action'''	+	! '''Recommended Action'''
	\| Verify the syntax of the variable and resend the request.		\| Verify the syntax of the variable and resend the request.
	\|-		\|-
		+	! '''Release'''
		+	\| Release 8.5(1), Release 8.5(3)
	\|-		\|-
-	~~! '''Release'''~~	+	! '''Associated CDETS #'''
-	~~\| Release 8.5(1)~~	+	\| None.
-	\|-	+
-	! '''Associated CDETS #'''	+
-	\| None~~'''~~	+
-	\|-	+
	\|}		\|}

-		+	[[Category:Cisco_Finesse,_Release_8.5]]
-	[[Category:~~Cisco Finesse~~, ~~Release 8~~.5]]	+

Kemacdon at 14:32, 5 July 2011

2011-07-05T14:32:45Z

← Older revision		Revision as of 14:32, 5 July 2011
Line 10:		Line 10:
	\|-		\|-
	! '''Possible Cause'''		! '''Possible Cause'''
-	\| You have sent a Set Call Data API request with one or more invalid variable parameters and ''no'' valid variable parameters. (For example, you sent the variable field as callWrapUpData instead of callWrapupData. This is invalid due to the case of the letter 'u'.)	+	\| You have sent a Set Call Data API request with one or more invalid variable parameters and ''no'' valid variable parameters. (For example, you sent the variable field as callWrapUpData instead of callWrapupData. This is invalid due to the difference in case for the letter 'u'.)
	The SET_CALL_DATA_REQ must cause a change in a valid call variable. Finesse does not verify fields sent in a SET CALL DATA API request. Sending an invalid variable does not prompt a CALL_DATA_UPDATE from CTI unless other valid variables are sent along with it. A successul response indicates that the request was received, but does not mean that the request has changed the variables.		The SET_CALL_DATA_REQ must cause a change in a valid call variable. Finesse does not verify fields sent in a SET CALL DATA API request. Sending an invalid variable does not prompt a CALL_DATA_UPDATE from CTI unless other valid variables are sent along with it. A successul response indicates that the request was received, but does not mean that the request has changed the variables.
	\|-		\|-

Cchetty: 1 revision

2010-10-01T00:49:04Z

1 revision

← Older revision

Revision as of 00:49, 1 October 2010

Rfarber at 19:02, 30 September 2010

2010-09-30T19:02:34Z

New page

== Set Call Data API Request does not invoke CALL_DATA_UDPATE ==

{| border="1"
|-
! '''Problem Summary'''
| The Set Call Data API request returns a successful reponse, but no CALL_DATA_UPDATE is received.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| You have sent a Set Call Data API request with one or more invalid variable parameters and ''no'' valid variable parameters. (For example, you sent the variable field as callWrapUpData instead of callWrapupData. This is invalid due to the case of the letter 'u'.)
The SET_CALL_DATA_REQ must cause a change in a valid call variable. Finesse does not verify fields sent in a SET CALL DATA API request. Sending an invalid variable does not prompt a CALL_DATA_UPDATE from CTI unless other valid variables are sent along with it. A successul response indicates that the request was received, but does not mean that the request has changed the variables.
|-
! '''Recommended Action'''
| Verify the syntax of the variable and resend the request.
|-
|-
! '''Release'''
| Release 8.5(1)
|-
! '''Associated CDETS #'''
| None'''
|-
|}

[[Category:Cisco Finesse, Release 8.5]]