[SIPForum-discussion] TCP FIN flag is set in a TCP containing multiple messages.

[Rongas, Alexandros]

Hello all,

Just a question in case someone can help. In some tests with sip/tcp, I
phase the following problem. Inside a TCP stream, the FIN flag is set to
true, because I close the socket of a call due to timeout. Also inside
the same tcp stream, 3 sip messages are contained for 3 different calls
(yes I know... it is a really unlikely case but unfortunately for me it
is reproducible...). 

A SIP proxy, gets confused and ignores the messages contained in this
tcp stream and mentions that this is because of the FIN flag. However,
my application cannot cope with this, because tcp FIN due to timeout is
set for different call than the other three messages (prack, ack for 200
OK and BYE) and the network card puts the 3 application layer messages
along with tcp FIN flag in one tcp message (tcp window is 49640). I hope
I have managed to put down on paper my problem correctly; this is my
first posting on the forum....
Does anyone have any information/ideas on how I should proceed? Is there
a way to reduce the tcp window? I am really on the dark on all these!

Thanx!!!!

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20070529/85053497/attachment-0002.html>