Useful links and information

Accessing WebRTC debug information in browsers

FireFox: about:webrtc

Chrome: chrome://webrtc-internals

STUN/TURN implementations

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 

You can also add ",timestamp:1" to that list if you want each log 
message to include timestamps. 

Debug Chrome

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

 linux log file:

.config/chromium/chrome_debug.log

Basic info: https://www.chromium.org/for-testers/enable-logging 

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
  • No labels