In a world of managed service and hosted collaboration solutions, there are a variety of ways to commission administrative tasks.
But for customers who still manage their own on-prem UC solutions, more often than not, they have received requests from their users to block certain numbers from dialing in.
Now, there are a few ways to go about blocking numbers. Using TCL scripts on gateways, using call handlers in Unity Connection, have carriers or circuit providers block them but none are as easy as configuring a single Translation Pattern in your Cisco UC Manager.
Let have a look.
For e.g.: We get a request to block all calls from ANI 1234.
A typical gateway has an Inbound Calling Search Space (CSS) configured with access to all internal extension and DIDs partitions (PT). In our example, we will call it Inbound_CSS
By adding a Translation Pattern (TP) as the first partition in Inbound_CSS, we can manipulate how to route the call.
The key, Route Next Hop By Calling Party Number parameter on the Translation Pattern.
Here’s how a typical call will route:
ANI_Filter_PT is added to Inbound_CSS as the first partition
Router Next Hop By Calling Party Number: Checked
This TP gets routed based on it’s CSS, ANI_Filter_List_CSS
Now as part of ANI_Filter_List_CSS, we have only one PT, ANI_Filter_List_PT
The ! Translation Pattern allows the call to route normally.
Here’s where we can add a new TP for 1234 to block the call from routing.
By adding just one TP, we can continue to control which calls get routed and which calls get blocked in the system.
The 1234 Translation Pattern in ANI_Filter_LIST_PT blocks the call to route normally, since it doesn’t have any CSS assigned and Route Option: Block this pattern is checked.
Now, what about calls with a blocked ANI (or unknown). Simple, we create a TP with a BLANK pattern
This goes to show how extensible and powerful translation patterns can be in your UCM environment.