![]() 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. This sends the call nowhere, and the calling party receives a reorder tone. Give the x-lation pattern a CSS that has access to NOTHING. Then, the gateway in Cisco CallManager must be configured to have a Content Services Switch (CSS) with access to this x-lation pattern first, based on the x-lation pattern partition. This is accomplished through translation patterns in the Cisco CallManager configuration.Īn x-lation pattern in Cisco CallManager must be created to match the inbound DNIS information (called party number). If a Media Gateway Control Protocol (MGCP) gateway (controlled by Cisco CallManager) is used, the only way to block unwanted calls is based on the DNIS information. If an H.323 gateway is used, incoming calls can be blocked based on ANI and DNIS information through translation rules on the gateway configuration.įor more information on how to block incoming calls with an H.323 gateway, refer to How to block incoming calls based on calling number and called number information with a Cisco IOS H.323 gateway. Then, make sure to consider any limitations of the gateway being used. ![]() Data Center Over Lords by Digital Life by Firewall.To determine the appropriate procedure, first determine whether it is desirable to block unwanted calls based on Automatic Number Identifier (ANI), or Dialed Number Identification Service (DNIS) information, or both.Aaron's Worthless Words by Bluebox Redbox by Daniels Networking Blog by Daryl Hunter – Network Cowboy.Sign me up! Follow Amy Engineer on Blogroll MGCP will require you to use CUCM 8.0 or later for this, check out this document.Įnter your email address to subscribe to this blog and receive notifications of new posts by email. *The process with SIP trunks is practically the same, your inbound dial-peer won’t be POTS, though. If you have another method you prefer, please share in the comments, would love to hear it. Test voice translation-rule 9 /5550005555/Īs with all things voice, there are eleventy-billion ways to accomplish a task, this post just covers one. You can also run the following command and see what the router *thinks* it will do when it sees the number you are trying to block: Then just substitute the to-be-blocked number into the voice translation rule. As I mentioned before, you can use your own cell phone number in the original configuration and confirm that the call blocking works. This is a good idea even if you think you know what the inbound dial-peer is because sometimes life is whimsical, and dial-peer configurations even more so.Ĭall-block translation-profile incoming CALLBLOCKĬall-block disconnect-cause incoming unassigned-number If you aren’t sure what your incoming dial-peer is, use the debug voip dialpeer allcommand and make a test call. ![]() To complete the configuration, add these two commands to your incoming POTS dial-peer. Name it something obvious so that the next administrator doesn’t have to beat you to death for your obscurity: Then set yourself up a lovely translation profile that references the rule you just created. ![]() Rule 1 reject /5550005555/ <<keep in mind this is the calling number you want to block, but I like to test initially with an outside number such as my cell phone that I can test with. The first thing you need to do is create yourself a voice translation rule, something like this ought to do the trick: Your mileage might vary a little with SIP trunks and will definitely vary quite a bit with MGCP.* Specifically, this is how I would block an incoming call on a Cisco voice gateway with an ISDN PRI attached. Welcome to a quick post on how to block an incoming call when you know the calling number you want to block. ![]()
0 Comments
Leave a Reply. |