New/changed option in new extension creation menu?

[AdStar]

Hello,

my company just spotted a little difference. In creating extension options since I remember there were blow options (please dont bother with this red arrow):



Now we see that "disallow use of extension outside the LAN" and "block remote tunnel connections" are gone and instead of this we have:

and worth to mention this option is enabled by default and before this change we didn't use option "disallow use of extension outside the LAN".

So far new users with this default new option enabled are working OK, but my question is. Should we expect any other "hiden" changes? We are not using any stun server so I am not really sure..
I will be grateful for any advice.

Best Regards.

 

[JohnS_3CX]

Hello,

I'm guessing you recently upgraded from an older version of 3CX, so there are probably quite a few changes you will notice and are too numerous to list in one post.

We changed this description to better describe what it does, and it basically prevents anyone with extension credentials to use the extension outside your LAN (ie. in case credentials are stolen or leaked on the internet). You should leave this setting ticked by default on all extensions for better security.

If you use 3CX clients and supported phones, you will not have any issues turning this on. Only enable it if you have a STUN phone.

 

[AdStar]

Hello John,

thank you for your quick answer!

So it will not have any side effects due to the fact that before this change we leave previous setting "disallow use of extension outside the LAN"? Basically in other word: It is just cosmetic change in naming of this option, did I understood you correctly?

And i understand that old 2 options "disallow use of extension outside the LAN" and "block remote tunnel connections" are something like compressed in 1 option now?

 

[JohnS_3CX]

Yes, you understood correctly - we changed the description on the option only but it does the same exact thing as before.

As for the tunnel option, no this is a separate option still. It mainly affects the old V15/V16 client which connected to 3CX using the tunnel port. If you turn it on you will prevent the extension from using the tunnel - this will also affect 3CX mobile clients so you should not enable it unless you have good reasons. Here are the defaults when making a new extension in V18:



- Remote STUN registration is blocked
- Tunnel is not blocked because it is secure and recommended to be used. If you tick it then the mobile apps and the legacy V16 client cannot make calls.

 

[SweetAction]

Yes, you understood correctly - we changed the description on the option only but it does the same exact thing as before.

As for the tunnel option, no this is a separate option still. It mainly affects the old V15/V16 client which connected to 3CX using the tunnel port. If you turn it on you will prevent the extension from using the tunnel - this will also affect 3CX mobile clients so you should not enable it unless you have good reasons. Here are the defaults when making a new extension in V18:

View attachment 34476

- Remote STUN registration is blocked
- Tunnel is not blocked because it is secure and recommended to be used. If you tick it then the mobile apps and the legacy V16 client cannot make calls.

Important to note that mobile apps will work somewhat even with remote tunnel blocked. For example, they can send/receive chat/sms, they can see presence, manage voicemail to some extent - basically everything but make phone calls.

 

[AdStar]

Seams to be clear for now. Thank you very much guys. I will back to the topic as something new might come up next days.

Cheers!

 

[Evolute IT]

Important to note that mobile apps will work somewhat even with remote tunnel blocked. For example, they can send/receive chat/sms, they can see presence, manage voicemail to some extent - basically everything but make phone calls.

Because that uses HTTPS, FYI.