Cisco finesse device not accessible

Posted on January 7, by Andrew or Andy but not Drew. Leave a Comment.

We are trying to login Finesse Desktop Agent and received the Error message as "Device not accessible. Contact your administrator". Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:. Learn more. Turn on suggestions.

Cisco finesse device not accessible

I have a quick question here It's been painful but i am getting. Contact system admin Which seems to be a bug, if you are over 2k users which i don't have. The only thing though, since i migrated these servers to the lab, i had to changed IP, DNS, hostname Therfore, i have lost my license files. Cucm is running on a default license which is fine but i have to get a new license for uccx. Go to Solution. This means the bugs 'should be' unrelated and unique to each solution. When you say "IPCP" I assume, you're talking about IP Communicator. This is accomplished by creating those Application Users accounts i. Make sure your device was added as a 'Controlled Device'. View solution in original post.

BeginnerPhoneMa n Level 1. Therefore, this Bug ID wouldn't be applicable.

I have a quite unusual issue. I have a problematic phone in which certain call center users cant log into on Finesse. Lets say for instance Kristy can log into any phone and workstation through Finesse however, on one specific workstation she can not and gets an error "Device not accessible. Please contact your system administrator. I have checked user roles and the users are exactly identical. I have replaced the phone and have the same issue.

Going to simplify this, I am wanting to create a new user that can login to Jabber on the PC and pick up calls in our Finesse group without a need for a desk phone, can someone help with this? I have created a new user, they are able to log into jabber and make calls on there, but when trying to log into Finesse I get a device not accessible error. I should be able to create a user and have them be able to make calls on Jabber as well as receive calls in Finesse without an issue. When I worked help desk we were able to do this, but I am unsure how this was set up. If anyone has any ideas please let me know. I have already tried to make a CTI point and put it into the application user without luck, as well as creating a CIPC device and doing the same. So far no luck. I am trying to get 2 things setup here at a new office. Currently we have CSRs that have to log into a desk phone with there extension and then are able to log into finesse into one of the extensions and use Jabber on the computer to answer calls remotely.

Cisco finesse device not accessible

Wonder if any of your fine folks could help me out with a UCCX The current work around I have in place is to lift the handset of the agent phone and then instantly the agent can change state until they logout again Hmmm Ok. How many seat licenses do you have? This is unlikely the problem because if you exceeded this threshold, then it would've likely generated a different error message. Do you know if the Publisher is the primary M server right now? If not, how long has the services been 'up'? All of the agents located in the same area, or are they spread across multiple locations?

What episode did kakashi die

This is accomplished by creating those Application Users accounts i. New here? Learn more. Contact your system administrator. Contact your administrator". On UCCX, you would check the following;. NoorMuhammadAhm adi Level 1. Go to solution. Knowledge Articles. Labels: Labels: Other Contact Center. I have replaced the phone and have the same issue. We are trying to login Finesse Desktop Agent and received the Error message as "Device not accessible. However, do you know the root cause of this??

I have a quite unusual issue. I have a problematic phone in which certain call center users cant log into on Finesse.

BeginnerPhoneMa n Level 1. That worked! Like Loading I have this problem too. Turn on suggestions. Before going over those steps the tag line , if you will, for this blog is one of my core approaches in life: Slow is smooth and smooth is fast. Find answers to your questions by entering keywords or phrases in the Search bar above. While in production. Remove the agent's device from the "RmCm" Application User group 4. Then, re-add the agent's device to the "RmCm" Application User group For me, by removing and re-adding the agent's device to the RmCm Application User group has resolved some unexplained login issues before. Go to Solution. If your network is live, ensure that you understand the potential impact of any command. I have checked user roles and the users are exactly identical. Jabber: cannot connect with servers.