Blocking one Incoming Number in CISCO CME
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2021 05:09 AM
Hi
I would like to block incoming call from 1-2 number, i tried creating a rule to reject but not working...extracts of my rules are give below, am I missing something here?
voice translation-rule 2
rule 1 some old rules.....
rule 2 some old rules.....
rule 3 some old rules.....
rule 4 some old rules.....
**this is the rule i added***
rule 5 reject /050********my blocking number goes here/
voice translation-profile INCOMING
translate called 2
!
voice translation-profile OUTGOING
translate calling 1
dial-peer voice 777 pots
description **INCOMING DIAL-PEER**
translation-profile incoming INCOMING
incoming called-number .
direct-inward-dial
port 0/1/0:15
- Labels:
-
IP Phones
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2021 05:24 AM - edited 02-10-2021 05:24 AM
Your configuration is not correct. Have a look at the block call part in this excellent document, In Depth Explanation of Cisco IOS and IOS-XE Call Routing - Cisco
IMO It's by far the best and most comprehensive document about how dial-peer matching and number modifications can be made that is currently available.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2021 06:02 AM
Thanks Roger.
So I can apply those all-block translation-profile incoming CALLBLOCK within my existing dial-peer, right?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2021 06:49 AM - edited 02-12-2021 06:33 AM
Yes you can do it on your existing dial-peer. Based from the referenced document and your shared information you'll do something like this.
voice translation-rule 164 rule 1 reject /8675309/ !Number that you want to block ! voice translation-profile CALLBLOCK translate calling 164 ! dial-peer voice 777 pots description **INCOMING DIAL-PEER**
translation-profile incoming INCOMING
call-block translation-profile incoming CALLBLOCK
call-block disconnect-cause incoming invalid-number
incoming called-number .
direct-inward-dial
port 0/1/0:15
To test/verify this you'll use this command.
test voice translation-rule 164 8675309
Should give you this result.
8675309 blocked on rule 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2021 08:41 AM
Thanks Roger I will try this...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2021 06:30 AM
I hope you are trying to block call based on the calling number in that case your profile should be as below.
voice translation-profile INCOMING
translate calling 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2021 06:30 AM
Thanks Nithin for your help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2024 11:48 PM
Thanks, this setup works well.
Is there any special syntax required for international numbers?
i.e if I want to block +61290901111 ? the Router doesnt appear to accept the + despite the router seeing that as the calling number in logs. Can you just put /61290901111/ ? or does it need a . or * in the front?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2024 11:58 PM
It depends on how you receive the calling number from your service provider. If you get it with a plus you’ll need to put the plus into your rule. To do that you’ll need to add \ in front of the +, so this /\+61290901111/. The reason for this is that + is a wild card, so you need to escape it when it should be literally used. See this document for more information on how voice translation rules work. Determine Voice Translation Rules
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2024 12:06 AM
Thank you, perfect!
