On Thursday, March 5, 2015 at 3:32:46 PM UTC, Eric Rescorla wrote:
> This isn't going to work very well, with any version of Firefox.
>
> The semantics of this SDP is that you are offering a bunch of audio
> streams, and that each of them is (for some unknown reason) with
> a different codec.
>
>
On Thu, Mar 5, 2015 at 9:46 AM, wrote:
> On Thursday, March 5, 2015 at 3:32:46 PM UTC, Eric Rescorla wrote:
> > This isn't going to work very well, with any version of Firefox.
> >
> > The semantics of this SDP is that you are offering a bunch of audio
> > streams, and that each of them is (for s
This isn't going to work very well, with any version of Firefox.
The semantics of this SDP is that you are offering a bunch of audio
streams, and that each of them is (for some unknown reason) with
a different codec.
Firefox prior to 37 only supports one audio stream so it will try to
accept the
On Friday, February 27, 2015 at 3:40:19 PM UTC, Ethan Hugg wrote:
> The team currently working on OpenH264 is doing features that make the
> conferencing use cases better (CABAC, T8x8, Chroma QP/QP scaling).
>
> The packetization is done on the Firefox side in the WebRTC code. All the
> implemen
I used Firefox 33.1, with JsSIP and Kamailio, with a call to our desktop
video-conferencing application running on Windows. We were assessing
interoperability between the audio and video codecs. Our application sent SDP
with one media line per payload, rather than one media line containing a lis
5 matches
Mail list logo