CCM 3.3 added a new check box on the Global Directory, the Parked Call Retrieval box. I beleive if that box is not checked for the ac user, you will see the behavior you described. Also, make sure you are using Attendant Console 1.2.1 client and server.
We had this problem at one point. We found that the issue was was a mismatch between the client and the server Attendant Console service issues. This can happen often on CCM 3.2(x) and 3.3(2) that are distributed with AC 1.1, and you upgrade to AC 1.2. Service packs applied to CCM zap the server-side AC daemon back to 1.1, which half-breaks the AC 1.2 client functionality and it isn't obvious at first what happened.
The Help->About menu in the AC client will give you both the client and server AC versions. Make sure both sides are at 1.2 something, and the server and client versions should be matched. If your server is at AC 1.1, reinstall the AC software on your CallManager(s). If your client is at 1.1, reinstall the client from the CCM plugins page after your CCM is running AC 1.2.
I can tell you that the Attendant Console has some wacky user interface issues in both the 1.1 and 1.2 versions. If you run into issues, contact TAC and they can hook you up with AC 1.2(1)ES3 (an engineering special release) or better.
Cisco asked us some time ago to integrate Call Parking into our Op's Console for a huge RFP in the US. We have full visual call parking per operator and all operators can see who has parked on which device along with the call details.
Cisco push us very hard for features and functions, with customers such as Heinz, Glaxo Wellcom and Ely Lilly they refuse to push their own free Attendant console and go with our enterprise type console.
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...