Phone Compatibility
Bring the phones you already use.
Thirdlane includes templates and separately managed firmware packages for supported desk-phone models. Manufacturer-assisted zero-touch provisioning is available for Yealink, Snom, and Fanvil; other supported vendors use generated configuration files and standard provisioning transports.
Zero-touch provisioning
Thirdlane directly integrates with the manufacturer redirect services below. You provide credentials for your vendor account; Thirdlane registers the provisioning server and device identifiers.
Yealink
RPS (Legacy) and YMCS
Snom
SRAPS
Fanvil
Remote Auto Provisioning
Phone provisioning coverage
Zero-touch provisioning is available for Yealink, Snom, and Fanvil. Other listed vendors use Thirdlane-generated configuration files and supported provisioning transports.
Zero-touch: RPS and YMCS
Yealink
Shipped templates and firmware packages for supported models, with vendor-account integration for redirect-server registration.
Zero-touch: SRAPS
Snom
Shipped templates and firmware packages for supported models, with SRAPS redirect-server integration.
Zero-touch: Remote Auto Provisioning
Fanvil
Shipped templates and firmware packages for supported models, with Fanvil redirect-server integration.
Template provisioning
HP Poly / Polycom
Provisioning templates for supported Poly and Polycom models, including model-specific line-key handling.
Template provisioning
Grandstream
Provisioning templates and separately managed firmware packages for supported Grandstream models.
Template provisioning
Cisco
Provisioning support for selected Cisco SIP and multi-platform phone families.
Manual or custom-template setup
Other SIP devices
Standards-compliant SIP phones and softphones can register manually, and administrators can adapt an existing template for additional models.
Provisioning capabilities
Phone Models management
Browse, filter, clone, and inline-edit phone templates. Full CRUD for custom models so you can support phones beyond the shipped library.
Per-model protocols
HTTP, HTTPS, FTP, FTPS, TFTP. Configurable globally and per model. Protocol-aware template variables so the same template adapts to whichever transport you use.
Custom template variables
Define global name/value pairs in Provisioning Settings; reference them from any phone template. Useful for environment-specific URLs, tenant identifiers, and feature flags.
ZTP redirection
Yealink RPS, Snom SRAPS, and Fanvil Remote Auto Provisioning so the phone finds Thirdlane on first boot — no per-device manual setup.
External Provisioning mode
Direct phones to download configs from a customer-managed DMS instead of Thirdlane’s built-in provisioning. Useful for service providers who centralize provisioning across multiple platforms.
S3 File Transport
Automatic upload of generated provisioning files to S3-compatible storage after each device is provisioned. Pairs with cloud DMS deployments.
Custom Script Transport
Run user-defined post-provisioning scripts with file paths and context variables — for hooks into your own audit, monitoring, or asset-management systems.
Hot Desking
Designated phones aren’t bound to a single user. Anyone with valid credentials can sign in and associate the phone with their extension for the session.
Practical patterns
- New deployment, new phones — buy phones with the vendor’s ZTP service. Pre-stage MAC addresses in Thirdlane, ship the phones direct to the user, plug in to provision.
- Migration from another platform — update the vendor redirect mapping for Yealink, Snom, or Fanvil devices so factory-reset phones locate Thirdlane without an on-site visit.
- Heterogeneous fleet — Yealink in HQ, Polycom in conference rooms, Grandstream in remote sites? One platform provisions all of them with consistent dial-plan and feature config.
- Service-provider model — multiple end-customer tenants, each with their own phone fleet. Per-model templates apply across tenants; per-tenant variables customize CLI, dial plan, and SIP servers.
- External DMS integration — if you operate a centralized DMS across multiple platforms, switch Thirdlane to External Provisioning mode and let your DMS serve the configs.
Phone not on the list?
Standards-compliant SIP phones and softphones register against Thirdlane regardless of whether we ship templates for them — you just lose ZTP on the unsupported model. The Phone Models management screen lets you clone an existing template and adapt it to a new device.
For volume deployments of a phone we don’t currently template, talk to us — adding template support for major models is straightforward.
Walk through provisioning.
We’ll show you ZTP for Yealink, Snom, and Fanvil; per-model templates; and the provisioning protocols that fit your network and security policies.