Precision on the audioTransport in bundle mode

1

Hi,

I have look thought the WebRTCConnection class. In case of bundle I don’t
really see why an AudioTransport is created.
It creates an Ice connection but I don’t where it is used. The audio
candidates generated are from the video Transport ( that is bundled). Same
for the delivery of data, audio packets come from videoTransport.

So why doing that?

Francois

2

Hi Francois,

You were right, the audioTransport was not needed in case of bundle. It was created an stayed in a “frozen” state because the ICE Candidates were never passed to it.
I’ve just updated it in the master branch. Thank you for pointing that out.
The WebRtcConnection/NiceConnection/DTLSTransport code at this point can be a little confusing as some decisions where taken before the current WebRTC scenario where trickle-ice, bundle, rtcp-mux and DTLS are implemented in Chrome. I’m planning to review some parts in the trickle_ice branch to improve it in that regard.

Cheers,–
Pedro Rodriguez

On 16 Oct 2014, at 08:32, Francois Temasys regnoult@temasys.com.sg wrote:

Hi,

I have look thought the WebRTCConnection class. In case of bundle I don’t really see why an AudioTransport is created.
It creates an Ice connection but I don’t where it is used. The audio candidates generated are from the video Transport ( that is bundled). Same for the delivery of data, audio packets come from videoTransport.

So why doing that?

Francois

–
You received this message because you are subscribed to the Google Groups “lynckia” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lynckia+unsubscribe@googlegroups.com mailto:lynckia+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

3

You’re welcomeOn Thursday, October 16, 2014 5:12:17 PM UTC+8, Pedro Rodriguez wrote:

Hi Francois,

You were right, the audioTransport was not needed in case of bundle. It
was created an stayed in a “frozen” state because the ICE Candidates were
never passed to it.
I’ve just updated it in the master branch. Thank you for pointing that out.
The WebRtcConnection/NiceConnection/DTLSTransport code at this point can
be a little confusing as some decisions where taken before the current
WebRTC scenario where trickle-ice, bundle, rtcp-mux and DTLS are
implemented in Chrome. I’m planning to review some parts in the trickle_ice
branch to improve it in that regard.

Cheers,

Pedro Rodriguez

On 16 Oct 2014, at 08:32, Francois Temasys <regn…@temasys.com.sg <javascript:>> wrote:

Hi,

I have look thought the WebRTCConnection class. In case of bundle I don’t
really see why an AudioTransport is created.
It creates an Ice connection but I don’t where it is used. The audio
candidates generated are from the video Transport ( that is bundled). Same
for the delivery of data, audio packets come from videoTransport.

So why doing that?

Francois

–
You received this message because you are subscribed to the Google Groups
“lynckia” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lynckia+u...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/d/optout.