1923416 - Check that MsectionIsDisabled instead of for port 0 to resolve Telegram A no media issue

Status: RESOLVED FIXED

(Core :: WebRTC: Audio/Video, defect, P3)

Description

[Dan Baker[:dbaker]]

We are incorrectly assuming port 0 is disabled in some instances even though bundling is used. This is causing media to not be sent/received.

Comment 1

[Dan Baker[:dbaker]]

Attachment: Bug 1923416 - Check if msection is disabled instead of if port is 0 when deciding to stop transceiver during negotiation;r?bwc

Comment 2

[Ryan VanderMeulen [:RyanVM]]

So I'm clear, this is a Beta-only patch? What's the plan for 133+?

Comment 3

[Dan Baker[:dbaker]]

(In reply to Ryan VanderMeulen [:RyanVM] from comment #2)

So I'm clear, this is a Beta-only patch? What's the plan for 133+?

I don't think I meant this for the beta repository my bad.

Comment 4

[Dan Baker[:dbaker]]

Attachment: Bug 1923416 - Added test case to verify transceivers are not disabled if port is 0 with bundling;r?bwc

Depends on D225151

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/226de61f8558
Check if msection is disabled instead of if port is 0 when deciding to stop transceiver during negotiation;r=bwc
https://hg.mozilla.org/integration/autoland/rev/66a2436a32be
Added test case to verify transceivers are not disabled if port is 0 with bundling;r=bwc

Comment 6

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/226de61f8558
https://hg.mozilla.org/mozilla-central/rev/66a2436a32be