ICE Connection problem with gateway
Reported by
sun.kyun...@gmail.com,
Jun 14 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36 Example URL: Steps to reproduce the problem: 1. make a call from chrome to gateway(public ip) 2. Local SDP has muliple candidates (chrome) a=candidate:733479167 1 udp 2122260223 10.0.1.80 64263 typ host generation 0 network-id 1 a=candidate:733479167 2 udp 2122260222 10.0.1.80 61614 typ host generation 0 network-id 1 a=candidate:1765146231 1 udp 1686052607 1.1.1.1 41409 typ srflx raddr 10.0.1.80 rport 64263 generation 0 network-id 1 a=candidate:1765146231 2 udp 1686052606 1.1.1.1 35374 typ srflx raddr 10.0.1.80 rport 61614 generation 0 network-id 1 a=candidate:2938106617 1 udp 41885439 2.2.2.2 54068 typ relay raddr 116.120.83.109 rport 41409 generation 0 network-id 1 a=candidate:2938106617 2 udp 41885438 2.2.2.2 59207 typ relay raddr 116.120.83.109 rport 35374 generation 0 network-id 1 a=candidate:1698429967 1 tcp 1518280447 10.0.1.80 9 typ host tcptype active generation 0 network-id 1 a=candidate:1698429967 2 tcp 1518280446 10.0.1.80 9 typ host tcptype active generation 0 network-id 1 3. Remote SDP has one candidate (Gateway) a=candidate:2131306554 1 udp 2130706431 3.3.3.3 6270 typ host a=ice-lite 4. Chrome start ice connection checking. (onsignalingstatechange - signalingState : checking) 5. after couple of time, Ice connection failed (onsignalingstatechange - signalingState : failed) What is the expected behavior? iceNegotiation should be completed so that onsignalingstatechange event should be invoked with connected value for signalingState. overall connection should be success. What went wrong? if ice negotiation is failed, therefore overall connection fails. Did this work before? Yes up to m50 Chrome version: 51.0.2704.84 Channel: stable OS Version: OS X 10.11.5 Flash Version: still this is working fine with m50 and opera
,
Jun 21 2016
deadbeef: can you have a look?
,
Jun 21 2016
Are you sure the gateway is responding to binding requests from Chrome? Can you attach a packet capture and Chrome log if possible (see: https://www.chromium.org/for-testers/enable-logging)? Thanks.
,
Jun 23 2016
,
Jul 11 2016
Ping sun.kyungsunlee@gmail.com. Please re-open this bug if/when you answer #3.
,
Jul 12 2016
This was not issue of chrome. we asked our gateway provider to have a look the situation. They changed the firmware because our gateway could not parse 16bit network id which was newly introduced for m51. after that issue was resolved. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by xunji...@chromium.org
, Jun 15 2016