This is actually a two part question... I recently installed the Cisco Unified Enterprise Attendant Console and server v. 18.104.22.168, and it's associated with Communications Manager v. 6.1.3. Our user logs into the Attendant Console. When a call comes through, it shows up just fine. But when I try to answer it by pressing the enter key, or by clicking on the answer button in the console software, it says that it's an "invalid state" (even though the call says it's ringing) and won't answer unless I physically pick up the handset on the 7942. I've checked the device/user association and DN/user association, and everything's associated with the user that can possibly be. That's one problem.
The other is, once I do answer a call, if I try to park the call or put it on hold, the call drops and hangs up on both sides. All CTI devices created by the Attendant Server are associated with the user. I've double checked the Calling Search Spaces on all the CTI devices and the CTI Route Point for the Queue, and they are the same as what we use on all of our phones, so they should be routable. User has all the necessary permissions in Call Manager that the Attendant Server installation guide requested. All CTI devices and the route point are registered with Call Manager. Can anyone point me to anything else that might cause this issue? Or give me an example of a configuration that does work?
Thanks for any assistance!