topic Re: CUCM Translation Pattern Called Number no Working for Blocked Call in Collaboration Applications

CUCM Translation Pattern Called Number no Working for Blocked Calls

FPENTEADO — Tue, 04 Feb 2025 12:42:08 GMT

I create a Translation Pattern with option to blocked by Called Number and this only work with Specific Pattern, not working with range Pattern

Example 744589, blocked calls to this Directory Number, but 74458X doesn't work, and call goes to Directory Number. I tried everything like change CSS, other options to cause blocked but doesn't work.

Re: CUCM Translation Pattern Called Number no Working for Blocked Call

Roger Kallberg — Tue, 04 Feb 2025 12:56:07 GMT

Sounds like there is a more specific match in a partition in the used CSS. The number analysis in CM will always select the best match and if you have the directory number and the translation pattern with the range match visible in the CSS used by the caller the call routing analysis will pick the more specific, ie the directory number.

Re: CUCM Translation Pattern Called Number no Working for Blocked Call

FPENTEADO — Tue, 04 Feb 2025 13:07:40 GMT

Translation Patter partition appears First than Directory Number partition in my CSS. They will not see first, and see most specific, even if partition for TP is "above" from DN?

Re: CUCM Translation Pattern Called Number no Working for Blocked Call

Roger Kallberg — Tue, 04 Feb 2025 13:36:10 GMT

Let say that the called number is 744589 and there is DN that is in PT named Internal that is 744589 and then you create a block TP in lets call in PT Blocked that matches 74458X. Both of these PTs are in the CSS visible to the caller. The result of the number analysis in CM will come out as that this TP is a less specific match than the DN. The order of partitions only have relevance when there are two or more equally matched items and in you're setup that's not the case.

Re: CUCM Translation Pattern Called Number no Working for Blocked Call

Roger Kallberg — Tue, 04 Feb 2025 21:09:17 GMT

If you want this to work you cannot have the partition with the directory numbers directly visible in the callers CSS. You could do something along with this.

Create a PT named Blocked
Create a PT named Allowed
Put these PTs into a CSS named Filter
Assign the Filter CSS to the calling device(s)
In the PT named Blocked create a TP that matches what you'd want to restrict calling to, for ex 74458X
In the PT named Allowed create a TP that matches for ex 7445XX. Set the outbound CSS on the TP to something that sees the PT where you have your DNs, lets say your DNs are in PT named Internal, then the egress CSS on the allowed TP needs visibility of that PT

This should result in that calls to numbers 74458X are not allowed, but anything else in 7445XX range is.