"There be dragons" ... in the latest days there was a rush of annoying attacks... no one of these I have seen so far has even the smallest chance to be successful, but they are annoying and use resources you can use better for your clients. For this reason I have made a few changes to GeoIP and Fail2ban. Now GeoIP is run on top of all iptables chains and it is not applied only to voip ports, but ALL ports, ALL protocols (udp, tcp and icmp), including port 22, so you need to be careful to not lock you out. As a "security" measure, my server IP is always in the "Always Allowed" list. The second big change is in Fail2ban... I have fought my laziness and I have coded the dynamic add ip/del ip in Fail2ban, without the need to reloading Fail2ban (reloading is annoying and uses a lots of resources).</dd><dd>Fixed an index creation problem on ph_phones</dd><dd>Two clients have reported a e really weird issue with mysql when running on 3.56.x ... mysql takes a lots of CPU and time processing a simple query used for logging activity on de_destinations table: <tt>select de_type_id_src,de_type_src,group_concat(concat(de_type_dst,'-',de_type_id_dst) order by de_ord desc) as destination from de_destinations where de_te_id='143' and de_type_id_src='345' and de_type_src in ('DID','DID-UNCONDITIONAL','DID-SMS') group by de_type_id_src,de_type_src order by de_type_src,de_ord desc</tt> This query requires the creation of a temp table and mysql makes it on the disk... and the weird thing is this query is made few times (probably because the user refresh the page). I have rewritten the query, so no temp table is needed.