Remote Provison on 3cx hosted.

[BrettBoggeman]

Hello everyone,

Newer to 3cx. Getting a hang of how the system works and configures. Does anyone know a work around the who not being able to stun or remote provision phone to the hosted without an sbc? What is everyone doing for work at home users? Just softphones?

Thanks

 

[cobaltit]

First, don't confuse terms. Whether you provision phone to remotely connect (or register) to 3CX via STUN or SBC it's still remote provisioning. And there's nothing to work around. You absolutely can configure a phone for STUN on 3CX hosted. It's just not supported.

But yes, due to issues with firewalls and such, soft phones or SBC are the recommended way to go. 3CX doesn't want to troubleshoot your network which is why STUN phones are not supported.

 

[JohnS_3CX]

Hi Brett


STUN: a remote phone connecting directly to the PBX over the internet. This is not supported on 3CX-hosted instances, so if you want STUN then the "workaround" is to deploy into your own cloud solution. There isn't much reason to complicate things to this degree though.

SBC: a remote phone that does not connect directly to the PBX. It connects to the local SBC, which then in turn has a tunnel connection going up to your PBX. This is more reliable and secure than STUN, and the only supported way of connecting up to a 3CX-hosted instance.


For remote workers where only one endpoint is needed, the easiest and recommended solution is webclient (with the accompanying chrome extension), or windows client, or the mobile client. This should cover the needs of most people, and makes a deskphone largely an unnecessary extra you no longer need to worry about.