I think we&#39;ve corrected this in master already. <span></span><br><br>On Sunday, July 31, 2016, Richard Chan &lt;<a href="mailto:richard@treeboxsolutions.com">richard@treeboxsolutions.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi list,</div><div><br></div><div>FreeSWITCH 1.6.9 and the default configurations:</div><div><br></div><div>FreeSWITHCH is using rtcp-mux on the B-leg without signalling in SDP (i.e. no rtcp-mux attribute).</div><div><br></div><div>If I change rtcp_audio_interval_msec to passthru or say 2000 then there is explicit rtcp-mux in the INVITE SDP.</div><div><br></div><div>The UAC I&#39;m using, sends a few packets to RTP+1, FreeSWITCH sends RTCP with source port the same as RTP, and the UAC auto-adjusts after 10 or so packets. This UAC always includes an a=rtcp line even if the RTCP port is RTP+1.</div><div><br></div><div>Is this a &quot;bug&quot;? I would expect FreeSWITCH to signal rtcp-mux on the B-leg.</div><div><br></div><div>(On the A-leg, FreeSWITCH doesn&#39;t use rtcp-mux and includes an explicit rtcp port in SDP).</div><div><br></div><div><br></div><div><br></div><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><font color="#000000" face="Droid Sans"><span style="font-size:15px">Richard Chan</span></font></div><div dir="ltr"><br></div></div></div></div>
</div>
</blockquote>