Blocking Inbound calls CUCM 8.6

[Romi Clemente]

Hello..

Please, If somebody can help me, I would be grateful..

I need to block some inbound calls on CUCM..Is it possible to do this on CUCM 8.6??...How can I do that?...

Thanks in advanced.

Regards.

[Jaime Valencia · Accepted solution]

Blocking  Calls Based on Calling Party ID

https://supportforums.cisco.com/docs/DOC-18367

Or if using H323 you can also do it at GW level, for that method, just search CSC as there are hundreds of threads on the subject.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

[William Bell · Accepted solution]

In addition to the great doc that Java is referencing (+5 J-man) I did a write up on "black listing" using both the GW translation profile method and the CUCM hotline feature.

http://www.netcraftsmen.net/blogs/cisco-cucm-blocking-calls-by-calling-party-number-id.html

HTH.

Regards,

Bill

http://ucguerrilla.com

[Ayodeji Okanlawon]

William,

I read your blog the other day on using the CUCM hotline feature. Excellent job! As nice as it is, it highlights a major disadvantage with MGCP gateways. What we could easily do with voice xlation profiles on h323, we have to use a series of xlation patterns on cucm hotline feature

Please rate all useful posts

"There is a wideness in God's mercy Like the wideness of the sea.There's a kindness in His justice Which is more than liberty"

[William Bell]

I don't know if I would attribute the disadvantage to MGCP. The reality is that MGCP is a master/slave protocol and the deficiency in this feature group is the responsibility of the Call Agent. Which, is UCM in this case. Though, I get your point. Of course, now that we have a way to workaround this disadvantage we can also work around the problem with using a peer2peer call processing model such as H.323 (or SIP) gateways. You can only have 15 rules in a translation profile and if you work at a company that is on a "black listing" warpath then 15 rules is a joke. The other challenge is if you have distributed gateways then you have to make sure rules are maintained across all of them. Not very admin-friendly.  In most environments, xlation profiles on H323/SIP are fine. But there are two customers that come to mind where the limitations were painful.

The hotline workaround may be a more scalable option overall and it can be applied to all ingress calls, regardless of GW protocol or GW origination point. I like this because it appeals to my inner control freak;-). I prefer to keep my call processing with the UCM as much as possible and minimize distribution of one-off configs on voice gateways.

At a minimum I think we can agree that it is nice to have choices.

Regards,

Bill

http://ucguerrilla.com

[Ayodeji Okanlawon]

William, +5 point on pointing out the scalability advantage. I totally agree with you on this been a major advantage if you need to deal with large requests. Excellent point.

Please rate all useful posts

"There is a wideness in God's mercy Like the wideness of the sea.There's a kindness in His justice Which is more than liberty"