3 Issues Pertaining to UC API for Monitoring

[chris.perry23]

We're currently trying to configure monitoring of Call Manager, Unity Connection, UCCX and CUPS. We are running into 3 issues and I thought I'd lump them into one topic but I can open 3 separate discussions if needed.

1) We get a meaningful response via browser but when scripting we're getting a 404 on perfmon for uccx even after we've enabled the API as per tac/the community post. Here is the link for reference: Solved: RisPort and Perfmon on UCCX 11.5 - Cisco Community

2) 401 authentication issues when attempting to utilize the PAWS api for backup status.

3) Nothing in the docs for a cert expiry endpoint in any of the api's that we have been able to identify. Is there a way to monitor this via the API or do we have to use some other method?

[dstaudt]

1) This works on my 11.5 lab.  I don't recall having to download a WSDL first to make it work, but it's likely I did that as a first step anyway on first testing it.  Perhaps check under Unity Connection Serviceability/Tools/Service Management and see if there are any suspect services not enabled (e.g. Connection Realtime Monitoring APIs).

2) Also seems to be working for me using just Basic Auth...if not using the main admin credentials, can you confirm the user has the correct rights? https://developer.cisco.com/site/paws/documents/developer-guide/authentication.html

POST https://ds-ucm115-1.cisco.com:8443/platform-services/services/MaintenanceService.MaintenanceServiceHttpsSoap12Endpoint/ HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: application/soap+xml;charset=UTF-8;action="urn:getBackupProgress"
Content-Length: 537
Host: ds-ucm115-1.cisco.com:8443
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.5.5 (Java/11.0.12)
Authorization: Basic QWRtaW5pc3RyYXRvcjpjaXNjb3BzZHQ=

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ser="http://services.api.platform.vos.cisco.com">
<soap:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Action>urn:getBackupProgress</wsa:Action>
<wsa:ReplyTo>
<wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
</wsa:ReplyTo>
<wsa:MessageID>uuid:26634481-3273-4a70-b537-ab4b874e4d6b</wsa:MessageID>
</soap:Header>
<soap:Body>
<ser:getBackupProgress/>
</soap:Body>
</soap:Envelope>

3) As of v14, the UC products do have a new certificate management API: https://developer.cisco.com/docs/certificate-management/

For previous releases, you will probably need to do some scraping, either of the admin HTML pages or the CLI (e.g. using Paramiko): https://www.cisco.com/c/en/us/support/docs/security-vpn/certificate-authority-ca/200753-Configure-CA-Signed-Certificate-via-CLI.html

If you need to further troubleshoot (particularly 1&2, 3 will be unsupported) I would suggest opening a DevNet support ticket: https://developer.cisco.com/site/support/