Hi,
Just a small correction.
Reason header should be of the following syntax:
400 Bad request SIP/2.0
......................
......................
Reason: SIP;cause=400; text= "Missing content-type header field"
Regards,
Arun
On Mon, Oct 13, 2008 at 1:19 AM, Avasarala Ranjit-A20990 <
[EMAIL PROTECTED]> wrote:
> I feel a 400 Bad Request response with Reason phrase as "Missing
> Content-type header field" is appropriate for this scenario
>
> E.g. 400 Bad request SIP/2.0
> ......................
> ......................
> Reason: Missing content-type header field
>
>
>
> Regards
> Ranjit
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Amit2 Sharma
> Sent: Monday, October 13, 2008 1:23 PM
> To: [email protected]
> Subject: Re: [Sip-implementors] Reject Response code for
> reinvitewithmissingcontent type header
>
> Hi,
>
> "400 Missing Content-Type header field" error response is appropriate as
> mandatory header is missing in this PDU:
>
> As per RFC-3261
> 20.15 Content-Type
> The Content-Type header field indicates the media type of the
> message-body sent to the recipient. The "media-type" element is
> defined in [H3.7]. The Content-Type header field MUST be present if
> the body is not empty. If the body is empty, and a Content-Type
> header field is present, it indicates that the body of the specific
> type has zero length (for example, an empty audio file).
>
> Regards,
> Amit Sharma
>
>
> ________________________________________
> From: [EMAIL PROTECTED]
> [EMAIL PROTECTED] On Behalf Of Attila
> Sipos [EMAIL PROTECTED]
> Sent: Monday, October 13, 2008 12:58 PM
> To: Anuradha Gupta; Rohit Aggarwal;
> [email protected]
> Subject: Re: [Sip-implementors] Reject Response code for
> reinvitewithmissingcontent type header
>
> No, then the user would look for the codec mismatch in the SDP.
>
> We need to use a response which helps the user find the problem.
>
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Anuradha Gupta
> Sent: 13 October 2008 08:22
> To: Rohit Aggarwal; [email protected]
> Subject: Re: [Sip-implementors] Reject Response code for reinvite
> withmissingcontent type header
>
> 400 bad request should be sent for syntactical errors, in the received
> PDU there is no syntactical error.
> Can "488 not acceptable here" be sent with warning header?
>
> Regards
>
> Anuradha Gupta
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Rohit Aggarwal
> Sent: Monday, October 13, 2008 12:48 PM
> To: [email protected]
> Subject: Re: [Sip-implementors] Reject Response code for reinvite
> withmissingcontent type header
>
> How about 400 Bad Request with an appropriate reason-phrase like
> "Missing Content-Type header field"?
>
> Regards
> Rohit Aggarwal
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Anuradha Gupta
> Sent: Monday, October 13, 2008 12:45 PM
> To: [email protected]
> Subject: [Sip-implementors] Reject Response code for reinvite with
> missingcontent type header
>
> Hi
>
> If reINVITE is received with SDP body but the content -type header is
> missing then it should be rejected with what response code.
>
> The sample reINVITE is:
>
> INVITE sip:[EMAIL PROTECTED]:3819 SIP/2.0
> To: 3275<sip:[EMAIL PROTECTED] <[EMAIL
> PROTECTED]>>;tag=AricentUA_816059597-27872
> From: 444<sip:[EMAIL PROTECTED] <[EMAIL PROTECTED]>>;tag=abc
> Call-ID: 5486
> CSeq: 3 INVITE
> Via: SIP/2.0/UDP 10.203.153.33:3010;branch=z9hG4bK6293480000-18296
> Allow: INVITE,BYE,CANCEL,ACK,PRACK,OPTIONS
> Contact: <sip:[EMAIL PROTECTED]:3010>
> Session-Expires: 300;refresher=uac
> Min-SE: 300
> Content-Length: 157
> Supported: timer, 100rel
> v=0
> o=EAST 12345 787 IN IP4 10.203.153.33
> s=session
> c=IN IP4 10.203.153.33
> t=0 0
> m=audio 5600 RTP/AVP 8
>
>
>
> Regards
>
>
>
> Anuradha Gupta
>
> Technical Leader
>
>
>
>
> ________________________________
> "DISCLAIMER: This message is proprietary to Aricent and is intended
> solely for the use of the individual to whom it is addressed. It may
> contain privileged or confidential information and should not be
> circulated or used for any purpose other than for what it is intended.
> If you have received this message in error,please notify the originator
> immediately. If you are not the intended recipient, you are notified
> that you are strictly prohibited from using, copying, altering, or
> disclosing the contents of this message. Aricent accepts no
> responsibility for loss or damage arising from the use of the
> information transmitted by this email including damage from virus."
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended
> solely for the use of the individual to whom it is addressed. It may
> contain privileged or confidential information and should not be
> circulated or used for any purpose other than for what it is intended.
> If you have received this message in error,please notify the originator
> immediately. If you are not the intended recipient, you are notified
> that you are strictly prohibited from using, copying, altering, or
> disclosing the contents of this message. Aricent accepts no
> responsibility for loss or damage arising from the use of the
> information transmitted by this email including damage from virus."
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended
> solely for the use of the individual to whom it is addressed. It may
> contain privileged or confidential information and should not be
> circulated or used for any purpose other than for what it is intended.
> If you have received this message in error,please notify the originator
> immediately. If you are not the intended recipient, you are notified
> that you are strictly prohibited from using, copying, altering, or
> disclosing the contents of this message. Aricent accepts no
> responsibility for loss or damage arising from the use of the
> information transmitted by this email including damage from virus."
>
> _______________________________________________
> 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
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended
> solely for the use of the individual to whom it is addressed. It may
> contain privileged or confidential information and should not be
> circulated or used for any purpose other than for what it is intended.
> If you have received this message in error,please notify the originator
> immediately. If you are not the intended recipient, you are notified
> that you are strictly prohibited from using, copying, altering, or
> disclosing the contents of this message. Aricent accepts no
> responsibility for loss or damage arising from the use of the
> information transmitted by this email including damage from virus."
>
> _______________________________________________
> 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
