To drop the dialog, you would just send a CANCEL. You could be able to specify a reason for the failure using the Reason header (RFC3326).
Reason: SIP ;cause=415 ;text="Unsupported Media Type" Sorry for the confusion. Regards, Attila >> -----Original Message----- >> From: Attila Sipos >> Sent: 08 February 2006 13:18 >> To: 'Sweeney, Andrew (Andrew)'; [email protected] >> Subject: RE: [Sip-implementors] How to handle a 18x response with a >> missingheader >> >> >> >> Oh sorry. >> It IS invalid to send a response to a response. >> >> >> >> >> -----Original Message----- >> >> From: Sweeney, Andrew (Andrew) [mailto:[EMAIL PROTECTED] >> >> Sent: 08 February 2006 13:16 >> >> To: Attila Sipos; Sweeney, Andrew (Andrew); >> >> [email protected] >> >> Subject: RE: [Sip-implementors] How to handle a 18x >> response with a >> >> missingheader >> >> >> >> >> >> Thanks, But I thought it was invalid to send a response to a >> >> response. I will go back through the RFC and check again. I >> >> guess I could always send a 487 as well. >> >> >> >> >> >> -----Original Message----- >> >> From: Attila Sipos [mailto:[EMAIL PROTECTED] >> >> Sent: Wednesday, February 08, 2006 4:10 AM >> >> To: Sweeney, Andrew (Andrew); [email protected] >> >> Subject: RE: [Sip-implementors] How to handle a 18x >> response with a >> >> missingheader >> >> >> >> >> >> >> >> This is difficult. No doubt you are asking this >> >> beacuse there is no explicit statement (as far as I >> >> can see) regarding your scenario in RFC3261. >> >> >> >> The RFC does however state that "The Content-Type header >> >> field MUST be present if the body is not empty.". >> >> >> >> I guess there are a variety of approaches: >> >> 1. reject it with 400 Bad Request >> >> 2. reject it with 415 Unsupported Media Type >> >> and say what you can accept with an Accept header >> >> (like what it says in 8.2.3 Content Processing) >> >> 3. assume that it's "application/sdp" and try >> >> to parse it as such. If you fail to parse it, >> >> return with 415 Unsupported Media Type. >> >> >> >> Maybe the 2nd is the most technically correct since >> >> it will at least tell the other people that you don't >> >> understand the one of the Content headers. >> >> >> >> The 3rd option would probably give the most interop >> >> but this is somewhat encouraging others to be a bit sloppy. >> >> >> >> With things like this, it's simply best to tell the >> >> makers of the offending UA that they're not compliant >> >> with one of the basic mandatory requirements of RFC3261. >> >> >> >> Regards, >> >> Attila >> >> >> >> >> >> >> >> >> -----Original Message----- >> >> >> From: [EMAIL PROTECTED] >> >> >> [mailto:[EMAIL PROTECTED] Behalf >> >> >> Of Sweeney, >> >> >> Andrew (Andrew) >> >> >> Sent: 07 February 2006 22:05 >> >> >> To: '[email protected]' >> >> >> Subject: [Sip-implementors] How to handle a 18x response with a >> >> >> missingheader >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> I have received a 183 message with a content length but >> >> >> no content type. What is the correct procedure for rejecting >> >> >> this message or dropping >> >> >> the entire dialog? >> >> >> >> >> >> Thanks >> >> >> _______________________________________________ >> >> >> Sip-implementors mailing list >> >> >> [email protected] >> >> >> >> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> >> >> >> >> >> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
