El Monday 31 March 2008 22:09:19 Iñaki Baz Castillo escribió:
> Hi, I'm trying to get the steps the Transport Layer must perform when
> receiving a request, but it doesn't seem to appear very "clear" in RFC 3261
> (at last I cannot find them).
>
> I've compiled the steps I've found and would like to know if they are
> correct in the order they appear, or if someone is missing or no needed.
>
> Steps:
>
> 1) If a mandatory header doesn't exist discard silently the message.
> Mandatory headers are To, From, CSeq, Call-ID, Max-Forwards, Via.
>
> 2) If TCP and there is not "Content-Length" reply:
>   "400 Content-Length header missing".  <-- other error more appropiate?
>
> 3) If body is truncated (less that indicated value in "Content-Length")
> reply: "400 Wrong content length"  <--- ???
>
> 4) Add Via "received" parameter if neccesary.
>
> 5) Try to match an existing server transaction (17.2.3). If a matching
> server transaction is found, the request is passed to that transaction for
> processing. If no match is found, the request is passed to the core, which
> may decide to construct a new server transaction for that request.


No help with this?  :(

-- 
Iñaki Baz Castillo
[EMAIL PROTECTED]

_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to