Cisco Bug: CSCui98226 - Personal Callback stuck in Call Status 'A' with Call Result '0'
Feb 13, 2019
- Cisco Unified Contact Center Enterprise
Known Affected Releases
8.0(1) 8.5(1) 9.0(3) 9.0(4)ES
Symptom: Tagging a call as ERROR but dialer didn't Set Call Result as 2 (ERROR). Due to this, it was stuck in Call Status 'A' with Call Result '0', and further personal callbacks were rejected. Conditions: Personal Callback. When processing onTerminated from Voice Gateway, it checks for error code >=300, here since it was 487, it was tagging this call as ERROR but dialer didn't Set Call Result as 2 (ERROR).
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