chrome://webrtc-internals

[bardu]

From the dump is there a way to tell whether a TURN server was involved to establish a connection?

[Vikas]

Hi,

You can look for googActiveConnection set to True in chrome://webrtc-internals. That will tell you the candidates used for the connection. 

/Vikas

[Alexandre GOUAILLARD]

hi vikas, 

I just gave it a try, and I have a few questions regarding this feature (nice work btw):

settings: chrome to chrome (all stable, 30.x), loopback on mac + one windows computer.

- I can see the address and the port of the used candidate, but it does not tell me the type ( host | srflx | relay ). Would it be possible to surface this as well? now I have to actually lookup within the candidate by IP:PORT to check the type of the connection eventually used.

- googActiveConnection only appears within the audio streams, and not the video streams. Is it expected? I thought there were separate candidates for each track, and I was expecting to see this info for each.

How does this relate to the stats API visible in the constraints-and-stats demo? In other word, how much is exposed in JS, and how much is chrome specific and only accessible through chrome://webrtc-internals.

thanks in advance.

regards,

alex.

--
 
---
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Stephan Bardubitzki]

Thanks for your response. I would like to explain my issue a bit more and to simplify I have remove all STUN servers and left only a TURN server.(My understanding is that a TURN server is also a STUN server)

Back to my issue: If I connect my Android smartphone over wifi to my laptop my video chat app works just fine, except the echo cancellation issue on Linux. So, googActiveConnection looks like this:

"Conn-audio-1-0-googActiveConnection": {

    "startTime": "2013-10-17T23:04:51.197Z",

    "endTime": "2013-10-17T23:05:29.267Z",

    "values": "[\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\",\"true\"]"

   }

However, connecting my Android smartphone over 3G/4G network fails and googActiveConnection looks like this:

"Conn-audio-1-1-googActiveConnection": {

    "startTime": "2013-10-18T23:06:31.510Z",

    "endTime": "2013-10-18T23:06:45.510Z",

    "values": "[\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\",\"false\"]"

   }

I noticed that googActiveConnection appears twice in the dump, means that that Chrome tried at the second attempt to use the TURN server to establish a connection?

[Vikas]

text inline.

On Friday, October 18, 2013 7:44:00 PM UTC-7, Alexandre GOUAILLARD wrote:

hi vikas, 

I just gave it a try, and I have a few questions regarding this feature (nice work btw):

settings: chrome to chrome (all stable, 30.x), loopback on mac + one windows computer.

- I can see the address and the port of the used candidate, but it does not tell me the type ( host | srflx | relay ). Would it be possible to surface this as well? now I have to actually lookup within the candidate by IP:PORT to check the type of the connection eventually used. 

 

I agree probably having information about 'type' would be useful.  

- googActiveConnection only appears within the audio streams, and not the video streams. Is it expected? I thought there were separate candidates for each track, and I was expecting to see this info for each.

I think that probably will happen when BUNDLE is used.  

How does this relate to the stats API visible in the constraints-and-stats demo? In other word, how much is exposed in JS, and how much is chrome specific and only accessible through chrome://webrtc-internals.

That's a good question, AFAIK the information in webrtc-internals is surfaced  mainly from stats api, are you talking about the other information displayed like local description success or failure, etc?

[Vikas]

Hi, 

Thanks for the feedback, Incase you observing connection issues only on 3G network it might be related to issue 2464.

/Vikas

[Vikas]

inline.

On Tuesday, October 22, 2013 11:20:13 AM UTC-7, Vikas wrote:

text inline.

On Friday, October 18, 2013 7:44:00 PM UTC-7, Alexandre GOUAILLARD wrote:

hi vikas, 

I just gave it a try, and I have a few questions regarding this feature (nice work btw):

settings: chrome to chrome (all stable, 30.x), loopback on mac + one windows computer.

- I can see the address and the port of the used candidate, but it does not tell me the type ( host | srflx | relay ). Would it be possible to surface this as well? now I have to actually lookup within the candidate by IP:PORT to check the type of the connection eventually used. 

 

I agree probably having information about 'type' would be useful.

Alex, you can track https://code.google.com/p/webrtc/issues/detail?id=2219 for type info.

[Alexandre GOUAILLARD]

thanks,

was tracking it already.

Also, i checked the latest apprtc code yesterday and saw some very interesting things on the infoDisplay. Nice work.

alex.