Thanks - tried master and saw that it is fixed. Regards Richard On Mon, Aug 1, 2016 at 11:48 AM, Michael Jerris <mike@jerris.com> wrote:
I think we've corrected this in master already.
On Sunday, July 31, 2016, Richard Chan <richard@treeboxsolutions.com> wrote:
Hi list,
FreeSWITCH 1.6.9 and the default configurations:
FreeSWITHCH is using rtcp-mux on the B-leg without signalling in SDP (i.e. no rtcp-mux attribute).
If I change rtcp_audio_interval_msec to passthru or say 2000 then there is explicit rtcp-mux in the INVITE SDP.
The UAC I'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.
Is this a "bug"? I would expect FreeSWITCH to signal rtcp-mux on the B-leg.
(On the A-leg, FreeSWITCH doesn't use rtcp-mux and includes an explicit rtcp port in SDP).
-- Richard Chan
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Richard Chan Chief Architect TreeBox Solutions Pte Ltd 1 Commonwealth Lane #03-01 Singapore 149544 Tel: 6570 3725 http://www.treeboxsolutions.com Co.Reg.No. 201100585R