Unlike other “report this problem” buttons, Jabber’s problem report doesn’t just fly into the cloud somewhere never to be seen again.
It actually contains a lot of useful information about things like: how services are discovered and assigned, what policies are defined, what devices are configured, etc. The problem report can be generated, but is located below:
One of the biggest questions I get is where configurations exist, and what takes priority ? Before looking at the file, I would have guessed 3 places, but as you can see below its actually 12!
1: TftpOverrideConfigStore  jabber-config.xml
2: LocalFileConfigStore  AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Config\jabberLocalConfig.xml
3: Ucm90ConfigStore  http://cucm.fqdn.com:6970/SPDefault.cnf.xml
4: PresenceAuthenticatorStore 
5: ServiceDiscoveryConfigStore 
6: PresenceConfigStore  Presence Server TFTP+CCMCIP Settings
7: RegistryConfigStore  HKCU\Software\Cisco Systems, Inc.\JabberWerxCpp
8: PresenceProductModeStore 
9: UrlProvisioningConfigStore 
10: BootstrapConfigStore  ProgramData\Cisco Systems\Cisco Jabber\jabber-bootstrap.properties
11: InMemoryConfigStore 
12: jabber-config-defaults.xml  Program Files (x86)\Cisco Systems\Cisco Jabber\jabber-config-defaults.xml
Each of these stores contain configuration elements in the form of <tags>, retrieved from either the local machine, or through HTTP GET requests
When Jabber is launched, Jabber first tries to read jabberLocalConfig.xml for cached settings, if any exists. It then attempts to reach the domain controller of the machine you are running on for SSO. If both of those fail, only then will it give you a login prompt. If no cached username is found, email is prompted for and DISCOVERY begins.
retrieve email address and parse domain:
Getting LastLoggedInUserName from ConfigFeatureSet
Getting servicesDomain from ConfigFeatureSet
Getting PresenceDomain from ConfigFeatureSet
ServicesDomain key not found, parsing email address.
Retrieved Email Address firstname.lastname@example.org
Retrieved DNS Domain ‘car.pnslabs.com’ from ‘Email Address from UserInput’
Domain is set to: car.pnslabs.com
check for webex im:
makeCasLookupForDomain result is ‘Code: NOT_WEBEX_CUSTOMER; CasUrl: http://loginp.webexconnect.com/cas/FederatedSSO?org=car.pnslabs.com;
check SRV records for on-prem and mra:
*—–* DNS query _cisco-uds._tcp.car.pnslabs.com. has succeeded.
*—–* DNS query _collab-edge._tls.car.pnslabs.com. has failed: DNS name does not exist.
determine home cluster:
*—–* Making HTTP request to: https://cucm.car.pnslabs.com:8443/cucm-uds/clusterUseremail@example.com
fetch user data:
setCurrentLocationOption start: description: Jeffs House ,id: fff8ffb0-1332-4da7-ba78-647b35aa25b2
IsGatewayAddressSubnetExists: gateway address: 00::50::56::E3::E5::50, subnet: 172.16.13.0, locations: 1