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

[reSIProcate-users] Why multiple ICE implementations?

From: Tom Chen <chentom60@xxxxxxxxxxx>
Date: Sat, 26 Sep 2015 15:55:39 -0700

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?

Tom

Follow-Ups:
- [reSIProcate-users] can someone recommend a voip sip test suite or tool ?
  - From: Tom Chen
- Re: [reSIProcate-users] Why multiple ICE implementations?
  - From: Daniel Pocock

Prev by Date: [reSIProcate-users] FW: NAT Traversal (ICE, STUN, TURN) support
Next by Date: Re: [reSIProcate-users] Why multiple ICE implementations?
Previous by thread: Re: [reSIProcate-users] FW: NAT Traversal (ICE, STUN, TURN) support
Next by thread: Re: [reSIProcate-users] Why multiple ICE implementations?
Index(es):
- Date
- Thread