Re: Firefox gather candidates for every media track even with max-bundle as bundlePolicy

2017-09-22 Thread prerak jain
On Friday, 22 September 2017 06:35:48 UTC+5:30, Nils Ohlmeier wrote: > Hi Prerak, > > > On Sep 21, 2017, at 02:27, prerak jain wrote: > > > > Firefox gathers candidates for every track which is added to the > > PeerConnection object even when bundle polic

Firefox gather candidates for every media track even with max-bundle as bundlePolicy

2017-09-21 Thread prerak jain
Firefox gathers candidates for every track which is added to the PeerConnection object even when bundle policy is set to max-bundle. As per the specs, it should only collect candidates for any one of the media track. Is there any way I can stop Firefox to gather candidates for all the tracks? ___

Re: Webrtc Simulcast: FF sending only one stream in simulcast enabled RTP session

2017-07-06 Thread prerak jain
On Thursday, 6 July 2017 04:43:01 UTC+5:30, Nils Ohlmeier wrote: > > On Jul 5, 2017, at 05:28, theashwin...@gmail.com wrote: > > > > We are testing FF/Simulcast with our SFU, expecting FF to send RTP of all > > three streams as advertised in SDP. > > > > simulcast parameters > > { > >

Does Firefox support temporal scaling for VP8 ?

2017-02-02 Thread prerak jain
Does Firefox support VP8 temporal scaling, if so how can I enable it. ___ dev-media mailing list dev-media@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-media

Re: DTLS 1.1 failure when Firefox 51 is initiating a call

2017-02-01 Thread prerak jain
On Thursday, 2 February 2017 01:54:23 UTC+5:30, ushun...@gmail.com wrote: > Hi Prerak, > > Thank you much for the info. When I made the client create an RSA P-256 > certificate and use it in PeerConnection (in fact, this is required with > Chrome 52 and later, when using OpenSSL 1.0.1g, for e.g

Re: DTLS 1.1 failure when Firefox 51 is initiating a call

2017-01-31 Thread prerak jain
On Saturday, 28 January 2017 05:49:38 UTC+5:30, ushun...@gmail.com wrote: > Hi, I am encountering a WebRTC DTLS issue with Firefox 51 and our WebRTC > gateway, which didn't happen with the previous version 50. This only happens > when Firefox initiates the call (it works fine when the gateway i