Skip to content
Thirdlane

Template Bundles

Template Bundles are the packages that supply Configuration Manager with everything it needs to provision a given family of phones: the provisioning templates (the model definitions and config-file templates a phone is built from) and, historically, the matching vendor firmware. When a bundle is installed, its phone models appear in Phone Models with the System scope (read-only), and their templates become available to the Bulk Generator and the Managed Device form.

Templates and firmware are now separate

In current releases the old all-in-one Template Bundles flow has been split into two independent concerns. Bundling per-vendor templates together with multi-gigabyte firmware images (Yealink alone is now over 2 GB) meant every install pushed several GB of files to disk, even on systems that only needed a couple of phones.

  • Phone templates ship preinstalled with the platform. They are delivered by the thirdlane-phone-templates-mte (multi-tenant) or thirdlane-phone-templates-ste (single-tenant) RPM, cover all supported phones at once, and are installed automatically. There is nothing for an administrator to install or choose - the templates are simply present.
  • Firmware is optional and admin-managed. Each vendor (or model family, when a vendor is too large to ship as a single RPM) is its own firmware bundle, managed on the Phone Firmware screen. Install only the bundles you actually need.

Because templates install automatically, the separate Template Bundles and Provisioning Settings steps that used to appear in the Initial Setup Wizard have been removed. Provisioning defaults are seeded at install time and can be adjusted later in Provisioning Settings.

Where the files live

Installed template files are placed under /etc/asterisk/provisioning/. Each supported phone gets a model description in models.d/, which is what marks those models as System (shipped) and read-only in Phone Models. To create an editable copy, duplicate or clone a system model into a global or tenant override.

Do not edit files under /etc/asterisk/provisioning/ directly - they are overwritten on every template-package upgrade. To customize templates, use /etc/asterisk/user_provisioning/ (system-wide) or /etc/asterisk/user_provisioning/<tenant>/ (per-tenant). The platform reads models.txt and template files from user_provisioning/<tenant>/, then user_provisioning/, then provisioning/.

Typical setup flow

  1. Confirm the phone templates are present (they install with the platform - no action needed for supported models).
  2. On Phone Firmware, install the firmware bundles for the vendors you use.
  3. Set system-wide and tenant provisioning defaults in Provisioning Settings.
  4. Use the Bulk Generator to create User Extensions, Inbound Routes, and provision phones from the default templates.

To request support for an unsupported phone, contact support@thirdlane.com.