Introduction

On this page you will find the results from an investigation into WebRTC conducted by the Service Activity 8 (SA8), Task 2 team of the GN4-1 project. Both the end report (WebRTC roadmap) and the internal deliverables (reports, proof of concepts, code) leading up to the end report are available here. The task ran from 1 May 2015 until 30 April 2016.

Reading guide

The WebRTC roadmap report builds on the combined result of discussions within the task, observations done through-out the task period and the results of various technology scouts. Please note we provide the individual internal tech scout reports and other materials as a service to the community, to help others to build on our efforts. They don't necessarily contain all results and observations but will definitely help anyone interested in the particular topic. The WebRTC roadmap report went through several external reviews. The individual tech scouts went through an internal Task 2 review and are rougher at the edges.   

Task members

Alf Hansen (UNINETT),Claudio Allocchio (GARR),  Franck Rupin (RENATER, left task 30 November 2015), Fréderic Loui (RENATER), Jan Meijer (UNINETT, task leader), Mihály  Mészáros (NIIFI), Rui Ribeiro (FCCN), Simon Skrødal (UNINETT, joined 1 January 2016)

Some useful (technical) links we gathered

GN4-1 SA8T2 on WebRTC: Useful links and information

The WebRTC roadmap report

is available here: D12-3_WebRTC-Requirements-RandE-Deployment-Roadmap.pdf

The individual WebRTC technology scouts

Useful links and information

Accessing WebRTC debug information in browsers

FireFox: about:webrtc

Chrome: chrome://webrtc-internals

ICE, STUN and TURN links

Interesting links

• http://www.slideshare.net/EyeballNetworks/any-firewall-eyeball-networks
• http://www.eyeball.com/standards/stun-turn-ice/

STUN/TURN implementations

• http://sourceforge.net/projects/stun/
• http://turnserver.sourceforge.net/
• https://www.resiprocate.org/ReTurn_Overview
• https://github.com/coturn/rfc5766-turn-server/
• https://github.com/coturn/coturn

Google REST API 

Google STUN/TURN REST API via APPRTC:

https://computeengineondemand.appspot.com/turn?username=1234&key=5678

{"username": "1449668921:1234", "password": "lOG0FK45ggYwEclHMlQ1bcipATE=", "uris": ["turn:104.155.26.71:3478?transport=udp", "turn:104.155.26.71:3478?transport=tcp", "turn:104.155.26.71:3479?transport=udp", "turn:104.155.26.71:3479?transport=tcp"]}

Debug FireFox

Firefox:

export NSPR_LOG_FILE=/home/ehugg/tmp/nspr.log
export NSPR_LOG_MODULES=signaling:5,mtransport:5,timestamp:1
export R_LOG_LEVEL=9
export R_LOG_DESTINATION=stderr

ICE media log:

 For ICE/STUN/TURN: 
     Set R_LOG_DESTINATION=stderr 
     Set R_LOG_LEVEL=3 (can be anything between 1 and 9) 
     Set R_LOG_VERBOSE=1 if you want to include the module name 
generating the message 

For "signaling" (SDP offer/answer handling) and media transport, we use 
the normal Mozilla logging infrastructure, which uses a comma-separated 
list of modules, each one with its indicated log level; for WebRTC, 
you'll be most interested in these: 
     Set NSPR_LOG_MODULES=signaling:5,mtransport:5 

Debug Chrome

google-chrome --enable-logging=stderr --v=4 --vmodule=*libjingle/*=9 --vmodule=*media/*=9

.config/chromium/chrome_debug.log

a) --vmodule=*source*/talk/*=3
b)  --vmodule=*third_party/libjingle/*=3
c) --vmodule=*libjingle/source/talk/*=3

--enable-logging=stderr --log-level=3 --vmodule=*libjingle/*=3,*=0