topic Re: Jabber Client unable to login from Public Network in Collaboration Applications

Jabber Client unable to login from Public Network

a.burlaos — Mon, 18 Mar 2019 02:23:41 GMT

Hi,

Does anyone encountered intermittent issue regarding the Jabber clients that won't be able to login from Public network?

The error encountered is "UDS clusteruser request failed" and "unable to determine home CUCM".

This problem occurred just this week, last week everything works fine. I also check the results of SRV Checker and everything is also works fine.

Expressway version: x8.10.3

Regards,

Arvie

Re: Jabber Client unable to login from Public Network

Jaime Valencia — Thu, 15 Mar 2018 14:14:05 GMT

Do you have more than one CUCM cluster configured with that expressway pair?

Re: Jabber Client unable to login from Public Network

a.burlaos — Fri, 16 Mar 2018 00:55:33 GMT

Only 1 cucm

Re: Jabber Client unable to login from Public Network

Jaime Valencia — Fri, 16 Mar 2018 03:48:41 GMT

You usually see those errors if you have multiple clusters using the same users and the home cluster not checked, or checked in more than one.

You'd need to review logs from CUCM and expressways to determine if it was a one time occurrence due to some error in the network or high CPU, etc.

Re: Jabber Client unable to login from Public Network

columba — Fri, 17 Feb 2023 08:35:49 GMT

I had this error with a missmatch of the CUPS Presence Domain (domain.local) and the external domain (domain.com).
Once I added the internal Domain (Domain.local) to Exp-C > Configuration > Domains it was working.

You can check your configuration here:
https://cway.cisco.com/csa-new/#/collabedge/results?fromInput=true