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

Mass re-provisioning IP Phones

Status
Not open for further replies.

Reso

Premier Customer
Basic Certified
Joined
Nov 7, 2019
Messages
16
Reaction score
1
  • 3CX Version, Standard Annual 18. update 2
  • Server OS, Debian 10
  • Is the 3CX Server Hosted and where? hosted on premise
  • IP Phone Make/Model/Firmware Grandstream 2135, 1628 yealink T19P E2, all are on supported firmwares
  • Provisioning Method: Local LAN
  • Has the Firewall Checker passed: yes
  • Are custom Phone Templates being used: No custom templates
Hello,

I am in the process of changing server of 4 digit extensions. My current server has around 400 extensions created. I can transfer the current extensions by exporting to a csv file. Problems rises when i have to provision all the phones again. Would i have to login to each individual phone and provision again. Or is there another less tedious way to do this. Thank you for reading
 
DHCP option 66.

If you have configured the phones in 3cx and specified the Mac address of each phone. Then all you would need to do is configure the provisioning url on your firewall and each end point will auto provision.
 
  • Like
Reactions: Reso
DHCP option 66.

If you have configured the phones in 3cx and specified the Mac address of each phone. Then all you would need to do is configure the provisioning url on your firewall and each end point will auto provision.
Thank you, will check it out
 
DHCP 66 would probably be the way to go if it's something you can configure on the network easily but, if for any reason you can't, you could:

1. Take a full backup and move away from server as a precautionary measure.
2. Export all extensions.
3. Edit the csv file so that extensions get converted to 4 digit extensions. Also edit the "InterfaceIP" column that holds the current local ip to hold the new local ip (of the new server).
4. Shutdown the old server and deploy the new one.
5. Complete installation with 4 digit extensions and then import the extension csv file.
6. If you then just factory reset all phones (could probably ask each user to do this for their own phone if you're not onsite) you should see them all come up as new devices in the "Phones" section so that you can then assign them to their extension. If you attempt to assign a phone to the wrong extension you'll get a message telling you to which extension the phone belongs to so you can then select the correct extension.
7. It will automatically take you to the extension's "Phone provisioning" tab where you'll just hit OK and the phone will get provisioned.

Important: The above process applies provided that the IP Phones are all configured as local devices and you will keep it this way. In addition, bear in mind that the extension csv file you export will only hold the first IP phone assigned to each extension meaning that this will not work if you have more than one IP phones for any extensions. Also, for the IP phones to come up in the "Phones" section after you reset them they have to be on the same subnet as the PBX as this is done via multicast.
 
  • Like
Reactions: Reso
DHCP 66 would probably be the way to go if it's something you can configure on the network easily but, if for any reason you can't, you could:

1. Take a full backup and move away from server as a precautionary measure.
2. Export all extensions.
3. Edit the csv file so that extensions get converted to 4 digit extensions. Also edit the "InterfaceIP" column that holds the current local ip to hold the new local ip (of the new server).
4. Shutdown the old server and deploy the new one.
5. Complete installation with 4 digit extensions and then import the extension csv file.
6. If you then just factory reset all phones (could probably ask each user to do this for their own phone if you're not onsite) you should see them all come up as new devices in the "Phones" section so that you can then assign them to their extension. If you attempt to assign a phone to the wrong extension you'll get a message telling you to which extension the phone belongs to so you can then select the correct extension.
7. It will automatically take you to the extension's "Phone provisioning" tab where you'll just hit OK and the phone will get provisioned.

Important: The above process applies provided that the IP Phones are all configured as local devices and you will keep it this way. In addition, bear in mind that the extension csv file you export will only hold the first IP phone assigned to each extension meaning that this will not work if you have more than one IP phones for any extensions. Also, for the IP phones to come up in the "Phones" section after you reset them they have to be on the same subnet as the PBX as this is done via multicast.
Thank you. Thiis is more or less what i plan to do. but most extensions are on different subnets as they are different locations. But i plan to set DCHP 66 on all the routers for different branch offices.
 
@Reso

Thank you. please explain what is PnP. Im not familiar with it
PnP is what we call Plug and Play and is the easiest method to provision an IP Phone with 3CX out of the box. It only works with the Local or SBC provisioning method. It goes something like this:

1. Start up an provisioned IP Phone on the same Lan of the PBX.
2. In the "Management Console >> Phones section" an entry will appear for that phone (gets detected).
3. You simply select that IP Phone entry and then assign it to an extension.
4. It then automatically gets provisioned with that extension.

You can check out our training material regarding this functionality for more information here(slide 5) : https://www.3cx.com/3cxacademy/videos/basic/configuring-ip-phones/

but most extensions are on different subnets as they are different locations.
By different locations do you mean they are remote? If yes, bear in mind that the procedure I provided is only for Local IP Phones, do you have a mix of Local, SBC and STUN devices? Can you provide more information on this as to avoid misunderstandings and any issues that may arise with this task?
 
By different locations do you mean they are remote? If yes, bear in mind that the procedure I provided is only for Local IP Phones, do you have a mix of Local, SBC and STUN devices? Can you provide more information on this as to avoid misunderstandings and any issues that may arise with this task?
Yes different locations mean remote locations. However, they are connected through leased lines and we can connect to them via intranet. They all have different subnets.

I think the most difficult task would be to factory reset all the phones. Is there a way to mass reset the phones
 
Last edited:
I think the most difficult task would be to factory reset all the phones. Is there a way to mass reset the phones
I've afraid you cannot mass reset IP phones via 3CX so only thing I can recommend is maybe going through the vendor's documentation to see if there's an alternative way of doing this.
 
Status
Not open for further replies.

Forum statistics

Threads
112,149
Messages
590,965
Members
165,170
Latest member
SupportRock