Example of ice-lite packets (not getting use-candidate attribute)

[pablo platt]

Hi,

I'm using Chrome and MCU with ice-lite.
Chrome sends the offer.

I've tried with google-ice in the SDP and with normal ice (no a=ice-options)
In both cases I'm not getting the use-candidate attribute in stun packets from Chrome.
When using google-ice I'm able to get RTP packets from Chrome.
When using normal ice or trickle, I'm not able to get RTP packets.

Is there a known issue with the use-candidate attributes?
Maybe something specific to ice-lite.

What is the difference between google-ice and normal ice packets?

Can someone show the Chrome and the MCU stun packets so I'll be able to compare with the packets I'm sending and see if I'm missing some attribute?

Thanks

[Justin Uberti]

Ice Lite is not supported with google-ice. 

However, USE-CANDIDATE will be sent when using ICE Lite with standard ICE.

--
 
---
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.

[pablo platt]

I'm able to validate Chrom's stun message integrity on the MCU but not sure I'm sending the correct stun response.

I'm sending a response with binding method with the transcation-id of the request.

The only attribute I'm adding is XOR-MAPPED-ADDRESS.

I'm using the server password - the same password used to validate the request. Is this correct?

Do I need to add the USERNAME attribute?

Do I need to add the fingerprint?

[pablo platt]

I've added the fingerprint and now it seems to work.

Thanks

[Justin Uberti]

You need to follow the steps in section 7.2 in RFC 5245. The examples should also help illustrate the correct behavior.

[Idit G]

I've experienced the same problems you described:

When using google-ice I'm able to get RTP packets from Chrome.
When using normal ice or trickle, I'm not able to get RTP packets.

My stun responses include the following attributes:
XOR-MAPPED-ADDRESS
MESSAGE-INTEGRITY
FINGERPRINT

Could you please include an example of your SDP and packets.
Any additional information about how you were able to make it work would be appreciated.

Thanks