Hi Folks,
Trying to use WSAPI to gather CDRs from a CUBE. I can get the app registered and it receives CDRs but fails after a time due to an inaccurate ResponseXcdrProbing message my app sends back. I followed the example of the xcc probing response shown in the doc https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/CUCIS_API/CUCIS_API_Guide/CUCISA_MSG.html but I get back a 200 with Unknown XML tag.
Here is the probe response I am sending.
<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n
<soapenv:Envelope xmlns:soapenv=\"http://www.w3.org/2003/05/soap-envelope\">\n
<soapenv:Body>\n<ResponseXcdrProbing xmlns=\"http://www.cisco.com/schema/cisco_xcdr/v1_0\">\n
<msgHeader>\n
{RID}\n
{TID}\n
</msgHeader>\n
<sequence>{SEQ}</sequence>\n
</ResponseXcdrProbing>\n
</soapenv:Body>\n
</soapenv:Envelope>"
Here is the error I get back in the 200 OK
<SOAP:Envelope
xmlns:SOAP="http://www.w3.org/2003/05/soap-envelope"
xmlns:xml="http://www.w3.org/XML/1998/namespace">
<SOAP:Body>
<SOAP:Fault>
<SOAP:Code>
<SOAP:Value>
SOAP:Sender
</SOAP:Value>
<SOAP:Subcode>
<SOAP:Value>
XML PARSER ERROR
</SOAP:Value>
</SOAP:Subcode>
</SOAP:Code>
<SOAP:Reason>
<SOAP:Text
xml:lang="en">
An unknown XML tag has been received
</SOAP:Text>
</SOAP:Reason>
<SOAP:Detail>
<XMLParserError>
<errorXMLDetail>
ResponseXcdrProbing
</errorXMLDetail>
<errorXMLMsg>
<?xml
version="1.0"
encoding="UTF-8"
?>
<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Body>
<ResponseXcdrProbing
xmlns="http://www.cisco.com/schema/cisco_xcdr/v1_0">
<msgHeader>
<registrationID>
123B97C:XCDR:myapp:158
</registrationID>
<transactionID>
125CA18:679
</transactionID>
</msgHeader>
<sequence>
1
</sequence>
</ResponseXcdrProbing>
</soapenv:Body>
</soapenv:Envelope>
</errorXMLMsg>
</XMLParserError>
</SOAP:Detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
GW debug shows
*Aug 17 18:14:05.079 EDT: //WSAPI//OUTGOING_MESSAGE:: type 3 SolicitXcdrProbing:
*Aug 17 18:14:05.079 EDT: registrationID 1B54074:XCDR:myapp:246
*Aug 17 18:14:05.079 EDT: sequence 8
*Aug 17 18:14:05.079 EDT: interval 120
*Aug 17 18:14:05.079 EDT: failureCount 4
*Aug 17 18:14:05.079 EDT: registered 1
*Aug 17 18:14:05.079 EDT: providerStatus 1
*Aug 17 18:14:05.079 EDT: //WSAPI/XCDR/wsapi_xcdr_encode_outbound_msg:
*Aug 17 18:14:05.079 EDT: //WSAPI/XCDR/wsapi_xcdr_encode_outbound_msg: Exit
*Aug 17 18:14:05.115 EDT: //WSAPI/XCDR/wsapi_xcdr_operation_unknown_namespace:
*Aug 17 18:14:05.123 EDT: //WSAPI/XCDR: magic[0x40BE] state[STEADY] owner[0x3F2ACACC] debFlag[6] sequence[9] failureCount[4] msgStatusHdlr[0x363EC528] timerExpiredHdlr[0x363EC3CC]
*Aug 17 18:14:05.123 EDT: //WSAPI/XCDR/wsapi_prober_response_validate:338: msg send_status[SUCCESS], msg resp_status[FAILED]req_msg_type[3], resp_msg[0x0] sequence[8]
*Aug 17 18:14:05.123 EDT: //WSAPI/ /wsapi_prober_response_validate: Prober resp invalid
I could not find a good example of ResponseXcdrProbing but there was an example of ResponseXccProbing in the doc which is what I went by, apparently there is a difference between XccProbing and XcdrProbing responses. If anyone has a working example of ResponseXcdrProbing, I would love to see what it looks like.
Thanks!
