WebRTC client not using tunnel from an external location?

[MpDay20]

Hi, in short: I've opened external port 5001 TCP and 5090 TCP/UDP. Everything is fine, but when I login to the Web Client from an external location and call with the Chrome WebRTC function, there is no audio.

I've read this: https://www.3cx.com/community/threads/3cx-phone-system-audio-ports-increased.60235/ and opened external port 9000-10999 UDP, and now I have audio with WebRTC from an external location, so it's working

However, is it possible to tunnel the WebRTC audio through the tunnel on port 5090 TCP/UDP? Because I don't want to open all those RTP ports for all my customers actually.

 

[Saqqara]

I very much doubt WebRTC will use 3CX Tunnel, due to the fact WebRTC is open source

3CX tunnel is unique to 3CX, and used by SBC and 3CX clients (Mobile, Windows)

 

[cobaltit]

h the tunnel on port 5090 TCP/UDP? Because I don't want to open all those RTP ports for all my customers actually.

So you don't want to configure the system as 3CX says it should be? But the answer to your question is no. The 3CX Tunnel is proprietary which is why it only works with the 3CX SBC and the 3CX apps. Everything else is going to be using the standard ports/protocols (SIP and RTP)