On 05.05.24 11:30, Olle E. Johansson wrote: It is built reusing existing components such as async task groups and sworker, but indeed it could change quite a bit how everything was handled so far for UDP. Still the config execution is down with dedicated processes created for the async task group, the modules should not be impacted. Adding to wiki will follow, the whole affair is still kind of work in progress, because I plan to add support for mixing old style pool-of-processes per socket with the new style of multi-threaded receiver for a group of processes. There are situations when Kamailio has to be configured to listen on many IPs or ports and on many of them the volume of traffic is rather low. There is the option to sent the number of workers per socket, but even having a single process per socket can become a hassle (e.g., too many database connections), say when you have to listen on 10s/100s of UDP sockets. TCP/TLS has a single pool of processes, so it is not impacted by number of sockets as it was UDP, but a similar multi-threaded approach could be considered as a configurable option as well. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com