Here is the beta version 1.1. It will require that you build a new version of wildfire from the subversion trunk. It also requires that you are running Asterisk 1.2 or newer.
There have been many improvements:
Fixed MANY presence issues!!!
Taking advantage of new events from asterisk 1.2 (ie the Dial event).
Taking advantage of new features of the asterisk-java api.
Better upgrade framework, based off the new upgrade framework in the upcoming wildfire release.
I should have clarified to say that the nightly builds or latest SVN code are required since this version of Asterisk-IM relies on Wildfire 2.6. We’'ll also be releasing a new version of Spark that has Asterisk-IM improvements:
Tried to run wildfire_2006-03-25.tar.gz along with the Asterisk-IM 1.1 Beta. I still have users that get stuck “on the phone” after receiving queue calls and dialing agentcallbacklogin.
Thanks for the bug report. I’‘m assuming that events are getting generated in ways that we wouldn’'t expect. Are the users still stuck on “on the phone” after a few minutes have passed?
Can you provide any more detail about how we can reproduce this? I don’‘t think we’'ve tried out queue calls yet.
Here’‘s an urgent request to somehow make this available to a poor Windows user who can’'t build a nightly.
Would it be possible for someone to build a version of Wildfire for windows that will work with this beta version 1.1 of the plugin? I’'d really like to get some of these issues resolved.
there are source builds and normal builds, there’'s no need to build one. If you need an installer instead of a zip file then please wait for Wifi 2.6, it should be released the 6th April.
restarting asterisk while the wildfire server is still running causes an endless loop of failed connection attempts. so far this is only corrected by restarting wildfire, (reloading the plugin might do it too.).
There is a bug in the asterisk-im module that causes dial to fail if you don’'t specify dial variables. Quick fix is to just add a junk variable to the config (A=B), or you can apply the simple source code patch that I posted in the thread and build your own jar.
I haven’‘t seen any responses from the developer about the patch, so use at your own risk It’'s been working fine for me, though.