Out of the sudden - no TURN connectivity

[Neil Young]

I'm having a web app which works fine as long as both parties are on the same network. It also worked fine in the past, if both parties were on a different network.

Out of the sudden I was triggered by a customer, who told me, that connections backed by LTE doesn't work anymore.

And in fact: I tried to reproduce with two browser windows on two different machines. If both machines are on the same network, all was fine.

If one machine was connected via LTE, there was no way to connect both, even though valid STUN and relay candidates were exchanged. 

In the end I stripped down the ICE server configuration on both machines to just TURN:

iceServers: [{
      urls: "turn:openrelay.metered.ca:80",
      username: "openrelayproject",
      credential: "openrelayproject"
    }]

I explicitly used a free TURN server, since I suspected the problem in my COTURN.

But this showed the same problem: No functionality in a mixed LTE/LAN scenario

What can be the issue here? 

[Sean DuBois]

Hey Neil,

That free TURN server only supports UDP (which could be the issue).

Is your COTURN server setup to use UDP/TCP/TLS?

What clients are you using? Does each side have a fully functioning
ICE/TURN Agent?

> --
>
> ---
> You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/8ef3092e-182c-4386-a9c8-18f055829a50n%40googlegroups.com.

[Neil Young]

Thanks for the follow up. It's a bit embarrassing but later the day I found the fault on my side... So no issue at all, but thanks again