Jabber - One user gets error when logging in.

[Stuart Cross]

Hi, 

I have an issue with just one user.  They can log into Jabber, but when they're logged in, they're is a message at the bottom of the client saying that the username and/or password is incorrect.  When you go to help and "show connection status"  There are errors next to Deskphone and Directory. It looks like it is unable to communicate with AD.

The user shows as an "Active" user in CUCM.  We deleted the user from CUCM and re-synchronised, still there is an issue.  We have changed the users AD password, still no luck.  We have also un-installed the Jabber client from the users machine, which again has had no effect.

Does anyone have an ideas?

Thanks

[Jaime Valencia]

Are you using it on deskphone mode??

As for the directory, how are you configuring it??

jabber-config.xml???

[Stuart Cross]

Neither deskphone or CSF will work. Red Cross on the both of them.  The error notification is Incorrect username or password Error code CJ:109:0

We use LDAP to synch the users into CUCM which in turn synchs to CUPS.  The user is "Active LDAP synch" in CUCM.  The user CAN log in to ccmuser with AD password ok......

[Md Hasan]

pls try setting upn_discovery_enablrd to false during jabber install

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/install_client.html#JABW_TK_C78084B0_00

[Stuart Cross]

Hi, 

This would be a global setting?  This is only effecting one user.  

[arunajay049]

Hi Stuart have you resolved the issue ?

[Stuart Cross]

Hello, 

Yes the issue was resolved.  There is a bug within Jabber that doesn't allow you to use a special character on the extended ASCI table.  So things like $ and £ are a few we found people were using that were causing issues.

So if you have the same issues, make sure users are not using these symbols.

Thx

[Stuart Cross · Accepted solution]

To Clarify.

Users were asked to make their windows AD account passwords more secure.  In doing this some users used certain characters not recognised by Jabber.  I believe the extended ASCII table characters were causing the problem (£, $ etc). Once users changed these back they all started to work no problem.