Not sure why would he see ping timeouts …
I suspect the reason to work on meet.jit.si is the fact we are running a turn server, which is used when needed in p2p connections and also to handle media over tcp if needed.
You just need to check webrtc-internals to see what is going on with the media, maybe.
See which are the candidates and the protocol user A is using when a successful call is established with meet.jit.si.
Also check the network tab in the developer console to see what are the ping errors, are they network errors or some error returned … something can reveal more to find it.
@markmadlangbayan webrtc is used everytime. P2P connection is established if possible and there are two participants, if it is not possible or more than two participants connection to the bridge is established.
Turn can be used for both the p2p connection and jvb connection. This said means that if there is a turn configured, p2p will always succeed.
If you disable on the client machine all udp and tcp traffic to the videobridge then the connection will go through the turn server when the jvb connection is needed.