Calling Party Transformation Help

[ricky-ho]

I was able to configure a DN "\+15552223333" and a corresponding Calling Party Transformation to make its outbound Caller ID display as "5552224444" on both internal (CUCM 88XX phones) and external (cell phones).

When I try to do the same thing with a DN "77777" that is assigned to a Device Profile (instead of a Device), the Caller ID on external calls displays "5552224444" correctly, but internal calls it still displays "77777".

Is there something I'm doing wrong?

It looks like both "\+15552223333" and "77777" are in the same partitions.

I can provide more details, I just don't know what else is pertinent.

[Maren Mahoney · Accepted solution]

You will have applied the Calling Party Transformation CSS to the outbound trunk to make the outbound caller ID what you want. Internal calls would not use the trunk and so would not be modified.

On the Phone configuration page there is a field "Caller ID for Calls From This Phone" that can do what you are asking. Uncheck the box for "Use Device Pool CSS", and select the Calling Party Transformation CSS that contains the modifier for 77777.

Maren

[ricky-ho]

Thank you Maren.

Even though I'm configuring Device Profiles that correspond to each agent, I had to uncheck the setting for "Use Device Pool CSS" on the physical phone device that the agent logs into. Additionally I had to make sure the CSS I selected had the Partition that "contains" the Calling Party Transformation Pattern Configuration. And I had to make sure this same CSS had the Partitions that allow internal and external calls (separate partitions). 

[Maren Mahoney]

The setting should only affect caller ID, and should only impact calling patterns that match. So create the one pattern and put it in a unique partition, then put that partition in a unique CSS and apply that CSS to the phone. You shouldn't need anything else in there.

Depending on how many of these patterns you need to create, and depending on how many Device Pools you have, applying the transformation CSS at the Device Pool may be the path of least resistance. But that entirely depends on your needs.

I'm glad it helped!

Maren

[Roger Kallberg]

If I read this correctly you’re saying that you have the partition(s) that allows calls internally and externally in the CSS used for calling party transformation. Is that correct? If so that’s absolutely incorrect. You should never have partition(s) used for calling party transformation routing and transformation in the same CSS as this would lead to unpredictable results. These should be kept separate from each other.

[ricky-ho]

Yes, I created a CSS called CSS-TRANSFORM.

It has 2 partitions right now: PT-INTERNAL-TP and PT-US-PSTN

If I remove PT-US-PSTN, I'm unable to make external outbound calls from the Device Profile.

If I remove PT-INTERNAL-TP, the Caller ID does not get transformed. This is the Partition that my Calling Party Transformation Pattern Configuration is set to.

Is this what you meant? If yes, then what is the proper way to do this?

[Maren Mahoney · Accepted solution]

You want two CSSes. CSS-Transform-Internal and CSS-Transform-External. Each with the relevant partition(s) [PT-Transform-7777 and PT-Transform-PSTN) and applied differently. @Roger Kallberg is 100% correct on that point.

Note that by using the "Caller ID for Calls from this Phone" you will modify the Caller ID before the call is sent through call routing. You should not need the partition where the 7777 is modified in the PSTN partition, but it wouldn't hurt anything either.

Maren

[Roger Kallberg · Accepted solution]

You should keep transforms in separate partition(s), one or multiple depending on your needs, and put these PTs into a CSS, or again multiple CSSs depending on your needs. Then you should put your call routing configuration, route patterns, translation patterns and directory numbers, in other partition(s), again one or multiple depending on your needs, and put these PTs into a CSS, or again multiple CSSs depending on your needs. It is imperative that you do not have transforms and call routing configuration mixed in either the same partitions or calling search spaces.

[ricky-ho]

So I created a new Partition for my Calling Party Transformation called PT-INTERNAL-TRANSFORM

I also created a new CSS called CSS-TRANSFORM that only has PT-INTERNAL-TRANSFORM

I changed the CSS of the DN "77777" on the Device Profile back to the original CSS (with the routing config, etc). I had originally changed this to CSS-TRANSFORM - I don't know for what reason.

And everything still seems to work with this segregation.

[Roger Kallberg]

Glad to hear that.