Have you ever wanted to block a call into CUCM based on the calling party number? Well, unless you used H323 Gateways and did call blocking logic at the gateway itself, there was no way to do this natively in CUCM.
I tried implementing this on CUCM 8.6.2 and and I am able to block calls based on calling number and route all other calls excpet for the calls without caller ID. They still get blocked even though I created a blank translation pattern exactly like the ! translation pattern.
As author of this document, I am interested in the issue you are seeing. The NULL translation needs to be in the same partition as your blocked patterns. Based on how digit analysis works, if a calling party number is present and does not match a blocked pattern, it should match the ! pattern and route. If there is no calling party number, then digit analysis should match the pattern and route the call. With that said, make sure the ! and translations look the same (partition and CSS).
If you have verified this, please get a CCM SDI capture of an inbound call and send me the trace file for review. Just make sure you provide the time and the called party number so I can trace it. My email is firstname.lastname@example.org.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...