Hi, To elaborate further, 415 is not related to just the Content-Type header, RFC 3261 clearly mentions that:
"If there are any bodies whose type (indicated by the Content-Type), language (indicated by the Content-Language) or encoding (indicated by the Content-Encoding) are not understood, and that body part is not optional (as indicated by the Content-Disposition header field), the UAS MUST reject the request with a 415(Unsupported Media Type) response." Similarly, for the 488 response "means that the user wishes to communicate, but cannot adequately support the session described." It may not necessarily because the user *does not understand/ support* but also due to the fact that the user is currently unable to proceed with this call based on the offered parameters. A typical example is that many fax machines do not allow simultaneous SIP-T.38 fax calls so the 2nd INVITE is typically rejected with a 488. Regards, Gaurav -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Attila Sipos Sent: Friday, February 10, 2006 3:51 PM To: Neeraj Chowdhury; [email protected] Subject: Re: [Sip-implementors] Query about 415 and 488 responses // >> 1) 415 Unsupported Media Type This means that it does not know about the Content-Type in the incoming request. >> 2) 488 Not Acceptable Here Used when there is nothing in the session description which this UA can understand or support. e.g. they offer you the g723 codec only but your UA can't support g723 then you use 488 as the response. Regards, Attila Attila Sipos http://www.vegastream.com >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] Behalf Of Neeraj >> Chowdhury >> Sent: 10 February 2006 09:51 >> To: [email protected] >> Subject: [Sip-implementors] Query about 415 and 488 responses // >> >> >> Please give me the details about when the UAS generates the following >> responses and what is the difference between both of them : >> >> 1) 415 Unsupported Media Type >> 2) 488 Not Acceptable Here >> >> With thanks >> Neeraj Chowdhury >> _______________________________________________ >> 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 _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
