Problems running wombat dialer 0.8.0

[eduardosolano85@gmail.com]

Helloo


Im having two issues:

1 - Im having this error to enter to wombat:

Callback failure:com.google.gwt.user.client.rpc.StatusCodeException: 500 Internal Server Error
HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: NLIC/0
   it.loway.tpf.transaction.servlets.common.ServletEnvironment.init(ServletEnvironment.java:103)
   ch.loway.tpf.gwt.srv.servlets.LowayGwtController.init(LowayGwtController.java:37)
   javax.servlet.GenericServlet.init(GenericServlet.java:212)
   com.google.gwt.user.server.rpc.RemoteServiceServlet.init(RemoteServiceServlet.java:166)
   org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:291)
   org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
   org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
   org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
   java.lang.Thread.run(Thread.java:662)
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.33 logs.




2 - Im trying to make outbound calls, so i already have an outbound route with XXXXXXX that uses SIP/FXO trunk. how do i configure the trunk in wombat??


please help me with this urgent

[QueueMetrics]

1. This error happens if MySQL is down when Wombat starts. Try restarting MySQL first and then manually restarting Wombat.

2. What we usually suggest is to create a context - say we call  it your-context - that will do the dialing, so that you address channels as Local/${num}@your-context/n

[eduardosolano85@gmail.com]

Hello

Thanks for your reply, but this issue still happening, when i restart my machine is the same thing.

What can i check?


About the dialing out is working now!

regards

[QueueMetrics]

It seems the startup order ow Wombat is incorrect. As a tweak, I suggest restarting WombatDialer in rc.local, so that we are sure that whatever happens before, Wombat is started last.