Behold the wonders and perils of a Session Description Protocol (SDP) generated by Chrome for WebRTC! See the source post by Antón Román for more background and commentary.
Want to learn more about SDP without reading the specs? Check out our posts on this topic: https://webrtchacks.com/?s=SDP
Help improve this!
WebRTC implementations are always changing, so this will require frequent updates.
Sorry the page does not work well on small screens – I need to work through some conflicts with bootstrap and the WordPress theme here.
Source code for this is located on github here: https://github.com/webrtcHacks/sdp-anatomy. See an error or line that should be added – just submit a pull request against the sdpdata.json file (strongly preferred) or make a comment in this google sheet.
Help on the visualization is certainly welcome too!
{“editor”, “chad hart“}
Want to keep up on our latest posts? Please click here to subscribe to our mailing list if you have not already. We only email post updates. You can also follow us on twitter at @webrtcHacks for blog updates.
Hi,
I have a somewhat working implementation of webrtc video chat. I do see video from both clients. Unfortunately it seems like it never accepts the ice candidate. I just keep getting candidates until the browser (canary 50) runs out of memory. Am missing something about how webrtc should accept ice candidates? My assumption was the browser’s webrtc implementation was managing the matching of ice candidates. Is there a manual way to match and manage all these ice candidates? Thanks in advance for any knowledge you might share.
If this isn’t enough SDP for you, you can also check out the SDP for WebRTC IETF draft here: https://tools.ietf.org/html/draft-nandakumar-rtcweb-sdp