# Consuming RTP

**URL:** <https://mediasoup.discourse.group/t/consuming-rtp/3676>\
**Category:** Integration\
**Created:** [December 4, 2021, 10:50am UTC](https://mediasoup.discourse.group/t/consuming-rtp/3676 "2021-12-04T10:50:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![OG-RTC](https://avatars.discourse-cdn.com/v4/letter/o/f475e1/32.png) [@OG-RTC](https://mediasoup.discourse.group/u/OG-RTC)\
**Post date:** [December 4, 2021, 10:50am UTC](https://mediasoup.discourse.group/t/consuming-rtp/3676/1 "2021-12-04T10:50:20Z")

</div>

Hi,

Documentation says:

**Once done, other endpoints (WebRTC endpoints or any others) can receive both, the FFmpeg audio and video track, by using the [transport.consume()](https://mediasoup.org/documentation/v3/mediasoup/api/#transport-consume) API as usual.**

I I want to consume audio and video, I need to create 2x transports on client side, 2x consumers (one audio consumer on the audio transport one videoConsumer on video transport) get the tracks from each and feed them to a video element? Or can I consume video and audio over the same RTP transport?

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/nazar-pc/32/369_2.png) [@nazar-pc](https://mediasoup.discourse.group/u/nazar-pc)\
**Post date:** [December 4, 2021, 11:10am UTC](https://mediasoup.discourse.group/t/consuming-rtp/3676/2 "2021-12-04T11:10:15Z")

</div>

You can use the same transport, audio and video will have different SSRCs, so as long as receiver can handle that, it will work.

BTW, if you work with the browser, you will most likely use WebRTC and not plain RTP.

---

<div class="post-metadata">

**Author:** ![OG-RTC](https://avatars.discourse-cdn.com/v4/letter/o/f475e1/32.png) [@OG-RTC](https://mediasoup.discourse.group/u/OG-RTC)\
**Post date:** [December 4, 2021, 11:14am UTC](https://mediasoup.discourse.group/t/consuming-rtp/3676/3 "2021-12-04T11:14:35Z")

</div>

Hi Nazar,

I am using RTP only to send traffic to media soup and using a browser webRTC client to consume it.

The way data is sent from ffmpeg is one port for audio another for video, and creating 2 producers (1 audio , 1 video ) on server side. Can I have 1 transport here for both audio and video?

about consuming those, you are saying on browser side, I can create 1 transport and then consume both the audio and video producers over same transport.

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/nazar-pc/32/369_2.png) [@nazar-pc](https://mediasoup.discourse.group/u/nazar-pc)\
**Post date:** [December 4, 2021, 11:47am UTC](https://mediasoup.discourse.group/t/consuming-rtp/3676/4 "2021-12-04T11:47:35Z")

</div>

Technically nothing prevents you from sending multiple audio and video tracks in the same RTP connection in either direction (and WebRTC uses RTP internally BTW). So yeah, you absolutely can do that.

---

<div class="post-metadata">

**Author:** ![OG-RTC](https://avatars.discourse-cdn.com/v4/letter/o/f475e1/32.png) [@OG-RTC](https://mediasoup.discourse.group/u/OG-RTC)\
**Post date:** [December 4, 2021, 11:55am UTC](https://mediasoup.discourse.group/t/consuming-rtp/3676/5 "2021-12-04T11:55:54Z")

</div>

I see, any idea how to send audio and video over same transport from ffmpeg for example?