When Cisco Unified IM and Presence servers are in a high availability enabled subcluster, the high availability can go into failover / failed over when one of the servers goes down or is rebooted. If this happens, you can't assign any new users to the subcluster without either bringing high availability back up, or disabling high availability for the server that is still working.
If you thought that this setting was in the CUP server admin pages, you'd be wrong. As I found here, you have to go into CUCM admin page to change this. It's under System > Presence Redundancy Groups. Click find, click on your subcluster, and Enable High Availability is there as a simple checkbox. Turn HA off and then back on again to get it back into a good state.
Showing posts with label cups. Show all posts
Showing posts with label cups. Show all posts
Friday, October 3, 2014
Thursday, October 2, 2014
Jabber 9 and 10.5 error: Starting a feature set failed and Incorrect Username or Password
If you encounter this error in Jabber 10.5:
Test/verify:
To verify this is the problem, try manual sign-in to CUCM (phone features only). If you can sign in to phone features, your problem is with CUPS. Make sure you have assigned this end user to a CUPS server and that the CUPS server is in a good state.
Starting a feature set failedor this error in Jabber 9.3 or higher:
Incorrect Username or Passwordwhen trying to sign in to Jabber using CUCM and CUPS (as opposed to Webex), and your typed password is actually correct, you may have a problem with your CUPS server and/or not have this user assigned to a presence server.
Test/verify:
To verify this is the problem, try manual sign-in to CUCM (phone features only). If you can sign in to phone features, your problem is with CUPS. Make sure you have assigned this end user to a CUPS server and that the CUPS server is in a good state.
Subscribe to:
Posts (Atom)