________________________________________ From: [email protected] [[email protected]] On Behalf Of [email protected] [[email protected]]
I’m working on technical SIP requirements for end-points devices and I can’t find an answer for one question. How UAS should behave receiving INVITE that contains SDP without one of following items: v, o, s ,t. For example having received IVITE without origin: v=0 s=TT c=IN IP4 10.15.21.1 t=0 0 _______________________________________________ Although it does not seem important to SIP usage that these lines be present in the SDP, in practice, they always are, so there is no improvement in robustness provided by not enforcing the rules regarding mandatory lines in SDP. Unfortunately, as far as I can tell, RFC 3261 does not provide an error that exactly covers the situation "the INVITE body has a media type (application/sdp) that I understand, but the body is malformed". It seems to me that the closest approximation is 488 Not Acceptable Here. That response should have a Warning header, but there is no warn-code that exactly describes the situation. So you would have to use warn-code 399, with a text field like "Malformed SDP -- mandatory v= line missing." Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
