1) Give the user limited access to /ccmadmin. You can create groups to limit him/her to the hunt group/list/pilot pages. You cannot limit what hunt groups they can modify though.
2) Have another directory number/line button on the supervisor's phone. Let them decide whether to CFA to the hunt pilot, or to another destination. The real hunt pilot DN would only be known by the supervisor. As far as everyone else knows, the hunt group's DN is actually the extra line on his phone.
CUCM will work this way :) I like Jonathan's trick with "front ending" the user hunt with a number that is the "actual" Hunt number that can be manipulated via the CFWDALL on another phone (good thinking!)
You have to keep in mind that a call that has routed via the Hunt Pilot will always ignore the CFWD Settings on Hunt Group Member phones. The normal way to control this then is via the Hunt Group Logout of member phones.
The following describes how the Call Forward settings on individual Hunt member phones are ignored when presented a call via the Hunt feature. Here is a clip;
The concept of hunting differs from that of call forwarding. Hunting allows Cisco CallManager to extend a call to one or more lists of numbers, where each such list can specify a hunting order that is chosen from a fixed set of algorithms. When a call extends to a hunt party from these lists and the party fails to answer or is busy, hunting resumes with the next hunt party. (The next hunt party varies depending on the current hunt algorithm.) Hunting thus ignores the Call Forward No Answer (CFNA) or Call Forward Busy (CFB) settings for the attempted party. This also applies to CFWD ALL settings.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...