The link on https://developer.cisco.com/site/sxml/develop-and-test/documentation/latest-version/index.gsp to download the current
10.5 Cisco Unified Communications Manager XML Developer Guide
goes to https://developer.cisco.com/site/sxml/develop-and-test/documentation/latest-version/index.gsp so basically creating a loop. What is the proper link to get the PDF?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I believe the 10.5 version is HTML/online only. We will clean up the download link.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The documentation for serviceability going forward is currently a work in progress and is being updated. However, if you are using CUCM 10.0, then the serviceability guide for CUCM 9.1 should work just fine. Here is the link to that: Cisco Unified Communications Manager XML Developers Guide, Release 9.1(1) - Serviceability XML API [Cisco Unified Commun….
If you run into any problems with serviceability just contact us back and we will be able to assist you.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Stephan,
I forgot to mention when using the WSDLs please refer to the doc literal Serviceability WSDLs and examples and not the rpc encoded. Please let me know if you have any further questions.
Thank You,
Jock
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I've never managed to get the WSDL working anyway (in .NET) so I've written my own implementation a while ago and I'm bringing that forward if new features arrive.
Bringing that lib forward usually means implementing for several new releases, so it is important to me to have all the documentations (or at least having a "what's changed" and if it is empty.. I know I have nothing to do)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Which specific WSDL's and calls are you looking to utilize?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Currently I'm only targetting RISPort
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
All of the doc literal WSDLs should be working correctly. I have tested most of them including Risport. However, I noticed on the link I sent you the addresses for the doc literal WSDLs were incomplete. The way to access them would be as follows:
Risport
https://<ServerName>:8443/realtimeservice2/services/RISService70?wsdl
PerfmonPort
https://<ServerName>:8443/perfmonservice2/services/PerfmonService?wsdl
ControlCenterServices
https://<ServerName>:8443/controlcenterservice2/services/ControlCenterServices?wsdl
ControlCenterServicesEx
https://<ServerName>:8443/controlcenterservice2/services/ControlCenterServicesEx?wsdl
LogCollectionService
https://<ServerName>:8443/logcollectionservice2/services/LogCollectionPortTypeService?wsdl
CDRonDemand
https://<ServerName>:8443/CDRonDemandService2/services/CDRonDemandService?wsdl
This should be all of the current WSDL locations for your version of CUCM.
I am not too familiar with .NET for processing them as I tend to lean towards Python when I can. However, whether I use a SOAP handler or send SOAP messages directly with my app or script I will utilize SOAPUI to test a specific request as to see what all is required of the request and what all I will get back. Please let me know if that is useful to you or if you are having a specific problem with the Risport API.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Comments
0 comments
Please sign in to leave a comment.