Block outgoing calls done from a voice-port

[dbygnes123]

Hi

I'm trying to reject certain outgoing calls done on certain phones connected to voice-ports (fxs) on my Cisco 3945 voice router. After reading about translation profiles and rules I ended up with the following test config:

!

voice translation-rule 10

 rule 1 reject /012345/

!

voice translation-profile test

 translate called 10

!

voice-port 2/0/7

 translation-profile outgoing test

 cptone NO

!

My understanding is that when I pick up the phone connected to 2/0/7 and dial 012345, the call should be rejected right?

However, that does not seem to be the case. Nothing is rejected and the call goes through without any issues.

The translation rule seems to be working when I test it though:

#test voice translation-rule 10 012345

012345 blocked on rule 1

Is it something I'm missing here? 

Any suggestions would be greatly appreciated! Thanks.

[Terry Cheema · Accepted solution]

Try applying to the dial-peer instead with call-block command:

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

Whats your Call Control CUCM or CUCME? If you have CUCM you can use translation patterns etc. for outbound blocking if you have CME you can also look into COR/LPCOR etc. in case, you dont get this working.

-Terry

Please rate all helpful posts

[dbygnes123]

Hi

Thanks for the reply.

I'm using CUCME. How can I restrict only certain phones when adding a translation profile to the dial-peer? If I add the translation profile that contains the reject rule to the dial-peer it would affect all phones using this dial-peer right? 

My goal is to have i.e: 

voice-port 2/0/6 can call 1234 and not 2345

voice-port 2/0/7 can call 2345 and not 1234

and so on.. 

Hope this makes sense.

[kkoeper12 · Accepted solution]

Terry is correct, you need to use the call-block command, not the translation profile command:

voice-port 2/0/7
 call-block translation-profile outgoing test

[dbygnes123]

Seems like I misunderstood. By adding call-block translation-profile outgoing test to the dial-peer belonging to the voice-port I was able to block the call. 

Thanks!

[Terry Cheema]

Glad to know your issue is resolved.

See you around.

Terry

[NBRK_Cisco]

KCUBE(cfg-translation-profile)#voice-port 0/1/0
KCUBE(config-voiceport)#call-block translation-profile outgoing Reject8
^
% Invalid input detected at '^' marker.

KCUBE(config-voiceport)#?
Voice-port configuration commands:
battery-reversal Enable FXS battery-reversal generation
bearer-cap Specify the bear capability
busyout Configure busyout trigger event & procedure
cable-detect enable cable detection
caller-id Configure port caller id parameters
comfort-noise Use fill-silence option
compand-type The companding type for this voice port
connection Specify Trunking Parameters
cptone Configure voice call progress tone locale
default Set a command to its defaults
description Description of what this port is connected to
disc_pi_off close voice path when disconnect with PI received
disconnect-ack FXS sending disconnect acknowledge

[Ayodeji Okanlawon]

Hi you need to apply the call block to the dial peer associated with the voice port. 

.......... 

"Seems like I misunderstood. By adding call-l translation-profile outgoing test to the dial-peer belonging to the voice-port I was able to block the call"

[NBRK_Cisco]

KCUBE(config-voiceport)#dial-peer voice 2291 pots
KCUBE(config-dial-peer)#call-block translation-profile ?
   incoming Specify incoming translation profile

KCUBE(config-dial-peer)#

[NBRK_Cisco]

now it is working. I dont know how to close this question.

[Muthurani Lavanya Paneerselvam]

Hello Terry

Thanks for sharing. +5 

Regards

Lavanya