Hi, I would like to apologize if I'm writing in the wrong place.
I have a web application using webrtc. During my tests I manage to force the use of TURN server to relay when I try to connect 2 clients together. Between chrome to chrome clients, everything works fine, here's what happens in short: chrome : what is my public IP TURN: here is your public IP chrome : can I connect? TURN : No! send credentials. ( 401 unauthorized ) chrome : here are the credentials TURN : Ok But when the clients are under Firefox, the client is constantly rejected ( 401 unauthorized ) and can never connect to the TURN. Chrome's wireshark view is full of tcp communication to the TURN server which are absent with firefox ( only STUN protocol communications ). Also firefox's communication looks more messy, firefox doesn't stark by asking his public address. I give to webRTC a set of 2 TURN server address: it's the same turn server but with transport=udp for the first, and tcp for the second. I tested with port 80, 423 or 3478 ( default ) for stun communications, still same result. I saw that TURN was supposed to not be supported, and other article saying that it is supposed to be supported, I have no clue what to think about it, could you clarify the situation? I also noticed that recently a problem of interoperability for video/audio channels between chrome and firefox. I tested it on my own app and few public demo on the net and the problem remain the same: when the second client accept to share his webcam, getUserMedia always throw an error "access to media denied" while user accepted it. The first client to accept his webcam always success. _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
