[Serdev] TCP problems
Katty Xiong
cyyxiong at yahoo.com
Tue Jan 9 20:44:56 UTC 2007
Andrei,
Thanks for your explanation. Could you also explain
how SER decides whether a SIP message is partial or
whole? Does it need a special character to seperate
two SIP messages?
I couldn't quite understand the code for handling tcp
message. Is the following lines in the function
tcp_read_req() used to decide if a SIP message is
complete?
if ((con->state==S_CONN_EOF) && (req->complete==0)) {
...
}
thanks,
Joy
--- Andrei Pelinescu-Onciul <andrei at iptel.org> wrote:
> On Jan 09, 2007 at 10:33, Katty Xiong
> <cyyxiong at yahoo.com> wrote:
> > 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 havent 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?
>
> It waits for the rest of the message (on tcp).
>
> > 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)?
>
>
> No, it doesn't, each message is handled separately.
> In fact on tcp ser
> just reads from the tcp stream until it gets a whole
> message, then
> processes it and then repeats the entire process.
>
>
> Andrei
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
More information about the Serdev
mailing list