Desktop: Incomplete participant list after conference or transfer via route point when CVP is used for queuing - Revision history

Dosproul: 1 revision

2013-01-10T20:33:17Z

1 revision

← Older revision

Revision as of 20:33, 10 January 2013

Lobruce at 21:24, 4 December 2012

2012-12-04T21:24:57Z

← Older revision		Revision as of 21:24, 4 December 2012
Line 5:		Line 5:
	! '''Problem Summary'''		! '''Problem Summary'''
	\| Due to the nature of CVP queuing, agents will not see a complete list of participants after a conference or a transfer is completed via the CVP route point. The participants that an agent is expected to see in some of the most common scenarios is described below.<br>		\| Due to the nature of CVP queuing, agents will not see a complete list of participants after a conference or a transfer is completed via the CVP route point. The participants that an agent is expected to see in some of the most common scenarios is described below.<br>
-	1) The agent that is conferenced will only see the CVP port as a participant and will not see any other participants that are on the conference call. The agent that initiated the conference will only see the caller and the CVP port as participants but will not see the other agent on the call.	+	1) The agent that is conferenced will only see the CVP port as a participant and will not see any other participants that are on the conference call. The agent that initiated the conference will only see the caller and the CVP port as participants but will not see the other agent on the call. <br>2) When a transfer is completed via a route point, the agent that receives the call will only see the CVP port as a participant. <br>3) If a conference is completed after an agent answers the consult call, when the conferenced agent ends the call, the agent that is connected to the caller will continue to see the CVP port as a participant. If the caller ends the call in this scenario, then the agent that was initially connected to the caller will continue to see the CVP port as a participant. <br>4) If the conference is completed while the call is still queued at the CVP port, then the CVP port will no longer be a participant once the conferenced agent ends the call. If the caller ends the call in this scenario, the agent that the caller was connected to initially will no longer see any participants on the call. This does not impact any call control operations on the call. <br>5) If a logged in agent calls the CVP route point, that agent will not see any participants when the call gets answered. <br>6) Agent in a conference will not be able to see the wrap-up data set by another agent on that call but the wrap-up data will get set correctly on the call.
-	<br>	+
-	2) When a transfer is completed via a route point, the agent that receives the call will only see the CVP port as a participant.	+
-	<br>	+
-	3) If a conference is completed after an agent answers the consult call, when the conferenced agent ends the call, the agent that is connected to the caller will continue to see the CVP port as a participant. If the caller ends the call in this scenario, then the agent that was initially connected to the caller will continue to see the CVP port as a participant.	+
-	<br>	+
-	4) If the conference is completed while the call is still queued at the CVP port, then the CVP port will no longer be a participant once the conferenced agent ends the call. If the caller ends the call in this scenario, the agent that the caller was connected to initially will no longer see any participants on the call. This does not impact any call control operations on the call.	+
-	<br>	+
-	5) If a logged in agent calls the CVP route point, that agent will not see any participants when the call gets answered.	+
-	<br>	+
-	6) Agent in a conference will not be able to see the wrap-up data set by another agent on that call but the wrap-up data will get set correctly on the call.	+
	\|-		\|-
	! '''Error Message'''		! '''Error Message'''
Line 27:		Line 18:
	\|-		\|-
	! '''Release'''		! '''Release'''
-	\| Release 9.0(1)	+	\| Release 9.0(1), Release 9.1(1)
	\|-		\|-
	! '''Associated CDETS #'''		! '''Associated CDETS #'''
Line 35:		Line 26:
	<br>		<br>

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

Dosproul: 1 revision

2012-06-28T16:05:50Z

1 revision

← Older revision

Revision as of 16:05, 28 June 2012

Vijsharm: /* Incomplete participant list after conference or transfer via route point when CVP is used for queuing */

2012-06-14T21:31:46Z

Incomplete participant list after conference or transfer via route point when CVP is used for queuing

New page

== Incomplete participant list after conference or transfer via route point when CVP is used for queuing ==

{| border="1"
|-
! '''Problem Summary'''
| Due to the nature of CVP queuing, agents will not see a complete list of participants after a conference or a transfer is completed via the CVP route point. The participants that an agent is expected to see in some of the most common scenarios is described below. 
1) The agent that is conferenced will only see the CVP port as a participant and will not see any other participants that are on the conference call. The agent that initiated the conference will only see the caller and the CVP port as participants but will not see the other agent on the call.
 
2) When a transfer is completed via a route point, the agent that receives the call will only see the CVP port as a participant.
 
3) If a conference is completed after an agent answers the consult call, when the conferenced agent ends the call, the agent that is connected to the caller will continue to see the CVP port as a participant. If the caller ends the call in this scenario, then the agent that was initially connected to the caller will continue to see the CVP port as a participant.
 
4) If the conference is completed while the call is still queued at the CVP port, then the CVP port will no longer be a participant once the conferenced agent ends the call. If the caller ends the call in this scenario, the agent that the caller was connected to initially will no longer see any participants on the call. This does not impact any call control operations on the call.
 
5) If a logged in agent calls the CVP route point, that agent will not see any participants when the call gets answered.
 
6) Agent in a conference will not be able to see the wrap-up data set by another agent on that call but the wrap-up data will get set correctly on the call.
|-
! '''Error Message'''
| None
|-
! '''Possible Cause'''
| This is the expected behavior when CVP is used for queuing.
|-
! '''Recommended Action'''
| None
|-
! '''Release'''
| Release 9.0(1)
|-
! '''Associated CDETS #'''
| None
|}

 

[[Category:Cisco_Finesse,_Release_9.0]]