I did this in my environment. I am now on 5.x and trying to remember exactly how it was configured... I think when assigning the phone device to your user, DO NOT configure it as your default extension. I had to add both the extension mobility device name and the phone to the rm user for IPCC to recognize. I remember having an issue with reporting the call as being answered properly in IPCCx but think that was resolved by NOT setting the default extension. Formally, as you mentioned in your post, the agent extension should not be shared in IPCCx...
Has anyone managed to get this working with IPCC Express 5.0 with CUCM 6.x? If I statically configure the phone with a DN, everything works fine, but if I set up a profile and log in on the same phone I get the following message:
"Login failed due to a configuration error. Please ask your system administrator to associate your phone with the RM JTAPI Provider user ID"
As the RM JTAPI user is an Application user in CUCM6, how is it possible to do this?
Yes it's possible. I have done this using IPCC 5.0 and CM 5.1. What you need to associate with the RM JTAPI app user is the physical IP phone device not the EM Device Profile. So your agents have to login to IP Phones that are already associated with your RM JTAPI.
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 ...