For message-oriented transports (such as UDP), one
message MUST not contain more one SIP messages. If
Content-length header is present then message body is
assumed to contain that many bytes. Additional bytes
beyond that MUST be discarded. If Content-length
header is missing then message body is assumed to the
end of message body.
If somebody puts multiple SIP messages over
message-oriented transports (such as UDP) with
Content-length header (in first SIP message) then only
first SIP message shall be considered and rest shall
be discarded. If Content-length is missing then
depending on the character appears between two SIP
messages and depending on the Content-type, either
rest of the SIP message shall be considred as the body
of first message or it shall lead to syntax error.
For stream-oriented transports (such as TCP), segment
may not align with SIP packet. For example, one TCP
segment may contain multiple SIP packets. One TCP
segment may contain (last)half of a SIP message and
(first)half of other SIP message.
One more complexity: The socket read/recv call is not
again aligned with TCP segment. One read/recv call can
pass bytes collected from mutiple TCP segments.
>Hi,
>
>Is it possible for a single network message to carry
>multiple SIP
>requests or responses ?
>
>With regards
>Vivek Gupta
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
