Cisco Bug: CSCte46033 - Agent call from HTTP Trigger results in call stuck in Offering state
May 04, 2017
- Cisco Unified Contact Center Express
Known Affected Releases
Symptom: Script receives an HTTP trigger, places an outbound call, locates an available agent, and then connects that agent with the outbound call. The script is working to the point of successfully delivering the call to the agent, but at the conclusion of the call the agent is stuck in a "Reserved" state and the call is left in CAD in an "Offering" state. Conditions: Script contains the following logic: 1. An HTTP trigger initiates the application. 2. An outbound call is made. 3. A CSQ resource is located using the outbound call contact (as opposed to the "triggering-contact") and the outbound call is delivered to the agent. 4. The agent answers and is connected to the outbound call destination. 5. Thereafter CAD does a pop to a website based on information received from the HTTP trigger.
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