Cisco Jabber - cannot communicate with the server

[ziqex]

Hello everyone,

One of the jabber clients is getting the "cannot communicate with the server" message. Same call manager config as other users.

When i run this jabber clients with my admin credentials end user is able to sign in.

Please advise what may cause this issue.

Thank you.

[Roger Kallberg]

Check if the end user in CUCM has these settings.

• Home cluster set. If you have multiple CUCM clusters it's important to only have the set on one.
  • You can check what cluster that the user is homed to by using this URL. https://<FQDN of a CM node>/cucm-uds/clusterUser?username=<user name>
• Assigned the rights of Standard CCM End Users and Standard CTI Enabled. Either direct by being set as members of the access groupf or by a custom group that gives the same roles as these two does.

[ziqex]

I have checked the end user configuration in the cucm.

Home Cluster is ticked in service settings.

Permission information includes Standard CCM End Users and Standard CTI Enabled in groups and roles.

Could you please advise about using this url:

https://<FQDN of a CM node>/cucm-uds/clusterUser?username=<user name>

whenever I enter cucm server name in front I am getting home cluster as cm node I have entered

e.g. for

cucm-aa-01/cucm-uds/clusterUser?username=test.user

home cluster cucm-aa-01

for 

cucm-bb-01/cucm-uds/clusterUser?username=test.user

home cluster cucm-bb-01

Thank you.

Regards,

Daniel

[Roger Kallberg]

This would be the result of this when I check this in our environment.

I am querying a CUCM in a remote DC where I know my user is not homed and getting the result for home cluster as usdenextcucm as shown on tags "result found" and "homeCluster".

[Roger Kallberg]

Is cucm-aa-01 and cucm-bb-01 different CUCM clusters or individual nodes in the same cluster? If they are different clusters it would likely indicate that the user is setup with Home Cluster in both CUCM clusters.

[ziqex · Accepted solution]

Cisco Jabber was re-installed with UPN setting disabled.

In order to disable the UPN for the Jabber install you can follow the below steps :

1. Open CMD on the machine that the Jabber client will be installed.
2. Navigate to the Directory where the MSI file is stored. For example: This PC >> Desktop. In order to navigate to a directory in CMD you can use the “CD” keyword.
3. Execute the following line : msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 UPN_DISCOVERY_ENABLED=false

Now, the jabber prompts for user details correctly and no error message is displayed.

Thank you.

Regards,

Daniel

[SirPopov]

Thank you so much ziqex! This command help me a lot   msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 UPN_DISCOVERY_ENABLED=false

[SteveK066]

I know this is somewhat old and there a lot of variables that can cause this - but in my case it was for a 'Generic' UCCX Jabber Account I created, not associated with an LDAP ID. I knew it wasn't my PC's Jabber, as I could log in with my own credentials. I found the issue was not related it being a non-LDAP associated account, but it was simply missing 'Standard CCM End Users' in Permissions Information in User Management.