< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

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



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.