The New Version 18 Desktop App, Simplicity as Standard

[NickD_3CX]

Are there any plans to include tunnel mode? this is a major backwards step in terms of security and limiting firewall policies to a single encrypted port which was the whole point of tunnel mode.

For remote users this is a huge backwards step

I'll slightly disagree here and I'll explain why.
In order for a 3CX Client to work it for sure requires access to the HTTPS port for the Presence information. This also applied for the legacy Windows App, so there is no change here.

Now the 9000-10999 port ranges are the audio ports used by 3CX for SIP Trunks as well, so we can say with a fair certainty that on most 3CX systems there are open as well. There is no real danger of leaving these ports open to all IPs on your Firewall, because nobody can use them to abuse your system, and 3CX does have protection against RTP injection.

Talking about encrpytion, the new Desktop App, as the WebClient, uses WebRTC, which uses a TLS connection for signalling (to HTTPS port) and DTLS for the Audio transmission (to/from ports 9000-10999) which is also encrypted.

I'm not seeing the step back...

 

[GoranC]

Hello,

I have a situation where some clients are accessing PBX from internet via public IP a.a.a.a which is forwarded to y.y.y.y internal IP of 3cx. Other clients are accessing 3cx directly to y.y.y.y leveraging split DNS. My question is, can I expect issues with this setup considering that my 3cx is configured to use a.a.a.a as "external IP configuration" under Network tab. I know that external IP configuration is used in contact field of the SIP message, so I'm not sure if this is going to affect those local customers which are using split DNS and v18 app on their PC.

Regards
Goran

 

[SweetAction]

Hello,

I have a situation where some clients are accessing PBX from internet via public IP a.a.a.a which is forwarded to y.y.y.y internal IP of 3cx. Other clients are accessing 3cx directly to y.y.y.y leveraging split DNS. My question is, can I expect issues with this setup considering that my 3cx is configured to use a.a.a.a as "external IP configuration" under Network tab. I know that external IP configuration is used in contact field of the SIP message, so I'm not sure if this is going to affect those local customers which are using split DNS and v18 app on their PC.

Regards
Goran

This should work, it's how we implement it and how Split DNS is designed to work.