Comments on: What if WebRTC SDP Munging was Prohibited? https://bloggeek.me/webrtc-sdp-munging-prohibited/ The leading authority on WebRTC Sat, 02 Jul 2022 17:03:38 +0000 hourly 1 By: Tsahi Levent-Levi https://bloggeek.me/webrtc-sdp-munging-prohibited/#comment-118509 Sun, 08 May 2016 05:33:03 +0000 https://bloggeek.me/?p=10304#comment-118509 In reply to Philipp Hancke.

Fippo – thanks as always

I guess I did forget that part of munging – the one on the incoming SDP from the remote participant.

]]> By: Philipp Hancke https://bloggeek.me/webrtc-sdp-munging-prohibited/#comment-118508 Fri, 06 May 2016 19:48:18 +0000 https://bloggeek.me/?p=10304#comment-118508 There are three more-or-less widely used use-cases.
1) restrict bandwidth using b= lines
2) changing the send codec
3) switching tracks on the fly

(1) is mangling done on the remote description, not affected by the proposed change.
(2) same same. You change the codecs you send by manipulating the remote description. Sounds weird? Welcome to SDP!
(3) This is somewhat tricky. Basically you can switch mic and cam on the fly by changing the ssrcs in a specific way. In Chrome. In Firefox, you just use RTPSender.replaceTrack. Alternatively, you check for RTPSender.replaceTrack and use it if available.

Not sure why this still-not-confirmed change is the end of SDP as we know it…

]]>