I want to forward a company number to the cellphone of an external worker, with no physical phone in the company. Because there is no phone device, I can't set the external phone number mask and I need to use a Calling Party Transformation Pattern.
I have created a translation pattern of the company phone number to a DN:
On the DN, I have set Forward All to the cellphone:
I have created a Calling Party Transformation Pattern so that the DN is translated to the company number:
The CSS of the Forward is called DE_Redirecting, and in this CSS is the Partition DE_Redirect.
In this DE_Redirect Partition, there is a route pattern that allows calling to the PSTN and the Calling Party Transformation Pattern I created.
When I call the company number, the call is sent out, but it is blocked by the provider because the DN is used instead of the company number:
Why is the Calling Party Transformation Pattern not applied?
Accepted Solutions
The CSS used for call forwarding needs to see the partition that is used for call routing, but not the partition that is used for the transformation pattern. The partition used for the transformation pattern should be in another CSS that is then set as the Calling Party Transformation CSS for outbound calls on the trunk. See the below pictures to make this clearer hopefully.
This CSS does and should not see any partition(s) that are used for call processing, just as no CSS used for call processing, for example call forward, directory numbers or direct calls, should see any partition(s) used for transformations. Hopefully that's clear enough.
Out of curiosity to what CSS on the trunk did you make the change?
From what I can tell you do have the call routing and transformation in the same partition. Per your outline both of them are in the DE_Redirect partition. As @b.winter wrote that is not recommended as it will cause undesirable effects and issues. You should have call routing configuration, like RP, TP and DN, in partition(s) that are different than the ones where you have transformations. Furthermore these two “types” of partitions should never ever be in the same CSS’(s). You should have specific CSS’s used for transformation and others used for call processing, ie call routing. Even if it works now as you say I strongly advise you to rework this so that you have separate CSS and partition(s) for call routing and another CSS and partition for transformations.
Also per your outline you seem to have a DN that is not assigned to any device. That’s really not recommended as that would make it impossible to use the cleanup method of removing all unassigned DNs within Route Plan Report. It would be advisable to use either Remote Destination Profile or a CTI port to assign the DN with.
I assume that you still have a call forward all set on the DN and as that uses the CSS that you have set there it must have visibility of the partition used for call routing.
The CSS set on the DN and the device has no relevance for call forward, those are used when you make a call from the device itself, that's not what happens for call forward.
The CSS used for call forwarding needs to see the partition that is used for call routing, but not the partition that is used for the transformation pattern. The partition used for the transformation pattern should be in another CSS that is then set as the Calling Party Transformation CSS for outbound calls on the trunk. See the below pictures to make this clearer hopefully.
This CSS does and should not see any partition(s) that are used for call processing, just as no CSS used for call processing, for example call forward, directory numbers or direct calls, should see any partition(s) used for transformations. Hopefully that's clear enough.
No worries. It was maybe not clearly enough explained in the first few responses you got. I’d appreciate if you would set my explanation as an answer to your question.
