On 11/14/2014 8:06 PM, Mario Carbajal wrote:
Yes, it does.
On Fri, Nov 14, 2014 at 9:58 PM, Eric Rescorla <[email protected]> wrote:
Can you confirm that it fails with two chromes and with two firefoxes?
On Fri, Nov 14, 2014 at 2:45 PM, Mario Carbajal <[email protected]>
wrote:
The signaling of my project being wrong was my first bet, but it seems to
happen everywhere.
http://webrtcdevelop.appspot.com/ and https://www.sharefest.me/ for
example.
Can you detail the firewalls and network topology for your test, as we
haven't seen this in the past (and haven't heard of Chrome having any
problem like this). Also, go to about:webrtc (preferably in Aurora) and
copy the data there for ICE and SDP and the Connection Log. Select All,
Copy, and paste into a file. Then file a bug at
https://bugzilla.mozilla.org/
Most NATs have bugs. Often serious bugs. Or you can configure them in
ways that can interfere. Random example: be very, very careful trying to
use DMZs in NATs; many times that can cause weird interactions depending
on when probes for ICE/STUN go in versus go out, leading the packets not
going where you expect them. A configured DMZ on certain NATs can break
p2p connections, even (especially) if the target device isn't the DMZ
device. That's just the tip of the iceberg for NAT bugs; if this is
happening just in a specific network a bug like this may be the cause.
--
Randell Jesup, Mozilla
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
