I know this topic has come up many times with the need for reporting to demonstrate jabber adoption.
I can see RTMT can show "Current connect Jabber Clients", but you would have to keep RTMT running 24x7 to see the long term trend.
I have heard “Cisco Prime Collaboration 11.0 Assurance and Analytics" probably has the ability to do analytics and generating some kind of usage report, but haven't tried.
Has anyone used it before, and confirm if it's capable to do so? Can you share a screenshot of the report?
And is there any third party tools can do this long term Jabber Clients usage reporting?
Thanks in advance to any feedback.
Solved! Go to Solution.
Apologies for late response, Now i can see jabber tab in analytics but how management can trust this data ?
I guess this doesn't provide complete information like Active user details or Call details which made from jabber .
We would like to enable this in our system also but I am not familiar with the process to use the Jabber Config xml file or where to change this in the webUI. We are on 12.5 so would prefer to use the WebUI to make the changes. The Cisco What's New from January 2020 also mentions that this has to be enabled in CM first but didn't see instructions there either. https://help.webex.com/en-us/n45okcs/What-s-New-in-Cisco-Webex-Analytics-and-Troubleshooting
Can someone post the instructions for making the changes in the WebUI to enable this?
Here you go.
You will need to look at what settings you have in your XML file and asses if they are still valid. Best way to do that is to look at the matching parameter reference document for your version of Jabber. One example is this that is for 12.9. Once you know what parameters you want to keep you need to configure them in the UC service type for Jabber Client Configuration. Once that's done you tie this UC service to your service profile(s). When your done with this you can remove the actual XML file from your TFTP server.
Roger - This is really helpful, looking to adjust this in the next maintenance window - just seeking information, on the cert requirement as I am not following why the need for GoDaddy cert in such where does it need to be installed, how to obtain this and is it truly needed. Note, we are using webex formerly (webex teams).
"You must install the following root certificate to use the telemetry feature: GoDaddy Class 2 Certification Authority Root Certificate. The telemetry server certificate name is "metrics-a.wbx2.com". To resolve any warnings about this certificate name, install the required GoDaddy certificate. For more information about certificates, see the Planning Guide."
AFAIK the certificate(s) needed are already present in CUCM trust store. We did not have to add any certs when we enabled this functionality.
Thank you for the quick answer. It looks like we don't have this cert in CUCM trust store, I would assume we can enable this feature wait for the client to complain then capture the cert and install it as root into CUCM.
If you don’t have the needed certificate(s) reach out to TAC, they should be able to help you out with providing the required certificate(s). If I remember correctly the certificate(s) should be in the tomcat trust store.
We have confirmed that we have the UC Telemetry settings are correct except our Organization ID is not listed correctly. If we add the Organization ID, do the clients have to reset or does it apply this change automatically to all users with that UC Service?