The general solution is to use a STUN server to determine their port mapping. Machine A sends a packet form port X to STUN. The router translated the port to Y, and the STUN server sees this and responds back to A telling him what the external port was. B does the same.
There's a difference between a STUN and a TURN server, Google provides free STUN servers to use, while it's not recommended for an app because you want to have control when things go wrong, it's definitely fine for a small project that's for learning if that's your case and can reduce your project complexity. (I also don't think it's that bad to use it on small projects that have some users ...
I checked to make sure that my TURN/STUN servers are properly functional and that the peerJS public server was up before trying again As mentioned before the IDs are not in use The call event seems to work properly and the addStream function does not seem to have trouble adding streams when invoked directly. I tried everything I could.
Chrome not detecting STUN success responses even if I can see the ...