Skip to content

CUCM Digit Manipulation

Digit Manipulation: External Phone Number Mask

We can get a result similar to that with Prefix Digits, by using External Phone Number Mask, which we configure at the calling party line and invoke it at the route pattern.

For example, the Branch1 phones must all be presented to PSTN with the DID number 4048812100. I can do this requirement by setting the External Phone Number Mask, at line 2001, to 4048812100:

cucm-digit-manipulation-2016-06-05 07_26_54
cucm-digit-manipulation-2016-06-05 07_27_20

Remember to set the Use Calling Party External Phone Number Mask checkbox at the route patterns. Otherwise, the External Phone Number Mask line setting will be ignored.

cucm-digit-manipulation-2016-06-05 07_56_29

Here is the result of calling PSTN from Branch1:

cucm-digit-manipulation-2016-06-05 07_58_27

Use External Phone Number Mask is set to On at the route pattern and to Default at the Route list detail

In this case we get the same output as in the previous paragraph.

Use External Phone Number Mask is set to On at the route pattern and to On at the Route list detail

We also get the same output as in the previous paragraph.

Use External Phone Number Mask is set to On at the route pattern and to Off at the Route list detail

CUCM does not take the External Phone Number Mask into account, because digit manipulation at the rout list detail trumps the digit manipulation at the route pattern. Branch1 phone calls the PSTN line with a Calling party number of 2001.

cucm-digit-manipulation-2016-06-05 12_46_28

Use External Phone Number Mask is not set at the route pattern and to On at the Route list detail

CUCM extends the calling party number to its full format, despite the fact that the route pattern does not use the External Phone Number Mask.

Digit Manipulation: Calling Party Transform Masks

In my home lab, I emulate a branch office that bought a single DID number from Telco; there is no one-to-one mapping between internal DNs and external numbers. All DNs must be mapped to the single DID number 4048812100.

digit-manipulation-2016-06-04 19_02_53

In my home lab, I use Calling Party Transform Mask at Branch1’s Route List detail level. I use it to transform any internal DN to the corporate DID number.

digit-manipulation-2016-06-04 19_01_35

What if we configure the Calling Party Transform Mask at the route pattern level and not at the route list detail level?

cucm-digit-manipulation-2016-06-05 15_04_13
setting the Calling Party Transform Mask on the Route Pattern of Branch1
cucm-digit-manipulation-2016-06-05 15_04_27
Left the Calling Party Transform Mask blank on the Route List detail

Here is the result of a call to PSTN:

cucm-digit-manipulation-2016-06-05 15_22_19

The Calling Party Transform Mask was simply ignored. It seems like the blank Calling Party Transform Mask field in the Route list detail is more powerful that its peer at the route pattern; it’s because digit manipulation at the Route list detail level trumps anything set at the route pattern.

Let’s do the other way around. We clear the setting at the route pattern and make the Calling Party Transform Mask at the Route list detail.

cucm-digit-manipulation-2016-06-05 15_24_18
cucm-digit-manipulation-2016-06-05 15_24_47

The call now is correctly presented.

cucm-digit-manipulation-2016-06-05 15_25_12

Please click on the next page to read the rest of the article.

Pages: 1 2 3 4 5

Published inCCNP Collaboration

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *

copyright 2020 keyboardbanger.com