Blogs



Cisco Developer Network will be presenting a CDN Developer Track at Cisco Live! London the week of January 31, 2011.

We are presenting technical sessions which highlight Application Programming interfaces (APIs) and Software Developer Kits (SDKs) for Cisco technologies such as Unified Communications, IOS, and Access Routing Technologies ¿ including the new Cisco Cius ...Read More

 

Showing 1 result.

Forums

« Back to Application Gateway Protocol

Can't call out to a web service

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Can't call out to a web service
url
Answer
7/17/10 2:27 AM
Can anyone provide any insight to this error message/code?  I'm using the simulator (if it matters).  It attempts to call a web service that has multiple web methods to retrieve routing data.
 
 
07/16/2010 16:42:23.734----------------------BEGIN XML DOC--------------------
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
  <GetAniLookupRoutingInformation xmlns="http://www.progressive.com/tad">
   <Ani>2295322091</Ani>
  </GetAniLookupRoutingInformation>
 </soap:Body>
</soap:Envelope>
07/16/2010 16:42:23.750-----------------------END XML DOC---------------------
07/16/2010 16:42:23.750-Opening server connection.
07/16/2010 16:42:23.750-Error in GetRouteInfoECC2 Method
07/16/2010 16:42:23.750-Error in MSXML Module.
07/16/2010 16:42:23.750--2147012890
07/16/2010 16:42:23.750-The URL does not use a recognized protocol

07/16/2010 16:42:23.750-
07/16/2010 16:42:23.750-GetRouteInfoECC2::Exit
Flag

RE: Can't call out to a web service
gatewayxml
Answer
10/22/10 8:45 PM as a reply to Vincent Crenshaw.
 
That error propagated from Microsoft is relatively vague and could mean many things -- the URL scheme could not be recognized or is not supported, the Web/XML service is not available or not processing XML over HTTP, etc.  A lot of dependence would reside with examining the characteristics of the URL, the Web/XML application, interface, and protocol being used for the RouteRequest.
 
Bottom line it appears that the issue probably due to the fact that you are trying to call a web service that has multiple web methods to retrieve routing data -- when GatewayXML requires a 1-to-1 mapping between each GatewayXML instance and Web/XML application.
 
If you still require additional support, then I would recommend the consideration of purchasing a Subject Matter Expert (SME) Contract or Custom Application Support (CAS/D2S) Agreement from your Services Account Team.
Flag

Collateral


No files available