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 your example, take 250 and move it to become the CTI-RP DN and create a new Hunt Pilot DN of 200 (with the same Line Group Members 501 & 502). On the CTI-RP DN Configuration page for 250 set the Call Forward All to 200. When a call comes in via 250 the users will be able to see that CLID on their phones to identify the proper response. Do the same for 260 :)
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...