Skip to content
Thirdlane

Extended Templates

An Extended Phone Template is a reusable, named phone configuration - built on a specific phone model - that pre-defines the programmable button layout (and optional raw config overrides) once, so you can apply it to many phones. Instead of assigning a bare Phone Model to each user and then programming buttons device by device, you assign the Extended Phone Template by name and every phone provisioned from it gets the same buttons. This is ideal when a whole team uses identical BLF/speed-dial layouts, or when you want a “standard sales phone” or “reception phone” definition you can reuse and update in one place.

To use an Extended Phone Template for auto-provisioning, specify its name instead of a Phone Model in User Extensions (either in default settings or individually) or in Device Provisioning.

Create/Edit Extended Phone Template

The form is organized into tabs:

Configuration

  • Name. A unique name for the template - this is what you select in place of a Phone Model.
  • Description. A short description of what this template is for.
  • Model. The phone model this template is built for. Button types and template files available depend on the selected model.
  • Time Zone. The time zone applied to phones provisioned from this template (translated per the model’s Translation Map).

Buttons

Define the programmable keys, in order. Each button row has:

  • Key. The button/key number on the phone.
  • Type. What the key does - options include Not assigned, Speed Dial, BLF (Busy Lamp Field), Line Key, Call Park, Prefix, Conference, Forward, Transfer, Hold, DND, Record, Multicast Paging, Group Pickup, Paging List, and Voicemail.
  • Value. The target for the key (for example the extension a BLF monitors or a speed-dial number), where the type needs one.
  • Label. The text shown next to the key on the phone display.
  • Account. The SIP account/line number the key is associated with.

Override

A free-form area for raw configuration lines to append for phones provisioned from this template, for settings that do not have a dedicated field.

Best practices

  • Build one template per role or team (“reception”, “sales”) rather than per person, so a layout change updates everyone who uses it.
  • Choose the Model that matches the actual hardware - available button types and the number of keys depend on it.
  • Keep the Override area for genuine exceptions; prefer the structured button rows so the layout stays readable and portable.