Re: [reSIProcate-users] Why multiple ICE implementations?

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

nICEr - is the ICE implementation that is being used in Firefox.  Is is completely separate from anything else in resiprocate.  There are some discussions about separating this out of the resip repository for that reason.

p2p - is a the start of a "reload" implementation and is not related to ICE

recon - is a user agent library that hopes to support ICE someday, but it does NOT today.  Some options for the future:  replacement of sipXtapi media layer with webrtc.org code (as Daniel has mentioned).  Or... integration of nICEr into recon, or... build ICE from scratch as part of the flow manager APIs.

Scott

On Sun, Sep 27, 2015 at 4:11 PM, Daniel Pocock <daniel@xxxxxxxxxx> wrote:

On 27/09/15 00:55, Tom Chen wrote:
> Hi,
>
> I see ICE has been implemented in multiple folders: nICEr, p2p,
> recon/sdp.... i am wondering why?which follows Rfc 5245 - Interactive
> Connectivity Establishment?
>
> reflow/FlowManager.cxx contains createMediaStream(), but it does not
> seem to implement candidates gathering & prioritizing which is essential
> in ICE.
>
> Is there a way to build reflow?

There has been some discussion about this in the past

Currently, we use the media stack from sipXtapi.  I don't believe the
ICE stuff has been supported.

One idea that has been suggested is that we could use the libjingle
media stack instead.  It is the same code that is used in the Chrome
browser for WebRTC.  libjingle is BSD licensed, it supports ICE and it
also supports many of the other things like codecs and DTLS-SRTP for
maximum interoperability.

It is not a trivial piece of work though, it may require some
sponsorship for this to be undertaken.
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/