Code: 40401 error

[UnChul Kang]

Hi.

My java webserver for KMS gives me code 40401 exception, when I put the ice candidate into the function, WebRtcEndpoint.addIceCanddiate.

Error adding candidate (Code:40401, Type:null, Data: {"type":"ICE_ADD_CANDIDATE_ERROR"})

Please help me. What should I do for this issue?

My icecandidate data from chrome browser looks like below.

{"candidate":"candidate:932508327 1 udp 2113937151 099658a2-24a9-418e-9f59-fe321fb2fb74.local 65467 typ host generation 0 ufrag kax2 network-cost 999","sdpMid":"0","sdpMLineIndex":0}

I think the blue color above looks like something weired. 

Thanks in advance.

[UnChul Kang]

I am using KMS version 6.9.0

2019년 6월 26일 수요일 오전 11시 4분 30초 UTC+9, UnChul Kang 님의 말:

[Tahir]

Hi,

099658a2-24a9-418e-9f59-fe321fb2fb74.local is actually multicast DNS (mDNS) name. This happens in Chrome when "Anonymize local IPs exposed by WebRTC" flag is enabled. When this flag is enable, it hides the client's private IP addresses for privacy reasons. I think Kurento Media Server does not understand this name and it generates error code 40401. "Anonymize local IPs exposed by WebRTC" flag used to be disabled by default in Chrome. But it seems that for Chrome 75 on Windows 10, the default value is set to enabled. So if you want to expose your private IP addresses, go to chrome://flags, search for "Anonymize local IPs exposed by WebRTC" and set it to disabled. It will then use your host IP addresses for ICE exchange instead on using mDNS names. I encountered this problem on chrome 75, Win 10. Chrome 75 on Ubuntu 18 still works with out changing any default values for Chrome.

If you are interested, you can read about mDNS at https://tools.ietf.org/html/rfc6762#section-13.

There is also an RFC draft about ICE and mDNS: https://tools.ietf.org/html/draft-ietf-rtcweb-mdns-ice-candidates-03 

I hope this helps.

Regards,

Tahir

[Paulo R. Lanzarin]

Just an addendum: the error is natural and not critical. It just means that Kurento can't resolve mDNS candidates

(neither does libnice AFAIK). Nothing should break.

You don't need to disable anonymization if you're willing to handle and/or muffle those errors.

If you have a STUN server set up in your browser, things will work even with mDNS enforcement (since Kurento most
probably will get valid srflx candidates). Moreover, if you request gUM permission beforehand, Chrome will stop

generating mDNS candidates (as of now; heard some rumblings, though, about generating them even when the user has given

gUM permissions in the future). You can also drop candidates by passing a mDNS regex over them before calling addIceCandidate

(so you avoid the error).

--
You received this message because you are subscribed to the Google Groups "kurento" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kurento+u...@googlegroups.com.
To post to this group, send email to kur...@googlegroups.com.
Visit this group at https://groups.google.com/group/kurento.
To view this discussion on the web visit https://groups.google.com/d/msgid/kurento/ba8f46f0-2a35-4fb1-91b0-0f335d4deefe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ganesh Patil]

Hi 

I am also getting the same error(ICE_ADD_CANDIDATE_ERROR). I tried by mDNS regex to drop the candidate. After change its ignoring candidate while addIceCandidate but I am not able to receive stream in processAnswer that mean SDP negotiation is failing. I am using the JAVA kurento  library to establish a connection. I tried by upgrading by kurento and library version to 6.11 but still  the same error is there. Could you please let me know is kurento library convert mDNS to DNS ot do we need any third party library for this task?

Thanks

To unsubscribe from this group and stop receiving emails from it, send an email to kur...@googlegroups.com.

[Ganesh Patil]

HI,

Can anyone please help me to fix this issue?