cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
951
Views
0
Helpful
1
Replies

GSAPI/ XCC – Error response from router for ResponseXccProbing message

I have developed a custom application based on the Cisco GSAPI as a .NET based console application. This application needs to intercept communicate with Cisco ISR-G2 Router and verify the calling number from external database in order to determine the next action i.e., whether to Allow/ Redirect/ Deny the call.

I am successfully able to register our application with the XCC provider on router and the router sends me back proper “ResponseXccRegister” message.

However, when app responds to the SolicitXccProbing with ResponseXccProbing message, it sends back an XML PARSER error message. The message format is similar to what Cisco suggests in the GSAPI document. We are not very sure what's wrong here!

Below are logs,

1)Registration Request/ Response Logs in our application

2018-05-30 08:43:26,275 INFO [1] CiscoApp.Program.RequestRegister - Sending RequestXccRegister message to router (924 bytes) at 5/30/2018 8:43:26 AM:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><RequestXccRegister xmlns="http://www.cisco.com/schema/cisco_xcc/v1_0"><applicationData><name>CiscoXCC</name><url>http://ClientIP:8090/CiscoXCC</url></applicationData><blockingEventTimeoutSec>6</blockingEventTimeoutSec><blockingTimeoutHandle>CONTINUE_PROCESSING</blockingTimeoutHandle><connectionEventsFilter>CREATED AUTHORIZE_CALL ADDRESS_ANALYZE REDIRECTED ALERTING CONNECTED TRANSFERRED CALL_DELIVERY DISCONNECTED HANDOFFLEAVE HANDOFFJOIN</connectionEventsFilter><mediaEventsFilter>MODE_CHANGE DTMF TONE_BUSY TONE_DIAL TONE_SECOND_DIAL TONE_RINGBACK TONE_OUT_OF_SERVICE MEDIA_ACTIVITY</mediaEventsFilter><msgHeader><transactionID>11111d</transactionID></msgHeader><providerData><url>http://routerIP:8090/cisco_xcc</url></providerData></RequestXccRegister></soapenv:Body></soapenv:Envelope>
2018-05-30 08:43:26,285 INFO [1] CiscoApp.Helper.SendMessage -
 ***** Received Response from router (400 at 5/30/2018 8:43:26 AM:
<?xml version="1.0" encoding="UTF-8"?><SOAP:Envelope xmlns:SOAP="http://www.w3.org/2003/05/soap-envelope"><SOAP:Body><c xmlns="http://www.cisco.com/schema/cisco_xcc/v1_0"><msgHeader><transactionID>11111d</transactionID><registrationID>F02C3B56:XCC:CiscoXCC:446</registrationID></msgHeader><providerStatus>IN_SERVICE</providerStatus></ResponseXccRegister></SOAP:Body></SOAP:Envelope>

2)SolicitXccProbing message from router and ResponseXccProbing sent from application

2018-05-30 08:43:56,286 INFO [5] CiscoApp.SocketListener.StartListening - <?xml version="1.0" encoding="UTF-8"?><SOAP:Envelope xmlns:SOAP="http://www.w3.org/2003/05/soap-envelope"><SOAP:Body><SolicitXccProbing xmlns="http://www.cisco.com/schema/cisco_xcc/v1_0"><msgHeader><transactionID>F02CB087:3128</transactionID><registrationID>F02C3B56:XCC:CiscoXCC:446</registrationID></msgHeader><sequence>1</sequence><interval>30</interval><failureCount>0</failureCount><registered>true</registered><providerStatus>IN_SERVICE</providerStatus></SolicitXccProbing></SOAP:Body></SOAP:Envelope>
2018-05-30 08:43:56,296 INFO [5] CiscoApp.SocketListener.StartListening -
 ***** Sending ResponseXccProbing message to router (399 bytes) at 5/30/2018 8:43:56 AM:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><ResponseXccProbing xmlns="http://www.cisco.com/schema/cisco_xcc/v1_0"><msgHeader><transactionID>F02C3B56:XCC:CiscoXCC:446</transactionID><registrationID>F02CB087:3128</registrationID></msgHeader><sequence>1</sequence></ResponseXccProbing></soapenv:Body></soapenv:Envelope>

3)Error response from router for ResponseXccProbing message

2018-05-30 08:43:56,307 INFO [5] CiscoApp.Helper.SendMessage -
 ***** Received Response from router (985 at 5/30/2018 8:43:56 AM:
<?xml version="1.0" encoding="UTF-8"?><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>ResponseXccProbing</errorXMLDetail><errorXMLMsg><?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><ResponseXccProbing xmlns="http://www.cisco.com/schema/cisco_xcc/v1_0"><msgHeader><transactionID>F02C3B56:XCC:CiscoXCC:446</transactionID><registrationID>F02CB087:3128</registrationID></msgHeader><sequence>1</sequence></ResponseXccProbing></soapenv:Body></soapenv:Envelope></errorXMLMsg></XMLParserError></SOAP:Detail></SOAP:Fault></SOAP:Body></SOAP:Envelope>

4)Router’s XCC logs

