Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Blocking Calls incoming calls in Gateway Router

Hello All

I've had a request to block an incoming number.  when researching I've found the cisco article:

http://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/64020-number-voice-translation-profiles.html

specifically:

Call Blocking Specific Calling Numbers

Configure a voice translation rule to block the desired calling number you want to block. This example uses 9193927393.

voice translation-rule 1
 rule 1 reject /9193927393/      

!--- Matches the defined number string and rejects the call.

!

!--- Apply the rule to a translation profile for the calling number. 
!--- You could also reject based on called or redirect-called numbers.

!
voice translation-profile call_block
 translate calling 1      

!--- Invokes voice translation rule 1 in order to determine 
!--- which calls to reject based on the calling number.

!

!--- Include the translation profile within a dial peer definition.

!
dial-peer voice 100 pots
 call-block translation-profile incoming call_block      

!--- Invokes the voice translation profile “call_block” on 
!--- inbound POTS calls that match this peer 
!--- in order to determine which calls to reject.

 call-block disconnect-cause incoming call-reject
 incoming called-number       

!--- Matches this peer for all inbound POTS calls.

 port 1/1:23

               

which was easy enough to configure.

I set it up with my cell phone number to test it first and when I test it with the debug I see:

LDS-CR-SR-VG01#test voice translation-rule 1 XXXXXXXXXX

XXXXXXXXXX blocked on rule 1

LDS-CR-SR-VG01#

(where XXXXXXXXXX is my cell phone number)

perfect. 

So I call the number and it still rings through. Weird....

So ran sh voice call status and I see this:

LDS-CR-SR-VG01#show voice call status
CallID     CID  ccVdb      Port        Slot/DSP:Ch  Called #   Codec    MLPP Dial-peers
0x167F2    2B22 0x2A906BD4 0/0/0:23.1       0/1:1   3732       None     27/11
1 active call found

LDS-CR-SR-VG01#

So now I know that it is coming in the correct dial-peer.  Then I watched it with q931 debug I see this output:

LDS-CR-SR-VG01#

Feb 28 00:49:41.116: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8  callref = 0x5945

        Bearer Capability i = 0x8090A2

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA18381

                Preferred, Channel 1

        Facility i = 0x9F8B0100A115020101020100800D552E532E2043454C4C554C4152

                Protocol Profile =  Networking Extensions

                0xA115020101020100800D552E532E2043454C4C554C4152

                Component = Invoke component

                        Invoke Id = 1

                        Operation = CallingName

                                Name Presentation Allowed Extended

                                Name = U.S. CELLULAR

        Calling Party Number i = 0x2180, 'XXXXXXXXXX' <-- Again my cell

                Plan:ISDN, Type:National

        Called Party Number i = 0xC1, '3732'

                Plan:ISDN, Type:Subscriber(local)

Feb 28 00:49:41.120: ISDN Se0/0/0:23 Q931: Received SETUP  callref = 0xD945 callID = 0x593D switch = primary-ni interface = User

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_get_profile_from_voiceport_internal: Found profile call_block defined on voice-port

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_get_profile_from_trunkgroup_internal:

   Voice port 0x2A906BD4 dsl=0 timeslot=1 does not belong to any trunk group

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_match: Skipping a call block rule; number=XXXXXXXXXX rule precedence=1

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_profile_match_internal: No match found

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_profile_subst_internal: Number parameters do not match ruleset in profile call_block

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_get_RegXrule: Invalid translation ruleset tag=0

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_profile_subst_internal: Error: ruleset for called number not found

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_get_profile_from_voiceport_internal: Found profile call_block defined on voice-port

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_match: Skipping a call block rule; number=XXXXXXXXXX rule precedence=1

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_profile_match_internal: No match found

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_profile_subst_internal: Number parameters do not match ruleset in profile call_block

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_get_RegXrule: Invalid translation ruleset tag=0

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_profile_subst_internal: Error: ruleset for called number not found

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_get_RegXrule: Invalid translation ruleset tag=0

Feb 28 00:49:41.120: //-1/xxxxxxxxxxxx/RXRULE/regxrule_profile_subst_internal: Error: ruleset for redirect-called number not found

Feb 28 00:49:41.120: //-1/0AA4364E993E/RXRULE/regxrule_stack_pop_RegXruleNumInfo: stack=0x2AA0E1D0; count=1

Feb 28 00:49:41.120: //-1/0AA4364E993E/RXRULE/regxrule_stack_pop_callinfo_internal: numinfo=0x31A2E104

Feb 28 00:49:41.124: //-1/0AA4364E993E/RXRULE/regxrule_stack_push_RegXruleNumInfo_internal: stack=0x2AA0E1D0; count=1

Feb 28 00:49:41.128: //-1/0AA4364E993E/RXRULE/regxrule_stack_push_RegXruleNumInfo_internal: stack=0x2AA0E1D0; count=2

Feb 28 00:49:41.128: //-1/0AA4364E993E/RXRULE/regxrule_dp_translate: No profile found in peer 11 for outgoing direction

Feb 28 00:49:41.128: //-1/0AA4364E993E/RXRULE/regxrule_dp_translate: calling_number=3199819900 calling_octet=0x21

        called_number=3732 called_octet=0xC1

        redirect_number= redirect_type=-1 redirect_plan=-1      redirect_PI=-1 redirect_SI=-1

Feb 28 00:49:41.128: //-1/0AA4364E993E/RXRULE/regxrule_stack_pop_RegXruleNumInfo: stack=0x2AA0E1D0; count=2

Feb 28 00:49:41.128: //-1/0AA4364E993E/RXRULE/regxrule_stack_pop_callinfo_internal: numinfo=0x31A2CFAC

