If you refer that the local port of a tcp connection initiated by kamailio is
sort of random number, not the port on which kamailio listens, then this is how
the TCP stack works. Homer likely takes the internal socket used to receive the
packet or the one specific for the interface to send out.
In tcp, it is not possible (or better said, rather impossible) to force local
socket for a tcp connection, you can search more on google about, for example a
discussion at:
*
https://superuser.com/questions/1118735/how-are-source-ports-determined-and-how-can-i-force-it-to-use-a-specific-port
I am going to close this issue -- if you want to discuss more on this topic,
the right place is [email protected] mailing list.
If I misunderstood what you reported and you still think it is an issue of
kamailio, reopen and try to describe from another angle, like what it is
happening for a specific case and what you expected to happen.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1532#issuecomment-398724607
_______________________________________________
Kamailio (SER) - Development Mailing List
[email protected]
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