*May 30 13:18:25.261: //WSAPI//OUTGOING_MESSAGE:: type 3  SolicitXccProbing:
*May 30 13:18:25.261: registrationID F04BD204:XCC:CiscoXCC:448
*May 30 13:18:25.261: sequence 1
*May 30 13:18:25.261: interval 30
*May 30 13:18:25.261: failureCount 0
*May 30 13:18:25.261: registered 1
*May 30 13:18:25.261: providerStatus 1
*May 30 13:18:25.261: //WSAPI/INFRA/wsapi_send_outbound_message_by_provider_info:
*May 30 13:18:25.261: //WSAPI/XCC/wsapi_xcc_encode_outbound_msg:
*May 30 13:18:25.261: //WSAPI/XCC/wsapi_xcc_encode_outbound_msg: Exit
*May 30 13:18:25.262: //WSAPI/INFRA/1/0/F04C4735:3144:tx_contextp 7F996ACD67B0 tx_id C48 context1 (1 1) context2 (0 0): out_url http://ClientIP:8090/CiscoXCC
*May 30 13:18:25.262: wsapi_send_outbound_message_by_provider_info: <?xml version="1.0" encoding="UTF-8"?><SOAP:Envelope xmlns:SOAP="http://www.w3.org/2003/05/soap-envelope"><SOAP:Body><SolicitXccPa/cisco_xcc/v1_0"><msgHeader><transactionID>F04C4735:3144</transactionID><registrationID>F04BD204:XCC:CiscoXCC:448</registrationID></msgHeader><sequence>1</sequence><interval>30</interval><failureCegistered><providerStatus>IN_SERVICE</providerStatus></SolicitXccProbing></SOAP:Body></SOAP:Envelope>
*May 30 13:18:25.262: //WSAPI/INFRA/1/0/F04C4735:3144/wsapi_send_outbound_message_by_provider_info: Exit
*May 30 13:18:25.262: wsapi_send_SolicitProbing:mem_mgr_mempool_free: mem_refcnt(7F9901562508)=0 - mempool cleanup
*May 30 13:18:25.275: //WSAPI/INFRA/wsapi_https_urlhook:
*May 30 13:18:25.275: //WSAPI/INFRA: app_name cisco_xcc in url /cisco_xcc in port 8090
*May 30 13:18:25.275: //WSAPI/INFRA: app url /cisco_xcc app port 8090
*May 30 13:18:25.275: //WSAPI/INFRA/wsapi_https_urlhook: Exit
*May 30 13:18:25.276: //WSAPI/INFRA/wsapi_https_post_action:
*May 30 13:18:25.276: wsapi_https_data_read: base_buf (7F9901562AC8)<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><Re.com/schema/cisco_xcc/v1_0"><msgHeader><transactionID>F04BD204:XCC:CiscoXCC:448</transactionID><registrationID>F04C4735:3144</registrationID></msgHeader><sequence>1</sequence></ResponseXccProbing><
*May 30 13:18:25.276: //WSAPI/INFRA/1960/0/wsapi_https_recv:
*May 30 13:18:25.277: //WSAPI/INFRA/1960/0/wsapi_https_recv: xml_parser_msg_parse fail, reason 7
*May 30 13:18:25.277: //WSAPI/INFRA/1960/0/wsapi_response_xml_fault:
*May 30 13:18:25.277: //WSAPI/XCC/wsapi_xcc_operation_unknown_namespace:
*May 30 13:18:25.277: //WSAPI/INFRA/1960/0/wsapi_response_xml_fault: Exit
*May 30 13:18:25.277: wsapi_https_data_write: <?xml version="1.0" encoding="UTF-8"?><SOAP:Envelope xmlns:SOAP="http://www.w3.org/2003/05/soap-envelope" xmlns:xml="http://www.w3.org/XML/1998/namespaOAP: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:erError><errorXMLDetail>ResponseXccProbing</errorXMLDetail><errorXMLMsg><?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Bodyisco.com/schema/cisco_xcc/v1_0"><msgHeader><transactionID>F04BD204:XCC:CiscoXCC:448</transactionID><registrationID>F04C4735:3144</registrationID></msgHeader><sequence>1</sequence></ResponseXccProbirrorXMLMsg></XMLParserError></SOAP:Detail></SOAP:Fault></SOAP:Body></SOAP:Envelope>
*May 30 13:18:25.279: //WSAPI/INFRA/wsapi_https_post_action: Exit

Thanks in advance!

1 Reply 1

Chester Rieman
Cisco Employee
Cisco Employee

Hi Mehul,

      I am seeing almost the exact same issue but with xcdr provider:
https://community.cisco.com/t5/communities-of-interest/gateway-service-api-wsapi-xcdr-keeplive/m-p/4674806

Wondering if you resolved this and what your working ResponseXccProbing message looks like if you don't mind sharing.
Thanks!