yes. Thats will be great because in some system design it must use same port that listening for sendinf like in UDP for example for transcoding SIP over WebSocket to SIP over TCP and masking registration behind thanscoder.

Like User sends registration, kamailio just Transcoding this request to TCP and then resend this registration packet to Asterisk.
With this example asteisk must originate all PACKETS to TCP port of kamailio but it tries to send it to port from wich request arrived and if use TCP it will not equal port that kamailio listening for TCP.

2016-09-08 13:17 GMT+03:00 Daniel Tryba <d.tryba@pocos.nl>:

On Thu, Sep 08, 2016 at 11:16:29AM +0200, Federico Cabiddu wrote:
> about this subject: linux kernel starting from 3.9 introduced SO_REUSEPORT
> which allows reusing TCP sockets.
> It could be interesting supporting this in Kamailio. I worked on a patch
> for this, I can open a PR and start a discussion if you think it's worth.

Interesting, I read about SO_REUSEPORT a couple of weeks ago but it
didn't dawn on me that it lets you have multiple sender sockets (by just
not accept()-ing). IMHO it is usefull for setups that use IP based
authentication with TCP instead of UDP (probably something the OP want
to do).

_______________________________________________
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