Subject: RE: [Sip] 200 for INFO

From: Jeff Van Dyke <[email-masked]>
Date: Thu, 21 Feb 2002 15:56:46 -0500

Aaron,
    The RFC specifically mentions that it only addresses the behaviors for INFO requests that do not contain a message body.  Message bodies are allowed, just not covered by the RFC.  So after reviewing this passage several times, we've interpreted this to mean that a UAS must send a 200 OK response to an INFO request that does not contain a message body.  The 200 OK is required even if the UAS does not understand any additional headers that may have been sent.  The 200 OK simply acknowledges that the INFO was received successfully.
    If the INFO request does contain a message body, additional semantics may apply and these are not addressed by the RFC.  In this case the UAS may send a response containing a message body or not, depending on the situation.
Regards,
    Jeff
  -----Original Message-----
  From: [email-masked] [mailto:[email-masked]]On Behalf Of Aaron Lo
  Sent: Friday, December 21, 2001 4:38 AM
  To: [email-masked]'
  Subject: [Sip] 200 for INFO

  Hi all,

  In RFC2976 SIP INFO Method sec 2.2 page 3, it reads 

   A 200 OK response MUST be sent by a UAS for an INFO request with
   no message body if the INFO request was successfully received for
   an existing call.  Beyond that, no additional operations are
   required.

  Does it mean that the 200 OK should not contain a message body, or does it mean that a 200 OK should be sent even if the INFO does not contain a message body? Can someone clarify? Thanks.

  Aaron