Hi Manju,
For case 1, UAS should respond with 400 Bad request and for other two cases, if
media type is not supported in m-line, then UAS should respond 415 and for
other reasons in m-line, it can respond 488/606 response.
Excerpt from RFC 3261:-
If a 415 (Unsupported Media Type) response is received (Section
21.4.13), the request contained media types not supported by the UAS.
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.
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.
Excerpt from RFC 4566:-
5.14. Media Descriptions ("m=")
<media> is the media type. Currently defined media are "audio",
"video", "text", "application", and "message", although this list
may be extended in the future (see Section 8).
Hope it clarifies.
regards,
Aman
Aricent
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of manju nath
Sent: Tuesday, March 27, 2012 5:08 PM
To: [email protected]
Subject: [Sip-implementors] what should be the response of UAS for wronge SDP
Hi
what should be the response of UAS if it receives an INVITE with SDP
conatins
1) wronge Connection field [c=] i.e *Invalid n/w typw* or *invalid
address type* or *invalid IP* (any one of the parameter is wronge)
Is it correct if UAS responds with *400 Bad Request*??? if not what
should be the resposne
2)wronge/unknown Media field [m=] i.e *Invalid Media protocol*
is
3) wronge/unknown Media field [m=] i.e *Invalid Media format* for media
mentioned (ex: for audio received format is 256 or some number (invalid))
Is it correct if UAS responds with *488 ?? if not what should be the *
response
--
*Thanks & Regards,*
*Manjunath.jootoor.*
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
