jabber client not getting correct Service Profile XML

[goranpilat]

Hello,

I tried to configure Jabber Client 12.1.3 on CUCM 12.5 with UC Service/Service Profile. I gave the user Service profile with the UC Service with Jabber configuration. When I save this UC service, I see my Jabber client restarting, thus trying to grab its configuration. However none of the config applied. Then I realised after pressing Shift+CTRL+D, I got 

Service Profile Configuration

https://cisco-cucm1.example.local:6972/SP73896702-4859-37f2-419c-f69e4c4555cf.cnf.xml

SERVICE_PROFILE_XML

https://cisco-cucm1.example.local:6972/SP73896702-4859-37f2-419c-f69e4c4555cf.cnf.xml

But when I go to the link, I get XML file of the service profile without Jabber part:

-<serviceprofile>

<versionstamp>1636104414-d1a63a67-fc16-495f-a8a7-d19621dbebc4</versionstamp>

<portaldefaultserver>cisco-cucm1.example.local</portaldefaultserver>

+<voicemail>

+<mailstore>

+<conferencing>

+<directory>

+<imandpresence>

+<cti>

+<videoconferenceschedulingportal>

</serviceprofile>

Why is jJabber grabbing wrong Service Profile file? And why is there Service profile XML which doesn't have Jabber part, since we are on 12.5?

BR

Goran

[b.winter]

Hello,

are you looking for the Jabber parameters, that were done in the jabber-config.xml in <12.0?

If yes:

It isn't located in the "SERVICE_PROFILE_XML", but in the "Jabber configuriation file".

[goranpilat]

Hi,

No, I know these parameters are supposed to be in jabber-config.xml. But in order to get jabber-config.xml, I expect Jabber client downloads service profile xml which should have entry with Jabber UC Service. However this entry doesn't exist (look at original post), and it should as this is CUCM 12.5, and this Jabber UC Service is configurable in GUI.

I hope I am somewhat clear

[b.winter]

Now I understand

Looking at the jabber logs, I would say, Jabber retrieves the file path in the response of the following request "https://<cucm>:8443/cucm-uds/user/<userid>"

I don't know, if it's also stated in the service profile xml. In my case, I couldn't open it, since the browser gives a weird certificate error.

And if it's empty, I guess it just requests the "default"-file "jabber-config.xml".

 

 

 

[goranpilat]

Hi,

You are right, Jabber profile is stated in the following link:

https://cisco-cucm1.example.local:8443/cucm-uds/user/USER

where I have chunk like this:

<serviceProfile>
<LDAPUserName/>
<LDAPPassword/>
<uri>http://cisco-cucm1.example.local:6970/SP73896702-4859-37f2-419c-f69e4c4555cf.cnf.xml </uri>
<uri>http://cisco-cucm2.example.local:6970/SP73896702-4859-37f2-419c-f69e4c4555cf.cnf.xml </uri>
<uri>http://cisco-cucm3.example.local:6970/SP73896702-4859-37f2-419c-f69e4c4555cf.cnf.xml </uri>
</serviceProfile>
<jabberProfile>
<uri>https://cisco-cucm1.example.local:6972/JAB_73896702-4859-37f2-419c-f69e4c4555cf.cnf.xml </uri>
<uri>https://cisco-cucm2.example.local:6972/JAB_73896702-4859-37f2-419c-f69e4c4555cf.cnf.xml </uri>
<uri>https://cisco-cucm3.example.local:6972/JAB_73896702-4859-37f2-419c-f69e4c4555cf.cnf.xml </uri>
</jabberProfile>

However my Jabber seems to be able to configure itself with the <serviceProfile> links, but it doesnt have <jabberProfile> links. Only

Jabber configuration file : 
https://cisco-cucm2.example.local:6972/jabber-config.xml 

which is old static file on TFTP

[b.winter]

Hey,

I edited my last reply. So maybe you missed the new information.

As I guess, if the link in <jabberProfile> is empty, Jabber just looks for the default-file "jabber-config.xml".