Hello,
„In Plan B, one “m=” section of SDP is used for video and audio respectively. If an application sends or receives multiple media tracks of the same media type, multiple “a=ssrc”
lines are listed in the same “m=” section.
In contrast, with Unified Plan every single media track is assigned to a separate “m=” section. If you use multiple media tracks, multiple “m=” sections are created.
From e.g.
https://www.callstats.io/blog/what-is-unified-plan-and-how-will-it-affect-your-webrtc-development
Cheers,
Henning
From: sr-dev <sr-dev-bounces@lists.kamailio.org>
On Behalf Of Daniel-Constantin Mierla
Sent: Tuesday, May 19, 2020 7:46 AM
To: Kamailio (SER) - Development Mailing List <sr-dev@lists.kamailio.org>; M S <shaheryarkh@gmail.com>
Subject: Re: [sr-dev] RTPEngine - Support for Unified Plan SDP Format
Hello,
what are the differences in building the SDP for the two types (plan-b vs unified-plan)? Can you (someone else) summarize? it will be useful to see what can be done for sdpops module.
On the other hand, rtpengine gets full SDP body from Kamailio and returns the new full SDP back, so here I do not think Kamailio's RTP engine needs update, maybe new flags to control if the change should be done or not (e.g., between
two webrtc endpoints, one with old format and the other with the new format).
Cheers,
Daniel
On 17.05.20 06:31, M S wrote: