Cisco Bug: CSCtc17462 - CVP keeps ring-back leg open unnecessarily
Dec 30, 2016
- Cisco Unified Customer Voice Portal
Known Affected Releases
Symptom: In a comprehensive SIP call flow where CVP first connects the ingress leg to a VXML gateway leg it will utilize a ringback dial-peer to generate ringback to the caller while it transfers the call from the VXML gateway to the final destination (egress gateway, CUCM, ...). CVP does this by disconnecting the call from the VXML gateway and then sending an INVITE to the ringback dial-peer. Only when mendia is established with the ringback dial-peer it will continue to send an INVITE to the egress gateway. When that destination sends a 183 Session In Progress and indicates it can generate ringback tone, CVP Call Server will re-negotiate media with the ingress leg to receive that ringback tone. It does however not instruct the ringback dial-peer to stop generating ringback, i.e. it only sends a BYE to that session once the egress session is fully up. This causes the ringback dial-peer session to continue streaming RTP to an ingress gateway for a while, even though that's no longer listening. Conditions: CVP in a comprehensive callflow.
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