Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CUPS client PW sync

Hello,

I've a cucmbe6.1(2) attached to a cups 6.0 server. Since cucmbe does not support ldap, we've a local user database. all users are cups enabled and presence works fine. If a user changes his password on cucmbe, the new password is not being updated or synced on cups client!

Any suggestions?

6 REPLIES
New Member

Re: CUPS client PW sync

That is the way it works. Even in CUPS 7.0 you still have that problem. Hopefully it will work like OCS sometime and use the windows logon account.

New Member

Re: CUPS client PW sync

so, if this "normal behaviour". which service has so be restarted in order to sync pw?

New Member

Re: CUPS client PW sync

I don't think CUPS will sync the password at the client level. Everytime the password changes they have to change it in the client. You can sync the passwords from Call Manager to your AD domain. When the users changes their network password their call manager password will change and stay in sync but it will not change at the client level as far as I know.

New Member

Re: CUPS client PW sync

misunderstoood. not the changing of the clients password is the question.

once more I've am business edition version with NO DLAP integration, since this is not possible!

So, after changing the user pw on ccm side, the cups SERVER is not aware of the new password!

The pw is being synced after cups SERVER reboot!

New Member

Re: CUPS client PW sync

So the problem is that you change the password on the CUCMBE server and the CUPS server does not get the new password so when you try to log into the CUPC client it fails? That sounds like some type of bug. I have not had that problem.

Red

Re: CUPS client PW sync

This is called "change notification failed". You may restart SyncAgent to work around that.

The root cause is clustermanager not able to set up a TLS connection between CUPS and CUCM. We need ClusterManager logs to troubleshoot. Possible cause could be:

#1 IP address/hostname was changed at some point.

#2 Secret password was changed at some point.

My blog:

http://htluo.blogspot.com/

173
Views
0
Helpful
6
Replies