<br><br><div class="gmail_quote">On Tue, Feb 14, 2012 at 10:40 AM, Sergey Okhapkin <span dir="ltr"><<a href="mailto:sos@sokhapkin.dyndns.org">sos@sokhapkin.dyndns.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But RFC 3388 says (in 1. Introduction):<br>
<br>
An SDP session description typically contains one or more media lines<br>
- they are commonly known as "m" lines. When a session description<br>
contains more than one "m" line, SDP does not provide any means to<br>
express a particular relationship between two or more of them. When<br>
an application receives an SDP session description with more than one<br>
"m" line, it is up to the application what to do with them. SDP does<br>
not carry any information about grouping media streams.<br></blockquote><div><br>If it's "up to the application what to do with them..." then the question is this: what do you want the application to do? Also, what is the "application" in this context? Anthony already showed that sending multiple m= lines is not only legal but is required if you need to have multiple ptimes. He even added a cheater param that lets you explicitly violate the RFC for the sake of interop with broken devices. It seems like FreeSWITCH not only "does the right thing" but it has a button you can press to "do the wrong thing for the sake of interop."<br>
<br>I suppose I'm not seeing what the problem is. Could you elaborate?<br><br>-MC<br></div></div>