Cisco Bug: CSCtb97379 - Inconsistent DisconnectedEv cause code after RT phone connected conf
Jul 07, 2017
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: For CTI Clients on Unified Call Center Express (UCCX), a Disconnected Event will be missing after an Agent on RT Pro phone does a connected conference between a caller and another phone, then one of the non-agent party disconnects. For CTI Clients such as CAD (Cisco Agent Desktop), the client will still think the agent is on a conference even though there are only two parties on the conversation. Conditions: The following is an example of such case: 1. Caller calls UCCX Route Point and gets directed to an Agent utilizing an RT phone. 2. RT phone agent picks up and initiates a new call on one of his secondary lines to another extension. 3. Once the other extension picks up, RT phone agent completes a connected conference between all three parties. The agent does this by clicking the conference hardkey, pressing the Active Calls softkey, and selecting the extension to conference. 4. Once all parties are connected into a conference, one of the non-agent party drops. There will be no Disconnected event sent to the CTI Clients. For CAD (Cisco Agent Desktop), it will still show that the Agent is still on a conference call even though there are only two participants in the conversation.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases