Technotes: How to block Incoming calls in CUCM 8.x based on ANI with MGCP gateway

Document

Nov 3, 2011 11:09 PM
Nov 3rd, 2011


Introduction

This document covers the Technotes for Blocking calls in Cisco Unified Communications Manager (CUCM) 8.x and later based on Automatic Number Identification(ANI) when CUCM is using MGCP Gateway.

  • ANI (Automatic number identification) is a feature of telephony intelligent network services which permits subscribers to display or capture the telephone numbers of calling parties.

  • DNIS (Dialed Number Identification Service) is a telephone service that identifies for the receiver of a call the number that the caller dialed. It's a common feature of 800 and 900 lines. If you have multiple 800 or 900 numbers to the same destination, DNIS tells which number was called.

Problem Description

When CUCMs are using MGCP gateways instead of H.323 gateways blocking calls based on ANI or Calling Number becomes difficult or not possible in older Cisco Unified Communications Manager (CUCM) versions which is below 8.x

From CUCM 8.x and later versions this task can be accomplished by using “Route Next Hop By Calling Party”

Note:

  • If an MGCP gateway is used, from CUCM 8.x and later versions incoming calls can be blocked based on ANI or Calling Number. In the Older version of CUCM which is below 8.x, the only way to block unwanted calls is based on the DNIS information.

Solution

Block calls based on ANI in CUCM 8.x when CUCM is using MGCP gateway

MGCP GW -> inbound calling CSS called “Screen_all-incoming_calls_ANI_CSS” -> match to Translation pattern ! which has

“Route Next Hop By Calling Party” checked which changes the behavior to route the calls based on Calling number not the called number to next Calling search space called -> “block_certain_ANI-calls_CSS” -> which matches following transalation patterns shown as an example,

The CSS “block_certain_ANI-calls_CSS” should see following translations:

1) ! translation pattern with a CSS contains “All Phones partition” – This allows calls to route normally into the cluster.

2) 8001201 Blocking Pattern – Block calls coming from caller ID 8001201

3) 8601202 Blocking Pattern – Block calls coming from caller ID 8601202

ANI.JPG

Additional Information

Block calls based on ANI and DNIS when CUCM is using H.323 gateway

If an H.323 gateway is used, incoming calls can be blocked based on either Automatic Number Identifier (ANI) or Dialed Number Identification Service (DNIS) information, or both, through translation rules on the gateway (GW) configuration.

For an example of how to block calls based on specific calling numbers (ANI), refer to the Call Blocking Specific Calling Numbers

For an example of how to block calls based on specific called numbers (DNIS), refer to the Call Blocking Specific Called Numbers

Block calls based on DNIS when CUCM is using MGCP gateway

If MGCP gateway is used with the Older version of CUCM which is below 8.x the only way to block unwanted calls is based on the DNIS information. This is accomplished through translation patterns in the Cisco CallManager configuration.

An Translation pattern in CUCM must be created to match the inbound DNIS information (called party number). Then, the gateway in Cisco CallManager must be configured to have a Content Services Switch (CSS) with access to this Translation pattern first, based on the Translation pattern partition. Give the Translation pattern a CSS that has access to NOTHING. This sends the call nowhere, and the calling party receives a reorder tone.

Note: This method of blocking calls can only be accomplished based on the DNIS information (called party number) and not on the ANI (calling party number) information.

To block calls in the same manner at the Cisco CallManager level, use translation patterns. To do this, the DNIS or called number can be specified in a route pattern, then applied to the gateway. In this case, the "****" that is used to block the call is the Route or Block this pattern option.

Note: This can only block unwanted calls based on DNIS information and not on the ANI information.

Related Information

Average Rating: 5 (1 ratings)

Comments

bvanturn Tue, 05/15/2012 - 09:50

Great doc, I remembered reading this before and it came in handy today to resolve a specific customer scenario!

scottbob09 Fri, 09/07/2012 - 12:50

This writeup was a little too high level for me.

I found one at DOC-18367 that is more my speed.

Paul McGurn Thu, 08/01/2013 - 20:49

This works well, but if you have multiple gateways, you'll want to spend some extra time planning the final-hop CSS.  This solution won't scale well by cloning for each gateway, so you'll probably want to standardize the flow to be more of a global/regional solution.

For use, that means that our final-hop Translation Patterns are tied to a Partition that is included in the CSS for each MGCP Gateway.  This works, but you'll want to design that part so that you don't have Translation Patterns that unintentionally overlap at each location, unless they translate to the same destination internally.

Very good write-up.

mpaneers Mon, 09/30/2013 - 01:01 (reply to Paul McGurn)

Thank you Paul for sharing your thoughts and ideas. Glad to hear it works well. 

Regards

Lavanya

Technical Community Manager - Voice

mark_fox Mon, 11/04/2013 - 12:29

Does this configuration also support ANI in the E164 format?  Supposing that it is being modified on the gateway.

Actions

Login or Register to take actions

This Document

Posted November 3, 2011 at 11:09 PM
Stats:
Comments:8 Avg. Rating:5
Views:27989 Contributors:8
Shares:1

Related Content

Documents Leaderboard