Local ICE candidate not generated for 1-1 video call using WEBRTC

[Hemanshu Belani]

Our 1-1 video call web-application is in UAT phase and we have tested our app postively with 30+ different user having different connections & infrastructure. However we are not able to connect to one of the peer using webrtc 1-1 video call. After debugging we found out that local ice candidate is not being generated.

peer.onicecandidate = function (event) {

            console.log("Generating Local ICE candidate");

            if (event.candidate){
            console.log(event.candidate);
            // Other code
            }                     
        };

I

t seems the onicecandidate was not triggered as no logs were there in console.

We are using google's STUN and our own COTURN, but still ICE candidate for this particular user was not generated and no error from webrtc.

We also tried using https://apprtc.appspot.com/ and still we were not able to connect to him.

after clicking 'i' on apprtc we saw that there was no RemoteAddr for the user and no data was being transferred.

Audio Tx:   PCMU, - bps, - pps

Any help would be great.

[Taylor Brandstetter]

Do you see the onicecandidate callback with a null candidate, or do you see no callback at all? If you see no callback at all, is it possible that setLocalDescription is failing?

I'd also recommend filing a bug, including a native log and a chrome://webrtc-internals dump in order to investigate this further.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/5ec474b3-f755-4b99-afbf-3408a8f2a73c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Christoffer Jansson]

Hi,

What browser and version are you using? https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ is a great test page for checking if you can generate different candidate types.

/Chris

On Wed, Sep 7, 2016 at 1:31 AM 'Taylor Brandstetter' via discuss-webrtc <discuss...@googlegroups.com> wrote:

Do you see the onicecandidate callback with a null candidate, or do you see no callback at all? If you see no callback at all, is it possible that setLocalDescription is failing?

I'd also recommend filing a bug, including a native log and a chrome://webrtc-internals dump in order to investigate this further.

On Mon, Sep 5, 2016 at 5:43 AM, Hemanshu Belani <hemansh...@kossine.com> wrote:

Our 1-1 video call web-application is in UAT phase and we have tested our app postively with 30+ different user having different connections & infrastructure. However we are not able to connect to one of the peer using webrtc 1-1 video call. After debugging we found out that local ice candidate is not being generated.

peer.onicecandidate = function (event) {

            console.log("Generating Local ICE candidate");

            if (event.candidate){
            console.log(event.candidate);
            // Other code
            }                     
        };

I

t seems the onicecandidate was not triggered as no logs were there in console.

We are using google's STUN and our own COTURN, but still ICE candidate for this particular user was not generated and no error from webrtc.

We also tried using https://apprtc.appspot.com/ and still we were not able to connect to him.

after clicking 'i' on apprtc we saw that there was no RemoteAddr for the user and no data was being transferred.

Audio Tx:   PCMU, - bps, - pps

Any help would be great.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.

To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/5ec474b3-f755-4b99-afbf-3408a8f2a73c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.

To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAK35n0au3NWyg6B7VQj2PspLwEYYPaZbD6E2DnAbxwQUfTZY1Q%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

/Chris

[Hemanshu Belani]

Hi,

There was no callback at all. setLocalDescription worked fine.

Unfortunately we couldn't enable native logs but we ran test on https://test.webrtc.org/ ( Screenshot attached).

The test page got stuck while checking for UDP packets.

We have a test slot with same user on Friday, 16th Sep. We will try to debug as much as possible and will also enable logging.

Thanks :)

On Wednesday, September 7, 2016 at 5:02:12 AM UTC+5:30, Taylor Brandstetter wrote:

Do you see the onicecandidate callback with a null candidate, or do you see no callback at all? If you see no callback at all, is it possible that setLocalDescription is failing?

I'd also recommend filing a bug, including a native log and a chrome://webrtc-internals dump in order to investigate this further.

On Mon, Sep 5, 2016 at 5:43 AM, Hemanshu Belani <hemansh...@kossine.com> wrote:

