Route pattern or Translation pattern

[neteng2323]

We don't normally do this as a rule but we have one particular person that has moved to a new location but still wants calls to his old DN coming to his new DN in the new location (different CSS) .  I know I can set up call forwarding but I'd rather handle this using a route pattern or translation pattern and let him "own" his old DN in the old CSS as well.    So which one is best for this and how to implement it?  I tried adding a translation pattern but it was giving me this error "Add failed. Cannot insert or update pattern. A DN exists with the same pattern and partition."

[Vivek Batra · Accepted solution]

First, you can't use route pattern as route pattern will always hit the gateway/trunk untill and unless you somehow get the work around of looping it back.

Second, translation pattern should work for you however you need to delete the users older DN. Once deleted, create new translation pattern with same as older DN. All respective callers should see this partition. This translation pattern CSS should see the partition of users new DN.

- Vivek 

[Carlo Poggiarelli · Accepted solution]

Hi.

+5 to Vivek for hi usual great suggestion :)

Just a more tip

You don't need to remove the DN before creating TP, Just create a new Partition and assign the suggested TP to that partition.

Than add that partition to all CSS in use and put it on top all other partition in order to let the CUCM to choose the TP before the internal DN.

Just another way to do it :)

HTH

Cheers

Carlo

[Vivek Batra]

Hi Carlo,

Yes.. Other way of doing it (+5) :)

-Vivek

[neteng2323]

Thank you both for your suggestions!