05-23-2018 11:21 AM - edited 03-17-2019 07:32 PM
CUCM version 11.5
Jabber version 12
I am trying to create an alternate jabber configuration file but it will not apply to my client.
File: jabber-config-testing.xml (verified UTF-8 encoding)
I have the filename entered in the Cisco Support Field for my CSF device but it will not apply to my Jabber client even after resetting and deleting the AppData/Cisco folder. It still loads the default jabber-config.xml. I verified this in the diagnostics menu.
Ideas?
Solved! Go to Solution.
05-23-2018 02:03 PM
That's not what I'm talking about, but yeah, the .xml needs to be formatted properly to work.
What I'm talking about is exactly how did you entered the value under the support field?? just the name of the .xml file??
05-23-2018 11:43 AM
After you uploaded the alternate config file, did you restart the TFTP service?
05-23-2018 01:10 PM
05-23-2018 01:21 PM
How did you configure the .xml you want to use in the support field??
It's not just the filename if that's what you're doing, the Jabber docs explain how it needs to be configured.
05-23-2018 01:56 PM
05-23-2018 02:03 PM
That's not what I'm talking about, but yeah, the .xml needs to be formatted properly to work.
What I'm talking about is exactly how did you entered the value under the support field?? just the name of the .xml file??
05-23-2018 02:06 PM
05-23-2018 02:36 PM
05-23-2018 03:37 PM
Correct, you need to specify that the data you're using there is a configurationfile so Jabber understands that it has to use that .xml and not jabber-config.xml which it's hard-coded to use.
05-27-2018 12:34 PM
05-27-2018 02:33 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide