Global Transformations: Called Party Transformation Pattern
Similarly to the Calling Party transformation pattern, we can define a global transformation pattern in order to apply a Called party transformation independently from other constructs.
Here we will leverage Calling Party transformation pattern for the national PSTN call pattern, at Branch1:
- Eliminate all manipulations previously done at the route pattern level
- create a transformation pattern partition Trans_PT
- create a transformation CSS for called party Trans_CSS
- assign Trans_PT to Trans_CSS
- create a global transformation with the national PSTN call pattern. Set the Called Party Transform Mask to XXXXXXXXXX, so that only the right-most 10 digits remain.
- At first, I thought the pattern should have been 1[2-9]XX[2-9]XXXXXX. But after running the Dialed Digit Analyzer and debug voip dialpeer at the Branch1 gateway, I found out that the Branch1 gateway was receiving the whole pattern 9.1[2-9]XX[2-9]XXXXXX from the Route list/Route group, and not 1[2-9]XX[2-9]XXXXXX as I thought.
So the transformation pattern should be 9.1[2-9]XX[2-9]XXXXXX
- for the Branch1 gateway, in the Call Routing Information – Outbound Calls, uncheck Use Device Pool Called Party Transformation CSS, and set the Called Party Transformation CSS to the Trans_CSS we created.
- reset the gateway. Make the call.
The Importance of resetting route lists, route groups and gateways
I have been told by one of my Cisco collaboration instructors that it is extremely important to reset route lists, route groups and devices, each time I modify something related to them.
For example, let’s suppose we have an inbound PSTN call to our HQ gateway in Pennsylvania. The inbound call is from a 717xxxxxxx line, located in Pennsylvania too. The telco provider is sending only 7 digits to our gateway:
Without digit manipulation, the result would look like this:
HQ gateway receives only 7 digits from a PSTN subscriber line.
We apply some digit manipulation: we tell the HQ gateway to add a prefix of 9717 to inbound subscriber calls:
Despite that we get the call, nothing happens. That’s because we did not reset the gateway.
We reset the gateway, and look at the result again: