[cisco-voip] jabber-config.xml not being downloaded or being ignored

Fri Nov 3 13:38:06 EDT 2017

Yea, the problem here is the clients don't download the jabber-config.xml
until they connect to CUCM which is later.

For first login, you'll need to use provisioning URLs, install switches, or
make a custom MSI.

On Fri, Nov 3, 2017 at 1:33 PM, Ben Amick <bamick at humanarc.com> wrote:

> Until the first registration they don’t get the service exclusion. If the
> client has any webex accounts it will attempt to connect to those first (or
> has had in the past – you have to put in a formal support ticket to get it
> removed). There’s a command line switch you can use on the installation of
> Jabber that will disable the webex on the initial install, and that’s the
> fix if they want to maintain having webex business accounts.
>
>
>
> Alternatively, you might be able to get a support ticket in to remove your
> domain from the webex DNS, which the company gets added to because of the
> cloud messaging built into webex, but I don’t know if they can neuter that
> without neutering the webex accounts proper.
>
>
>
> Ben Amick
>
> Unified Communications Analyst
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *ROZA, Ariel
> *Sent:* Friday, November 3, 2017 1:27 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] jabber-config.xml not being downloaded or being
> ignored
>
>
>
> I have a preexisting installation CUCM 10.5.2 that I am troubleshooting.
>
>
> Jabber for Windows clients ask for Webex credentials for login, although
> the jabber-config.xml file exists and is configured to exclude Webex
> services.
>
> I have checked every possibility and can´t see what I´m missing here.
>
>
>
> The jabber-config contents are this:
>
>
> <?xml version="1.0" encoding="utf-8"?>
> <config version="1.0">
> <Policies>
> <ServiceDiscoveryExcludedServices>WEBEX</ServiceDiscoveryExcludedServices>
> </Policies>
> <Directory>
> <DirectoryServerType>UDS</DirectoryServerType>
> </Directory>
> </config>
>
>
>
> I have tried Jabber clients 11.6.4 and 11.8.2
>
>
>
> The file is loaded to both TFTP serves in the cluster
>
> It´s accessible via URL
>
> The name is lowercase and the format is UTF-8
>
> I restarted the TFTP servers when needed
>
> The Cisco Support Field in the CSF device is empty.
>
> In the Jabber Client I used the Diagnostics Tool (CTRL-SHIFT-D) and
> checked that all setings are ok.
> I reset the client, cleared all the files under %APPDATA%\Local\Cisco\ and
> %APPDATA%\Roaming\Cisco and restarted the client.
>
> The Jabber Client can log on, if done manually, specifiing the
> "Callmanager 9 "mode and the server name/IP. If I switch to Automatic, it
> asks for Webex credentials (My customer has a couple of Webex accounts, but
> not enough for all the enterprise, hence he wants avoid Webex).
>
> I checked the jabber.log, but I didn't get any clues.
>
>
>
> Is there anything I am missing from the process?
>
>
>
> P.S I also posted this question here: https://supportforums.cisco.
> com/t5/jabber-clients/jabber-config-xml-not-being-
> downloaded-or-being-ignored/m-p/3209901#M20756
>
>
>
> Regards,
>
>
>
> Ariel.
>
>
>
>
>
> *Ariel Roza*
>
> *Support Engineer / Southern Cone *
>
> t: +54 11 5282-0458 <+54%2011%205282-0458>
>
> c: +54 9 11 5017-4417 <+54%209%2011%205017-4417>
>
> Av. Belgrano 955 – Piso 20 – CABA – Argentina – C1092AAJ
>
> www.la.logicalis.com
> <http://cp.mcafee.com/d/avndz8Qd2hJ5-VEV7cTKUedTdEEILIFzxO9EVdEEILIFzDDSjqabbXPUVVZMSyyUqejhPuZQrCO6GOIl1hdJnor6TbCOrqKMSdKndFEzJIWqen-LP3atTS7eLsKCOVvxP1EV78LIth5dqWqJS7-l3PWApmU6CQjrVK_nhjjpd7dQXCzATsS02fTzWApmQ-lenMTqlblbCqOmbAaJMJZ0kIToHMd9_7wqr73DD7zpFrJaBGBPdpb6BQQg2eA27NbSH1Sh7wZkYQggHcQg4fB0yq84aC87RR3Q3h1m9Ew8va14Qgi8MH7Q3rzNI2Yfibf0>
>
>
> *_________________________________________________ **Business **and
> technology working as one*
>
> [image: cid:image006.png at 01D298D0.103CDF50]
>
>
>
> [image: Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: tw]
> <http://cp.mcafee.com/d/FZsScxMw86QnXCzAsPuXwUTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSCyeSPFEVvW_ccFTvosWZOWrbB-7c6zAsy-NR4kRHFGTovVkffGhBrwqrjdLCXZt5ddAQsTjKqejtPo0epykV_7BY2JicHqvawlSuGCXiFqFsPmiNsxlK5LE2BCX5u1FfUY3joUsYUYrdbtFkJkKpH9oQKCy0hQwg-9uRoeO8Y7GDCy25pCy0xYE4jh0xkN0-KEuwq8aNd413Vg8Cy2h65o-wrsudLXfABNj7eYz>
>  [image: Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: fb]
> <http://cp.mcafee.com/d/avndy0OrhvKqehPdXK3ztPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPqq8XreCzB_HYMODtZxPHTbFIKnUsMqehObX7khjmKCHtx_BgY-F6lK1FJAS-rLRQkQSjhPteVEVdTdw0_En-DeXrO5qBunNrifQMaR8OJFYG5MHIZlNdBxNxVxAQsT7f6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3joUsYUYrdbtFkJkKpH9oQKCy0hQwg-9uRoeO8Y7GDCy25pCy0xYE4jh0xkN0-KEuwq8aNd413Vg8Cy2h65o-wrsudHYAdjUN3>
>  [image: Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: yt]
> <http://cp.mcafee.com/d/1jWVIq3x0i6jqbZPhOepLtMsrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrjh7rpQQsLZvC6kXLIetuVtdBO_3C3hOehvoWyaqRQRrIfYG7DR8OJMddI6TPt-KyCCOqerFTd79KVI04mGTdIx_bUvkzaSDOEvIZldSBiRiVCIByV2Hsbvg5bdSaY3ivNU6CNMVVNUSqmXiFqFsPmiNFtd40zF0xYiZGMtAhUflfd44aPd413Vg8Cy12Fy1ZtgZ0Qglyq827Owhd44ycaNZ0SUYry6MgP60t>
>
>
>
>
> Logicalis Argentina S.A. solo puede ser obligado por sus representantes
> legales conforme los límites establecidos en el acto constitutivo y la
> legislación en vigor.
>
> El contenido del presente correo electrónico e inclusive sus anexos
> contienen información confidencial.
>
> El mismo no puede ser divulgado y/o utilizado por cualquiera otro distinto
> al destinatario, ni puede ser copiado de cualquier forma.
>
>
>
> Confidentiality Note: This message is intended for use only by the
> individual or entity to which it is addressed and may contain information
> that is privileged, confidential, and exempt from disclosure under
> applicable law. If the reader of this message is not the intended recipient
> or the employee or agent responsible for delivering the message to the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this communication in error, please contact the sender
> immediately and destroy the material in its entirety, whether electronic or
> hard copy. Thank you
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20171103/ff638708/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.jpg
Type: image/jpeg
Size: 5139 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20171103/ff638708/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 6706 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20171103/ff638708/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.jpg
Type: image/jpeg
Size: 1229 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20171103/ff638708/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.png
Type: image/png
Size: 1468 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20171103/ff638708/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.png
Type: image/png
Size: 1470 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20171103/ff638708/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.png
Type: image/png
Size: 1384 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20171103/ff638708/attachment-0003.png>