08-02-2016 09:42 PM - edited 03-17-2019 06:16 PM
Hi, all
Which win, jabber-config or service profile?
I configured selfcareURL in jabber-config.xml as CUCM FQDN.
When I pushed self care portal button, open the self care portal and displayed URL was CUCM IP address.
I checked cachedTFTPConfigStore, and it was correct.
Then I checked cachedUcm90ConfigStore, it also had selfcareURL and it set IP address.
I'm sure that Service Profile influences cachedUcm90ConfigStore settings.
So I wonder which configurations are prior.
CUCM:10.5.1
Jabber:11.1.2
Katsuaki
08-03-2016 12:05 AM
hi
i guess you are trying to logging in jabber automatically via SRV Records.
In that case , if you are using cisco-uds records then Service profile takes the preference and whatever you configure in it.
08-03-2016 05:22 PM
Thank you for replying.
Yes, I'm trying to logging with SRV records, _cisco-uds.
I understand Service Profile wins jabber-config.xml.
Then I have a new question.
I want to disable selfcareURL in Service Profile, but the parameter doesn't exist in it.
I know Self Care Portal Default Server under Enterprise Parameter influences selfcareURL.
However, I don't set the Self Care Portal Default Server, and I cheked it was set NONE by default.
And I know since I select NONE, Jabber defaults to the Publisher.
Do you have any ideas for this problem?
Katsuaki
08-03-2016 11:42 PM
hi ,
you cannot disable self care portal in jabber. Please refer to the below defect.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCux44512/?reffering_site=dumpcr
There are 2 workaround for this in case user selects the self care option in jabber then they won't be directed to cucm.
1. specify imp server ip in enterprise parameter on cucm..
2. manually specify a IM&P server to log in to via the client "Advanced Settings" menu.
i hope this helps you
08-03-2016 12:01 PM
According to Cisco docs, the Service Profile takes precedence over the jabber-config.xml file. However, I noticed the parameters/attributes specified within the jabber-config.xml are referenced in the jabberLocalConfig.xml file, which then determines the client settings.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_0/CJAB_BK_D657A25F_00_deployment-installation-guide-jabber-110/CJAB_BK_D657A25F_00_deployment-installation-guide-jabber-110_chapter_01011.html
What method are you using to advertise the Self Care Portal? You can 1) configure the selfcareURL within the jabber-config.xml file, or 2) you can enter the CUCM Publisher Ip Address or Hostname under the System > Enterprise Parameters > Self Care Portal Default Server. However, I believe - if you identified your CUCM servers by Ip Address under CUCM > System > Server... then you need to enter the Ip Address as the Self Care Portal Default Server.
-Mark
08-01-2017 10:15 AM
Hi,
Just wanted to check if the below link answer your question.
https://bst.cloudapps.cisco.com/bugsearch/bug/cscut72237
https://bst.cloudapps.cisco.com/bugsearch/bug/cscvb16647/
Thanks
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