STUN issue. 401 response

[Jairo Canales Alfonso]

Hello,

I am working on a WebRTC client that uses ice4j to process STUN/TURN messages, which are in the WebRTC standard. In the Firefox implementation of STUN stack, they reply to a Binding Request User a 401 (Unauthorized) packet at the beginning of the communication, but after repeating some times the Binding Request User the answer becomes the expected Binding Success Response (with an XOR-MAPPED-ADDRESS).

I have read in the RFC 5245 that "If the STUN transaction generates a STUN error response that is unrecoverable (as defined in [RFC5389]) or times out, the agent sets the state of the pair to Failed". I've done a modification in my ice4j to adapt the STUN stack to this situation, but I feel I'm working out of the standard accepting 401 messages at the beginning of the pair resolution.

I enclose a wireshark capture that shows the situation in https://dl.dropboxusercontent.com/u/51409718/stun401ice4j.pcap .

Thank you.

[Eric Rescorla]

This should be fixed in Beta.

https://bugzilla.mozilla.org/show_bug.cgi?id=886120

> _______________________________________________
> dev-media mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-media
>