Introduction

This is a dashboard outlining a WebRTC project I worked on for purposes of understanding the protocol and, more importantly, to see how certain behavior manifests itself in the WebRTC logs each browser provides.

These projects all work, but will vary in levels of refinement.

For whatever reason, Firefox doesn't seem as capable as Chrome when it comes to connecting machines on different networks. It will work in some scenarios, but not others. If you encounter issues establishing the connection between both peers, switch to Chrome if you aren't already using it.

• project1
  • Send text messages only
  • No STUN server involved, so you must open 2 browsers from the same machine.
  • Connection negotiated in-band (i.e. there is an initiator and receiver)
  project1a
  • Same as above, but connection is negotiated out-of-band (i.e. there is no initiator or receiver). Instead, a connection ID is used to identify the connection to both peers. Here, we're assigning an ID of 188.
• project2
  • Send text messages only
  • A STUN server is involved, you can use 2 different machines in different networks, no problem.
  • Connection negotiated in-band (i.e. there is an initiator and receiver)
• project3?mic=true&webcam=true
  • Send text messages, video, and audio.
  • A STUN server is involved, you can use 2 different machines in different networks, no problem.
  • Connection negotiated in-band (i.e. there is an initiator and receiver)
  • A signaling server is available, but it only logs SDP entries. Users can submit and view entries here under a mutual meeting ID value.
  project3?webcam=true
  • Same as above, but this only involves text messages and webcam.
  project3?mic=true
  • Same as above, but this only involves text messages and microphone.
• -IN PROGRESS- project4?mic=true&webcam=true
  • This will be used to test screen-sharing.
• Parse "Enable diagnostic packet and event recording" output; should be a .log file.
• Parse "Download the 'webrtc-internals dump'" output; should be a .txt file.