RisPort and Perfmon on UCCX 11.5

[gabriel.caclin]

Hi there,

I am fighting with UCCX 11.5 to access the RISPort and Perfmon api for monitoring purposes.

I wrote python scripts to get status of services, partitions and other detailed stuff for CUCM/IMP/Unity afterplaying a bit with the API documented here: https://developer.cisco.com/docs/sxml/#perfmon-api-reference

Works great, typicall call the services on the host, on ports 8443.

But here is the problem. I wanted to do the same for UCCX and it looks these API are not available, or at least not on port 8443.

So I played around on other potential ports, without success. Of course I checked the related network services were up and running.

I raised a case at the TAC to have their advice on it, which returns me to the Port utilization in UCCX document. It shows that RisPort is on  TCP 5001 and Perfmon on port TCP 5002, used for SOAP monitor.

So I grab my Postman, modify my query, but nothing better.

Is anyone having the same concern or had a chance to find out how to do this on UCCX ?

Thanks a lot!

[gabriel.caclin · Accepted solution]

After getting in touch with TAC, a requeue, I finally get an killer engineer who spot in a minute the issue !

These API works as well on UCCX (same port 8443, and not 5001...), however the APIs are not correctly initialized, that's why it is not working.

It must be first issued the URL https://<UCCX_IP>:8443/logcollectionservice/services/DimeGetFileService?wsdl which will return data in the browser.

After that, the URLs for API will work:

https://<UCCX_IP>:8443/perfmonservice2/services/PerfmonService?wsdl

https://<UCCX_IP>:8443/realtimeservice2/services/RISService70?wsdl

It is not documented, neither defect open. So if it can helps.

[Kevin10]

This workaround doesn't seem to be working for me on my UCCX 12.5 server. Not sure if there's something I need to be persisting from the DimeGetFileService URL connection, or if this workaround no longer works in the newer version.

The first connecting to DimeGetFileService succeeds and I get the expected response back, but my subsequent connection to PerformService comes back with a 404.

Wondering if your fix is still working, or if anyone has any notes on anything else that might be different in the new version, or anything else I need to look at here.

I'll keep plugging away and reply back when I figure out what I'm missing.