Cisco Bug: CSCuo69589 - Cdcc is stuck waiting for DevicePauseResponse from RouteList
May 05, 2016
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: call to Unity connection and then make a external call from unity connection. the call will be fine. but the call disconnect, the voicemail port cannot release. Conditions: the outbound call go through the router list. the first trunk cannot route the call due to unavailable channel. and then go to next one and still fail. then go to next one and success. the issue just happen when the first trunk fail to route the call. The problem is that the Cdcc is stuck waiting for DevicePauseResponse from RouteList on a device that has already sent a ReleaseComplete (cause No Circuit Available). Although the RouteList rerouted the call to the GW on Node 5, the Call Control could not be moved to Node 5 and hence the VM port that initiated the transfer is stuck.
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