Blocking one Incoming Number in CISCO CME

[MaheshKumaramangalath43734]

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

[Roger Kallberg]

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.

[MaheshKumaramangalath43734]

Thanks Roger. 

So I can apply those all-block translation-profile incoming CALLBLOCK within my existing dial-peer, right?

[Roger Kallberg · Accepted solution]

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

[MaheshKumaramangalath43734]

Thanks Roger I will try this...

[Nithin Eluvathingal]

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

[MaheshKumaramangalath43734]

Thanks Nithin for your help

[bix99]

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?

[Roger Kallberg]

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 

[bix99]

Thank you, perfect!

[bekzod-fakhriddinov]

Hi, question regarding this : if call is sip with invite  : From: " 8111561760" < sip:2123631633@a.b.c.d>  , what number should be under rule to reject this spam call this number 8111561760  or this number 2123631633  ?  thanks 

[Roger Kallberg]

The call is routed based on SIP URI, so you’ll need to look at the number you have in that field in the inbound invite.

[bekzod-fakhriddinov]

thank you 

[bekzod-fakhriddinov]

before applying blocking user was receiving 20-30 spam calls,  after appying reject transl profile on the cube user received only 1 call during the day... profile with 3 rules : ^477194....; ^52477194....; ^\+52477194....   , call which was received came as 477194.... , test transl profile for all 3 number types shows blocked... Does this mean there is possibility that call can slipped in trough blocks (maybe because of high volume of spam calls)?  Double checked all dial-peers incoming has this blocking transl profile... Thanks

[Roger Kallberg]

No that’s not how this works. Are you sure that the call is matching the expected dial peer in the inbound direction. If you’re running a reasonably current version of IOS you should be able to see the call details in the trace data that the router is collecting.