New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 1692 link

Starred by 24 users

Issue metadata

Status: Assigned
Last visit > 30 days ago
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Sign in to add a comment

If media profile is not SAVPF on the offer, Chrome does not start ICE

Reported by, Apr 25 2013

Issue description

What steps will reproduce the problem?
1.  Offer Chrome an SDP is specifies RTP/SAVP
2.  Chrome sets the SDP, but ICE does not begin.

What is the expected result?
ICE candidate gathering should begin.

What do you see instead?
ICE does not start, so the application cannot continue.

What version of the product are you using? On what operating system?
Version 26.0.1410.64 m, Windows 7

Please provide any additional information below.
Previous versions of Chrome worked fine with SAVP.  This seems like a regression.  Also, SAVPF really isn't related to ICE so it shouldn't prevent it from starting.

I can post a link to a demo app that reproduces the problem.

Comment 1 by, Apr 25 2013

The problem can be reproduced by doing the following:

1 ) Point the first browser to
2 ) Allow media access
3 ) Point the second browser to
4 ) Allow media access

5 ) Click connect on the first browser.
6 ) Click connect on the second browser.

At this point, the first browser will offer an SDP to the second.  The jsp page has a line that will convert SAVPF to SAVP.  This causes the second browser to hang after it sets the SDP.

Note that this scenario works in previous versions of Chrome, and does not cause a problem if the Chrome gets an answer SDP with SAVP.  Seems to happen only with the offer.

Project Member

Comment 2 by, Apr 29 2013

@mallinath, I can reproduce it with Apprtc. Is SAVPF mandatory now?

When Canary gets such offer with SAVP instead of SAVPF, it would generate Answer without any audio/video. And the log says: "Audio(/Video/Data) is not supported in the answer", "No BUNDLE information, not bundling". So no candidate would be allocated.
Project Member

Comment 3 by, May 8 2013

Labels: Area-PeerConnection
Project Member

Comment 4 by, Jun 21 2013

As confirmed with Ronghua, now we only support SAVPF. I think this issue could be closed?
If we report error in SLD or SRD then you can close this, otherwise we should report the error with proper error message.
Project Member

Comment 6 by, Jun 21 2013

I tried to add error callbacks to SLD/SRD and none of them is fired. Answer would be generated. Just ICE candidate gathering won't start. So you are right we should report the error with proper error message. 

Comment 7 by, Jun 6 2014

Project Member

Comment 8 by, Dec 11 2014

Labels: Mstone-42 EngTriaged
Project Member

Comment 9 by, Dec 11 2014

Status: Assigned
Per, we need to support non-SAVPF (by treating as SAVPF).
Project Member

Comment 10 by, Feb 19 2015

Labels: -Mstone-42 Mstone-44
This looks like it's not hitting m42.  Update it if I'm wrong.
Project Member

Comment 11 by, Jan 29 2016

Labels: -Mstone-44 no longer resolves, so I can't use the steps in #1 to determine if this is still an open issue. But since I don't see any CLs linked to this bug, I'm assuming it hasn't been fixed. I'm therefore leaving this in an open state, but I am removing the milestone label since this bug hasn't been updated in quite some time.
Do we have any updates on that? We're getting the same issue as well. Emitting an error would definitely help until it's fixed
Project Member

Comment 13 by, Apr 7 2016

Project Member

Comment 14 by, Apr 13 2016

 Issue 5765  has been merged into this issue.
Project Member

Comment 15 by, Nov 8 2016

Labels: Pri-3
29.9 KB View Download

Sign in to add a comment