What is Erwin the Wombat doing sitting on a large cup of coffee? well, he’s been working quite a bit lately.
We have just released version 0.7.5, that is meant mostly as a bug fix release but also adds some architectural improvements.
- First, we fixed a number of issues to improve the accuracy of call and queue tracking. The bottom line is that the dialer is more efficient when tracking queues and will try to keep them fully saturated at all times. We also fixed a number of error conditions that were reported by our partners.
- Secondarily, we changed the log storage model. This means that logs will no longer make entities impossible to delete. Logs will also be scanned more efficiently for large systems (over 1M records).
- The third important item is that the dialer will now start up immediately as the web application is loaded, unless you just performed an update. This means that you will not have to log in to restart the dialer after a system reboot.
- The fourth important item is that from the Reports page you can now export to CSV the details of all the calls that were placed in a set of runs. This was a popular demand.
- Last but not least, the dialer view is way more clear when tracking queues - you can now see who is logged on, how many calls are being placed, and how many channels are used by that queue.
The downside is that the upgrade may take a while to run - as logs have to be converted, the updater processes about 30,000 calls per minute - so if you have a log database of one million calls, the upgrade may take about 45 minutes to complete. We suggest making a complete backup of the database beforehand, just in case.
What remains to be done for 0.8? a public regression test. We are working on a suite of tests that will let you run a stress test of WombatDialer on your own systems, to assess system capacity and gettiong familiar with the different dialing modes Wombat offers. This will be a simplified and cleaned-up version of the one we use internally to test the capacities of a release. We are also working on a tutorial of how to run a blended inbound/outbound call-center using WombatDialer and QueueMetrics.
We welcome your feedback about what you would like to see in new releases - we have a public suggestion jar at http://wombatdialer.userecho.com/