![]() In older versions of Cisco IP Telephony Systems, call-blocking based on ANI was typically accomplished by using Translation-Profiles on Cisco IOS Voice Gateways, or ISR’s or CUBE (Cisco Unified Border Element).Ĭall-block translation-profile incoming blacklistĬall-block disconnect-cause incoming call-reject This blog focuses on all of the needed steps, and specifically the extra steps required when configuring this when using SIP as your primary gateway protocol versus MGCP or H323. We’ve seen many blog postings covering the steps to do this, however you have to read many different ones to properly implement and understand this configuration end-to-end, and more specifically, how to implement this when you are using SIP for your interior gateway protocol. Another scenario is maybe the caller is malicious, or keeps prank calling, so you may choose to simply reject the call, or send it to a specific pre-recorded message.Ī client may also want to block marketing calls, recruitment calls, or any other call that is generally unwanted. For example, if the Caller-ID or ANI (Automatic Number Identification) is that of a specific customer, then they may want to direct that call from that customer’s home number to a dedicated support representative, IVR, or Voice Message System. Data Center Over Lords by Digital Life by Firewall.Some clients will request that their IP telephony system have the capability to block inbound calls into their organization, or to route these calls to a specific destination, solely based on the “Caller-ID” being sent by the caller.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.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |