From: Maxim Sobolev <[EMAIL PROTECTED]>
Yes, this is my best pick at the moment, however, I am little bit unsure
as SDP syntax is not part of SIP RFC.
Since there doesn't appear to be any more specific response, 400
appears to be the only choice.
Dale
_
Neelakantan Balasubramanian wrote:
> Looking at RFC 3261, 400 Bad request is a better response. A Reason/Warning
> header can be added in the response.
>
> 21.4.1 400 Bad Request
>The request could not be understood due to malformed syntax. The
>Reason-Phrase SHOULD identify the syntax
plementors] Proper negative final status code for
malformed SDP
Hello,
i would suggest use of 403 Forbidden.
415 is usually sent if UAS doesn't like media-type received in Content-type
header
488 is sent for a syntactically correct, but semantically wrong SDP offer.
Say a mid-call codec mo
Harsha. R wrote:
> Hello,
> i would suggest use of 403 Forbidden.
>
> 415 is usually sent if UAS doesn't like media-type received in
> Content-type header
> 488 is sent for a syntactically correct, but semantically wrong SDP
> offer. Say a mid-call codec modification that is not acceptable.
Hmm
Hello,
i would suggest use of 403 Forbidden.
415 is usually sent if UAS doesn't like media-type received in Content-type
header
488 is sent for a syntactically correct, but semantically wrong SDP offer.
Say a mid-call codec modification that is not acceptable.
Regards
Harsha
2008/12/6 Maxim Sob
Hi,
I wonder what proper status code UAS should generate for the INVITE that
contains clearly malformed SDP. I see several candidates in 3261:
- 400 Bad Request
- 415 Unsupported Media Type
- 488 Not Acceptable Here
- 606 Not Acceptable
What do people think?
Thanks!
Regards,
--
Maksym Soboly
