Erizo handle of RTP headers and WebRTC utility code

I am looking forward to give a hand with erizo fixing a couple of things that I’ve identified that might be improved. Once I’ve started to read the source code I’ve found that Licode defines for example an RtpHeader[0] class which defines almost the same members that RTPHeader struct defines in WebRTC source[1]. Also notice that WebRTC has his own mechanism to handle extensions and looks like Licode has his own too.
I would like to start supporting CVO extension for external output but I’ve found that while WebRTC has utility code to parse the extension and access the value in a friendly way, that work needs to be duplicated in Licode (at first galance) instead of take advantage of it.
Would be great if you can point me out a few things to start working on support CVO extension.



1 Like