Hello All,
We are mostly a Snom shop here, so the change a year or so ago to the .rpm based provisioning mostly went unnoticed by us. We're now looking into moving to Polycom's, in some part to ring the benefits of the new provisioning. I've got two VVX411's sitting on my desk that I need to get up and going for testing and am having trouble finding where exactly we should make changes.
Eric's post (here: https://www.thirdlane.com/forum/upcoming-phone-provisioning-features-rp…) does point out that we can still make customization's in the old user_provisioning, but what I'm not certain of is if we should instead be using the translation maps for these types of adjustments. The helper text for Template Variables mentions "in your template you can define a custom variable" but i'm not clear whether these variables should be defined directly in the appropriate file in /etc/asterisk/provisioning, or back in the old user_provisioning folder, at which point I'm not certain I see the benefit of the new method.
As a simple example, one of the things we'll need to setup across models and PBX's is our Sip proxy, which in the old method would have meant addin it to the polycom_line.cfg in user_provisioning. Is this still the best method for accomplishing this or is there a better way?
I apologize for the somewhat vague questions, but appreciate any guidance on better understanding these new feautres. For the record, we're running 8.0.3.10 across all deployments, and have already done the install of the template bundles.
that is not how the
that is not how the provisioning system works... it will not show you two copies. It works in heiristical order... in MTE it searches /etc/asterisk/user_provisioning/tenant/{file} for a specific file. THEN if it doesnt exist it tries /etc/asterisk/user_provisioning/{file} and finally /etc/asterisk/provisioning/{file} ... the entries in models.txt works _exactly_ the same way in terms of searches. As long as the device name (example [polycom-vvx500] ) is the same, there will not show a duplicate entry.
yes, in your example copying polycom_line.cfg to /etc/asterisk/user_provisioning/ or /etc/asterisk/user_provisioning/tenant/ where tenant is the name of the tenant as it appears in thirdlane (case sensitive) and make your customized changes.
If you wanted to have a variable replacement, then user_provisioning and its subset is the correct place for the modification.
Jake,
Welcome to the catch 22 that is the new provisioning system.
The new provisioning system concept of RPM based templates works great IF and it is a BIG IF, you have no need to customize the templates. However, if customization is needed, the new provisioning system is a bit of a step backwards as you have you to do everything from the console and manually create all of the template files that Thirdlane reads to allow it to be chosen as a "phone model". Alternatively, you COULD modify the polycom template files "in place", but then you need to extra careful that you update the RPM templates, because if you do, your customizations will be overwritten by the RPM update.
My suggestion would be to install the polycom RPM templates, copy the polycom_*.cfg files into user_provisioning and modify the templates there. Create a "models.txt" file in user_provisioning with the contents of the models.d/polycom.txt file (fromt he RPM templates). Then, uninstall the RPM templates so Thirdlane does not see 2 of every polycom model.