Access to info from chrome://webrtc-internals

[andy424]

Are some of the dynamic statistics accessible at the javascript layer in some round about fashion rather than just from the chrome://webrtc-internals URL? For instance, if available send or receive bandwidth is deemed too low, it is better to not offer video and just make an audio call. An application can decide if it had access to more information that is currently only available in the webrtc-internals flag.

timestamp	Wed Oct 09 2013 12:24:02 GMT-0500 (CDT)
ssrc	1766417153
googTrackId	WdRroNgEiP6l6RfGfjYIvZ8ukBiMkjjsrTvwv0
transportId	Channel-video-1
bytesReceived	1800743
packetsReceived	3357
packetsLost	11
googFirsSent	0
googNacksSent	-1
googFrameWidthReceived	640
googFrameHeightReceived	480
googFrameRateReceived	27
googFrameRateDecoded	30
googFrameRateOutput timestamp Wed Oct 09 2013 12:25:38 GMT-0500 (CDT) googAvailableSendBandwidth 128000 googAvailableReceiveBandwidth 114638 googTargetEncBitrate 128000 googActualEncBitrate 136750 googRetransmitBitrate 0 googTransmitBitrate 136750 googBucketDelay

[andy424]

view-source:chrome://webrtc-internals/ has these relevant lines

	<script src="chrome://resources/js/util.js"></script>
	<script src="chrome://webrtc-internals/webrtc_internals.js"></script>
	My question is whether these js files accessible and where do we get the source code for these js files? Thanks in advance

[Philipp Hancke]

That information is available through the getStats API. http://code.google.com/p/webrtc/source/browse/trunk/samples/js/demos/html/constraints-and-stats.html shows one way to use it.

I recently commited something which uses this to calculate packet loss per interval:

https://github.com/ESTOS/strophe.jingle/commit/f4e45a46b413f6466ebdeca498d9aaf52b90c5bd#diff-b62bc16806d0e3cfe92775fd203fc330R663

More generally, you query results[i].names() and do a results[i].stat(name) for each name -- see dumpstats from the sample page.