If blocking the CLID using the CUCM method then either you must block all CLID on a particular device or use Line CSS for PERMIT purposes, which I'm not fond of.
If blocking the CLID using the CUBE method then all matches to the dial-peer would have blocked CLID. I could potentially create a dial-peer that uses a special prefix in order to avoid overlapping, but I thought I'd check with the experts.
Ideally, I'd like to be able to tweak the sip-profile rule so that it checks the From header for particular Calling Numbers and applies Privacy based on that. However, I don't know of a way to do an if statement in sip-profiles. Any thoughts on how to best handle selective outbound CLID blocking?
From my experience "a dial-peer that uses a special prefix in order to avoid overlapping" this is the way to go then you can hide your CLID with any call you make by dialing a prefix, so today you can show your CLID to your mobile device and tomorrow you dial the prefix and it hides it.
Don't know if anyone out there has any other suggestions.
I'd like to be able to tweak the sip-profile rule so that it checks the From header for particular Calling Numbers and applies Privacy based on that. However, I don't know of a way to do an if statement in sip-profiles - I can help you on this.
Here is the sample test config. Calling number - 6060 , Called number- 2444 , CUBE ip -10.0.2.3
I'll definitely use Hemanus's suggestion, but as always I like to create as little hassle for the end-user as possible.
To expand on Manish's great examples, I understand the ability to modify single header fields, but the scenario presented would be a bit more complicated. Rather, the idea would be to check the From field for a matching SIP URI, and if the SIP URI matches, modify the Privacy header. Example below...
The above INVITE would be passed to the PSTN and we've now achieved selective caller ID blocking. The problem with this scenario is I'd like to evaluate one header field and modify another based on the result. I've never had a neccessity for this before, but I'd be very interested to see it in action. Thanks again for all your help!
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...