Setting up Wildfire and Asterisk-IM

Hi guys,

We’'ve just setup an asterisk server and are toying with Jabber.

I’'ve setup up Wildfire and am trying it out, I just instaleld the Asterisk-IM plugin. The plugin shows up in the Wildfire Wbe Admin and I was able to setup the manager login. I can verify that Asterisk-IM connects to the asterisk box and logs in succesfully (i see a bunch of debug message on the Wildfire console and the login in the Asterisk CLI).

My problem is that I cannot specify the Phone mappings, when I click on phone mappings I get a page with only the Wildfire menu buttons. The phone mapping options do not show up on the screen. If it is any help the entire HTML page is complete (i.e. ends with </html>) but the “content” is missing.

Any help would be greatly appreciated.

I found this log message in ./log/error.log:


2006.09.18 12:40:48

[

|org.jivesoftware.wildfire.container.PluginServlet.service%28PluginServlet.java: 104%29]

javax.servlet.ServletException: org.jivesoftware.database.DbConnectionManager.closeConnection(Ljava/sql/ResultS et;Ljava/sql/PreparedStatement;Ljava/sql/Connection;)V

at org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl .java:825)

at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.j ava:758)

at org.jivesoftware.wildfire.plugin.phone.phone_002dusers_jsp._jspService(phone_00 2dusers_jsp.java:619)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)

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

at org.jivesoftware.wildfire.container.PluginServlet.handleJSP(PluginServlet.java: 234)

at org.jivesoftware.wildfire.container.PluginServlet.service(PluginServlet.java:92 )

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

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:830)

at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:69)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:11 8)

at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.util.LocaleFilter.doFilter(LocaleFilter.java:65)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingF ilter.java:41)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.admin.PluginFilter.doFilter(PluginFilter.java:69)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:98)

at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:821)

at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler. java:471)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)

at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)

at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.ja va:633)

at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)

at org.mortbay.http.HttpServer.service(HttpServer.java:909)

at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)

at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)

at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)

at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)

at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)

at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

Well, I checked out the latest version in SVN and built asterisk-im.jar. I was having problems with the interface trying to add my server records and stuff. I noticed that it was trying to run the database update scrpt for asterisk-im each time I was starting wildfire.

After looking at asterisk-im_mysql.sql it seemed that the new table structure was not being created, so I dropped the old tables and executed the SQL and got the server side interface working.

I’‘m now having trouble with the client, I’‘m not seeing notifications come up when I get incoming calls and am not able to originate calls from Spark. From what i’'ve read here it seems that Spark can figure out by itself that asterisk-im is installed and gives you asterisk realted functionality automatically, is this correct?

and… i fixed the second issue as well. It was the old FQDN / ip mismatch problem…

Message was edited by: statik213

Depending upon which version of Wildfire you are using, I think only the latest nightly builds currently fix this, but the beta1 and I don’'t know how far back had an issue where plugins were not being updated correctly. There was quite a hefty change on the database side of things so its imperitive that these upgrade scripts are run for the smooth functioning of what is currently in SVN and the current beta 1.2.0 plugin.

Thanks,

Alex

Well, I checked out http://svn.jivesoftware.org/svn/repos/asterisk-im/trunk and built that.

The supplied MySQL script would fail for table “upgrades” as it is just a plain old CREATE table. You cad add a DROP TABLE IF EXISTS and then create the new tables (losing all data of course).

Building latest version from SVN fixed the problem.