Moving extensions from on-premise LAN to remote. SBC?

[LRS]

We have on-premise PBX with a static IP and FQDN, with 6 x Yealink T46G extensions on internal LAN.

iOS clients already connect externally OK through tunnel.

What do we need to do to connect the Yealinks to work from home?

I assume will need to reprovision the Yealinks once set correctly, but do we select the SBC option? And do we need a SBC installed aswell as the PBX on the same machine?

 

[eddv123]

You can if each extension is at a users house setup the extension in STUN mode:
https://www.3cx.com/docs/manual/configuring-ip-phones/#h.ul2fzupi6t22/

In my opinion sticking to Apps only would be the best option however, remote handsets on home networks (behind provider pre-configured routers) can offer more trouble than its worth.

Each home with an SBC would probably not be the way to go as you need to provider the hardware for the device to run on.

 

[AWS2P]

What do we need to do to connect the Yealinks to work from home?

It's not the same answer if you mean 6 phones in same home or each at different house ?
In same place , a SBC is the solution, now if each phone is alone in a location then STUN is the way.

But if you are doing this in Covid19 conditions and searching something working with no pain , App on smartphone or webclient is the first solution you should consider, as it is really quickly done.

 

[LRS]

To test, we provisioned one phone as STUN. The MAC address and url tied and sent to Yealink's RPS.

User took handset home, factory reset. Then after extension number and voicemail pin entered, the phone correctly provisioned itself with BLF etc but won't connect to our PBX on it's fixed IP address.

So provisoning port ok but something else blocked?

 

[eddv123]

Provisioning port = HTTPS 443/5001 (whichever you set on install).

If your phone is stuck saying "no service" then its your SIP port that cannot access the remote server most likely (SIP Registration).