That's the correct parameter to block it at GW level. If it is already restricted and CCM is still sending it something might have been save on cache. you can try restarting CCM service to refresh the change.
I have made some changes and now the caller ID is working fine for the calls except those call that is using call forwarding
I am using call manager 4.2.1 and I have set up "calling Line ID presentation" under the calling party transformations on route pattern level to show the outgoing calling number.
When I set it up as "default", then the outgoing caller ID show the individual outgoing caller ID correctly.
When I set it up as " private", then the outgoing caller ID would appear as Private number.
However... if I do a call forward all on a phone to a mobile number, then it will show the pilot point of the DDI block instead of the individual DID number or " private" .... any idea why this is not working for the phone if " call forward all" has been set?
I use a phone to call 90003522, then I set up call forward all to a mobile on this extension 3522 to 0423848200. then when the phone ring on my mobile, it will be showing 90003500 which is the pilot point of the DDI range. no matter what setting I put in the call manager under the "calling Line ID presentation" , its still showing the pilot number of the DDI range.
if i call directly from the handset 3522 to my mobile, then i am able to control whether the number will be display as 90003522 or Private via the "calling Line ID presentation"
I have attached the debug here as well.. any idea?
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...