outgoing call blocking on FXO port on cisco ISR

[LynK]

does anyone have any experience with call blocking on a CME site with FXO ports going to a provider. I cannot seem to get this working. I want to block SCAM toll CIDs that are not international, but get charged international rates.Here is an example of our output:

Code Select Expand


voice translation-rule 12
rule 1 reject /721......./
rule 2 reject /758......./
rule 3 reject /767......./
rule 4 reject /784......./
rule 5 reject /787......./
rule 6 reject /809......./
rule 7 reject /829......./
rule 8 reject /849......./
rule 9 reject /86[8-9]......./
rule 10 reject /876......./
rule 11 reject /939......./
rule 12 reject /664......./
rule 13 reject /242......./
rule 14 reject /246......./
rule 15 reject /264......./
rule 16 reject /268......./
rule 17 reject /284......./
rule 18 reject /340......./
rule 19 reject /345......./
rule 20 reject /441......./
rule 21 reject /473......./
rule 22 reject /649......./
rule 24 reject /670......./
rule 25 reject /671......./
rule 26 reject /900......./
rule 27 reject /976......./
!
voice translation-profile BLOCK_NON_US_2
translate calling 12
translate called 12
!
dial-peer voice 100 voip
description *** Local Calling ***
translation-profile incoming BLOCK_NON_US_2
translation-profile outgoing BLOCK_NON_US_2
call-block translation-profile incoming BLOCK_NON_US_2
call-block disconnect-cause incoming invalid-number
huntstop
destination-pattern 9[2-9]......
voice-class codec 1
no vad
!
dial-peer voice 200 voip
description *** Long Distance Calling ***
translation-profile incoming BLOCK_NON_US_2
translation-profile outgoing BLOCK_NON_US_2
call-block translation-profile incoming BLOCK_NON_US_2
call-block disconnect-cause incoming invalid-number
huntstop
destination-pattern 91[2-9]..[2-9]......
voice-class codec 1
no vad


Here is the output of the FXO Ports:

Code Select Expand


voice-port 0/1/0
supervisory disconnect dualtone mid-call
secondary dialtone
timeouts call-disconnect 3
timeouts ringing infinity
timeouts wait-release 2
timing hookflash-out 500
connection plar opx ******5452
station-id name
caller-id enable
!
voice-port 0/1/1
supervisory disconnect dualtone mid-call
secondary dialtone
timeouts call-disconnect 3
timeouts ringing infinity
timeouts wait-release 2
timing hookflash-out 500
connection plar opx ******5452
station-id name
caller-id enable
!
voice-port 0/1/2
supervisory disconnect dualtone mid-call
secondary dialtone
timeouts call-disconnect 3
timeouts ringing infinity
timeouts wait-release 2
timing hookflash-out 500
connection plar opx ******5452
station-id name
caller-id enable
!
voice-port 0/1/3
supervisory disconnect dualtone mid-call
secondary dialtone
timeouts call-disconnect 3
timeouts ringing infinity
timeouts wait-release 2
timing hookflash-out 500
connection plar opx ******5452
station-id name
caller-id enable
!
voice-port 0/2/0
supervisory disconnect dualtone mid-call
secondary dialtone
timeouts call-disconnect 3
timeouts ringing infinity
timeouts wait-release 2
timing hookflash-out 500
connection plar opx ******5452
station-id name
caller-id enable
!



What am I missing ?!?!? 

[icecream-guy]

the plug?


sorry couldn't resist. 

I have none such experience, sorry

[LynK]

the plug?


sorry couldn't resist. 

I have none such experience, sorry

Ristau... I like you. Got any openings? LMAO.

[icecream-guy]

the plug?


sorry couldn't resist. 

I have none such experience, sorry

Ristau... I like you. Got any openings? LMAO.

I don't think you want to work in a closing data center with a  hard march 2018 shutdown, and no room to move anywhere, and no budget for the move.  in fact, people are jumping like rats off a sinking ship.  as a matter of fact, we may have some openings...

[Dieselboy]

Is the call being made outbound from your network to the POTS line?

First off, that translation rule will be matching that string anywhere in the dialed number. So;

voice translation-rule 12
rule 1 reject /721......./

matches 721.......
also
matches 0548795721.......

You can fix that by putting a carrat at the beginning which says, match this at the beginning (PS I don't know, you may be wanting to match the number how you have it already)

So with the carrat:
voice translation-rule 12
rule 1 reject /^721......./

I havent ever used a "reject" tranlation rule before. But with translation rules you normally have "translate outgoing 12" on the dial-peer that will point to the fxo port. How are your dial-peers set?

Lastly, CME does have a decent class of control and it's pretty easy once you actually understand how it works. REF: http://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/42720-configuring-cor.html

Basically, create a rule for those numbers above, and give them a label like RESTRICTED
then create a COR list and not include the list above
I last set up COR for an exam back in 2010 so I'm struggling to remember. But at the time I realised that with COR you could set up a single CME system and partition it off for multiple "customers". I think I figured out you could have duplicate telephone numbers but due to COR, it's like a CME Voice VLAN in a sense that each cor can be kept separate so if you provision a COR per customer you could do it that way.
Never heard or seen of it done like that but thought it was cool

Let us know how you go with the translation rules?

Some voice shortcuts:

List the translation rules:
show run | sec translat

List the dial-peers:
show run | sec dial-pee

Go to a specific dial-peer 99:
show run | sec dial-pee.+99

Likewise, go to dial-peer 10:
show run | sec dial-pee.+10

Dial pee

[deanwebb]

Hehehe

dial pee

[icecream-guy]

Hehehe

dial pee

good one,   my favorite is

show ip int br | ex ass

[Dieselboy]

 

I do "show urn" a lot. Not that funny, but would be if an actual urn was to appear

[deanwebb]

If an urn and a pope appeared, I would be highly impressed.