During hangouts call, no media was sent nor received [Unified plan] |
||||||||||
Issue descriptionChrome Version: 68.0.3432.0 [Canary] OS: Mac High sierra 10.13.4 What steps will reproduce the problem? (1) In DUT: Open the Chrome with the following command using terminal, (2) open -a "Google Chrome" --args --profile-directory=testprofile1 --user-data-dir=/tmp/test1 --enable-blink-features=RTCUnifiedPlanByDefault& (3) Go to hangouts.google.com and join the meeting from other device [It can be any device] What is the expected result? Meeting goes well without any audio or video issues. What happens instead? Hangout calls are connected but video/Audio feed from DUT device is not sent to the peer device. The vice versa of peer device media is not received by DUT as well. The status looks like a call is active but with issues. This happens every time we perform hangouts call. 100% reproducible.
,
May 17 2018
This issue is not reproducible in Windows 10 machine.
,
May 18 2018
,
May 21 2018
Re-marking as pri 2, since this likely requires action from Hangouts team.
,
May 21 2018
hbos@: Can you take a look and reassign if necessary?
,
May 21 2018
Running with RTCUnifiedPlanByDefault is the same as passing {sdpSemantics:"unified-plan"} to the RTCPeerConnection constructor.
Hangouts may need to update something, but it is very likely something is not working correctly due to bug 845149 . Tentatively making it blockedon, to be investigated today or tomorrow.
,
Aug 21
Ping !
,
Aug 21
Unified Plan with transceiver is now supported in M69 if --enable-blink-features=RTCUnifiedPlanByDefault is used (or if {sdpSemantics:"unified-plan"} is passed to the RTCPeerConnection constructor).
This bug likely requires action from the Hangouts team. It is not clear to me from the description that there is a Chrome bug here, Hangouts could be doing something relying on assumptions about Plan B behavior no longer valid. It is definitely possible to set up calls in Unified Plan, but I am unfamiliar with Hangouts codebase.
I will run a build and see if I can repro in top of tree.
,
Aug 21
Yes Hangouts needs to be updated, it is attempting to use Plan B SDP despite Unified Plan being used. I see this in the console: "Uncaught (in promise) InvalidAccessError: Failed to set remote answer sdp: Media section has more than one track specified with a=ssrc lines which is not supported with Unified Plan." Robin do you know who to talk to about Unified Plan?
,
Aug 21
,
Aug 21
Re-opening, I need to check Unified Plan -> Unified Plan, I was testing Unified Plan -> Plan B.
,
Aug 21
Filed related issue: https://crbug.com/webrtc/9649
,
Aug 21
Okay, even in Unified Plan -> Unified Plan calls a promise is rejected with: "Uncaught (in promise) InvalidAccessError: Failed to set remote answer sdp: Media section has more than one track specified with a=ssrc lines which is not supported with Unified Plan."
,
Aug 21
I also experienced this crash after the promise was rejected: https://crbug.com/876520 . Crashes are possible regardless and need to be investigated separately so that applications can fail gracefully, but in either case the Hangouts call is rejected prior to the possible crashes because it us using Plan B SDP, which is not allowed in Unified Plan. Other than the filed bugs, there is nothing to do on the Chrome side. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by vasanthakumar@chromium.org
, May 17 2018