I was just testing this out in our lab a little while back. You can change this behaviour by setting up a new DN on a CTI Route Point that "front ends" (via Call Forward All) the Hunt Group. The calls to this new DN will still reach the Hunt Pilot but will strip off the CLID and replace it with it's own. This way your users will see the proper Hunt Pilot CLID :)
So, for example, if one of your Hunt Pilot DN's is 5000. Take 5000 and move it to become the CTI-RP DN and create a new Hunt Pilot DN of 2100 (with the same Line Group Members). On the CTI-RP DN Configuration page set the Call Forward All to 2100. When a call comes in via 5000 the users will be able to see that CLID on their phones to identify the proper response.
The above will help the Hunt users to identify the call was placed for 5000 and they can provide the proper response.
But we also wanted the user who is initiating the call should also see only 5000 (with a alerting name too) on his IP Phone.. can this be done ??
Basically if a user calls 5000 from his IP Phone, immediately it displays the 2100 (the callforwarded number), so this we wanted in such a way the it should still display as 5000 (with alerting name configured on the cti routepoint) instead of 2100 (the callforwarded number)....
I see that I misread your requirements here so I went back to the lab to test this out. I could not achieve want you are trying to do no matter what I changed. You can however prevent the Hunt Pilot DN from being shown on the Callers IP Phone by changing these settings (on the Hunt Pilot page).
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: firstname.lastname@example.org 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 ...