Maybe I used a wrong word. With "malformed" I meant a Header with something wrong (in my case a reliable 183 with a RSeq out of the allowed range). RFC3261 says a lot about how the UAS should treat "malformed" headers (for instance, ignoring them if not strictly needed), but I didn't find anything about the UAC when receiving provisional responses. In the case I'm facing, having a right RSeq is essential for sending back a PRACK, so it is not clear to me if the UAC should CANCEL the call (if the early dialog exists) or ignore the response at all.
Hope this clarify the question. Andrea -----Original Message----- From: Ivar [mailto:[EMAIL PROTECTED] Sent: giovedì 24 maggio 2007 15.25 To: Andrea Rizzi Cc: sip-implementors@cs.columbia.edu Subject: Re: [Sip-implementors] UAC behavior when receiving malformed provisional responses How you pass malformed response to transaction ? ???? SIP message parser fails to parse header or at least validate them, that response never should passed to transaction. It up to you what you to with it, log it, inform user if UA, ... . Andrea Rizzi wrote: > RFC3261 seems to me to not address the UAC behavior when receiving a non-100 > provisional response containing a malformed header. > > > > Has anybody any suggestion about? > > > > Andrea > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
