cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements


        IMPORTANT! The sandboxes that can be reserved will be undergoing maintenance
from 12:01AM PDT Friday May 21 until 11:59PM Sunday May 23.
During this time, reserved sandboxes will be unavailable.
Always-On sandboxes are not affected and should still be available.
1529
Views
2
Helpful
3
Replies
Anshu.Garg1
Beginner

Cisco Jabber 11.9.x

Cisco has decided to encrypt the Jabber configuration file (more specifically, jabberLocalConfig.xml). The XML file has been replaced with a .dat file which is encrypted.

Our application reads the device name corresponding to the Cisco Jabber user from the xml file. But since the file is now encrypted, our application can no longer read it.

My question is the following:

"Is there is a way that our application can use to figure out if the end user has logged into the Jabber or he has just started it?"

3 REPLIES 3
jacoadam
Contributor

Hello Anshu,

Sorry for the delay in response! I would recommend opening an official support ticket to get this issue solved. You can do that here: https://developer.cisco.com/site/devnet/support/

This will be the best place to get access to a dedicated collaboration expert.

Thanks!
Jacob

dstaudt
Cisco Employee

I suspect reading the xml config file was never intended to be a stable 'developer interface', and I also suspect there is no easy option to disable the encryption (if customers would even let you.)

Information on the devices associated to a user can be retrieved from UCM via web the AXL web services AP (see <getUser>)I: https://developer.cisco.com/site/axl/

If you want to determine the real-time registration status of a particular device (i.e. a Jabber client), there is the Serviceability RisPort API:

https://developer.cisco.com/site/sxml/documents/api-reference/risport/

Has anyone got a documented way to get around this issue please?

As per anshu.garg1 above, we rely on the local xml file to pick up the connected device name which was working perfectly with previous versions.

To use the AXL api it would appear that we would need to setup a specific user, which we would need to invoke the AXL api with, as it seems that by default, no users have access to this api.  This seems counter intuitive, as Jabber must itself get a list of connected devices for the current signed in user, in some way?

Many thanks

Steve

Content for Community-Ad