@JaredBusch said in Yealink W52P config files:
@fuznutz04 said in Yealink W52P config files:
This was the most secure way that we could think of to securely provision remote phones. (aside from VPN that is.) I'd be interested to hear how you or others securely provision remote extensions. Is there a better way?
The answer there varies.
For most companies, I would used raw HTTP(S) with IP based whitelist as a first choice. Why? Because they have fixed IP blocks.
If you are dealing with roving users, then yeah, it is harder to decide what to do.
Yep, we use HTTPS with username/password, but not a whitelist currently. Once the phones are provisioned, the chances of them needing re-provisioned is fairly low, unless their is a configuration change that we want to push out. As of now, everyone would automatically get the new info. If I implement a whitelist, then it would become more difficult to push an update to roaming users, but certainly not a deal breaker, seeing as we could just update the whitelist as needed.
How often do you have your phones checking the provisioning server for changes?