Utilizing the ice-lite feature

[Mark]

I have a situation where I want to use ice-lite in an outbound (from Chrome) media session.  When I get back the SDP createOffer success, I inject a "a=ice-lite" just after the "c=" connection info line.  I leave everything else the same, including the other ice attributes, then set that modified SDP via setLocalDescription into peerConnection which later goes on to look for candidates (firing out STUN packets etc). So how do I tell it to not look for candidates?  I'm on "Chrome 27.0.1453.81" which seems to have the feature, so clearly I'm not doing something right. Having the ice-ufrag and ice-pwd are ok as my public server will respond to the direct ice bindings once the SDP response comes back from it.

For example:

[...]
c=IN IP4 0.0.0.0 a=ice-lite a=rtcp:1 IN IP4 0.0.0.0 a=ice-ufrag:jPn+jecWlzyelGmu a=ice-pwd:dOKCeSJ3Sfk5LgU0PeYQlGEZ a=ice-options:google-ice a=sendrecv [...]

So other than adding ice-lite, what other modifications are required?  I welcome any pointers, thanks, Mark.

[Vikas]

Thanks for the feedback, Can you test this by passing null instead of
a STUN/TURN server when you create peer connection?

/Vikas

[Justin Uberti]

Chrome does not support acting as an ICE Lite endpoint. Can you explain why you want to do this?

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Mark]

When I set null into the config for the peer connection, I'm still seeing ICE candidates come back in the JavaScript callback.  The candidates are valid (i.e. my public IP even though I'm behind a NAT) so clearly some kind of ICE interaction is happening.  I did a network capture and I'm seeing a TLS connection go to clients4.google.com with a bunch of exchanges with the server happening.  About 3 seconds later, I (finally) see the STUN bindings go to my media server.  Thoughts?  Thanks.

[Mark]

It looked to me like Issue 882 (ICE Lite) support was committed into M27.  I need call setup (audio and video) latency to be as low as possible.  My service is hosted entirely in the public address space (both signaling and media) so address discovery is not needed.

[Justin Uberti]

Chrome supports talking to a remote ICE Lite endpoint. It does not support acting as an ICE Lite endpoint.

Even without ICE Lite, you should get candidates immediately. See https://webrtc.googlecode.com/svn/trunk/samples/js/demos/html/pc1.html for an example.