[Nice] New SDP parsing API

Olivier Crête olivier.crete at collabora.com
Tue Feb 5 00:55:04 PST 2013


Good work!

On Mon, 2013-02-04 at 23:39 -0500, Youness Alaoui wrote:
> To summarize the new API, you can now call :
>    sdp_string = nice_agent_generate_local_sdp(agent);
> which will generate a single string containing a listing of all your streams,
> components, their credentials and candidates. You can then send that string as
> is to a remote user, which would call :

This should be available at least be per-media, ideally even
per-candidate (to support trickling). Having it per-media without the m=
line means that one can just put the blob from libnice inside you SDP
without having to mangle it. Possibly also add some API to get the
recommended default candidate (ie, the lowest priority).

> The SDP can also be used in a SIP call, but of course, you'd need to add your
> codec list to it and parse it to change the 'm' line to add the payload types to
> it. Other than that, it's a valid SDP according to the ICE RFC.

Also, not everyone uses the RTP/AVP profile, for example WebRTC mandates
RTP/AVPF, I would just not provide an m= line at all.

Also, please check https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-02
as I believe this will become major user (it's the candidate API for

Olivier Crête
olivier.crete at collabora.com

More information about the nice mailing list