Daniel-Constantin Mierla writes:
> One idea was to add udp_children and sctp_children parameters (or just
> one like socket_children) that will count as they are set and will
> affect next listen, like:
>
> socket_children=2
> listen=127.0.0.1
> socket_children=8
> listen = ...
>
> The other idea was to define a socket block, like:
>
> socket {
> listen=...
> children=2
> # -- other attributes per socket when needed
> }
>
> First option would be easier, since does not introduce much new stuff,
> the second is more structured.
either would be ok if it is too difficult to dispatch udp requests to
common pool of processes.
-- juha
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
