Call Control: Reflecting state of a call that is ringing at the far end after Unified CCE failover

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
m (1 revision)
(One intermediate revision not shown)
Line 16: Line 16:
|-
|-
! '''Release'''  
! '''Release'''  
-
| Release 8.5(3)
+
| Release 8.5(3), Release 9.0(1) 
|-
|-
! '''Associated CDETS #'''  
! '''Associated CDETS #'''  
| <span style="font-weight: bold">
| <span style="font-weight: bold">
-
</span>None.
+
</span>None
|}
|}
<br>
<br>
-
[[Category:Cisco_Finesse,_Release_8.5]]
+
[[Category:Cisco_Finesse,_Release_8.5]]
 +
 
 +
[[Category:Cisco Finesse, Release 9.0]]

Revision as of 16:05, 28 June 2012

Call state of a call that is ringing at the far end is displayed as "Active"

Problem Summary If an agent makes a call to another device and CTI failover occurs while that call is ringing at the far end, the call is displayed as “active” on the desktop of the agent who initiated the call.
Error Message None.
Possible Cause Unified CCE returns the LocalConnectionState of the agent's device as CS_CONNECT, which Finesse interprets as a call with state ACTIVE.
Recommended Action Because there is no loss in functionality, the agent can continue to operate normally.
Release Release 8.5(3), Release 9.0(1) 
Associated CDETS #

None


Rating: 0.0/5 (0 votes cast)

Personal tools