[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    RE: [Sip-implementors] Query on 415 response
From:       "Jerry Ipe Thomas" <jerry () dlink ! co ! in>
Date:       2005-02-28 4:46:23
Message-ID: !~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAtA9TMQwa6U66W2rFILQVGcKAAAAQAAAA88U4KZb7k0afmdXPu8IVbwEAAAAA () dlink ! co ! in
[Download RAW message or body]

Hi Rayees,
If you are a B2BUA or if you need to be bothered about the SIP body,
then IMHO,
you should return one of the following depending on what role you play.

21.4.26 488 Not Acceptable Here

   The response has the same meaning as 606 (Not Acceptable), but only
   applies to the specific resource addressed by the Request-URI and the
   request may succeed elsewhere.

   A message body containing a description of media capabilities MAY be
   present in the response, which is formatted according to the Accept
   header field in the INVITE (or application/sdp if not present), the
   same as a message body in a 200 (OK) response to an OPTIONS request.

21.6.4 606 Not Acceptable

   The user's agent was contacted successfully but some aspects of the
   session description such as the requested media, bandwidth, or
   addressing style were not acceptable.

   A 606 (Not Acceptable) response means that the user wishes to
   communicate, but cannot adequately support the session described.
   The 606 (Not Acceptable) response MAY contain a list of reasons in a
   Warning header field describing why the session described cannot be
   supported.  Warning reason codes are listed in Section 20.43.

   A message body containing a description of media capabilities MAY be
   present in the response, which is formatted according to the Accept
   header field in the INVITE (or application/sdp if not present), the
   same as a message body in a 200 (OK) response to an OPTIONS request.

   It is hoped that negotiation will not frequently be needed, and when
   a new user is being invited to join an already existing conference,
   negotiation may not be possible.  It is up to the invitation
   initiator to decide whether or not to act on a 606 (Not Acceptable)
   response.

   This status response is returned only if the client knows that no
   other end point will answer the request.

Further, in RFC 3261, 415 is defined as

21.4.13 415 Unsupported Media Type

   The server is refusing to service the request because the message
   body of the request is in a format not supported by the server for
   the requested method.  The server MUST return a list of acceptable
   formats using the Accept, Accept-Encoding, or Accept-Language header
   field, depending on the specific problem with the content.  UAC
   processing of this response is described in Section 8.1.3.5.

Regards,
Jerry


-----Original Message-----
From: Rayees Khan [mailto:rakhanhss@yahoo.com] 
Sent: Thursday, February 24, 2005 4:04 PM
To: sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] Query on 415 response



Hi all,


I have a query on 415 response. 
Suppose a SIP server receives an INVITE request with
SDP. It realizes that it cannot support some of the
attributes that are mentioned in the SDP. 

What header would it use to inform the Client about
the same in 415 response?


regards
Rayees


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



[prev in list] [next in list] [prev in thread] [next in thread]