Hello Alex,
I just briefly looked into it, did not digged into the code much. Kamailio is doing some queuing in TCP async mode (default) e.g. if there is some delay in sending out the data.
One idea - have a look to the core parameters
- tcp_wq_blk_size
- tcp_conn_wq_max
and change them to see if it makes a difference in your particular situation.
Cheers,
Henning
Am 08.01.20 um 00:39 schrieb Alex Balashov:
Yes, I understand the formal properties of TCP and that anything is possible. Thank you for explaining.
What I am asking is whether Kamailio takes pains to ensure--I suppose, if one must be labouriously precise, to maximise the probability--that multiple SIP messages are packaged into separate packets. To the extent it can do so.
On Tue, Jan 07, 2020 at 05:50:18PM -0500, Greg Troxel wrote:
Alex Balashov abalashov@evaristesys.com writes:
On Tue, Jan 07, 2020 at 03:29:13PM -0500, Greg Troxel wrote:
there is no real meaning to the end applications to what bytes of user payload are in which TCP segments within packets.
No, not to the application. But perhaps to third-party packet analysis systems which reconstruct SIP state from what they see on the wire. :-)
They need to reassemble segments and cope anyway. There's a long history of evading firewalls by creative fragmentation.