• We do not provide troubleshooting help for unsupported phones. Please try with a supported phone.
  • V20 Update 10 Alpha 2 Learn more

Solved Fully automated provisioning of IP Phones - Zero Touch

Status
Not open for further replies.

Harjeet

Bronze Partner
Basic Certified
Joined
Jun 22, 2021
Messages
85
Reaction score
20
Hi Guys
we are looking to do our very first 3CX install for a small hotel.
there will be 6 phones (we can get yealink T41).

what we want is full automated management of phones. like we want to assign each phone and extension and provision it , which i can do easily as remote/stun and provision a phone. but if someone factory resets a phone , it should then automatically re-provision and assign same extension without anyone doing anything.

so far with my testing if I remote/stun provision a yealink/fanvill phone and factory reset then phone it comes online but on phone it asks for EXTno and Password (vmPIN) .which is something we don't want it to do. it should just automatically be assigned to an extension that it was previously assigned.

is this possible?

Regards
Harry
 
I would suggest you look at putting an SBC on site and setting up DHCP option 66 to auto provision your phones. STUN will require authentication. If you continue down the STUN path you'll need to start messing with port forwarding.

https://www.3cx.com/sip-phones/dhcp-option-66/
 
  • Like
Reactions: Evolute IT
Hi Harry,

For local phones, DHCP Option 66 is the best solution, if the goal to become auto-provisioned upon reset.

For remote phones, you can do the exact same thing, but use an SBC instead as this will make your deployment much easier and will not be reliant upon static IPs and port forwarding.
 
  • Like
Reactions: Evolute IT
Hi Guys ,
I just setup test bed with two fanvil x4 phones, i got SBC setup on raspberry pi4 and I can see phones in pbx phone list. so i assigned phones to extensions., they works fine.
then if I do a factory reset of a phone , it won't auto provision/assign to same extension instead its coming up as NEW on pbx phone list.

i have tried with dhcp option 66 by putting SBC IP for it.

not sure what i am missing here.
 
PBX is running on our AWS EC2 instance.
 
Last edited:
with SBC on the same subnet is it not supposed to auto-provision using PNP without using DHCP option 66 ?
yes it works now with http link in option 66.

so just to confirm with pbx in cloud, for remote phones in office I will always need a SBC and option66 with http link in order to achieve fully automatic provisioning. in that case I believe all phones needs to be same make/model for http link to be same ?
 
The provisioning url is unique to the 3CX system and not each model of phone.so it can be used across the range of phones that use dhcp option 66.
 
that's great. thanks guys its working as expected
 
Status
Not open for further replies.

Forum statistics

Threads
112,147
Messages
590,960
Members
165,167
Latest member
Finatra.us