This version fixes a major issue with session handling that could theoretically allow an user to bypass security checks on the configuration interface.

The CVE for this will be published soon.

From the Reports page in WombatDialer, under the Call Outcomes panel, it is possible to see a breakdown of those call outcomes grouped by the number of recall it happened to. This way you can see, e.g., how many calls were completed the first time they were placed, how many on the first recall, how many on the second, and so on.

This feature, sometimes known as "Called Counts", can be very effective in deciding how "deep" you recall policy must be set to optimally reach your targets.

Also, on the Realtime page, the panel "Active Lists on Run" was sometimes hard to use because buttons would appear on the very bottom of the panel. Now that’s fixed.

We added a new section to the User Manual called "Automatic Lists" because we felt that a number of customers would not get what AUTO lists are for by reading the current documentation. And - worse - they would end up using them incorrectly. Automatic lists are very handy, but their expected behavior can sometimes be misleading.

If you use AUTO lists, make sure you check it out at https://docs.loway.ch/WombatDialer/020_WD_Concepts.html#AUTOLISTS

It is not possible anymore to add numbers to a campaign that has no active run - this makes no sense. Previously these numbers would be added to the AUTO list for the campaign, but not actually dialled. Now this triggers an error.

The CPS parameter for a trunk could not be set - it is not meant to, as it is a derived parameter based on rlMaxMsg and rlMsgEvery settings, but you had to remove it from the JSON description of a trunk to change it. Now it is fixed.

Now WombatDialer supports MySQL 8.0.36 out of the box when installing with yum; previously you had to change its password policy to allow WD to use it. MariaDB is always supported and is in general easier to work with - but you choose.

To access the WombatDialer web-app, you now have a fixed symlink /usr/local/queuemetrics/wd-current that will always point to the correct one.

The DbTest transaction used on first installs and upgrades was made a bit easier on the eye and external links were fixed.