Our 1-1 video call web-application is in UAT phase and we have tested our app postively with 30+ different user having different connections & infrastructure. However we are not able to connect to one of the peer using webrtc 1-1 video call. After debugging we found out that local ice candidate is not being generated.

peer.onicecandidate = function (event) {

            console.log("Generating Local ICE candidate");

            if (event.candidate){
            console.log(event.candidate);
            // Other code
            }                     
        };

I

t seems the onicecandidate was not triggered as no logs were there in console.

We are using google's STUN and our own COTURN, but still ICE candidate for this particular user was not generated and no error from webrtc.

We also tried using https://apprtc.appspot.com/ and still we were not able to connect to him.

after clicking 'i' on apprtc we saw that there was no RemoteAddr for the user and no data was being transferred.

Audio Tx:   PCMU, - bps, - pps

Any help would be great.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.

To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.

[jitendra swami]

Hi Hemanshu,

Were you able to resolve the issue. Some of my users are facing the same issue.

restarting the browser solves the problem for them.

Thanks,

[Hemanshu Belani]

Hi Jitendra,

   Unfortunately we were not able to find a root cause as this issue happened only with 1 of our user. 

   As a workaround we asked him to use our application (or apprtc)  on a different network and it worked.

  We are guessing its something related to firewall, But not sure.

[Saurabh Jain]

Hi guys,

I have the same exact problem.

Tried several webrtc test pages including the appr.tc page.

Opened chrome:webrtc-internals - in all cases I see no onIceCandidate / addIceCandidate messages

Also, the webRTCTroubleshooting page gets stuck on UDP test.

Tried the same test pages on a different machine with the same version of chrome on the same network - and there it works fine !?! - just not on my laptop.

Tried resetting chrome settings to get rid of all plugins etc.. - no change

Tried disabling Windows firewall and re-run tests - no change

Any ideas ??

Please help - thx,

Saurabh

[Philipp Hancke]

can you get a chrome debug log as shown on https://webrtc.org/native-code/logging/ ? (you might want to set verbosity higher, e.g. 4)

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.

To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/913f0af5-8e0a-493d-b6c5-67be0645d7de%40googlegroups.com.

[Saurabh Jain]

Well I tried launching chrome with the debug flags as suggested and ran the trickle-ice test https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/

.. and to my surprise - it did not fail!

Had this same URL open in another chrome window that had previously been opened without the debug flags - clicked on Gather candidates - and it worked there as well!

Tried a few other webrtc test pages - they all seem to work fine now!

One thing to note - about an hour ago - for some possibly unrelated reason - my laptop crashed (just plain shut down instantly?? - has never done this before) - so I had restarted it - relaunched chrome and recovered tabs.

So, perhaps it was the restart that fixed things?  - (I don't suppose it was in any way the act of launching chrome with debug flags - right?)

Will post if the problem reappears.

Thanks for the response.

On Thursday, February 23, 2017 at 11:29:28 PM UTC-8, Philipp Hancke wrote:

can you get a chrome debug log as shown on https://webrtc.org/native-code/logging/ ? (you might want to set verbosity higher, e.g. 4)

2017-02-23 23:31 GMT+01:00 Saurabh Jain <sjwo...@gmail.com>:

Hi guys,

I have the same exact problem.

Tried several webrtc test pages including the appr.tc page.

Opened chrome:webrtc-internals - in all cases I see no onIceCandidate / addIceCandidate messages

Also, the webRTCTroubleshooting page gets stuck on UDP test.

Tried the same test pages on a different machine with the same version of chrome on the same network - and there it works fine !?! - just not on my laptop.

Tried resetting chrome settings to get rid of all plugins etc.. - no change

Tried disabling Windows firewall and re-run tests - no change

Any ideas ??

Please help - thx,

Saurabh

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.

To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.

[jitendra swami]

Hi Saurabh,

It is happening with some of our users as well. A browser restart always fixed the problem for them.

Thanks,