FusionPBX works fine for provisioning SIP phones. It was built to provision phones for the local system, as mentioned in a previous message. However, it was also built to be able to provision phones for other PBX servers as well. Flexibility was an important consideration as I wanted to make FusionPBX provisioning as useful as possible. I talked to someone in the last two weeks who used FusionPBX provisioning for another PBX. It was designed for this purpose from the beginning when I wrote it..
Here are some things to consider.
Maintain multiple vendors
If you need to support multiple phone vendors, then this would require learning to maintain them with different provisioning tools, one for each vendor. With FusionPBX, you learn how to maintain one, and you get the ability to support many different phone vendors using the same web interface.
Security vulnerabilities
The phone vendor provisioning has also had some major security vulnerabilities. The major phone vendors are a large and valuable target for hackers. Some of these vendor provisioning are for only sending the phone to a provisioning server. Others give the vendor phone control of the end point. This means a higher risk if they are compromised.
Support end-of-life phones
FusionPBX supports provisioning templates for phones long after the vendor considers them end-of-life
