- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Fri, 20 Jun 2014 09:58:51 +0200
- To: Iskren Chernev <iskren@imo.im>, "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 06/20/2014 01:48 AM, Iskren Chernev wrote: > @harald thank you for the link. I'm looking forward to it being implemented. > > I'm currently using the stats interface of google chrome > (non-standard), but as Raju pointed out -- it would be much better if > the connected/completed event can have the candidate it connected > through. In the case of multiple transports, it will be somewhat complex, though - you can't indicate just one of the transports, and if you indicate all of them, how do you know which one you're looking for? If the data is already provided, it seems better in a first iteration to let you answer these questions for yourself - by firing off a getStats call from the onstatechange handler, and getting the data you want. > > On Thu, Jun 19, 2014 at 7:06 AM, Makaraju, Maridi Raju (Raju) > <Raju.Makaraju@alcatel-lucent.com> wrote: >> On 06/19/2014 01:41 AM, Iskren Chernev wrote: >> >> Once a connection has been established (PeerConnection >> >> iceConnectionState is completed or connected), is there any way to get >> >> the current ice candidate that is being used for the connection? >> >> >> >> I want to know if its a p2p connection or one going through a turn server. >> >> >> >> >> >> Once implemented, you should be able to get the selectedCandidatePairId of >> the RTCIceComponentStats - see https://www.w3.org/2011/04/webrtc/wiki/Stats >> [Raju] As was discussed in rtcweb threads, IMO there should be a much >> quicker and deterministic way of knowing the selected candidate than via >> stats. Ideally, the best time to know this is when ICE connection state >> reached “completed” state, probably via setting evt.candidate info in >> oniceconnectionstatechange() callback. >> >> >> >> BR >> >> Raju
Received on Friday, 20 June 2014 07:59:28 UTC