![]() This method is only applicable to SIP and H.323 configurations. Translation rule 99 defines several patterns that should be rejected. Here we have dial-peer 99 handling inbound calls from the PSTN and it is configured to check the call setup and match it against the configured translation-profile. 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. Note: This can only block unwanted calls based on DNIS information and not on the ANI information.įor more information, refer to Route Pattern Configuration.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. In this case, the "knob" that is used to block the call is the Route or Block this pattern option. To do this, the DNIS or called number can be specified in a route pattern, then applied to the gateway. To block calls in the same manner at the Cisco CallManager level, use translation patterns. 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. 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |