Cisco Bug: CSCvs89295 - Calling party transformation mask is selected based on the pre transform calling number
Jun 04, 2020
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: The calling party transformation mask is selected based on the pre transform calling party number (extension assigned to the IP Phone). Conditions: >> For a better understanding please refer the below example: ++ Call flow: ----------------- IP phone -> CUCM -> sip trunk -> Cube ++ Calling number: 1002 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Pre transform calling number ++ Let's assume that 1002 initiated a call to 4444 ++ Now according to the CUCM config, let's say that there is a route pattern (4444) configured which is supposed to route the call out to a cube via a SIP trunk ++ Under the route pattern 4444, we have configured a prefix *64 under the Calling Party Transformations section ++ So when the call reaches the route pattern, the calling number is transformed to *641002 ++ We also have configured 2 calling party transformations in CUCM 1. Calling party transformation 1 is configured with pattern 1002 (configured with calling party transformation mask 123) 2. Calling party transformation 2 is configured with pattern *641002 (configured with calling party transformation mask 456) ++ The route pattern 4444 is configured to send the call to a SIP trunk ++ The SIP trunk is configured with a calling party transformation CSS under the Outbound calls section to transform the calling party by using a calling party transformation. ++ This is the point where we are confused, as to which calling party transformation will be selected among 1002 and *641002. ++ According to the DNA it was *641002 but we were observing from the SIP messages and the actual behavior that 1002 calling party transformation was being selected. ++ There is defect filed for incorrect behavior of the DNA (CSCvs56049) ++ Now when choosing the calling party transformation, CUCM will choose the pattern which is matching the pre transform calling number and the calling number will be transformed to 123.
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