Hello Daniel,
the "6.0" sounds good to me, its indeed a major change for the main network
protocol in the server.
It was discussed also some time ago at the developer meeting(s) that this would be
probably a good reason for a larger version increment.
Nice extension to the core, thank you.
Henning
-----Original Message-----
From: Daniel-Constantin Mierla via sr-dev <sr-dev(a)lists.kamailio.org>
Sent: Mittwoch, 8. Mai 2024 14:03
To: Kamailio (SER) - Devel Mailing List <sr-dev(a)lists.kamailio.org>
Cc: Daniel-Constantin Mierla <miconda(a)gmail.com>
Subject: [sr-dev] Proposing 6.0.x for next stable release series
Hello,
I am proposing to switch the development version to target 6.0.x as next
major series. I have pushed a new mode for receiving UDP traffic via a multi-
threaded process, useful when having to deal with a rather large set of UDP
sockets. While it is built reusing some existing components (async workers
group and sworker design), it changes substantially how the core can deal with
the sip traffic. Similar approach might be added for TCP (TLS), but right now
this transport is already using a single pool of works for all sockets, so it
doesn't faces the same issues as with UDP for large number of sockets.
The old way of handling UDP traffic is not removed, it is still the default, the
new one needs testing, of course.
Furthermore, the socket global parameter (which is an alternative to
listen) can now take a port range to the bind field, simplifying the config when
Kamailio has to listen on large number on consecutive ports.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@
asipto.com)
twitter.com/miconda --
linkedin.com/in/miconda Kamailio Consultancy,
Training and Development Services --
asipto.com
_______________________________________________
Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-
dev-leave(a)lists.kamailio.org