cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2066
Views
5
Helpful
24
Replies

Cisco CVP Standalone Outbound

Muhammed Ashiq
Beginner
Beginner

Dears,

 

We are trying to implement Cisco CVP Standalone Outbound as described by Engineer Mr.Paul Tindal.

https://twitter.com/tindallpaul/status/919638559702822912

 

Below are the setup we are using,

Cisco PCCE 12.0

Cisco CVP 12.0

Cisco VVB 12.0

Voice Gateway 29XX

 

Did anyone implemented this setup.Need help in VVB Configuartion.

24 Replies 24

That's correct Muhammed, just multiple applications plus whatever polling number you want each of them to use.

Muhammed Ashiq
Beginner
Beginner

Hi Mr. Paul,

 

We are running this setup for 1 month successfully.

Last week there was a slowness in application while picking the records from the database.

From the analysis we could see below errors.

VXML Application Error Logs :

10.76.109.206.1643210665592.503027.OutAOLBeneActSA,01/26/2022 18:25:41.936,A VoiceXML error occurred of type "error.badfetch": request (http://10.76.109.206:7000/CVP/Server) was timed out after 60000 milliseconds.

10.76.109.206.1643210665592.503027.OutAOLBeneActSA,01/26/2022 18:25:41.936,An error has occurred.

 

10.76.109.206.1643210665592.503027.OutAOLBeneActSA,01/26/2022 18:25:41.998,A VoiceXML error occurred of type "error.badfetch.http": Audio Prompt URL null failed

10.76.109.206.1643210665592.503027.OutAOLBeneActSA,01/26/2022 18:25:41.998,An error has occurred.

 

10.76.109.206.1643210620717.502995.OutAOLBeneActSA,01/26/2022 18:25:41.998, The error was: Another thread is currently working on this session.  This means the original thread took too long to complete what it was doing.  To prevent abnormal behaviour the original thread will exit immediately.  The call should not be affected.

com.audium.server.MultipleThreadException: Another thread is currently working on this session.  This means the original thread took too long to complete what it was doing.  To prevent abnormal behaviour the original thread will exit immediately.  The call should not be affected.

at com.audium.server.session.ControllerData.isCurrentThreadOwner(ControllerData.java:5310)

at com.audium.server.voiceElement.DecisionElementBase.service(DecisionElementBase.java:395)

at com.audium.server.controller.Controller.goToDecision(Controller.java:4319)

at com.audium.server.controller.Controller.goToElement(Controller.java:4069)

at com.audium.server.controller.Controller.continueCall(Controller.java:3753)

at com.audium.server.controller.Controller.goToElement(Controller.java:4169)

at com.audium.server.controller.Controller.continueCall(Controller.java:3753)

at com.audium.server.controller.Controller.goToElement(Controller.java:4169)

at com.audium.server.controller.Controller.continueCall(Controller.java:3753)

at com.audium.server.controller.Controller.goToElement(Controller.java:4169)

at com.audium.server.controller.Controller.continueCall(Controller.java:3753)

at com.audium.server.controller.Controller.goToElement(Controller.java:4169)

at com.audium.server.controller.Controller.continueCall(Controller.java:3753)

at com.audium.server.controller.Controller.goToElement(Controller.java:4169)

at com.audium.server.controller.Controller.continueCall(Controller.java:3753)

at com.audium.server.controller.Controller.goToElement(Controller.java:4169)

at com.audium.server.controller.Controller.continueCall(Controller.java:3753)

at com.audium.server.controller.Controller.goToElement(Controller.java:4161)

at com.audium.server.controller.Controller.continueCall(Controller.java:3753)

at com.audium.server.controller.Controller.goToElement(Controller.java:4169)

at com.audium.server.controller.Controller.continueCall(Controller.java:3753)

at com.audium.server.controller.Controller.goToElement(Controller.java:4169)

at com.audium.server.controller.Controller.continueCall(Controller.java:3753)

at com.audium.server.controller.Controller.doPost(Controller.java:1167)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)

at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)

at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522)

at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1095)

at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:672)

at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1502)

at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1458)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

at java.lang.Thread.run(Thread.java:745)

 

And we could see that for the New Call request from VVB, VXML Subsystem is processing this new call after 10 seconds and there by the delay.

 

How can we resolve this ?

 

Muhammed, this looks like an application issue rather than a problem with the outbound mechanism so very hard to say without seeing the application and logs.   Is it using a custom element at point it fails?

We are using custom application and elements.

What will be impact if :

  •  we decrease the fetchtimeout under the VoiceXML Property of application
  • we decrease http client response timeout in VVB

If your problem is with the backend not responding, decreasing timers just means the client side in the VVB will fail sooner if it doesn't get the next document.   It won't prevent the server-side problem.  Unless you know why this is happening, I'd be a bit concerned about the server-side processing that's giving rise to the many iterations through these methods when processing a single HTTP request from the VVB.

 

at com.audium.server.controller.Controller.continueCall(Controller.java:3753)

at com.audium.server.controller.Controller.goToElement(Controller.java:4169)