[Serdev] TCP problems

[Katty Xiong]

Hi, 

I am using SER (Ottendorf) and SIPp for some
performance study and get several errors when using
TCP protocol. From the packet trace, I notice when TCP
publicize zero window at SIPp or SER side, SIP message
will get truncated or several partial or whole SIP
message get combined in one TCP packet, which leads to
error. I haven’t checked the code yet, but if somebody
already knows this off the head, please clarify me of
the following questions.
1) When SER receives a truncated SIP message, how does
it handle the partial message? 
2) When SER receives a packet that has one partial SIP
message combined with another partial SIP message, how
does it handle the packet?
3) When SER receives several SIP messages in one TCP
packet, how does it handle the packet?
4) Does SER care how TCP send one SIP message (in
several TCP packets, combined with other SIP
messages)?

I joined the alias recently, so if the alias already
had discussions on TCP stream behavior and its effects
on SER implementation, could somebody point the link
to me?

Thanks,
Joy


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com