New UCCX user can't log into Finesse.

[Steve Tessier]

I have created a new user.  This user has extension mobility and is a Finesse user.  I have created many users with this kind of profile.  I can see the user in RMCM.  I can even see the phones MAC address they logged into in controlled devices.  When they try to log into Finesse they get the following error.  Cannot authenticate with the notification service.  There may be a configuration mismatch.  Please contact your administrator.  I have gone through the programming and even removed the user all the way back to Active Directory and rebuilt them.  Call Manager is 11.5 and UCCX is 11.6 and our phones we use are 8845.

[Anthony Holloway]

"I can even see the phones MAC address they logged into in controlled devices."

Actually, that's not how that works. You do not add the physical phone to the controlled devices list of the RMCM user. Just the Device Profile, and you didn't mention that you added the Device Profile to the RMCM user as a CTI Controlled Device Profile, so that might be your issue.

"The Extension Mobility (EM) profile needs to be associated with the RmCm user and the physical phones that the agents may be expected to use should not be associated to the RmCm user."
Source: UCCX Administration Guide

[Steve Tessier]

After reading the responses it looks like my issue is the physical phone listed in controlled devices. I will try and remove that phone and leave the users UDP profile in controlled CTI devices and see what happens. Thanks for the feed back!

[Chris Deren]

Assuming as pointed out by Anthony (+5) the issues is not EM profile association, have you tried restarting CCX notification service, there are couple older bugs matching your error:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvb19751

https://quickview.cloudapps.cisco.com/quickview/bug/CSCvc94546

and similar threads:

https://community.cisco.com/t5/contact-center/user-login-error-quot-cannot-authenticate-with-the-notification/td-p/2707601

[lleweyiss]

Hi Chris or Anthony,

Having same exact issue.  Most users utilize Extension Mobility and the UDP is what is associated to rmjtapi user.

Existing Agents can log in with no 'Notification Service' error, it is only new users I added today.  

Removed everything and added everything back.  Saw those 2 BUGs mentioned, none reference UCCX 11.6.1  (my version), both mention issue occurred after some fail-over.  I have had no fail-over and on both the PUB & SUB the service has been running since Jan 15 2019.

If the recommended action is  still to restart the Notification Service,  is there any sort of disruption to the agents that are already logged in?  (does it log agents out? or set them to Not Ready?)

Also, is it a quick action?  (if any disturbance I have to submit a Change Request and provide details of 'how long',  'effects to agents', etc)  - Plus it determines when I will be allowed to do the restart (example: after hours)

[Joey Gore]

We just ran into this issue with CUCM 12.5 and UCCX 11.6.2.10000-38 (ES01-9). Restarting the Notification and Finesse Tomcat services on both nodes fixed the issue and the error-ed users can now log into Finesse. The Bug (CSCvc94546) states that it is fixed in UCCX 11.6(1) but it's clearly not.  We are planning on upgrading UCCX to 12 within the next month or so. Do we know if it contains this bug?

[elvizo.fernandes@hcahealthcare]

We have been hit with the bug as well for a trauma 1 transfer center/access center, had to restart the two services. hopefully 12 has this issue fixed.

[Doug Johnstone]

Did upgrading to v12.0 fix the issue?

[Joey Gore]

Unfortunately, it still appears to exist on UCCX 12.0. I have 4 new agents that are experiencing the issue right now. 

[Doug Johnstone]

Thanks for letting me know Joey.

Cisco bug id is showing v12 as being fixed so its good to know that its not before upgrsding and finding out the hard way.

Cheers

Doug

[Joey Gore]

I haven't yet opened a TAC case to confirm we are hitting the bug, but following the steps of restarting the Cisco Notification Service and Cisco Finesse Tomcat services did indeed "fix" the issue once again.

[Joey Gore]

Also exists in 12.5.1.10000-31 unfortunately. Will confirm in the morning if restarting the Notification and Cisco Finesse Services on both nodes still resolves the issue.

Edit: Confirmed. Restarting the services fixed the issue.

[mrvoipstuff]

Just wondering any luck with this in v12 ? appears from your earlier comments the issue is not fixed in any of the v12 release..can you pls. confirm ? we are facing this in v11.6.2...