Make plans now to attend XMPP integration with CVP 2012/06/14 @ 10:00 AM at Cisco Live! in San Diego. ...Read More

 



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

 

Recently noticed that there have been repeated questions from our developer community complaining that they can't seem to get the beep to work with <record>. They have set the beep attribute to "true" alright, and the reference guide even says this is supported but why doesn't it work?
...Read More

 

August 01, 2006
Earlier today, as I was typing a comment in our internal issuing-tracking system, I hit backspace to correct a typo. WHAM! I go back to the previous page, and my long-winded comment is gone. Apparently I somehow left the context of the text area (did I tab, or spuriously click, or??), which causes backspace to act as a hotkey for "Back". The web browser was not very forgiving of my mistake.

Are your IVR applications forgiving? They should be.
...Read More

 

Mark Gibbs over at Network World has put together a spiffy little scoring system for customer service systems (including many criteria for IVR systems). How would callers score your IVR using Mark's guidelines? Place a call and find out, you may be surprised.
...Read More

 

If you're using JNDI to connect to your database through Tomcat, then it's possible you've had to deal with database connection pool leaks. Your code tests fine, it's been reviewed, but in load tests or in production your app is unable to acquire database connections, the pool is empty!

Fear not, there are some handy parameters which can be set in your application's XML configuration file (in tomcat/conf/Catalina/YOUR_IP/YOUR_APP.xml):
...Read More

 

Showing 6 results.
Items per Page 50
of 1
First Previous Next Last

CVP Forum

« Back to General Discussion - All Versions

Web service element fails without trying

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Web service element fails without trying
Answer
2/8/13 11:57 PM
The situation is that I have a web service that I want to call from a VXML application. I can call the web service from SOAP UI (a test tool) running on the VXML server. It works fine; I get a good response.
 
When I use the same WSDL in a Web Service element in Call Studio, the WSDL imports fine (even from a remote URI) and it understands what to send and receive. But, when I try to run the VXML application, either in Call Studio debug mode or in a deployed application on the CVP, nothing happens. WireShark shows no HTTP activity (which I can see when running SOAP UI), and the element just fails to Error. Relevant part of the error log may be this:  
 
Root Cause: java.lang.NullPointerException     at com.audium.server.webservices.soapenv.RequestEnvelope.createEnvelopeDocumentLiteralWrapped(RequestEnvelope.java:260)     at com.audium.server.webservices.soapenv.RequestEnvelope.(RequestEnvelope.java:101)     at com.audium.server.webservices.ServicesDispatcher.invoke(ServicesDispatcher.java:178)     at com.audium.server.webservices.WebservicesElement.invokeService(WebservicesElement.java:51)     at com.audium.server.voiceElement.WebservicesElementBase.service(WebservicesElementBase.java:396)     at com.audium.server.controller.Controller.goToWebservices(Controller.java:2910)     at com.audium.server.controller.Controller.goToElement(Controller.java:2689)     at com.audium.server.controller.Controller.continueCall(Controller.java:2511)     at com.audium.server.controller.Controller.doPost(Controller.java:733)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:879)     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)     at java.lang.Thread.run(Thread.java:662)
 
That points to the ServicesDispatcher, which is the part of Java that hands SOAP requests over to the network layer. Again, it's not getting a bad response; it's failing to send a request.
 
Any advice would be welcome.
Flag

RE: Web service element fails without trying
Answer
2/20/13 4:15 PM as a reply to David Wall.
David, since you opened a SR for this issue and it was determined by engineering you need to:  
 
At the bottom of the file (Line 63). I copied it from the original one.   My test steps are,
1.       Import the wsdl to a SoapUI project.
2.       Create Mock service in SoapUI
3.       Access the SoapUI Mock Service, and get the wsdl (modified by SoapUI, and the server address points to SoapUI Mock service)
4.       Insert Web Service element in Call Studio, and use the url of SoapUI directly (for example http://SoapUIServerIP:8088/mockQICAgentInfoSOAP12Binding?WSDL ).  
This was due to a  “Connection Refused” error.   11.133.21.70.1360721498132.19.QIC,02/13/2013 13:11:42.960,The error was: HTTP transport error: java.net.ConnectException: Connection refused: connect The error was:

1234567 The root cause was: javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection refused: connect com.audium.server.AudiumException: … …  
Flag