Feb 28 00:49:41.128: //-1/0AA4364E993E/RXRULE/regxrule_stack_push_RegXruleNumInfo_internal: stack=0x2AA0E1D0; count=2

Feb 28 00:49:41.128: //-1/0AA4364E993E/RXRULE/regxrule_stack_pop_RegXruleNumInfo: stack=0x2AA0E1D0; count=2

Feb 28 00:49:41.128: //-1/0AA4364E993E/RXRULE/regxrule_stack_pop_callinfo_internal: numinfo=0x31A2CFAC

Feb 28 00:49:41.128: //-1/0AA4364E993E/RXRULE/regxrule_stack_push_RegXruleNumInfo_internal: stack=0x2AA0E1D0; count=2

Feb 28 00:49:41.132: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8  callref = 0xD945

        Channel ID i = 0xA98381

                Exclusive, Channel 1

Feb 28 00:49:41.148: ISDN Se0/0/0:23 Q931: TX -> ALERTING pd = 8  callref = 0xD945

Feb 28 00:50:01.552: ISDN Se0/0/0:23 Q931: TX -> CONNECT pd = 8  callref = 0xD945

Feb 28 00:50:01.564: ISDN Se0/0/0:23 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x5945

Feb 28 00:50:01.564: %ISDN-6-CONNECT: Interface Serial0/0/0:0 is now connected to 3199819900 N/A

Feb 28 00:50:06.744: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0x5945

        Cause i = 0x8290 - Normal call clearing

Feb 28 00:50:06.744: %ISDN-6-DISCONNECT: Interface Serial0/0/0:0  disconnected from XXXXXXXXXX , call lasted 5 seconds

Feb 28 00:50:06.744: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8  callref = 0xD945

Feb 28 00:50:06.752: //-1/0AA4364E993E/RXRULE/regxrule_stack_pop_callinfo_internal: numinfo=0x0

Feb 28 00:50:06.764: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x5945

Feb 28 00:50:06.768: //-1/0AA4364E993E/RXRULE/regxrule_stack_pop_RegXruleNumInfo: stack=0x2AA0E1D0; count=2

Feb 28 00:50:06.768: //-1/0AA4364E993E/RXRULE/regxrule_stack_pop_callinfo_internal: numinfo=0x31A2CFAC

I'm not sure why this isn't working.  I've attached the running config so you can peer through that and see if I've made an error, but it looks ok.  It feels like I'm so close but missing something little.

Any help appreciated.  Thanks for reading!

Everyone's tags (4)
1 ACCEPTED SOLUTION

Accepted Solutions

Blocking Calls incoming calls in Gateway Router

Dustin, please apply these commands to your incoming dial-peer pots (dial-peer voice 27 pots):

call-block translation-profile incoming call_block

call-block disconnect-cause incoming call-reject

Please rate helpful answers

HTH

GAbriel

6 REPLIES
Hall of Fame Super Silver

Re: Blocking Calls incoming calls in Gateway Router

Telco is sending you last 4 digits, is that what your rule matches?

Chris

Sent from Cisco Technical Support iPhone App

New Member

Blocking Calls incoming calls in Gateway Router

Thanks for the response

For the DNIS the Telco is sending the last for of the DID as the called party number, but they are sending 10 digits for the calling party number, and that is what I'm trying to block.  The rule matches my cell phone number and that is what should be blocked.

LDS-CR-SR-VG01#test voice translation-rule 1 XXXXXXXXXX

XXXXXXXXXX blocked on rule 1

Blocking Calls incoming calls in Gateway Router

Dustin, please apply these commands to your incoming dial-peer pots (dial-peer voice 27 pots):

call-block translation-profile incoming call_block

call-block disconnect-cause incoming call-reject

Please rate helpful answers

HTH

GAbriel

New Member

Blocking Calls incoming calls in Gateway Router

Thanks for the response Gabriel

I applied the settings to dial-peer 27 and it worked!  I'm a little confused as to why though...

When I watched the call come in it said it was in dial-peer 11 (sh voice call status).  Also according to the dial-peer destination pattern it should be using that (dial-peer 11) as the DNIS from the telco is 4 digits.  I thought that dial-peer 27 was for outbound (local calls) hence the forward 7 digits. 

I love that it works and I've very apprecative for the advice but do you think you can elobrate on the why?  I'm totally confused and my personality needs this.  I need to understand the why not just get the answers.  Hope its not too much of a inconvenience.  I really do appreciate it!

Blocking Calls incoming calls in Gateway Router

Hello Dustin,

as mentioned in the document and original post, the  call block translation rule should be applied on the Inbound POTS  dial-peer.

The call came in thru the port 0/0/0:23 and hence it matched the inbound dial-peer 27 in which we need to apply the translation profile to block the call.

dial-peer voice 27 pots

description PRI 7digit call

preference 1

destination-pattern 8[2-9]......

incoming called-number *.

port 0/0/0:23

forward-digits 7

and the called number is 3732, so it matched the outbound dial-peer 11 to send the call to CUCM

!

dial-peer voice 11 voip

description To CM Phones

call-block translation-profile incoming call_block

call-block disconnect-cause incoming call-reject

preference 1

destination-pattern [2-8]...

session target ipv4:10.30.1.10

incoming called-number *.

voice-class codec 1 

dtmf-relay rtp-nte h245-alphanumeric

!

For better understanding on the inbound & outbound dial-peer matching process, please refer this link.

http://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/14074-in-dial-peer-match.html?referring_site=smartnavRD#topic1

Hope this answers your query. let us know if you have any more questions please.

//Suresh

Please rate all the useful posts.

//Suresh Please rate all the useful posts.
New Member

Blocking Calls incoming calls in Gateway Router

Thanks for the explanation and link.  Great information.  Thank You!

2540
Views
0
Helpful
6
Replies
CreatePlease to create content