[cisco-voip] Jabber 11.8 issue

[Matthew Huff]

Another item to check:

o) If you are using CUCM for service discovery (have a SRV record for _cisco-uds._tcp.<domain>), then in order to do discovery the user account in CUCM has to be a member of the "Standard CCM End User" access group in order to be able to access the XML configuration file to discover the jabber server.

----
Matthew Huff             | 1 Manhattanville Rd 
Director of Operations   | Purchase, NY 10577
OTA Management LLC       | Phone: 914-460-4039
aim: matthewbhuff        | Fax:   914-694-5669

-----Original Message-----
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Pawlowski, Adam
Sent: Friday, October 20, 2017 1:03 PM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Jabber 11.8 issue

Norm,

I went through some materials and had documented the causes for that message (which show up in a PRT) as best I can. 

"Cannot communicate with server" in my notes always boils down to the workstation not actually being able to reach the server for whatever reason. Either whatever SRV record it sees is pointing it somewhere it cannot go, or the other option is the " ServiceDiscoveryNoNetworkConnectivity " error wherein Jabber believes that it has no network connectivity. I haven't seen that one on sign in but have seen it on resume on Mac before.

Jabber also generates this message if you set the minimum version in the IM and Presence server to something like "11.8.4" but the Mac version never made it past 11.8.1 - if the version isn't allowed it says this.

I don't believe it says this if you don't check the "Home Cluster" box somewhere in the end user for the user to have a home cluster but it will throw an error for that as well. 

Regards,

Adam Pawlowski
Network and Classroom Services
University at Buffalo
716.645.8489


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip