cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Community Helping Community

CUCM Digit Manipulation Order of Operation

2632
Views
20
Helpful
3
Comments

Digit manipulation can be classified as:

    a. Implicit: As part of routing process
        ○ Translation Pattern
        ○ Route Pattern
        ○ Route Lists

    a. Explicit: Transformation after routing decision
        ○ Incoming Calling/Called Party Settings on gateways, trunks (or device pools)
        ○ Calling/Called Party Transformation CSS on gateways, trunks (or device pools)
        ○ Calling Party Transformation CSS on phones (or device pools)

 

As the call is being processed, the order by which digit manipulation applied is as follow:

You can see that the closer to the gateway, the higher the precedence of the manipulations. It is important to remember that if you manipulate on RP without modifying RL-RG manipulations (left them as default values), RP manipulations will take effect. If you modify any parameter in RL-RG manipulations (even if one), RP manipulations will be fully ignored. Same is applicable with Xformation Patterns and RL-RG manipulations.

 

Example#1

 

Let's assume that you changed 'Calling Party Transform Mask' under RP > Calling Party Transformations and changed 'Called Party Number Type' under RL-RG > Calling Party Transformations, in this case all settings under RP > Calling Party Transformations will be ignore including 'Calling Party Transform Mask'. The settings  under RL-RG > Calling Party Transformations will be used even the empty one for 'Calling Party Transform Mask'.

 

Example#2

 

Let's assume that you changed 'Calling Party Transform Mask' under RP > Calling Party Transformations and changed 'Called Party Number Type' under RL-RG > Called Party Transformations, in this case all settings under RP > Calling Party Transformations will be used and all settings under RL-RG > Called Party Transformations will be used.

Comments
Frequent Contributor

Hello,

 

What is the expected behaviour if I have the following:

1. Route Pattern with "Use Calling Party's External Phone Number Mask"enabled - this effectively uses the mask set on the Phone DN. Nothing else enabled on the RP transformations. Let's say DN is 2000, External Mask on DN is +43XXXX

2. SIP Trunk Outbound "Calling Party Transformation CSS" with Calling Party Transformation that has "Use Calling Party's External Phone Number Mask"  disabled and for example "Calling Party Transformation Mask" configured for some specific mask like for example 9XXXX

 

This is important as the matched calling party number in step 2 has to be coordinated with the expected result in step 1 - masked or unmasked number.

For example:

Step 1 - result - calling number changed to +432000

// assuming the next step should match on the masked DN number

Step 2 - result - 92000

Or will one of those maskings be ignored?

 

Beginner

Hi @Stoyan Stoitsev

 

Since the SIP Trunk is close to destination for OB calls the scenario 2 will take effect. And by the way Route pattern transformations apply only when a route pattern is pointed directly to a gateway.

 

Please check the para 6 in the link for more reference.

http://www.ciscopress.com/articles/article.asp?p=1745737&seqNum=4

 

Thanks,

Muk

 

Please Rate, if helpful.

Beginner
@Mohammed al Baqari wrote:

Digit manipulation can be classified as:

    a. Implicit: As part of routing process
        ○ Translation Pattern
        ○ Route Pattern
        ○ Route Lists

    a. Explicit: Transformation after routing decision
        ○ Incoming Calling/Called Party Settings on gateways, trunks (or device pools)
        ○ Calling/Called Party Transformation CSS on gateways, trunks (or device pools)
        ○ Calling Party Transformation CSS on phones (or device pools)

 

As the call is being processed, the order by which digit manipulation applied is as follow:

You can see that the closer to the gateway, the higher the precedence of the manipulations. It is important to remember that if you manipulate on RP without modifying RL-RG manipulations (left them as default values), RP manipulations will take effect. If you modify any parameter in RL-RG manipulations (even if one), RP manipulations will be fully ignored. Same is applicable with Xformation Patterns and RL-RG manipulations.

 

Example#1

 

Let's assume that you changed 'Calling Party Transform Mask' under RP > Calling Party Transformations and changed 'Called Party Number Type' under RL-RG > Calling Party Transformations, in this case all settings under RP > Calling Party Transformations will be ignore including 'Calling Party Transform Mask'. The settings  under RL-RG > Calling Party Transformations will be used even the empty one for 'Calling Party Transform Mask'.

 

Example#2

 

Let's assume that you changed 'Calling Party Transform Mask' under RP > Calling Party Transformations and changed 'Called Party Number Type' under RL-RG > Called Party Transformations, in this case all settings under RP > Calling Party Transformations will be used and all settings under RL-RG > Called Party Transformations will be used.


Thanks Mohammed. Definitely cleared some issues for me. Very helpful. Want to confirm the rule again (Even I see that you have explained).

Called party xformation on Gateway ports (MGCP) will also follow the same rule. 

e.g

  1. Called 1.212-234-5567 (RP with Pre Dot & +1) --> (RL / RG1 without DM ) --> SIP Gateway -- SP to Get +E164. (+1 from RP)
  2. Called 1.212-234-5567 (RP with Pre Dot & +1) --> (RL / RG2 with DM of Pre Dot & 1 ) --> MGCP VG --> SP to get 1212-234-5567 (1 from RG2)
  3. Called 1.212-234-5567 (RP with Pre Dot & +1) --> (RL / RG3 without DM ) --> MGCP VG (called Xform to append 123--> SP to get 123-212-234-5567 (123 from called xform)

Thanks for assistance. 

Nasir

CreatePlease to create content
Content for Community-Ad
FusionCharts will render here