You've answered to yourself, TCP connections are session-based so the client always uses an "ephemeral" port which is chosen dynamicaly by the TCP stack of the OS. So depending on what you actually need to achieve, it might be an option to set the port information in the scenario manually to 5060 (in Via etc.) and use netfilter (iptables) to src-nat the sent packets' source address and port to those you want (10.249.130.10:
5060)

But bear in mind that it will be possible to establish only one such TCP session per remote socket address, as when a TCP session ends, there is a guard time during which any packet coming from the same socket address at client side is ignored by the server.

Pavel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to