Cisco Bug: CSCtf04411 - RDNIS is populated in Calling Party on Mobility Connect calls
Jul 27, 2017
- Cisco Unified Communications Manager (CallManager)
- Cisco Unity Connection Version 7.1
- Cisco Unified Communications Manager Version 7.1
Known Affected Releases
Symptom: For Mobility Connect calls, the Redirecting number is being inserted into the Calling Party number in the following scenario. The "Calling Party Selection" for the Gateway config in CUCM is set to "Last Redirect Number (External)." A call is placed to a phone that has Mobility Connect enabled. The call is extended to the Remote Destination number. The ANI for that call is the Remote Destination number and not the original calling party. This is because "Calling Party Selection" is set to "Last Redirect Number (External). The last redirect number is this case is the Remote Destination number, but in the case of Mobility Connect calls this shouldn't occur. The calling party should be the originating calling party. Conditions: The "Calling Party Selection" for the Gateway config in CUCM is set to "Last Redirect Number (External)."
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