msgbartop
Various ramblings-on, mostly about Red5
msgbarbottom

02 Oct 14 WebRTC notes

I’ve been working on a WebRTC project recently and I’ve found a few tidbits I’d like to share. First of all I want to recommend a book that makes for an outstanding reference: WebRTC: APIs and RTCWEB Protocols of the HTML5 Real-Time Web, Third Edition Secondly, these sites:

Third, as anyone who has worked with this technology has noticed, each browser that offers support for WebRTC comes with its own implementation and quirks. I’ve been working with Chrome and Firefox exclusively for my project, but it is possible to use most of the other browsers out there by using an adapter library or plugin. Below I’ll give a quick set of things I’ve encountered:

  1. DTLS is required
  2. ICE is required
  3. SHA-256 fingerprints are required for DTLS, SHA-1 doesn’t cut it
  4. Firefox does not support BUNDLE, but Chrome does
  5. Using BUNDLE requires the use of RTCP-Mux
  6. The safest codecs to use are PCM and VP8, as Chrome isn’t supporting h.264 at the moment
  7. ICE candidates are best sent after the offer via your signaling channel
  8. When Chrome is in the answer position and is read-only, it doesn’t send a fingerprint in its answer (I’m sure this is a bug, so I submitted it: bug report)

Additional links:

WebRTC drafts:

That’s it for now in a nutshell; my journey continues…

 

 

Tags: , ,


Fatal error: Call to undefined function akismet_counter() in C:\xampp\htdocs\paulgregoireblog\wp-content\themes\googlechrome\footer.php on line 9