# SDP on the wire

**URL:** <https://mediasoup.discourse.group/t/sdp-on-the-wire/2015>\
**Category:** mediasoup libraries\
**Created:** [November 11, 2020, 12:43pm UTC](https://mediasoup.discourse.group/t/sdp-on-the-wire/2015 "2020-11-11T12:43:04Z")\
**Posts on this page:** 9\
**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:** [November 11, 2020, 12:43pm UTC](https://mediasoup.discourse.group/t/sdp-on-the-wire/2015/1 "2020-11-11T12:43:04Z")

</div>

Hello,  
I am reading that in mediasoup the SDP is not sent over the wire.  
Does it mean the SDP is generated on the client side and mediasoup server, and then encapsulated into an RTPParameter and sent as part of signaling? Can I think of the client as having one end as webRTC SDP and the other end as RTPParameter going into mediasoup?

---

<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:** [November 11, 2020, 2:31pm UTC](https://mediasoup.discourse.group/t/sdp-on-the-wire/2015/2 "2020-11-11T14:31:36Z")

</div>

SDP is parsed/generated on the client because that is what browsers currently support, on server-side though SDP is not used at all.

> Can I think of the client as having one end as webRTC SDP and the other end as RTPParameter going into mediasoup?

Not only RTP parameters, but yes, that is roughly correct.

---

<div class="post-metadata">

**Author:** ![micaelgallego](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/micaelgallego/32/103_2.png) [@micaelgallego](https://mediasoup.discourse.group/u/micaelgallego)\
**Post date:** [November 12, 2020, 12:48am UTC](https://mediasoup.discourse.group/t/sdp-on-the-wire/2015/3 "2020-11-12T00:48:50Z")

</div>

The project [https://github.com/versatica/mediasoup-sdp-bridge](https://github.com/versatica/mediasoup-sdp-bridge) will provide a way to negotiate with mediasoup using SDPs (just like other WebRTC peer).

It is still in development, but the PR [https://github.com/versatica/mediasoup-sdp-bridge/pull/2](https://github.com/versatica/mediasoup-sdp-bridge/pull/2) has a working prototype.

Regards

---

<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:** [November 14, 2020, 7:03am UTC](https://mediasoup.discourse.group/t/sdp-on-the-wire/2015/4 "2020-11-14T07:03:24Z")

</div>

Ok so can we say that mediasoup client takes the web browser generated SDP, makes it prettier and sends that into as part of an RTPParameter over signaling?

---

<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:** [November 14, 2020, 1:20pm UTC](https://mediasoup.discourse.group/t/sdp-on-the-wire/2015/5 "2020-11-14T13:20:33Z")

</div>

It would be the easiest to just go straight to source for such kinds of questions: [https://github.com/versatica/mediasoup-client/tree/v3/src](https://github.com/versatica/mediasoup-client/tree/v3/src)

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [November 14, 2020, 1:31pm UTC](https://mediasoup.discourse.group/t/sdp-on-the-wire/2015/6 "2020-11-14T13:31:51Z")

</div>

Not even to the sources. If someone is using mediasoup-client he must know that no SDP is being sent to the server (given that he is the responsible of carrying those parameters).

---

<div class="post-metadata">

**Author:** ![max](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/max/32/468_2.png) [@max](https://mediasoup.discourse.group/u/max)\
**Post date:** [January 13, 2021, 9:37pm UTC](https://mediasoup.discourse.group/t/sdp-on-the-wire/2015/7 "2021-01-13T21:37:39Z")

</div>

Is there a specific reason SDP isn’t used server-side? I don’t know enough about the structure of the messages themselves to determine why it would make more sense to make something custom vs SDP + any additional metadata mediasoup uses.

Max

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [January 13, 2021, 9:55pm UTC](https://mediasoup.discourse.group/t/sdp-on-the-wire/2015/8 "2021-01-13T21:55:29Z")

</div>

> **[SDP: Your Fears Are Unleashed (Iñaki Baz Castillo) - webrtcHacks](https://webrtchacks.com/webrtc-sdp-inaki-baz-castillo/)**
>
> After providing some background on SDP in WebRTC and ORTC, Inaki Baz Castillo explains all the issues the use of SDP for parameter exchange is creating

---

<div class="post-metadata">

**Author:** ![max](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/max/32/468_2.png) [@max](https://mediasoup.discourse.group/u/max)\
**Post date:** [January 14, 2021, 12:25am UTC](https://mediasoup.discourse.group/t/sdp-on-the-wire/2015/9 "2021-01-14T00:25:00Z")

</div>

Yes! This is exactly what I was looking for. Thanks for sharing! ORTC sounds like a dream.

Max
