Exclude number from translation pattern

[Gordon Ross]

Say I have a translation pattern of 01632 12XXXX

I'd like to exclue 01632 123456 from the pattern.

Creating a null pattern of 01632 123456 won't work as CUCM will check the freshly translated number for another match (and so rematch the same pattern)

This is on CUCM 8.6

Any suggestions?

Thanks,

GTG

[Carlo Poggiarelli]

Hi Gordon.

You can create a specific translation pattern for 01632123456 and select "Block this pattern" option or leave empty "called party transform mask"

HTH

Regards

Carlo

Please rate all helpful posts

"The more you help the more you learn"

[Gordon Ross]

But surely "Block this pattern" will cause the call to be rejected?

And a blank Called Party Transformation Mask would result in a Null translation which will mean that CUCM would rematch the same pattern when it itteratively tries to find a match.

GTG

[Joseph Martini]

The first thing that comes to mind is that CUCM will find the most specific match, so if you do have a translation pattern

01632 12XXXX and a translation pattern 01632 123456, which leaves the number unmodified, the 01632 123456 would be matched even if the two patterns are in the same partition.  Then as long as the translation pattern CSS cannot see itself or the other 01632 12XXXX pattern you should be all set to route the call to the final destination.

[Gordon Ross]

But once CUCM performs a translation pattern, it checks the new number for matching translation patterns.

So a pattern matching 01632 123456 translating to 01632 123456 will match, be translated, and CUCM will then search again for a matching pattern, find 01632 123456 (again!),  translate it to 01632 123456, etc. ad infinitum.

GTG

[Joseph Martini]

My last point prevents the looping you're thinking of. 

Then as long as the translation pattern CSS cannot see itself or the  other 01632 12XXXX pattern you should be all set to route the call to  the final destination.

Example:

Translation pattern for 01632 123456 is in partition A, and does nothing to the number, so after the translation pattern match you still have 01632 123456 as the called number.  There's a setting on the translation pattern for Calling Search Space (CSS), set this to CSS_partition_B only.  Now you are correct that CUCM will check again for matches, but we have removed partition A from the available partitions so the translation pattern cannot be matched again since partition A is no longer in our CSS.  The final destination device for 01632 123456 would of course have to be in partition B in this example to ring.

[Mohsin Khan Feroz]

In that Case, Creat a Specific Xlation pattern with 01632 123456 and give the "Called Party Translation" as any digits which has no Route either internally or Externally.

If you Do not want to Route the call then Block it. If you Want to route the call then provide the route.

How do you want to treat this call?

Rate if it helps!

Mohsin..

[Carlo Poggiarelli]

Hi Gordon.

Since you haven't specified which destination you want to send a call for that number, I assumed that the call has to be rejected.

Regards

Carlo

Please rate all helpful posts

"The more you help the more you learn"