Thoughts/recommendations for desk phones with remote (auto) provisioning

[NCariaga]

Hi.. we're looking for a desk phone that we can use with 3CX. Since majority of us are working remotely, we wanted the phones to have auto provisioning that would allow us to remotely provision the desk phone as it gets delivered to the user when we order it from any online store. We tried Fanvil but I think its' auto provisioning process was too much work for us. We had to come into multiple systems for the desk phone auto provisioning get to work.

In my mind, our ideal provisioning process would be once we get desk phone mac address, we can just go into a single site/server/portal we can make the phone configuration to set up the phone remotely...

Appreciate your thoughts and feedback on this. Thank you.

 

[Saqqara]

What you want to do, auto provision on stun is not possible

You have two options,

1. Configure the phones using stun, the end user will have to enter extension number and voicemail to configure the phone. This setup is the same for all supported phones

2. Configure the phone as stun In the management console. Get the end user to access the phone web front end , and enter the provisioning url into the phone manually

Another option, use 3cx softphone apps instead of a physical handset

 

[NCariaga]

What you want to do, auto provision on stun is not possible

You have two options,

1. Configure the phones using stun, the end user will have to enter extension number and voicemail to configure the phone. This setup is the same for all supported phones

2. Configure the phone as stun In the management console. Get the end user to access the phone web front end , and enter the provisioning url into the phone manually

Another option, use 3cx softphone apps instead of a physical handset

Hi.. thanks for quickly reverting back.. I have updated my earlier post as it seems like I was unable to articulate my question at first. When we tested Fanvil, we created a test STUN server that connects to their default home server. In doing so, we realized the whole process requires too much work. I was wondering if you know others who does better at this

 

[Evolute IT]

Hi.. thanks for quickly reverting back.. I have updated my earlier post as it seems like I was unable to articulate my question at first. When we tested Fanvil, we created a test STUN server that connects to their default home server. In doing so, we realized the whole process requires too much work. I was wondering if you know others who does better at this

If you use any supported phones (Snom, Yealink, Grandstream and Fanvil), and set them as STUN, 3CX takes care of the RPS. You simply factory reset the phone and after a few minutes, it will ask for a username/password, which is simply the ext number and voicemail PIN as password. The provisioning will work automatically just like that.

No need for your own account

 

[NCariaga]

If you use any supported phones (Snom, Yealink, Grandstream and Fanvil), and set them as STUN, 3CX takes care of the RPS. You simply factory reset the phone and after a few minutes, it will ask for a username/password, which is simply the ext number and voicemail PIN as password. The provisioning will work automatically just like that.

No need for your own account

Sorry I'm quite confused. Is this the same when I go to" Settings > Advanced (Section) > Network > Public IP"? Currently, we configured our instance on static IP. Should we set this to dynamic to get STUN enabled?

 

[Saqqara]

Sorry I'm quite confused. Is this the same when I go to" Settings > Advanced (Section) > Network > Public IP"? Currently, we configured our instance on static IP. Should we set this to dynamic to get STUN enabled?

No this is the setting for your wan IP address , if you do not have a fixed ip address\

There is no configuration required to get stun working , enabled by default - just make sure the firewall test passes

 

[Saqqara]

Look at the instructions for Remote phones: Provision via RPS server for the model of the fanvil phone

https://www.3cx.com/sip-phones/

 

[Evolute IT]

Sorry I'm quite confused. Is this the same when I go to" Settings > Advanced (Section) > Network > Public IP"? Currently, we configured our instance on static IP. Should we set this to dynamic to get STUN enabled?

If you are unsure on that level, I recommend you get a 3CX Partner (like us or others) to help you get setup and maybe teach you if you want to manage it yourself.

 

[JohnS_3CX]

A word of advice regarding any STUN phones whatsoever:

While it's not too hard to deploy one to any remote worker (even when pre-provisioning before you send it out to them) it does have its downsides:

• Consumer modems can often be found to block SIP due to ISP restrictions
• ALG (or helpers): enabled on modems by default and can mess up signalling
• Audio packets can get blocked: you end up with no audio, or one way audio
• Ports closing: while you can make outgoing calls, you might keep missing inbound calls
  
  
  
• Registrations failures and no audio are the most common issues we get in the forum

Most of these problems can be overcome, and you can get reliable STUN phones.
Unfortunately you will not be in a position to control for all those factors!



The best solution for remote workers has always been the 3CX apps (mobile or desktop).

 

[ltctech]

A word of advice regarding any STUN phones whatsoever:

While it's not too hard to deploy one to any remote worker (even when pre-provisioning before you send it out to them) it does have its downsides:

• Consumer modems can often be found to block SIP due to ISP restrictions
• ALG (or helpers): enabled on modems by default and can mess up signalling
• Audio packets can get blocked: you end up with no audio, or one way audio
• Ports closing: while you can make outgoing calls, you might keep missing inbound calls
  
  
  
• Registrations failures and no audio are the most common issues we get in the forum

Most of these problems can be overcome, and you can get reliable STUN phones,
Unfortunately you will not be in a position to control for all those factors!



The best solution for remote workers has always been the 3CX apps (mobile or desktop).

A lot of these issues are prevalent because 3CX insists on using unencrypted SIP signaling over UDP with remote STUN phones. Switching STUN remote phones to use encrypted SIP over TCP aka SIPS would improve reliability not to mention security when combined with SRTP.

It may not fix all the no audio or one way audio issues but it would at least prevent firewalls from tampering with SIP packets.