CDR - CDRonDemandService endpoint in CUCM 12?

[istibekesi]

On a recently installed CUCM 12, I'm trying to access CDR on demand service. Double checked Cisco Unified Serviceability, everything looks fine, the service is enabled and status is running.

However, the endpoint was used before is not valid:

https://<CUCM IP>:8443/CDRonDemandService/services/CDRonDemand
AXIS error - No service at this this URL

For CUCM 11 it was working fine. CDRonDemand endpoint has changed in CUCM 12?

[dstaudt]

Can you try https://<server>:8443/realtimeservice2/services/CDRonDemandService

Per the guide here: https://developer.cisco.com/site/sxml/documents/api-reference/cdr-on-demand/

I suspect that the previous URL you are referencing was for the deprecated 'RPC' SOAP flavor of the API...

[istibekesi · Accepted solution]

The URL in the guide does not work for me either.

However, I've got the answer from a DevNet ticket meanwhile:

I was using AXIS 1, which is not deprecated in CUCM 12.

The URL used  "https://<IP>/CDRonDemandService/" to access the SOAP services is in deprecation plan which uses AXIS 1 framework.

We are already providing AXIS2 support services with following  URL "https://<IP>/CDRonDemandService2/ ".

If Customer want to access the AXIS1 SOAP services , they have to activate by running below command in their machine .

soapservicecontrol.sh  CDRonDemandService CDRonDemand start/stop  8443 "

[ghinson]

Hey there;

I'm on a 12.5 system trying use the CDR on demand API to view a list of files returned via SOAP, but I keep getting the "No file found within the specified time range" error, using the following WSDL URL: https://ccm-hostname/CDRonDemandService2/services/CDRonDemandService?wsdl

However if I ssh to the same pub locally and view the processed folder I can see several files in there that exist between the  in0=202207111300 and in1=202207111400 date ranges (also setting in2=True) that I'm passing to the API, see below:

admin:file list activelog /cm/cdr_repository/processed/20220711/cdr*
cdr_Hinsonlabs-125_01_202207111339_42 cdr_Hinsonlabs-125_01_202207111340_43
cdr_Hinsonlabs-125_01_202207111342_45 cdr_Hinsonlabs-125_01_202207111347_46
cdr_Hinsonlabs-125_01_202207111359_47 cdr_Hinsonlabs-125_01_202207111402_48
cdr_Hinsonlabs-125_01_202207111404_49 cdr_Hinsonlabs-125_01_202207111405_50
cdr_Hinsonlabs-125_01_202207111409_51 cdr_Hinsonlabs-125_01_202207111412_52
cdr_Hinsonlabs-125_01_202207111413_53 cdr_Hinsonlabs-125_01_202207111427_54

Any ideas on why I keep getting the "No file found within the specified time range" error?

[dstaudt]

That seems right at first glance.  Could you perhaps provide the full/raw HTTP request, maybe we can spot something..?

I would note that the service endpoint indicated by the CDRonDemandService2 WSDL is unfortunately incorrect, and should be:

https://cucm_pub:8443/CDRonDemandService2/services/CDRonDemandService

but I don't think you're getting the usual error about no service endpoint found...unless you got the old CDRonDemand service enabled and are using that..?

[ghinson]

Thanks for the quick response. Seems that providing :8443 in the WSDL URL didn't make a difference, as I could browse to that URL and see the WSDL file with and without the :8443 port reference. In either case I tested it both ways via the API and I get the "No file found within the specified time range" error in both conditions, even though via command line I can see files in the "processed" folder in the path I provided previously. I'll try later today to provide a the response from SoapUI or other SOAP client. I was using the zeep SOAP client with Python when I encountered the no file found error.

[ghinson]

when attempting to run the get_file_list in Postman, I get "unexpected subelement in0", see attached image. I also used the following link to format the Body of the POST command sent to the server: https://developer.cisco.com/docs/sxml/#!cdrondemand-api-reference/get_file_list

[dstaudt]

Unfortunately the example in the docs seems to have been carried forward from olden times...it has some extraneous namespaces, and - crucially - has a trailing '/' on the end of the xmlns:soap namespace (which reproduces your problem).

The docs have been updated with samples based on the CUCM 14 WSDL: https://developer.cisco.com/docs/sxml/#!cdrondemand-api-reference/get_file_list
The doc also suggests restarting the CDR repository manager services on CUCM as a possible fix/workaround...any chance you can try that?

[ghinson]

Thank you for the updated XML syntax. My postman test is working now, as it is now returning the list of expected files I knew existed on the CUCM in that date/time range, see attached screenshot.I also figured out what was happening with the zeep module, which was a separate issue. All is working now, I'm getting the same file list via postman and zeep SOAP clients, thanks again for your help!