Hi @themusicman, thanks for the contribution!

A couple of notes:

• current example is almost the same as the echo example so we add a lot of code that we need to maintain and update as API changes
• handling RTCP in ex_webrtc is a little easier as we get those packets automatically. I can see why Pion has a separate example for this as they need to call ReadRTCP in a loop (link)

I would favor adding a clause for RTCP in our echo example that just ignores those packets. We can add a short comment too. Something like this:

  defp handle_webrtc_msg({:rtcp, _packets}, state) do
    # do something with RTCP packets
    {:ok, state}
  end

This way:

• we show how to receive RTCP packets
• we don't add too much extra code that needs to be maintained
• we don't send messages to the FE or log them in the console so the output is clean

@mickel8 Fair points.

I updated the PR.

Is there anything that you want help with in regards to the project? Maybe RTCP Sender and Receiver Reports?

Thanks for the PR @themusicman! i have deleted the comment as we are going to talk about RTCP in our guides section (in hex docs) at some point.

Is there anything that you want help with in regards to the project? Maybe RTCP Sender and Receiver Reports?

That's something @LVala is already working on!
When it comes to the roadmap itself, I am working on ICE features (mDNS and TURN servers support) .

Other things I have in my mind but are not planned for 0.2 (i.e. neither @LVala nor me are going to work on them)

• support for AV1 codec, see AV1 payloader #35
• datachannels
• ex_webrtc_dashboard - more metrics, performance optimizations
• jitter buffer

and many more, I will update the list later this evening 😉

@mickel8 I was thinking about suggesting datachannels too. I will look into that some and come up with a plan for implementation and present it to you. What do you think about that?

@themusicman Sounds great!

@themusicman I've created a new section in our Roadmap where I put things that can be addressed: #28