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

Issue 763671 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Nov 2017
Cc:
█ emadomara@chromium.org
webrtc-network-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

WebRTC - iceGatheringStateChange not called after onIceCandidate with a turnserver

Reported by zubairsh...@gmail.com, Sep 9 2017 
Steps to reproduce the problem:
1. Connect to a Server to receive JavaScript files that initiates Peer Connection
2. In the config TURN server is specified
3. Application should receive an SDP from the Chrome Browser

What is the expected behavior?
I opened a RTCPeerConnection, during Ice negotiation the last step is IceGatheringStateChange which generates SDP for the application. TURN server url is specified in the config. This works perfectly fine on Windows 64 bit Chrome browser, but does not work on Chrome 32-bit on Android. Please see attached file. The line marked in RED does not happen on Android 32 bit Chrome browser for the version number specified. Also note that once the TURN server url is removed and only STUN server url is specified, Chrome behaves as expected. 

What went wrong?
IceGatheringStateChange does not reach to state = Complete during Ice negotiation and therefore the SDP is never generated for the application. 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 60.0.3112.116 32-bit  Channel: stable
OS Version: 6.0.1; SM-T350 Build/MMB29M
Flash Version:
WebRTC-SDP.docx
14.2 KB Download

Comment 1 by guidou@chromium.org, Sep 11 2017

Components: -Blink>WebRTC Blink>WebRTC>Network

Comment 2 by anatolid@chromium.org, Oct 12 2017 

Ping for triaging.

Comment 3 by deadbeef@chromium.org, Oct 12 2017

Labels: Needs-Feedback
Is it possible that a STUN request from one of the device's network interfaces is timing out? Can you gather a native log (https://webrtc.org/native-code/logging/)?

If so, this is expected behavior. See: https://bugs.chromium.org/p/webrtc/issues/detail?id=7844
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 13 2017

Status: Archived (was: Unconfirmed)
No feedback was received in the last 30 days from reporter "zubairshams@gmail.com", so archiving this. Please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment