The main feature that everybody kept asking for, is finally here - that is, the ability to cancel a number from blacklists. We used to offer a number of workarounds that would handle the majority of real-life cases, but by having a separate black-list cancellation action the dialer is decidedly more flexible. As with most things Wombat, a cancellation does not mean a deletion of a record - no information is vert o be lost! - but an update where the reason for cancelling is kept for further analysis.

We made sure that both HTTP notifications and the Asterisk dial-plan receive all relevant attributes for your call - the current WombatID, the name of the list, the main number vs the current number, and the current recall. This will make it easier to integrate Wombat in complex scenarios where data travels between multiple different systems.

When reworking blacklists, we took a deep dive and came out with a complete new section of the User Manual - "Understanding blacklists" - that shows you the interactions between lists, blacklists, multinumbers and API calls, with some real-life examples. We felt that the existing documentation was a bit scattered and there was a need of a general tutorial of such an important feature.

We also created a set of examples that complement the API section of the User Manual, and show a complete example of how campaigns and call lists can be created and edited from scratch, only by using the Configuration APIs. This is available on GitHub at https://github.com/Loway/OpenWombatDialerAddOns - and if you have examples or corrections to share, feel free to send us a PR.

Now that CentOS 7 is recahing its end-of-life, we wanted to make sure that our WombatDialer package is easy to install on CentOS 8/9 and Rocky Linux 8/9 . Additionally, it is expected to work effortlessly on a wide range of distributions that are derived from RHEL.

And if you don’t like RHEL derivatives, and don’t want to run the Docker version, we reworked the Debian installtiion tutorial on the User Manual to make sure it would work flawlessly on a current system.

We made sure that modern versions of both MySQL and MariaDB are fully supported, so you have a choice. And while our automated installs still ship with Java 8, Java 11 is fully supported - it offers marginally better performance for very busy systems, and future-proofs your software investment.